- From: Renato Iannella via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Jul 2017 03:52:01 +0000
- To: public-poe-archives@w3.org
My concern is that we increase the barrier for implementors (producers and consumers) as there will now be additional processing. It makes sense for those that want "reliability" to do that, but I don't think this will be consistent across **all** ODRL implementations. I can image large communities/companies **only** supporting profiles, but that does not mean all ODRL implementors must do that. A good read is the Web architecture Extensibility: https://www.w3.org/TR/2004/REC-webarch-20041215/#extensibility Especially the part under "Two strategies have emerged..." My proposal is that: 1) if there is a Profile declared, then you MUST understand all vocab terms 2) if no profile, then you interpret the vocab terms "as is" So, a Profile becomes ODRL's "must understand" strategy -- GitHub Notification of comment by riannella Please view or discuss this issue at https://github.com/w3c/poe/issues/210#issuecomment-317621316 using your GitHub account
Received on Tuesday, 25 July 2017 03:52:02 UTC