Example Practices: CAP Elements Version 1.0

Committee Note Draft 01 11 April 2013 Specification URIs This version: http://docs.oasis-open.org/emergency-adopt/cap- elements/v1.0/cnd01/cap-elements-v1.0-cnd01.doc (Authoritative) http://docs.oasis-open.org/emergency-adopt/cap- elements/v1.0/cnd01/cap-elements-v1.0-cnd01.html http://docs.oasis-open.org/emergency-adopt/cap- elements/v1.0/cnd01/cap-elements-v1.0-cnd01.pdf Previous version: N/A Latest version: http://docs.oasis-open.org/emergency-adopt/cap-elements/v1.0/cap- elements-v1.0.doc (Authoritative) http://docs.oasis-open.org/emergency-adopt/cap-elements/v1.0/cap- elements-v1.0.html http://docs.oasis-open.org/emergency-adopt/cap-elements/v1.0/cap- elements-v1.0.pdf Technical Committee: OASIS Emergency Management Adoption TC Chairs: Thomas Ferrentino ([email protected]), Individual Rex Brooks ([email protected]), Network Centric Operations Industry Consortium Camille Osterloh ([email protected]), Individual Editors: Yu Chen ([email protected]), Google Inc. Anthony Mancuso ([email protected]), Google Inc. elements-v1.0-cnd01.html Draft 01. CAP Example ElementsPractices: Version 1.0 [CAP-Elements-v1.0] format used: referencing should be the following document When this citation format: Citation at page by using Committeethe “ Committee’s Technical emailOthersto list. commentsshould send the Technical the Committeeon to document Technical members comments this should send version” notedfor possibleabove “Latest laterrevisionslocation ofthis document. abovelevel Checkon also The the date. ofis TC the approval Adoption listed above. was Managementlast the OASIS This revised Emergency document orby approved Status: feeds. web providespractices This example for public disseminationalertsdocument of CAP via Abstract: work: Related cap-elements-v1.0-cnd01 translate it intolanguages than other English. applicable copyrights, to as forthset IPR in the Policy,must OASIS be or required followed) as to ordocument deliverable produced by Technical an Committee OASIS (in which case the rules copyright the references notice OASIS, or to asexcept for needed purpose the of developing any However, thisdocumentworks. itself may be not modified in any including way, by removing abovethat the copyright notice and this section included are on all such derivative copies and published, copied, distributed, and orin whole part, without restriction anyof kind, provided works that on comment explain or otherwise it or assist in its implementation may be prepared, documentThis and of translations it may be furnishedcopied and to others, and derivative website.OASIS PropertyIntellectual Rights (the IPR Policy Policy"). "OASIS The full All capitalized interms the text following have the meanings assigned them to in the OASIS Copyright OASIS© Open All Rights2013. Reserved. Non-Standards TrackNon-Standards http://docs.oasis-open.org/emergency/cap/v1.2/os/CAP-v1.2-os.html  open.org/emergency-adopt/cap-feeds/v1.0/cap-feeds-v1.0.html  is to: related This document Common AlertingCommon Version 1.2 Protocol CAP Example FeedsPractices: Version 1.0 http://www.oasis-open.org/committees/emergency-adopt/ http://docs.oasis-open.org/emergency-adopt/cap-elements/v1.0/cnd01/cap- The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply Send A Comment Send A . This Non-Standards is a Work Product. Track ” button onCommittee’s button the Technical web” . 11 April 2013. OASIS Committee April11 Note OASIS2013. . . July01 OASIS2010. Standard. . . Latest version. . Copyright © Copyright OASIS Open Reserved.Rights© All 2013. Policy http://docs.oasis- . may be found at the . . . 112013 April Page 2 of 16

[Type the document title] PURPOSE. ORRIGHTS MERCHANTABILITY ANY WARRANTIES IMPLIED OF OR FOR A FITNESS PARTICULAR THATWARRANTY OF THEUSE THE OWNERSHIP HEREIN INFRINGE INFORMATION WILL NOT ANY EXPRESS ALLINCLUDINGDISCLAIMS WARRANTIES, ORBUT IMPLIED, LIMITED ANYNOT TO documentThis and the containedinformation is herein provided an on "AS IS" andbasis OASIS successors or assigns. The limited permissions granted aboveare perpetual not and will be by revoked OASIS or its cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply This Non-Standards is a Work Product. Track Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . 112013 April Page 3 of 16

