Re: [poe] Mechanism for specifying constraints

An update of the definition of each constraint left operand in the Vocab would help. But I'm not sure it would solve everything. Indeed as you say I could find some info in the IM about these operands. But it really didn't feel natural at all. Like, the first time I see an operand I would think "oh but what does this thing stands for exactly?" and then when finding an example later I would think "oh, ok actually when they say X they mean the beginning of X" and then when encountering another operand Y I would realize that the 'semantic precision' is defined in a quite different way. So I think something should be done in the IM too.
I'm sorry I can't be more precise in my feedback. The matter is awfully complex, and the POE WG deserves praise for trying to tackle it. But that's also why I'm suggesting to move the whole constraint thing to another companion spec. That would also give the opportunity to replace the entire companion spec by something more appropriate if one is found later, without having to jeopardize the core POE standard.

About SHACL I was thinking of linking to the SHACL expression of the constraint from e.g. a Permission, like this

"permission": [{
         "target": "http://example.com/game:9090",
         "action": "odrl:play",
         "shaclConstraint": ":shaclExpression"
}]

Where :shaclExpression of the constraint could be either a document URI, or a literal that is formed by the constraint. Whatever the SHACL expression is. Maybe a Shapes graph, or a SPARQL query with some encapsulation. Sorry I'm not a SHACL expert...


On 05/05/17 03:35, Renato Iannella wrote:
> I think we need to update the definition of each constraint left operand in the Vocab to make sure it is clearly defined/described. We say this in the IM, so we just need to check that in the vocab.
> So, for example, we should say how "event" is used with the operators.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <https://github.com/w3c/poe/issues/161#issuecomment-299351700>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnprR3B4rSdADAUXgbWyCRSB30Bzgkkks5r2nz4gaJpZM4NNr9a>.
>


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

Received on Wednesday, 17 May 2017 14:35:42 UTC