- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 May 2017 15:40:39 +0000
- To: public-poe-archives@w3.org
This sounds rather stupid a decision, sorry to say it. Why re-defining a whole hierarchy apparatus? If you want to represent 'hierarchies' it means that you have a rather 'conceptual' approach of actions anyway. But maybe I need to see your requirements. It's not clear from the minutes, why these would be different from what SKOS means to tackle. Btw odrl:alsoRequires may have some good motivation, but the name surprises me. Why 'also'? Is there some kind of 'primaryRequires' relationship anywhere? On 19/05/17 16:56, Renato Iannella wrote: > F2F: Update model to support hierarchies (relationship) expressible between Actions > > RESOLUTION: That we introduce the terms odrl:narrowerThan and odrl:alsoRequires to the Information Model. These are applicable to Assets, Parties and Actions > > requires = other actions that it requires (eg share must include distribute) > > both are transitive > > REMOVE all SKOS !!!! > > http://www.w3.org/2017/05/19-poe-minutes.html > > @simonstey <https://github.com/simonstey> @sabrina <https://github.com/sabrina> to propose definitions and examples > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <https://github.com/w3c/poe/issues/160#issuecomment-302725687>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnprVjtFLY920rRLUnxwC2Fje-4MiO5ks5r7a24gaJpZM4NNr8L>. > -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/poe/issues/160#issuecomment-302737541 using your GitHub account
Received on Friday, 19 May 2017 15:40:45 UTC