[Type the document title] 3 2 1 Table Contentsof cap-elements-v1.0-cnd01 C.Appendix B.Appendix A.Appendix Non-Standards TrackNon-Standards A.2 CAP Community Canadian A.1 NOAA (National Oceanic and Atmospheric Administration) 3.4 ExpirationAlert vs. Update 3.3 expirationAlert 3.2 updates Alert 3.1 thatAlerts span jurisdiction boundaries Path:XML alert/restriction) Alert 2.7 Public Aggregators Should Ignore aCAP Messages with Restriction Element (CAP 2.6 CAPPrepare Usage Documentation 2.5 richcontentProvide by linking resources to XML (CAP Path: alert/info/resource) alert/info/severity, alert/info/certainty)and 2.4 urgency,Customize severity, eventcertainty to XML (CAP Paths: alert/info/urgency, 2.3 Take care XML with encoding alert/info/instruction) 2.2 usefulInclude descriptions and (CAPinstructions XML alert/info/descriptionPaths: and 2.1 Optimize alertareas (CAP Path:XML alert/info/area) 1.1 References (non-normative) A.2.2 Environment CanadaA.2.2 CanadianA.2.1 Community Challenges Alerting CAPthat AlertsImpact CAP Element Usage Introduction Cap Practices Alert Revision HistoryRevision Acknowledgments ...... The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply ...... This Non-Standards is a Work Product. Track ...... Copyright © Copyright OASIS Open Reserved.Rights© All 2013...... 112013 April ...... Page 4 of 16 15 13 12 12 12 12 11 10 10 10 10 16 9 8 8 7 7 7 6 6 5 5

[Type the document title]

open.org/committees/download.php/6334/oasis-200402-cap-core-1.0.pdf Common Protocol Alerting 1.0.March Verison Standard 2004. OASIS [CAP-1.0] open.org/committees/download.php/15135/emergency-CAPv1.1-Corrected_DOM.pdf Common Protocol Alerting 1.1.01Verison October Standard 2005. OASIS [CAP-1.1] http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.htm [CAP-1.2] A. generation.” The expressed comment “Needa forinternational good/example practices used for alert Workshop need forthisnote from came noteThis example provides related practices certain to elements in CAPcontained alerts. The Introduction cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards References (non-normative) This noteThis covers:   Common ProtocolAlerting Version 1.2 , made , theat Emergency Policy Alerting Workshop, Montreal, Canada, 1-3 May, 2012. Alerting Challenges Alerting CAPthat AlertsImpact CAP Element Usage The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply Comment 6, Comments & Questions, Emergency Policy Alerting This Non-Standards is a Work Product. Track . . July 01 OASIS 2010. Standard. Copyright © Copyright OASIS Open Reserved.Rights© All 2013. l

https://www.oasis- . https://www.oasis- 112013 April Page 5 of 16

[Type the document title] B. B. structures representing softwareCAP within messages applications.) or form;ASN.1 these principlesapply equally case in either as well as in the caseof internal data certain CAP (Notethat elements. an instance a of CAP maymessage be in eitherserialized XML sectionThis summarizes some exampleimplementation pertaining practices to use the of completed. a variousAs result, implementations of CAP alertmessagescan different.look quite The Common Protocol Alerting flexibility provides mostin the how of CAP data elements are CAP ElementUsage cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards Optimize alert areas alert Optimize (CAP Path:XML alert/info/area)      provide precision. acceptable simplify the on function polygon. In cases most polygon a of verticesless than can 20 unreasonable ofnumber for points polygona alertarea, it may necessarybe use to a derived mapping from data foran boundaryirregular such as shoreline). a To avoid an an official boundary with hundreds (for sides example,of a polygon is automatically dropped. This can happenwhen an alertarea is definedby reference a source that gives may interfere the with efficient processing of CAPa alert, and can result in an alertbeing If possible, overly-complex simplify polygons. Having many too coordinates in a polygon coordinates should more haveno than five decimal places. areas, precision, generally,the not should greaterbe than one and, meter therefore, reflect its true accuracy(distance accurate meters,kilometers,to CAP etc.).For alert area shape, precisionthe any of one coordinate value of (number decimal places) should a alertingWhen the area wholeis the Earth certain (e.g., space weather hazards), kilometer ratherthan zero. latitude threewith decimal places (about 100radius meters), the .1ought be to impliedprecision by the centercircle's coordinates. instance,For givencenterpoint a what yoube intend). general, In the radius be should comparablein scale to the Examine the of use a zero-radius itcircle, implies as a geometric (which point may not may enforce not this rule. point. isrequirementThis a of the CAP specification mappingeven though some tools polygons. anyClose For polygon in CAP, the first must point identical be to last the -90,-180 -90,180 90,180 90,-180, -90,-180 Watch forfalse of precision coordinates in geometric shapes. theRegardless of alert

"bounding box" (SW polygon SW) SENW NE be should used CAP areain the element:  haveanot warning area. earthquakes, which usually definedbyare point a since and, they occur quickly,may decision. For policy example, zero-radiusa circle may thebe option only for thatNote zero-radius circles, technicallywhile incorrect,may reflect an intentional Example: The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply NOAA This Non-Standards is a Work Product. Track (National Oceanic and AtmosphericAdministration Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . 112013 April Page 6 of 16

[Type the document title] D. C. cap-elements-v1.0-cnd01 E. Non-Standards TrackNon-Standards Include useful descriptions and instructions (CAP XML and Paths: descriptions instructions Include useful Customize urgency, severity, certainty to event (CAPXML Paths: Take care XML with encoding      alert/info/urgency, alert/info/severity, and alert/info/certainty) alert/info/description and alert/info/instruction) is available from the from publisheda source,if Note possible. originators.for U.S. Hazard-alerting guidance simplify processing recipients, by text in CAP use alertsshould common phrases, drawn the the public specified or target ofaudience the To alert. enhance understandingand should actionablebe and focusshould on protectiveappropriate action be to taken by text should relevant and be useful the for audience in the alertarea. Instruction text The whenever such possible, for characters.check and/or non-UTF-8 characters. CAP editing softwarethat permitskeyboard entry should, pasting” from web pages or as word-processors, such insertions often include hidden UTF-8 encoded well. as Care be should taken when inserting text by “cuttingand UTF-8 encoded. The source code of programsany that modify such XML must files be maximumFor interoperability, CAP a alert thatmessage is serialized XMLas be should only utilize utilize only this value [unknown] element when the truly value is unknown." (RIM)Model Subcommitteeprovides following the guidance:"... practitioners should "unknown certainty"). Note Emergency the Management Reference OASIS Information severity” (extraordinary threat life to or property) is underplayed because it has an "immediate (responsive urgency" action be should taken “extreme immediately) or “minimal.” to helps This underplaying avoid event,an such as eventwhen an with value is Further, unavailable. value “unknown”the be not should treated as equivalent bestIt's use to "unknown" Urgency, an and Severity, event and the level desired responseof that to event. eachvalues of alertinstance correspondshould the to characteristics the of specific light snow,thunderstorms, and winds.strong The Urgency, Severity, and Certainty example, “Special NOAA’s Weather Statement” alerthas been used such forevents as Many alert eventscan elicit range a of urgency, andseverity, certaintyvalues. For across hazardacross respect types with the to separate CAP aspects Urgency,Severity,of and thatNote the "Advisory,” terms “Watch,” and are “Warning" usednot consistently  SPECIFICATION creation provided guidance in weather event, predictions event, about and the its impact. alert Excellent consistentlyhighare quality,and usually include oninformation current the Example: The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply NOAA World Meteorological Organization/Public Weather Services This Non-Standards is a Work Product. Track . . and (National Oceanic and AtmosphericAdministration) descriptions WFO WEATHER SEVERE PRODUCTS Copyright © Copyright OASIS Open Reserved.Rights© All 2013. elements forfree-formallow text. The

