This is a follow-up to #260 which attempts to resolve the long-running issue #10 regarding the extent to which profiles constrain the Thing Description Information model, and is a replacement for PR #125.
The work so far in #260 includes many of the constraints from the original Core Data Model section in six sub-sections of a new Common Constraints section:
Security
Discovery
Links
Errors
Semantic Annotations
Default Language
My proposal in this PR is to replace the content of the remaining Information Model section (what's left from the original "Core Data Model" section) with a Best Practices section which includes some of the key remaining constraints as recommendations.
The content of the current Information Model section is still very contentious and we are running out of time to agree on which constraints to keep. This proposal is a compromise which retains some of the key constraints from that section as recommendations which I think we can get quick consensus on.
I have explained the rationale behind the removal of other more rigid constraints in great detail in other issues and PRs, but I'm happy to answer any questions about constraints that others feel should be kept.
This is a follow-up to #260 which attempts to resolve the long-running issue #10 regarding the extent to which profiles constrain the Thing Description Information model, and is a replacement for PR #125.
The work so far in #260 includes many of the constraints from the original Core Data Model section in six sub-sections of a new Common Constraints section:
My proposal in this PR is to replace the content of the remaining Information Model section (what's left from the original "Core Data Model" section) with a Best Practices section which includes some of the key remaining constraints as recommendations.
The content of the current Information Model section is still very contentious and we are running out of time to agree on which constraints to keep. This proposal is a compromise which retains some of the key constraints from that section as recommendations which I think we can get quick consensus on.
I have explained the rationale behind the removal of other more rigid constraints in great detail in other issues and PRs, but I'm happy to answer any questions about constraints that others feel should be kept.
Preview | Diff