-
Type: Bug
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: WS-BRSP Basic Profile Version 1.2 CSPRD01
-
Fix Version/s: None
-
Component/s: Public reviews
-
Labels:None
-
Environment:
Style
1.4 Notational Conventions reads in part:
*****
Extensibility points in underlying specifications (see "Conformance Scope") are presented in a similar manner:
EnnnnExtensibility Point Name - Description
where "nnnn" is replaced by a number that is unique among the extensibility points in the Profile.
*****
Really need to avoid "similar" under all conditions. Just a noise word as far as standards are concerned.
Depending on where you want to define the format of Requirements and Extensibility Points, consider something like:
*****
Requirements are identified by an R, followed by four digits and then the requirement text.
Extensibility points are identified by an E, followed by four digits, an Extensibility Point Name and explanatory text.
*****
That may seem a bit dry but the purpose of standards prose is to convey the same message to everyone reading it. (That a goal, not a certainty.)