- From: Dave Longley <dlongley@digitalbazaar.com>
- Date: Wed, 31 Aug 2011 00:33:27 -0400
- To: public-linked-json@w3.org
On 08/30/2011 07:17 PM, Markus Lanthaler wrote: >>> Section 4.6 I am fairly opposed the idea of overriding keywords. That >> is really a rope to hang ourselves in terms of readability of a >> dataset. Also, what are the consequences if the context file is read >> from the web as an external file? Doesn't it radically change the >> interpretation of a specific JSON-LD file with or without an access to >> that context? >> >> This is actually a bit wrong, we're not actually overriding the meaning >> of @subject or @type, but allowing aliases for those keys that affect >> the processing algorithm. I think that it should be an error to >> override @subject, @type, @iri, etc. > Is this really aliasing? Then the spec is completely misleading about this > as it always talks about *overriding keywords*. Yes, it is aliasing. I updated the spec language to reflect this since it was a bit confusing. -- Dave Longley CTO Digital Bazaar, Inc.
Received on Wednesday, 31 August 2011 04:33:51 UTC