Certainty value only when the . 112013 April Page . 7 of 16

[Type the document title] G. G. F. cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards Provide rich content by tolinking resources (CAPXML Path: Prepare CAP Documentation Usage     alert/info/resource)  maintenance is sometimes necessary. accessiblePublicly and regularly updated documentationCAP element of usage and supplemental information. andcomplete actionable itself; informationby in a provide only should element include to essential warning information. The basic CAP payload be should retrieval of URLa HTTP. over Therefore, CAP messagesshould use NOT the The element generally invokes secondary a mechanism, suchdelivery as recipients such distinguish to extensions richmediafrom content. Inextension. such cases, appropriate an MIME type be should to specified enable specifichighly data structures that be cannot adequately handled by the The element may alsobe used a as means a extend to CAP messagewith can client andaccess display the linked resource). helpsThis message a to receiver better understand the context theof event(a web feed Use the http://nws.weather.gov/haz_simp/ Certainty. (The National Weather is Service considering these simplifying terms–see http://capan.ca/index.php/en/cap-cp/ Example: Good CAPCanadian profile (CAP-CP) documentation available at    Example: ValueName include should the “Usage,” term and the parameter's Value should documentation be should provided :in a the parameter's beshould documented. clearly reference A the to other URL or location theof Locally-specified usage of elements in alerts a with scope "Public" usages. designers If possible, of new CAP origination tools or procedures to refer should contain the to URL documentation.the Map. Map. ShakeMapsUSGS has theirwebsite on that linked.can be Example: tsunamis, large For WCATWC links provides their to Tsunami Energy myParameterUsage The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply This Non-Standards is a Work Product. Track url-to-parameter-usage-doc element embedto links content, to such as images or files.audio ). . Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . 112013 April Page 8 of 16

[Type the document title] such messages. (“ < CAP a message that also has < a aIn messagevalidated against the schemaCAP 1.2 the restriction element should occuronly in “Public”) cannot relied to on be evaluate < the Aggregators of CAP intendedmessages for distributionpublic (i.e., where the value is H. cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards restriction> Public” Public Alert Aggregators Ignore Should a with CAP Messages Restriction Element(CAP Path:XML alert/restriction) , “ Private” or element can occur with anythe of enumerated values of The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply This Non-Standards is a Work Product. Track “ scope> Restricted” of “ Restricted” restriction> ), ), onlybut "Restricted" a is definedfor Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . In. CAP prior schemas, the element. element. . 112013 April Page 9 of 16

