@acka47 the core of the complaint is that people want to handle one key and one key only. they don't want to map terms to IRIs, or IRIs to terms. they'd prefer picking exactly one symbol and use that as the property key.
Top-level
@acka47 the core of the complaint is that people want to handle one key and one key only. they don't want to map terms to IRIs, or IRIs to terms. they'd prefer picking exactly one symbol and use that as the property key. 1 comment
|
@trwnh And I always thought that this is some of the LD patterns that easily make sense: to globally identify each term used in your data by an IRI *and* to use the same IRI as a link to the term's documentation. Apparently, I was wrong.
OTOH, I get it when people don't think they need (to understand) JSON-LD but I also think it is not too much to ask to follow community patterns by slapping a context link into your JSON.