- From: Renato Iannella via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Aug 2017 01:19:01 +0000
- To: public-poe-archives@w3.org
riannella has just labeled an issue for https://github.com/w3c/poe as "Model": == Which property of type Duty has a consequence property? == The IM of 21 August defines in 2.5.3 Duty Class > Note that the consequence property must not be used on a Duty that is already a consequence for a Permission duty or Policy obligation. There is an issue: * The Duty Class defines: A Duty may have none, one or many consequence property values of type Duty. * Result: the properties obligation, duty, remedy and consequence are of type Duty and have therefore a consequence property * The Note above excludes a consequence property inside a consequence instance only for duty and obligation ... * ... therefore remedies may have an unlimited nesting of consequences. Suggested solution 1: change the definition of the consequence property of the Duty Class to: A Duty may have none, one or many consequence property values of type Duty if used with any property except the consequence property itself. (This stops nesting consequences.) Suggested solution 2: exclude the consequence property from the basic Duty Class. Then define the Duty-Extended Class as sub-class of Duty Class and add the consequence property and set the type to Duty Class. Then apply the Duty-Extended Class to obligation, duty and remedy. See https://github.com/w3c/poe/issues/222
Received on Friday, 25 August 2017 01:18:59 UTC