WA and JSON-LD default context

Hi all,

We have a question about JSON-LD that might be of interest to this group.

As part of our efforts to move forward towards more advanced modelling scenarios, we have been debating the need for a JSON-LD context for ourselves (extending the WA) to reduce the number of prefix declarations and eventually further simplify the labels by even removing the prefix as it is currently being done in WA spec.

While looking at the best practices we stumbled across the “RDFa Core Initial Context” [1] which also defines a default context for JSON-LD with a list of default prefixes. We were wondering if you might know how normative this specification is since it is not mentioned in the JSON-LD specification and if there is significant adoption (I guess that this is only critical for RDF engines). My understanding is that there should be still a way to explicitly state the default context (at least for back compatibility), either at the protocol level or context level.

Btw, with regards to WA specs (and also Open Annotation), and if this really happens to be normative, it might be relevant to make some note about it in both the model and protocol specs... or even explicitly import the default in the current WA context.

Looking forward to your feedback...

[1] https://www.w3.org/2011/rdfa-context/rdfa-1.1

Best regards,
Hugo Manguinhas
Technical R&D Coordinator

T: +31 (0)70 314 0998
M:
E: hugo.manguinhas@europeana.eu
Skype: hugo.manguinhas


Be part of Europe's online cultural movement - join the Europeana Network Association: http://bit.ly/NetworkAssociation

 #AllezCulture!
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. If you are not the named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.

Received on Friday, 6 May 2016 10:23:34 UTC