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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-comment message

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


Subject: Re: [emergency] 45-day Public Review for EDXL Situation Reporting (EDXL-SitRep) V1.0


Elysa, Rex,

I'm not sure if these are edits allowable under this current 45 day review, but here are a couple questions/suggestions.

Line 195  appears to be duplicate words [Types Types]
"Provide separate specific formats for the distinct Situation Report Types Types in order to simplify implementation and use"

Line 644 in Element IncidentType provides a definition for CBRNE (Chemical, Biological, Radiological, Nuclear or High-Yield Explosive threat or attack); whereas

Line 935 in Glossary provides a shorter abbreviation (Chemical, Biological, Radiological, 935 and Nuclear)

Suggest updating Line 935 definition to be the same as in 644.


Best regards,

Patrick Gannon


On 6/4/2012 3:42 PM, Chet Ensign wrote:
The OASIS Emergency Management TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 45-day public review:

Emergency Data Exchange Language Situation Reporting (EDXL-SitRep) Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
08 May 2012

URIs:
The complete package of the prose specification document and related files are available in the ZIP distribution file at:

https://www.oasis-open.org/committees/download.php/46170/edxl-sitrep-v1.0-csprd02.zip

Specification Overview:
This XML-based Emergency Data Exchange Language (EDXL) Situation Reporting specification describes a set of standard reports and elements that can be used for data sharing among emergency information systems, and that provide incident information for situation awareness on which incident command can base decisions 

TC Description: 
The OASIS Emergency Management Technical Committee has recently completed and approved as a Committee Specification, the Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0. 

In addition to completing and approving the Emergency Data Exchange Language Situation Reporting v1.0 Committee Specification 02 and advancing it to a second Public Review, it is expected that this TC will also complete and approve The Emergency Data Exchange Language Distribution element v2.0 as a new Committee Specification Draft and advance it also for Public Review. 

Public Review Period:
The public review starts 5 June 2012 and ends 20 July 2012. The specification was previously submitted for public review [2]. This 45-day review is limited in scope to changes made from the previous review. Changes are highlighted in the diff-marked PDF file in the review package.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

Additional information about the specification and the OASIS Emergency Management TC may be found at the TC's public home page located at:

http://www.oasis-open.org/committees/emergency/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled "Send A Comment" at the top of the TC public home page, or directly at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=emergency

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/emergency-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of Emergency Data Exchange Language Situation Reporting (EDXL-SitRep) Version 1.0, we call your attention to the OASIS IPR Policy [3] applicable especially [4] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification. 

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.

========== Additional references:

[1] OASIS Emergency Management TC 
http://www.oasis-open.org/committees/emergency/

[2] Public Reviews:
45-day public review, 16 November 2011: https://lists.oasis-open.org/archives/tc-announce/201111/msg00004.html

[3] http://www.oasis-open.org/who/intellectualproperty.php

[4] http://www.oasis-open.org/committees/emergency/ipr.php
http://www.oasis-open.org/policies-guidelines/ipr#s10.2.2
RF on RAND mode

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393


---------------------------------------------------------------------
To unsubscribe, e-mail: emergency-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: emergency-help@lists.oasis-open.org









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