OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (EMERGENCY-95) TEP 1.1 - TAB-1312: Keywords "CONDITIONAL" is REQUIRED or OPTIONAL


    [ https://issues.oasis-open.org/browse/EMERGENCY-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61402#comment-61402 ] 

Patti Aymond commented on EMERGENCY-95:
---------------------------------------

Reporter: Patrick Durusau

> TEP 1.1 - TAB-1312: Keywords "CONDITIONAL" is REQUIRED or OPTIONAL
> ------------------------------------------------------------------
>
>                 Key: EMERGENCY-95
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-95
>             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: 
> ***** 
> In addition, within this Specification, the keyword “CONDITIONAL” should be interpreted as potentially “REQUIRED” or “OPTIONAL” depending on the surrounding context. 
> ***** 
> It isn't cricket to use a keyword to mean opposite things depending on context. 
> "CONDITIONAL" appears only twice in this document: 
> Both under unitNumber, 
> ****** 
> Usage: CONDITIONAL; MAY be used once but only once [0..1] 
> Constraints: CONDITIONAL (If "providerKind" is EMS, then "unitNumber" is REQUIRED) 
> ***** 
> Elements often have occurrence or co-occurrence constraints. 
> It is sufficient to state the constraint without the "CONDITIONAL" keyword, thus: 
> Delete: 1.4 "In addition, within this Specification, the keyword “CONDITIONAL” should be interpreted as potentially “REQUIRED” or “OPTIONAL” depending on the surrounding context." 
> unitNumber, delete "CONDITIONAL" so that the remaining text reads: 
> Usage: MAY be used once but only once [0..1] 
> Constraints: If "providerKind" is EMS, then "unitNumber" is REQUIRED 
> which agrees with standard markup practices.



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]