- From: Sean Johnson <belucid@acm.org>
- Date: Sun, 07 Dec 2014 10:07:45 -0500
- To: public-linked-json@w3.org
Hello again, The JSON-LD 1.0 Processing Algorithms and API recommendation has numerous broken links to: http://www.w3.org/TR/json-ld-api/#dfn-type-mapping #dfn-type-mapping isn't an anchor target defined anywhere. I'm implementing 6.2) Create Term Definition ( http://www.w3.org/TR/json-ld-api/#create-term-definition ), but I'm a bit confused on 10.3, 11.6 (and so on) where the result of passing all the error checking is to set something on the "term definition". Maybe I'm confused on what's a term definition? I thought the term definition I'm creating was just an entry in the context, and I was just adding JSON keys/values to the context that I'm merging the local context into (in the overall picture of context processing). So my understanding was I'll be adding things like "@type" in 10.3 and "@reverse" is 11.6. But it seems the term definition is something else being referred to in 10.3) 11.6) etc., it's a stateful object in the Ruby implementation with a boolean flag for the term being reversed for example. I understand "@reverse" getting a blank node identifier or an absolute IRI, but "reverse flag" getting true… say what? The algorithm seems to be referring to something that's not been defined anywhere before. What's getting the true value for a reverse flag? This portion of the spec, create term definition is a bit less clear, and the broken links don't help. Any suggestions? Cheers, Sean
Received on Sunday, 7 December 2014 15:08:18 UTC