RE: Updated ODRL in JSON DRAFT

> So we would not then really use the current URI (http://www.w3.org/ns/odrl/2/)
> instead we would go to final versions using http://www.w3.org/ns/odrl/21/
>
> Cheers...
> Renato Iannella

I would still use /ns/odrl/2/, because that's a URI which is only used by anything 'new' (i.e., the RDF, the harmonised XML namespace, etc.)

I would further suggest that any post-harmonisation changes which actively break (rather than simply marking as deprecated) anything are given a new major version number and new URI -- although I would tend to avoid doing that in practice anyway. Changes which introduce new terms or are otherwise backwards-compatible should have a new minor version number, to allow conformance reporting (e.g., "this application understands ODRL 2.4 or earlier fragments"), but maintain /ns/odrl/2/.

M.

--
Mo McRoberts - Chief Technical Architect - Archives & Digital Public Space,
Zone 2.12, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA,
MC3 D6, BBC Media Centre, 201 Wood Lane, London W12 7TQ,
0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E

Received on Tuesday, 3 June 2014 07:16:05 UTC