[OASIS Issue Tracker] Created: (OBIX-157) Confusing normative and non-normative text, ending in ambiguity

Confusing normative and non-normative text, ending in ambiguity
---------------------------------------------------------------

                 Key: OBIX-157
                 URL: http://tools.oasis-open.org/issues/browse/OBIX-157
             Project: OASIS Open Building Information Exchange (oBIX) TC
          Issue Type: Bug
          Components: OBIX 1.1 Specification
    Affects Versions: OBIX 1.1 XSD PR02
         Environment: TAB Review
            Reporter: Toby Considine
            Assignee: Toby Considine


"The use of ""example,"" to signal non-normative text is mixed with normative text, making it difficult for the reader to separate normative from non-normative material. 

One example (by no means the only one): 7.3 Is Attribute: 

***** 
Note that element names such as bool, int, or str are abbreviations for implied Contracts. However if an Object implements one of the primitive types, then it MUST use the correct OBIX type name. For example if an Object implements obix:int, then it MUST be expressed as <int/>, rather than <obj is=""obix:int""/>. Therefore it is invalid to implement multiple value types - such as implementing both obix:bool and obix:int. 
***** 

I count: 

Note - non-normative 
MUST - normative 
For example - non-normative 
MUST - normative 
invalid - ? normative or non-normative 

In 69 words, the text switches from noromative to non-normative four (4) times and then ends up ambiguous as to normative or non-normative. 
"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira