Re: [poe] What's the immutable core of ODRL that cannot be changed by Profiles?

I would also argue against a media type. Since ODRL can be serialised in multiple ways, and have multiple profiles, it seems to me that Occam's razor is to mint  URI for the core profile which tells you that the JSON-LD, or Turtle, or XML, or Foo, conforms (only) to the core profile. Any other profile can assume that the processor understands core, of course. But, again, I really think this WG would do well to defer as much of the discussion as possible to the DXWG or we may end up with Recs later this year that are at odds with early drafts of highly relevant work that may render it obsolete. We can say now that profiles need a URI. Those profiles may be available in multiple serialisations for human and machine readability and will therefore have their own mime types. I am not arguing for creating a dependency on the DXWG, rather, I think we can just talk in terms of profiles without going into detail about how they should be serialised. My inclination is to define a URI for the default/core profile as a means of indicating that a client or Policy *only* uses the core - however unlikely that is. This would then support the kind of negotiation by profile that Lars is working on.

-- 
GitHub Notification of comment by philarcher1
Please view or discuss this issue at https://github.com/w3c/poe/issues/173#issuecomment-310346821 using your GitHub account

Received on Thursday, 22 June 2017 10:56:35 UTC