[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EMERGENCY-73) TEP 1.1 - TAB-1337: 5 Conformance - vagueness
Patti Aymond created EMERGENCY-73:
-------------------------------------
Summary: TEP 1.1 - TAB-1337: 5 Conformance - vagueness
Key: EMERGENCY-73
URL: https://issues.oasis-open.org/browse/EMERGENCY-73
Project: OASIS Emergency Management TC
Issue Type: Bug
Components: TEP
Environment: Conformance
Reporter: Patti Aymond
Assignee: Patti Aymond
5 Conformance reads in part:
"it meets the general requirements specified in Section 4;"
It isn't clear what "general requirements" you have in mind.
Do you mean:
4.1 "Routing Header" Elements?
Be aware that Emergency Data Exchange Language (EDXL) Distribution Element v1.0, http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf
DOES NOT appear as a normative reference in 1.5 Normative References
When you correct that, consider whether conformance requires the TEP Message to appear as the content of ContentObject in EDXL-DE and/or reference EDXL-DE to establish the requirements for another delivery mechanism to carry a TEP Message.
--
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]