Re: Broken links in the spec

Thanks Gregg!

> I ran the spec through the W3C Link Checker [1], and it passes 
> cleanly. Indeed, this is a requirement before a spec can be published. 
> In particular, dereferencing the #dfn-type-mapping fragment takes me 
> to the part of the document with the following text:

The link was close enough to where I clicked it that my browser didn't 
react, and I missed the fancy semantic <dfn id="…"> tag when I looked 
through the source for the target of the link. My bad.

I'm not sure why I allowed the boolean reverse property to confuse me. I 
guess since it was something derived from the presence of the @reverse 
keyword rather than directly found in the local context I thought maybe 
it was going somewhere else.

> A Term Definition is a structure used to hold information about a term 
> found within a @context. They typically contain IRI, Type and 
> Language, and Container mapping information, and indicate if this is a 
> reverse term. Term Definitions are an abstract concept not included 
> directly within a context, but derived from it as part of processing. 
> This information becomes important during both compaction and 
> expansion.

At its core my key confusion was about the abstract/concrete nature of 
the active context. Since I'm working through the implementation bottoms 
up (IRI expansion, Value Expansion, Context Processing, Term Definition 
before Expansion for example) I'd made the erroneous assumption that the 
active context would be a literal part of the expanded output and so I 
didn't see the role of reverse true/false.

After carefully re-reading the linked active context/term definitions 
explanation again, I'm back on track.

Cheers,
Sean

>
> [[[
> The active context contains the active term definitions which specify 
> how properties and values have to be interpreted as well as the 
> current base IRI, the vocabulary mapping and the default language. 
> Each term definition consists of an IRI mapping, a boolean flag 
> reverse property, an optional type mapping or language mapping, and an 
> optional  container mapping. A term definition can not only be used to 
> map a term to an IRI, but also to map a term to a keyword, in which 
> case it is referred to as a keyword alias.
> ]]]

Received on Monday, 8 December 2014 09:57:37 UTC