@agreiner please refer to the multiple Use Cases that clearly identify that profiles are transitively hierarchical (they inherit all constraints of base profiles). So provide a way to "flatten" these things out so that clients do not need to walk the hierarchy if a server is willing to do the work to flatten them out. or look at the SKOS spec, and the way skos:broaderTransitive is defined - and may be entailed from skos:broader (or provided entailed in the resource at the server's discretion) fair enough to think about best practices for entailment (and avoiding run-time entailment) but the rationale is clear enough, and the requirements have been discussed multiple times and agreed, so now we need to focus on a solution, not re-opening the debate. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/486#issuecomment-434193153 using your GitHub accountReceived on Tuesday, 30 October 2018 07:04:28 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:25 UTC