[OASIS Issue Tracker] (EMERGENCY-93) TEP 1.1 - TAB-1314: Markup occurrence terminology

Patti Aymond created EMERGENCY-93:
-------------------------------------

             Summary: TEP 1.1 - TAB-1314: Markup occurrence terminology
                 Key: EMERGENCY-93
                 URL: https://issues.oasis-open.org/browse/EMERGENCY-93
             Project: OASIS Emergency Management TC
          Issue Type: Bug
          Components: TEP
         Environment: Normative
            Reporter: Patti Aymond
            Assignee: Patti Aymond
            Priority: Critical


1.4 Terminology reads in part: 

***** 
E.g. [1..1] means REQUIRED, exactly once, [..*] means OPTIONAL, any number of times. 
***** 

Actually, that's not markup language is it? That's from modeling. 

What's wrong with using + one or more, ? optional, and * zero or more, as standard notation? More likely to be read correctly by markup users. 

BTW, you do know that your XSD schema controls in the event of a conflict with the standard? 

The TC Process document: https://www.oasis-open.org/policies-guidelines/tc-process#specQuality, under 7(a) provides in part: 

***** 
Where any definition in these separate files disagrees with the definition found in the specification, the definition in the separate file prevails. 
***** 

So you really don't have to repeat the constraints you have in the schema in any formal way in the prose text. The schema already has that covered. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)