Re: A start on a list of EM standards

All -

Was wondering about the "scope" of the standards (defacto, de-jure etc) in
the final report. There are numerous standards used in EM applications
that could be included beyond what is already listed. For example,
GeoRSS/AtomPUB is used in numerous alerting and warning applications. Then
there AIXM/GML for the sharing of aeronautical information between
authorities, authorities and airports, airports and authorities and so
forth. And there is all the work being done by NENA for the US Next
Generation 911 system, including an information model for sharing
geospatial content between and among local governments and PSAPS.
Definitely a controlled vocabulary in that model. There are many more,
which is why I ask the question.

Cheers

Carl


> This would be a good reference for our report. How exhaustive did you find
> his paper? scope of standards he covered?
>
> I have added these references to the final report, in the following
> section
> for now
> http://www.w3.org/2005/Incubator/eiif/wiki/EIIF_Final_Report#Existing_standards_and_technology
>
> chamindra de silva
> http://chamindra.googlepages.com
>
>
> On Fri, Apr 3, 2009 at 2:26 AM, Gary Berg-Cross
> <gbergcross@gmail.com>wrote:
>
>> Eli Rohn reported on "A Survey of Schema Standards and Portals for
>> Emergency Management and Collaboration" at ISCRAM 07
>>
>> Here are the schemas (not Portals) he reported on in  Table 1:
>> Emergency Schemas and Portals
>>
>>  ANML Advisory and Notification Markup Language facilitating emanation
>> of data relating to software vulnerabilities US  Schema
>>
>> CAP  Common Alerting Protocol to collect and relay instantaneously and
>> automatically all types of hazard warnings and reports locally,
>> regionally and nationally for input into a wide variety of
>> dissemination systems US Schema
>>
>>
>> EDXL  Facilitate emergency information sharing and data exchange
>> across the local, state, tribal, national and non-governmental
>> organizations of different professions that provide emergency response
>> and management services
>> US Schema
>>
>> IEEE 1512
>> A family of standard messages for traffic incident management, public
>> safety, hazardous material incident, and management of entities
>> external to centers.
>> US Schema
>>
>> LGCL  A controlled vocabulary for local government and community
>> resources categorized in a hierarchical structure under headings
>> familiar to citizens.
>> UK Schema
>>
>> IPSV The Integrated Public Sector Vocabulary is an 'encoding scheme'
>> for populating the e-Government Metadata Standard (e-GMS) subject
>> element of metadata.
>> UK Schema
>>
>> RWE Notification of Road Works and Highway related Events among local
>> and central government, emergency services and the media
>> UK Schema
>>
>> SDEP Street events Data Exchange Protocol
>> UK Schema
>>
>> HCCHE
>> A schema that enables electronic exchange of highway related inquiries
>> and problem reports received from the public.
>> UK Portal and Schema
>>
>>  RTA
>> Facilitates the exchange of road traffic accident data between the
>> Compensation Recovery Unit and the National Health Service for the
>> recovery of insurance compensation to injured parties.
>> UK Portal and Schema
>>
>> Gary Berg-Cross,Ph.D.
>> gbergcross@gmail.com
>> http://ontolog.cim3.net/cgi-bin/wiki.pl?GaryBergCross
>> SOCoP Executive Secretary
>> Principal, EM&I Semantic Technology
>> Potomac, MD
>>  301-762-5441
>>
>>
>>
>> On Thu, Apr 2, 2009 at 1:44 PM, Chamindra de Silva
>> <chamindra@opensource.lk> wrote:
>> >
>> >
>> > On Thu, Apr 2, 2009 at 7:16 PM, <paola.dimaio@gmail.com> wrote:
>> >>
>> >> Assessing Interoperability in Emergency Management Standards
>> >>
>> >>
>> >>
>> >>
>> >> http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=04494315
>> >>
>> >
>> > Paola this would be a reference for the gap analysis we require.
>> >
>> > chamindra de silva
>> > http://chamindra.googlepages.com
>> >
>> >
>>
>>
>>
>> --
>>
>

Received on Tuesday, 7 April 2009 14:20:33 UTC