|· · ·|
|Open||cscott||T44063 [Epic] Provide a plain linked data interface for accessing entities|
|Resolved||hoo||T101837 [Story] switch default rdf format to full (include statements)|
|Open||None||T50143 Implement complete RDF mapping for entities (tracking)|
|· · ·|
Hi Lydia (and all), it's Chiara from the BBC here. I post here to allow everyone working on this issue to comment back to me. To make it brief, any idea of when this task is going to be implemented? Thanks!
One the mailing list, Stas brought up the question "which RDF" should be delivered by the linked data URIs by default. Our dumps contain data in multiple encodings (simple and complex), and the PHP code can create several variants of RDF based on parameters now.
I think the default should be to simply return all data that is in the dumps. This would address the BBC's use case of building a linked data crawler that fetches live data rather than using dumps. Such a crawler would not have any way to specify which part of RDF is needed, since linked data is such an extremely simple, parameter-free API.
Dump format however does not contain the data on the referenced entities (due to the fact that dump has all entities anyway, so no reason to repeat), while full one does. Not sure if that fits the use case mentioned or not.
Data on the referenced entities does not have to be included as long as one can get this data by resolving these entities' URIs. However, some basic data (ontology header, license information) should be in each single entity export.
Including more data (within reason) will not be a problem (other than a performance/bandwidth problem for your servers).
However, if there are further ideas and small improvements that will take time to implement, it would be good to switch to "dump" as the default right now. It is already a big improvement over the current (statement-free) default. Further improvements can then be done in small steps.