Thank you kindly Dave. What I ended up doing - based on your feedback - was to make the following changes: The input document was modified to: "x:purpose": { "@type": "@id" }, "https://example.org/pub/x#purpose": { "@type": "@id" } Which catches both ways purpose can be made. And in the new context I make sure it comes out correctly with "x:purpose": { "@type": "@id" } Just in terms of JSON-LD going forward, may I suggest that's there's "Principle of Least Surprise" violation going on here and that compact IRIs in the @context should be expanded in this case (and maybe others). D. On Fri, Jan 17, 2014 at 10:55 AM, Dave Longley <dlongley@digitalbazaar.com>wrote: > I posted an answer for you at Stack Overflow. > > On 01/17/2014 10:19 AM, David Janes wrote: > > I've posted a question to Stack Overflow about JSON-LD Compaction, if > > anyone would like to take a stab at answering it (here or there). > > > > > http://stackoverflow.com/questions/21185001/json-ld-compaction-and-compact-iris-as-values > > > > Thanks, > > D. > > > -- > Dave Longley > CTO > Digital Bazaar, Inc. >Received on Saturday, 18 January 2014 16:55:43 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:40 UTC