[Type the document title] J. J. alertsduplicative deliverycan clog and channels desensitize recipients. corroboration. However, inconsistent alerts canconfusion, cause and a number large of issuing its own Multiple alerts alert. generally are acceptable avoid to providegaps and national boundaries. amongPoor coordination agenciesalerting can result in each agency suchHazards as meteorological and geological eventsoften cross province, town, city, state, and I. Alerting Challengesthat ImpactCAP Alerts cap-elements-v1.0-cnd01 disseminators, feedsand delivery systems determineto how the long alert will visibleto remain recipients. Unless explicitan time is bespecified, toit will up the various an Determining the alert’s K. and tips technical improvecan help quality the and accuracyof alertupdates. conditions,and moving and CAP elementthe structurallyneed be to valid. The following process updatingAlert can complex.be Theof content an alert needs be to to updated reflect changing Non-Standards TrackNon-Standards Alert Alert updates Alerts that span jurisdiction boundaries that span Alerts Alert Alert expiration       IDs of all alertsreferring previous theto same thatevent haven'texpired. Use action recommendations. This ensure helps that CAP feedclients not do miss changes. Issue CAP updatesinstead of new alertsto reflect changing circumstances or protection the alertto expire. should updatedbe previous before the expires, version unless it is the to intention allow obtaining current alertinformation foruse alert in timely updates. aAt alerts minimum Regularly updatealerts. creators/maintainers Alert should establish for protocols sub-element, in the alerts. help identify the duplication theis through use aof common identifier, suchthe as If there overlapping are or duplicatealerts by issued differentauthorities, one way to jurisdictions are receiving comparable alertinformation from sources.other administrative boundaries unless originator is the certain that people in adjoining threat or event. shouldThe area be not constrained (“clipped”) to politicalor The CAP element be should to used area describe the at from risk the subject policies, procedures or regionalwarning centers should considered. be efforts. If frameworkssuch existing are considered not adequate, the establishmentof existing inter-jurisdictional processes and agreements coordinate to their warning Agencies and alertissuingbodies in the same region should,leverage where possible, time is extremely helpful for CAP feedclients and downstream other alert The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply This Non-Standards is a Work Product. Track to earlier to point alerts. The system alerting needs to the record time duringalert issuance can be challenging, yet having Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . Page Page 112013 April 10 of 16

