Transcript OASIS: Integrating Standards for Web Services, Business

OASIS
Organization for the
Advancement of
Structured
Information Standards
Introduction Slide Decks
Purpose
n
Education and orientation
l
l
n
By members
By prospective members
Promotional briefings
l
l
By members
By prospective members
n
Ex. To their mgmt, for approval to join OASIS
Slide Decks to be produced
n
n
n
n
n
OASIS introduction
OASIS process introduction
Technical Committee (TC) introductions
Sub-Committee (SC) introductions
Product overviews
Maintenance Schedule
n
Updated quarterly
l
l
n
Updates to be submitted in month following quarter
Status statements as of end of quarter
TC deck updates by TC’s
l
Subject to TC discussion
Targets
n
n
Single slide summaries
<=10 slide presentations
Technical Committee Slide
Deck
n
n
n
n
n
n
n
OASIS introduction page
Technical committee introduction page
Sub-committee listings
Products listings
Sub-committee / product associations
Sub-committee introduction pages
Product introduction pages
OASIS
n
Mission
l
n
n
n
To drive the development, convergence and adoption
of open standards for the global information society.
Not-for-profit consortium
Founded in 1993 as SGML Open
Global representation
l
l
l
5,000+ participants representing …
600+ organizations and individual members in …
100+ countries
Technical Committee
introduction page
n
n
n
Mission statement
Vision statement
Primary Beneficiaries
Ex. Emergency Management TC
n
Mission
l
n
Vision
l
n
Create emergency-related standards for data
interoperability.
Issue once, for distribution to all with a need
to know, and authority to receive.
Direct Stakeholders
l
Public safety officials, broadcasters
Sub-committee listing
n
Title and acronym only
l
Ex. Messages and Notification (Msg-Not)
Product listing
n
Title and acronym only
l
Ex. Common Alerting Protocol (CAP)
Sub-committee / product
associations
n
Sub-committee acronym followed by
product acronyms (or names)
l
Ex. Msg-Not: CAP, EDXL, EDXL-DE, ...
Sub-Committee introduction
page
n
n
n
Mission statement
Vision statement
Direct stakeholders
Product introduction pages
n
n
n
n
Purpose statement
Usage status
Current version
Status / current activity
Ex. Common Alerting Protocol
(CAP)
n
Purpose
l
n
Usage status
l
n
Adopted throughout US, Canada, Europe for public alerting and to
lesser extent, restricted alerts
Current version
l
n
Open, non-proprietary digital message format for all types of alerts
and notifications, public, restricted and private. Supports routing,
filtering and conversion to other formats.
v1.1 Errata 28 August 2006
Status
l
l
v1.2 at technical committee review stage. ETA Q4 2009
v2.0 efforts to commence when v1.2 completed
Product Overview
n
n
n
n
n
n
Product introduction page
Features summary
Benefits summary
Adoption
Timeline
Additional information
l
Focus on clarity, highlight key feature,
implementation challenges, etc.
Ex. Product introduction page
Common Alerting Protocol (CAP)
n
Purpose
l
n
Usage status
l
n
Adopted throughout US, Canada, Europe for public alerting and to
lesser extent restricted alerts
Current version
l
n
Open, non-proprietary digital message format for all types of alerts
and notifications, public, restricted and private. Supports routing,
filtering and conversion to other formats.
v1.1 Errata 28 August 2006
Status
l
l
v1.2 at technical committee review stage. ETA Q4 2009
v2.0 efforts to commence when v1.2 completed
Ex. Features
CAP Features
n
n
n
n
n
n
n
n
Public, private and restricted messaging
Updates and cancels
Actual, testing and exercises
Every alert defined by urgency, severity and certainty
Categorized to common themes. Ex. Meteorological
Alert area may be defined using GIS, and or
geocodes
Supports resources
Adaptable to specific user communities
Ex. Benefits
CAP Benefits
n
n
n
Single system can be used to support alerts of
all urgencies, severities and certainties
Messages may be filtered based on urgency,
severity and certainty, category, location, etc.
Easily converted into last mile formats,
including SMS, RSS, etc.
Ex. Adoption
CAP Adoption
n
n
n
Adopted as ITU standard
Endorsed by US federal and state governments,
in use in state systems, being implemented in
national systems
Endorsed by Canadian federal and provincial
governments, in use in provincial system, being
implemented in national alert aggregation
system
Ex. Timeline
CAP Timeline
n
n
n
n
n
n
n
Submission by Art Botterrell
1.0 March 2004
1.1 October 25
1.1 Errata October 2007
ITU Adoption
1.2 ETA October 2009
2.0 ETA 2011
Ex. Elaboration
CAP is in the background
<?xml version="1.0" encoding="utf-8"?>
<geocode>
<alert xmlns="urn:oasis:names:tc:emergency:cap:1.1">
<valueName>profile:CAP-CP:Location:0.3</valueName>
<identifier>NBMASASui10286</identifier>
<value>1301006</value>
<sender>DAllport</sender>
</geocode>
<sent>2009-07-17T23:49:40.0436089+00:00</sent>
</area>
<status>Exercise</status>
</info>
<scope>Public</scope>
<info>
<code>profile:CAP-CP:0.3</code>
<language>fr-CA</language>
<msgType>Alert</msgType>
<event>Routier - Fermeture de route</event>
<info>
<responseType>Monitor</responseType>
<language>en-CA</language>
<urgency>Immediate</urgency>
<event>Roadway - Roadway Closure</event>
<severity>Minor</severity>
<responseType>Monitor</responseType>
<certainty>Observed</certainty>
<urgency>Immediate</urgency>
<audience>Doug Allport</audience>
<severity>Minor</severity>
<onset>2009-07-18T12:00:00+00:00</onset>
<certainty>Observed</certainty>
<expires>2009-07-19T12:00:00+00:00</expires>
<audience>Doug Allport</audience>
<senderName>Doug Allport</senderName>
<onset>2009-07-18T12:00:00+00:00</onset>
<headline>Routier - Fermeture de route - Doug Allport, Exercise</headline>
<expires>2009-07-19T12:00:00+00:00</expires>
<web>http://www.gnb.ca/0113/index-e.asp</web>
<senderName>Doug Allport</senderName>
<category>Transport</category>
<headline>This is a test Road Closure Alert</headline>
<eventCode>
<description>Free form text field</description>
<valueName>profile:CAP-CP:Event:0.3</valueName>
<instruction>More free form text here</instruction>
<value>roadClose</value>
<web>http://www.gnb.ca/0113/index-e.asp</web>
</eventCode>
<contact>NB DOT 888-555-5555</contact>
<parameter>
<category>Transport</category>
<valueName>layer:CAPAN:eventLocation:point</valueName>
<eventCode>
<value>45.2449203344103,-66.11091613769532</value>
<valueName>profile:CAP-CP:Event:0.3</valueName>
</parameter>
<value>roadClose</value>
<area>
</eventCode>
<areaDesc>1301006 - Saint John</areaDesc>
<parameter>
<geocode>
<valueName>layer:CAPAN:eventLocation:point</valueName>
<valueName>CAP-CP:Location:0.3</valueName>
<value>45.2449203344103,-66.11091613769532</value>
<value>1301006</value>
</parameter>
</geocode>
<area>
</area>
<areaDesc>1301006 - Saint John</areaDesc>
</info>
</alert>
Issuer
interfaces with
form, IVR,
custom
application, etc.
Issuing
Application
produces
CAP
Aggregator
Distributor
Recipient
collects and
shares
CAP
converts CAP
to common and
proprietary
protocols
interfaces with
common
products and
services. Ex.
Television,
phone, ...
Ex. Elaboration
CAP is adaptable
n
US Integrated Public Warning System Profile
l
n
Canadian Profile of CAP (CAP-CP)
l
n
Defines event codes and location code references
and requirements, in support of Emergency Alert
System and other legacy systems
Defines event codes and location code references
and requirements in support of national needs,
including automated translation
Canadians are including event location
references