← Prev in month ← Prev in thread

[OASIS Issue Tracker] (EMERGENCY-84) TEP 1.1 - TAB-1323: EDXL-CIQ, EDXL-CT, EDXL-GSF, EDXL-SitRep - drafts are not eligible as Normative References

From
OASIS Issues Tracker <>
Date
2015-12-03T21:31:03+00:00
ID
Thread
[OASIS Issue Tracker] (EMERGENCY-84) TEP 1.1 - TAB-1323: EDXL-CIQ, EDXL-CT, EDXL-GSF, EDXL-SitRep - drafts are not eligible as Normative References
Patti Aymond created EMERGENCY-84:
-------------------------------------

             Summary: TEP 1.1 - TAB-1323: EDXL-CIQ, EDXL-CT, EDXL-GSF, EDXL-SitRep - drafts are not eligible as Normative References
                 Key: EMERGENCY-84
                 URL: https://issues.oasis-open.org/browse/EMERGENCY-84
             Project: OASIS Emergency Management TC
          Issue Type: Bug
          Components: TEP
         Environment: Style
            Reporter: Patti Aymond
            Assignee: Patti Aymond
            Priority: Critical


1.5 reads in part as follows: 

[EDXL-CIQ] W. Joerg, OASIS Committee Specification Draft Emergency Data Exchange Language Customer Information Quality http://docs.oasis-open.org/emergency/edxl-ciq/v1.0/csd02/ , September, 2011 

[EDXL-CT] W. Joerg, OASIS Committee Specification Draft Emergency Data Exchange Language Common Types http://docs.oasis-open.org/emergency/edxl-ct/v1.0/csd02/, November, 2011 

[EDXL-GSF] W. Joerg, OASIS Committee Specification Draft Emergency Data Exchange Language GML Simple Features http://docs.oasis-open.org/emergency/edxl-gsf/v1.0/csd01/, September, 2011 

[EDXL-SitRep] Emergency Data Exchange Language Situation Reporting (EDXL-SitRep) Version 1.0. 4 May 2012. OASIS Committee Specification Draft 01 / Working Draft 18. 

Each of these documents claims to be a draft and not a final work product deliverable by an OASIS TC or an OASIS Standard. 

That being the case, these drafts could be changed at any time to introduce requirements inconsistent with their current state. 

The unstable nature of drafts makes it impossible to make normative references to which an implementer must conform in order to conform to the standard in question. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
← Prev in month ← Prev in thread