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