W3C home > Mailing lists > Public > public-annotation@w3.org > August 2015

RE: @context file

From: Timothy Cole <t-cole3@illinois.edu>
Date: Sat, 15 Aug 2015 17:18:49 -0500
To: "'Ivan Herman'" <ivan@w3.org>, "'W3C Public Annotation List'" <public-annotation@w3.org>
Message-ID: <025101d0d7a8$5d0ec130$172c4390$@illinois.edu>
Ivan-

As discussed the changes to @context mean that agents creating JSON-LD can use type instead of @type and id instead of @id -- which is good, but what about when annotations stored as RDF are to be disseminated in JSON-LD?  

I'm not clear from what I can discover from the JSON-LD Processing Algorithms and API document and from the test reports done for JSON-LD exactly how @context mappings are used when serializing RDF as JSON-LD (it does look that there is provision for applying @context, just not sure I understand all the rules, and when there is a choice -- as there would be for @type/type and @id/id, I would assume that the transforming agent has some discretion). 

Is this another question for Greg, or do you or James know, or does someone else?  

Or maybe we have to provide libraries for this?

Or maybe this is not an issue?

I ask not only as regards type and id, but because there is additional aliasing in @context we could consider to make the JSON-LD serialization seem more natural. 

By the way, I appreciate you fixing up the Wiki page examples. Thank you.

-Tim Cole



-----Original Message-----
From: Ivan Herman [mailto:ivan@w3.org] 
Sent: Wednesday, August 12, 2015 11:17 AM
To: W3C Public Annotation List <public-annotation@w3.org>
Subject: @context file

I have made the changes we agreed upon on the @context file, both on the github repo and on /ns.

Ivan


----
Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Saturday, 15 August 2015 22:19:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:39 UTC