- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Jun 2017 07:22:26 +0000
- To: public-poe-archives@w3.org
This is a very good move forward! Still I would insist that there should be nothing in the spec that encourages people to hijack URIs, which is a bad practice. It's not only about letting users the opportunity to do things in an ok way, it's about discouraging them to do bad things. But I guess we were almost already there when in your previous comment you suggested that in example 19, the assignee is "http://example.com/user44/friends/age/gt/17". This was good, sorry I didn't react on this. I was in a hurry as the first part of your comment was hinting that I was advocating throwing the baby (constraint mechanism) with the bathwater (hijacking URIs), which was not the case :-) On 19/06/17 05:52, Renato Iannella wrote: > The uid has moved to a "Should" now. > > So, this is possible: > > |odrl:assigner [ a odrl:Party ; foaf:name "Bob" ; ] | > > See #174 <https://github.com/w3c/poe/issues/174> > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <https://github.com/w3c/poe/issues/164#issuecomment-309332471>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnprYvTuO4Go_-94A0_V5TWK5a5WhCQks5sFfCCgaJpZM4NNsHV>. > -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/poe/issues/164#issuecomment-309359290 using your GitHub account
Received on Monday, 19 June 2017 07:22:32 UTC