- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Aug 2017 08:27:04 +0000
- To: public-poe-archives@w3.org
@riannella while writing https://github.com/w3c/poe/issues/211#issuecomment-324255580 I noticed that the problem is inside the Duty Class: some properties of type Duty may have a consequence, others not. And the remedy property slipped in inadvertently, sorry. My conclusion after having had a deeper look into https://github.com/w3c/poe/files/1240662/states.pdf is: * The Rule Class should have only a minimal processing model, only what is shared across Permission, Prohibition and Duty * We need a detailed processing model for these three sub-classes of Rule as they are quite different. * I'm still not happy with having a class named "Duty" and a property of other classes named "duty". A wrong case of the first character can cause confusion in the documentation and in the communication about ODRL. (I'm aware of the history: in ODRL 2.0/.1 the Duty Class was only the type of the duty property of the Permission Class, nothing else. Now 4 properties are of this type and one of them is named "duty".) -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/215#issuecomment-324258825 using your GitHub account
Received on Wednesday, 23 August 2017 08:27:03 UTC