- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Jun 2017 09:39:59 +0000
- To: public-poe-archives@w3.org
6. I'm afraid I won't have time to check everything in that (impressive!) commit right now, but I've looked at the first changes and they do fix the problem I had with the definition! 12. I won't argue that the ODRL constraints always amount to selecting a part of a resource. But some are clearly (e.g. the part of 18+ friends in user44's friend group, or the position within an asset). And my hope was that looking at existing patterns for these requirements would fix some problems (i.e. the hijacking of URIs). On 06/06/17 06:04, Renato Iannella wrote: > Updated all Actions and removed assigner/assignee and perm/prohibt from the definitions > > Confirmed by WG thread: https://lists.w3.org/Archives/Public/public-poe-wg/2017May/0039.html > > commit dfa9279 <https://github.com/w3c/poe/commit/dfa9279bdfde28ae0dd1e01a3c565c4a561f8a79> > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <https://github.com/w3c/poe/issues/185#issuecomment-306375946>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnprRRmKaJsO6vjnicUVuobGAUBxEDWks5sBM_jgaJpZM4NgAZZ>. > -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/poe/issues/185#issuecomment-306434691 using your GitHub account
Received on Tuesday, 6 June 2017 09:40:05 UTC