-
Type: Bug
-
Status: New
-
Priority: Blocker
-
Resolution: Unresolved
-
Affects Version/s: OSLC Core Specification v3.0 WD
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:
References
-
Proposal:
OSLC Attachments 3.0 - 04 February 2016
At the expense of perhaps being repetitive, I would rethink the location and division of references. Generally speaking those are the second major section of the standard, in part because you may be relying upon them to impose further constraint (my earlier comment about normative references) on the items you define.
CF also my comments on separation out your requirements from conformance clauses.
A short hand way to think about that issue, separation of requirements from conformance is to consider requirements as defining/declaring what the rules are. No arguments, persuasion, etc., you are just announcing the rule.
All URLs conform to (insert ref).
Somewhere else, you say:
Sever type X MUST conform to:
list of sections
section about URLs
Makes it much easier to maintain and extend in the future.