[Type the document title] L. L. general of idea the ofduration alert the public. Thethe following though steps, not perfect, haveproven useful forgiving people a cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards Alert ExpirationAlert vs. Update Alert expiration time.expiration Here is an example: may consider to wish adding an additional that explicitly states that the event be will updated (if Ifit is theknown). originator can predict the ofexpiration the event, it Typically, originatoran uses the tosub-element express next timethe the alert  A defaulttime setcan be several ways: default If the issuer iscertain not when the will event expire, it may be to desirable fill in a 2012-02-28T16:45:00-06:00 EventEndTime     clients andclients other recipients to have time update.pull in the exactlynot the same theas so that the -Note the if alertexpiration is time certain, the issuer can send updatethe early, or more after the and updateseveryissues 30 the minutes, that poll example more slowly).For theif agency measuresissues gauges flood alert (setting it slightlyafter the next updatetime avoid helps gaps forclients The can Warning active be daysfor 2 by default. Tornado can beWarning active hoursfor 2 by default, a while Hurricane The durationactive can be fixed. The The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply time for for time alert,the sothat the alert be won’t indefinitely. effective This Non-Standards is a Work Product. Track time can time dependentbe the on type. event example, For a can time severalbe hours aheadof the time can time setbe next after the expected updatetime forthe time is time 30 minto hrs 2 before the time time Copyright © Copyright OASIS Open Reserved.Rights© All 2013. time. time. ensuresThis that the CAP feed time can be minutes45 . time, and this time, and Page Page 112013 April 11 of 16

[Type the document title] A.1 A.1 toguidance CAP other alert andoriginators distributors. The appendixdescribes features specific of CAP alert implementations that may provide useful A.Appendix cap-elements-v1.0-cnd01 (see federal,Canadian provincial, and private agencies that have adoptedthe CAP Canadian Profile The Community Canadian listed practices are bybelow used NAADS. Theyalsoare by used many A.2.1 behalf of authorities.other aggregates redistributesand CAP alert messages, but alsocan originate CAP Canadian alerts on (National NAADS Aggregation Alert &Dissemination System) is primarilya feedservice a that A.2 Non-Standards TrackNon-Standards  http://rss.naad-adna.pelmorex.com/ https://alerts.weather.gov/cap/us.php?x=0 Common Alerting - Protocol Profile Canadian (CAP-CP)    CAP Community Canadian NOAA Oceanic and Atmospheric (National Administration) Canadian Community Canadian Compatibility with multiple clients Succinct understandableand Clear alert Alert vs.Alert event     short phrase short phrase that describes area.an descriptionThe area varies being from list a of to towns, namea of region, a a to http://www.nws.noaa.gov/geodata/ geocodes UGC and shapes definedand are updated the on NOAA website geocodes. FIPS6 targeted are Alerts both custom a to and apolygon to more one andor UGC alert (e.g., severealert (e.g., thunderstorm advisory, rainfreezing warning) Distinct of notion event an severe (e.g., thunderstorm, rain)freezing an versus  Miller; Miller; Nevada; Sevier” Kings Canyon,” “Columbia; Hempstead; Howard; Little Lafayette; River; Example: “Central Beaufort SeaCoast,” from“Sierra Nevada Yosemite to CapAlert Practices The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply This Non-Standards is a Work Product. Track Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . . Page Page 112013 April 12 of 16

[Type the document title] also established its own CAP practices. Several Environment Canada are practices listedbelow. Environment Canada agency is an that has alsoadopted CAP Canadianthe Profile, and which has A.2.2 cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards      EnvironmentCanada Secure Secure CAP content Modeling subject eventthe alert foreach it moves as across areas languages Canada of Multiple languages (English and French) always are to bothpresent serve official Simplified and exaggerated polygons Secure CAP content                Alert updatecontainsAlert still a area active and an area.expired areaExpired contains AllClear. landingDifferent pages in Content is professionally translated. Separate exaggerated boundaries beyond complicated boundaries forPolygons threat the area are simplified in theof number vertices and have have found common usage. definedAlthough not in the Profile,Canadian Digital in signatures CAPeach alert ueName> profile:profile_name:version:valueNameof in the element… profile andImplements layer CAPspecific parameters through a consistent use element Declares the a usage of profile within CAP a message thethrough Canadian- Profile (CAP-CP (through message use Profilesthe of Layersand see – Embed to Ability multiple definedpractices (byentity) single in a CAP alert http://www.nws.noaa.gov/geodata/ geocodes UGC and shapes definedand are updated the on NOAA website geocodes. FIPS6 targeted are Alerts both custom a to and apolygon to more one andor UGC keyPublic published at areaStill active contains updated and time. Separate blocks foreach area. The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply . This Non-Standards is a Work Product. Track block for each language. http://dd.meteo.gc.ca/public-keyring/ ) for for language.each Copyright © Copyright OASIS Open Reserved.Rights© All 2013. Common Protocol Alerting . Page Page 112013 April 13 of 16

[Type the document title] cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards     http://www.nws.noaa.gov/geodata/ geocodes UGC and shapes definedand are updated the on NOAA website geocodes. FIPS6 targeted are Alerts both custom a to and apolygon to more one andor UGC http://www.nws.noaa.gov/geodata/ geocodes UGC and shapes definedand are updated the on NOAA website geocodes. FIPS6 targeted are Alerts both custom a to and apolygon to more one andor UGC The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply This Non-Standards is a Work Product. Track Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . Page Page 112013 April 14 of 16

[Type the document title] Greg Trott Greg Paulsen Norm Camille Osterloh Elysa Jones HamGary Steve Hakusa CoakleyPhil ChristianElliot BrooksRex BotterellArt Allport Doug Participants: acknowledged: individualsThe following haveparticipated creationin of the thisspecification and gratefully are B. Appendix cap-elements-v1.0-cnd01 WestfallJacob Non-Standards TrackNon-Standards Individual Alerting for Common Protocol for the AustralianCustodian CAP-AU standard Government CanadaEnvironment Individual Individual Individual Google Google Individual Consortium IndustryCentric Network Operations Individual Exchanges (MASAS-x) National Information Situational Multi-Agency Awareness Systems-Canada Acknowledgments The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply This Non-Standards is a Work Product. Track Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . Page Page 112013 April 15 of 16

[Type the document title] Appendix C.Appendix cap-elements-v1.0-cnd01 Non-Standards TrackNon-Standards 1.0 021.0 wd 011.0 wd Revision - 11 -04/04/13 03/26/13 01/14/13 01/11/13 Date Revision History The patent provisions of the Policy The OASIS of IPR do patent provisions not the apply This Non-Standards is a Work Product. Track Tony Mancuso Tony Mancuso Editor Christian, Norm Paulsen. comments Art from Botterell and Elliot Incorporated and content responded to Updated draft with content.additional Added text editsand Elliot from Christian. developed EMA-Collateral by Docs SC).and from CAPprior feedand element doc Initial Draft CAP element(copied content MadeChanges Copyright © Copyright OASIS Open Reserved.Rights© All 2013. . Page Page 112013 April 16 of 16

[Type the document title]