strawman for informal feedback on splitting of constraints that differ for vanilla vs chocolate cases

Once the WG decides how to resolve some of those cases (proposals already 
exist for ~ 12), the lucky editors have to draft it.
We'd prefer drafting it one consistent way once, of course.

The alternatives we've come up with so far are mocked up below, under the 
assumption that the WG resolved vanilla => basic and chocolate => 
advanced; no such proposal or resolution has occurred, it just seemed more 
realistic to use something remotely sensible in our spec not ice cream 
flavors (even Tosci's...hmmm).

No WG resolution is needed, in the end it's editorial; if you care to 
express an opinion before we choose one and base non-trivial amounts of 
work on it, the usual -1/0/+1 sense we use for formal decisions is fine.


Without context:
(proposal 1) LDP servers MUST (basic)/SHOULD (advanced) ... 
(proposal 2) Basic LDP servers MUST, and advanced LDP servers SHOULD, ... 
(proposal 3) Basic LDP servers MUST ... . Advanced LDP servers SHOULD do 
so. 


With some context:



Example conformance rules
The following informative examples show how LDP assigns conformance 
criteria to each class of LDP servers using a single rule.
Example: the same criteria apply to both basic and advanced LDP servers
LDP servers SHOULD ...  
The preceding rule is equivalent to the following pair of rules:
Basic LDP servers SHOULD ...  
Advanced LDP servers SHOULD ...  

Example: different criteria apply to basic and advanced LDP servers
Trying out different ways of covering each class while minimizing text 
duplication here. Final format TBD.
(proposal 1) LDP servers MUST (basic)/SHOULD (advanced) ... 
(proposal 2) Basic LDP servers MUST, and advanced LDP servers SHOULD, ... 
(proposal 3) Basic LDP servers MUST ... . Advanced LDP servers SHOULD do 
so. 
Each of the preceding rules is equivalent to the following pair of rules:
4.8.2 Basic LDP servers MUST ... 
4.8.2 Advanced LDP servers SHOULD ... 


Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario

Received on Thursday, 10 October 2013 16:21:04 UTC