[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EMERGENCY-78) TEP 1.1 - TAB-1332: When does must mean MUST?
Patti Aymond created EMERGENCY-78: ------------------------------------- Summary: TEP 1.1 - TAB-1332: When does must mean MUST? Key: EMERGENCY-78 URL: https://issues.oasis-open.org/browse/EMERGENCY-78 Project: OASIS Emergency Management TC Issue Type: Bug Components: TEP Environment: Normative Reporter: Patti Aymond Assignee: Patti Aymond The keyword "MUST" appears as lowercase "must" at: 3. EDXL Tracking of Emergency Patients "then the XML schema shall always take precedence and the other artifact(s) must be changed to match the XML schema." ? Unnecessary in any event because the TC Process mandates that the XML Schema always prevails. 126.96.36.199 List redefinition "Note that list redefinition may pose significant risk to interoperability and therefore, whether the list is completely redefined or only partially, best practices suggest that the extension mechanism must be used, to signal that risk." ? regular use of must? 3.4.1 EDXL Distribution Element (EDXL-DE) If other routing/transport mechanisms are being used, they must support at least the meta-data used by the DE, as described henceforth (non-normative). ? BTW, you do realize that the majority of 3 is non-normative, yes? 188.8.131.52 Identifying MessageType "f the default value list is used (”urn:oasis;names:tc:emergency:EDXL:DE2.0:Defaults:StatusType”) the functional name for the EDXL-TEP “Message Type” takes the form of an XML enumeration where the value must be one of:" Is that another namespace? Suspect you meant "MUST" here. 184.108.40.206 Signature "A digital signature must be provided in the form of a graphic image carried by the EDXL-DE message header as separate content object." I suspect this was meant to be "MUST" as well. -- This message was sent by Atlassian JIRA (v6.2.2#6258)