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

For the IIIF context documents we decided to include only the major version
in the URI, as we follow the semantic versioning notion that anything
backwards incompatible requires a new major version.  Then we add to the
context as needed for any minor or patch versions.

See:
    http://iiif.io/api/annex/notes/semver.html
And:
    http://iiif.io/api/image/2/context.json


And for Open Annotation, we have the full version:
    http://www.w3.org/ns/oa-context-20130208.json
that redirects to:
    http://www.w3.org/ns/oa.jsonld


Rob



On Sun, Jun 8, 2014 at 3:15 AM, ☮ elf Pavlik ☮ <
perpetual-tripper@wwelves.org> wrote:

> Howdy,
>
> 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.
>
> I see it somehow relevant to this issue: "JSON-LD Context security
> considerations" https://github.com/web-payments/web-payments.org/issues/21
>
> 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?
>
> o/
>
>


-- 
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305