Ok, then I suggest this definition of the Profile Mechanism using a more verbose but as I think also clearer wording: > To create an ODRL Profile, the ODRL Core Vocabulary classes can be extended by sub-classes with optional additional properties, the Core Vocabulary properties can be extended by sub-properties, further instances of classes and properties defined by the Core Vocabulary or this Profile can be defined. The table below shows some typical extensions, a new Profile is not limited to them: What about these phrases in the Profile Definition examples: * ... and define it as disjoint with all other Policy subclasses (except Set). * ... and define it as disjoint with all other Rule subclasses. Is that only a hint or a normative requirement? -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/300#issuecomment-374132124 using your GitHub accountReceived on Monday, 19 March 2018 08:17:01 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:47:04 UTC