RE: [json-ld.org] Charles Greer's JSON-LD syntax spec review (#230)

On Thursday, March 14, 2013 4:36 PM, Dave Longley wrote:

> > > 6.4 "last-defined-wins mechanism." This looks more like a "most
> > > recently defined" mechanism, because of nested scopes. I could be
> > > misinterpreting "last-defined-wins" though.
> >
> > I, as a non-native speaker, can't really see a difference. It's
> > not the temporally last (which most recently would suggest to me)
> > but the "closest"one if you look from the current element towards
> > the tree's root.
> 
> I suspect that he means that "last-defined" might indicate "last in
> the document" whereas "most-recently" seems to be a better match to
> "the 'closest' one if you look from the current element towards the
> tree's root". I don't think he means temporally (though, really, in
> this case it's the same), rather, each time you define a term, that
> definition becomes the "most recent". It also becomes the "last"
> defined, but what "last" is relative to is perhaps unclear since that
> word carries a natural meaning both in a nested scope and at the scope
> of the whole document. A native speaker might be less inclined to
> mistaken "most recent" for "last in the document" than "last defined"
> because the word "recent" itself is scope-limiting. Hopefully that
> explanation makes sense; as a native-speaker myself, I didn't confuse
> "last-defined" with something other than its intended meaning, but
> that may just be because I already understood how term definitions
> work. In attempting to take a step back, I can see his point and think
> we ought to change it to "most-recently-defined". I don't think that
> change would cause more confusion than it might remedy.

OK, thanks a lot for the explanation. I've updated the spec accordingly:

https://github.com/json-ld/json-ld.org/commit/3cf0b117a00bead12600f327ceef289d7f0e4395



--
Markus Lanthaler
@markuslanthaler

Received on Thursday, 14 March 2013 16:38:32 UTC