- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Aug 2017 09:11:06 +0000
- To: public-poe-archives@w3.org
@riannella thanks for all the changes. **re cardinality of property values** See 2.1 Profile - a single profile property may hold one to many profile ids: Checking this feature for other properties I agree that currently by the specification also e.g. the action property of the Rule Class must occur one time (and not more) but may hold multiple actions ids. BUT: * may the uid property of Policy Class hold multiple identifiers? It must not! * for the permission, prohibition and obligation the current specification says "A Policy MUST have one and MAY have many permission, prohibition, or obligation properties for Rules." ... and in fact the same serialisation syntax is used for multiple e.g. permissions like for multiple profiles. * My conclusion: to provide an unambiguous definition of properties the cardinality of their values must be written down in the IM. Footnote: as JSON-LD supports using a single value and an array of values for the same property the Examples don't help to find out the cardinality. My suggestion: * The IM should express explicitly the cardinality of property values = if multiple values are ok then "... one or may have many ..." should be used - everywhere. * The IM should ignore the syntactic sugar of Turtle or JSON which allows to wrap multiple values by a single formal property - that's a serialisation issue, not a model issue. -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/215#issuecomment-320898283 using your GitHub account
Received on Tuesday, 8 August 2017 09:11:10 UTC