W3C home > Mailing lists > Public > public-linked-json@w3.org > June 2014

Re: [Best Practices] Context document - modifying and versioning

From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
Date: Mon, 09 Jun 2014 21:20:17 +0200
Message-ID: <539608F1.3090002@wwelves.org>
To: Markus Lanthaler <markus.lanthaler@gmx.net>, 'Linked JSON' <public-linked-json@w3.org>
On 06/09/2014 09:11 PM, Markus Lanthaler wrote:
> Hi Pavlik,
> 
> On Sunday, June 08, 2014 12:16 PM, ☮ elf Pavlik ☮ wrote:
>> I see a pattern with versioned contexts like many Web Payments specs:
>> https://web-payments.org/specs/source/identity-credentials/#a-typical-identity
>>
>> And also context without version, like Hydra Core
>> http://hydra-cg.com/spec/latest/core/#documenting-a-web-api
>>
>> AFAIK one for schema.org will also have no version information.
> 
> Yep. It's a design decision and also a matter of taste. I personally don't like putting version information in URLs for things like these. This is very similar to namespace URLs. FOAF, still one of the most popular vocabularies, is stuck with a 0.1 version in its URL for more than a decade now:
> 
>    http://xmlns.com/foaf/0.1/
> 
> Some people thus use dates instead of version numbers. I don't find that much better:
> 
>    http://www.w3.org/2000/01/rdf-schema#
>    http://www.w3.org/1999/02/22-rdf-syntax-ns#
> 
> As long as you don't introduce breaking changes, there's no need to version. If you do, you end up with a different thing. You can just as well give it a different name then.
> 
> 
>> I see it somehow relevant to this issue: "JSON-LD Context security
>> considerations" https://github.com/web-payments/web-payments.org/issues/21
> 
> Maybe, maybe not. The simplest thing to do if it is security-sensitive is to just embed it (or expand the document before storing it permanently).
> 
> 
>> Since changing content of the context document can completely change
>> meaning of data, maybe creating some kind of JSON-LD Context Best
>> Practices document could help many people with playing safe when
>> altering contexts used in data already out(in) there?
> 
> Changing vocabularies is even worse. So, there's really just one advice: as soon as it is out, you can't change it anymore. The good thing is that there are infinitely many URLs. Just mint a new one.
> 
> The problem with Best Practice documents etc. IMO is that people rarely read them... and typically no one wants to write them (exactly for that reason). If someone volunteers, I'm sure no one would object to hosting it directly on json-ld.org.
Thank your for sharing your perspective Markus! I'll wait for few more
comments and then will try to write some kind of summary.
Received on Monday, 9 June 2014 19:22:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:41 UTC