INFOD Use Case Scenario OGF21, Seattle, WA, USA raghul@utk.edu

Overview Status Steve Fisher (RAL) INFOD prototype First Responder - Use Case Scenario INFOD Registry Implementation Issues of Concern Demo Extended specification Dieter Gawlick (Oracle) 2

An Information Dissemination Scenario Notification Message differs based on the entries created and the subscriptions Registers as a Publisher Sends Alert message Notification Message Registers as a Subscriber and defines subscription identifying dynamic consumers Alert Msg: Category: Fire, Chemical Urgency: Immediate Notification Message Matches Entities based on entries created Alert Msg: Category: Fire Urgency: Immediate Action: Stop Police ABC Chemicals Alert Msg: Category: Fire Urgency: Immediate Action: Evacuate INFOD Registry Service Registers as a Subscriber, defines subscription based on client necessities. Alert Msg: Category: Fire Urgency: Immediate Action: Detour Notification Message County Office Notification Message Registers as a Subscriber, defines subscription identifying consumers and describes message format. Alert Msg: Category: Fire, Chemical Registers as a Consumer Service Providers Notification Message Hospital Alert Msg: Category: Fire Urgency: Immediate Action: Detour Alert Msg: Category: Fire Urgency: Expected Action: Evacuate Alert Msg: Category: Fire, Chemical Urgency: Immediate Registers as a Consumer Notification Message Registers as a Consumer Fire Station Fire Station Alert Msg: Category: Fire, Chemical Severity: Extreme, (Minor ,Moderate) Chemical Types: XXX Notification Message Alert Msg: Category: Fire, Chemical Severity: Extreme Chemical Types: XXX 3

First Responder Use Case Scenario Publisher Publisher Sensor Fusion Center Weather Station APD 2000 Chemical Sensor 2 INFOD Registry Publisher Chemical Sensor 1 Alerting System Consumer Plume Analysis First Responder 1 Subscriber/Consumer/Publisher Consumer First Responder 2 E911 Center Subscriber/Consumer INFOD Message Exchange Information Notification 4

Property Vocabulary Instance INFOD Resources Subscribers and Consumers are modeled as independent entities. Subscriptions are created by a subscribers, conforming to a subset of consumer. Publisher Consumer Consumer Subscriber Subscription defines the event of interest at the publisher, the message to be generated in response to an event and helps identify consumers dynamically. INFOD Registry Publisher Entry Subscriber Entry Subscription Consumer Entry Structured Information Model, user communities are identified by property and data vocabularies. Data Source Entry Property Vocabulary Instance Entries categorize real world entities and define constraints identifying other entities of interest Data Vocabulary Property Vocabulary Vocabulary instances characterize the entries, on which constraints are evaluated in the registry. Entry Resource – not an entry Creation of resource Reference (EPR) Data sources associate publishers to data vocabularies; the metadata of the publisher. Notification (by INFOD registry) Notification (by Publishers) 5

INFOD Registry Implementation Identifying and Registering Vocabularies Property Vocabulary Data Vocabulary Create Entries Publisher Subscriber Consumer Define Property Vocabulary Instances Publisher’s create Data Source entries Subscriber’s define Subscriptions Matching Entries Registry Notification Publisher to Consumer Notification 6

Community User Property Vocabulary Sensor Property Vocabulary Property Vocabulary Predicates Comments Sensor Identification Unique id for sensor Sensor Description Details on the sensor Location Physical location of sensor Contact Information Person to be contacted Associated Organization The owner of the sensor Community User Property Vocabulary Property Vocabulary Predicates Comments Identification Identifier for the Organization Name Name of the Organization Description Text Description Location Physical location information Contact Information Person to me contacted Vocabulary predicates are an abstraction from NIEM (National Information Exchange Model) 7

Registering Property Vocabulary Request Message <infod:CreatePropertyVocabulary> <infod:VocabularyName>SensorPropertyVocabulary</infod:VocabularyName> <infod:PropertyVocabularyDescription>Vocabulary for sensor and alerting systems </infod:PropertyVocabularyDescription> <infod:VocabularyBody> <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" > <xsd:import namespace=http://niem.gov/niem/niem-core/2.0 schemaLocation="http://niem.gov/niem/niem-core/2.0" /> <xsd:element name="sensorPropertyVocabulary"> <xsd:complexType> <xsd:sequence> <xsd:element name="SensorIdentification" type="nc:IdentificationType" /> <xsd:element name=”SensorDescription” type=”nc:ItemType” /> <xsd:element name="Location" type="nc:LocationType" /> <xsd:element name="ContactInformation" type="nc:ContactInformationType"/> <xsd:element name="AssociatedOrganization" type="nc:OrganizationItemAssociationType" /> </xsd:sequence> </xsd:complexType> </element> </xsd:schema> </infod:VocabularyBody> </infod:CreatePropertyVocabulary> Response Message <infod:CreatePropertyVocabularyResponse> <infod:PropertyVocabularyReference> <wsa:Address>http://infod.firstrespondernetwork.com/PropertyVocab1 </wsa:Address> </infod:PropertyVocabularyReference> </infod:CreatePropertyVocabularyResponse> 8

Data Vocabulary Sensor/Alert Data Vocabulary (NIEM and CAP - Common Alerting Protocol) Data Vocabulary Predicates Comments Activity Description between time period Event Description at a specific time Substance Description of a chemical material Status Actual, Exercise, System, Test Message Type Alert, Update, Cancel, Ack, Error Scope Public, Restricted, Private, Urgency Immediate, Expected, Future, Past Response Type Shelter, Evacuate, Prepare, Execute, Monitor, Assess, None Severity Extreme, Severe, Moderate, Minor Certainty Very likely, Likely, Possible, Unlikely Category Geo, Met, Safety, Security, Rescue, Fire, Health, Env, Transport, Infra, CBRNE, Other Weather Sensor Data Vocabulary ( DWML –Digital Weather Markup Language) Data Vocabulary Predicates Comments Location Weather information at a location Time Information at a specific date & time Temperature Temperature unit as an attribute Wind Speed With units as an attribute Wind Direction As an angular measure Humidity As a relative or specific value 9

Registering Data Vocabulary Request Message <infod:CreateDataVocabulary> <infod:VocabularyName>WeatherInformationDataVocabulary</infod:VocabularyName> <infod:DataVocabularyDescription> Weather information in DWML </infod:DataVocabularyDescription> <infod:VocabularyLanguage> http://niem.gov/niem/niem-core/2.0</infod:VocabularyLanguage> <infod:VocabularyBody> <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" > <xsd:import namespace="http://niem.gov/niem/niem-core/2.0 " schemaLocation="http://niem.gov/niem/niem-core/2.0" /> <xsd:element name="sensorNetDataVocab" type="DataVocabularyType" /> <xsd:complexType name="DataVocabularyType" > <xsd:sequence> <xsd:element name="Activity" type="nc:activityType" nillable="true"/> <xsd:element name="Event" type="nc:eventType" nillable="true"/> <xsd:element name="Substance" type="nc:substanceType" minOccurs="0" /> <xsd:element name="capAlertStatus" minOccurs="0"> <xsd:simpleType> <xsd:restriction base = "xsd:string"> <xsd:enumeration value = "Actual"/>….. </xsd:restriction> </xsd:simpleType>…… </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:schema> </infod:VocabularyBody> </infod:CreateDataVocabulary> Response Message <infod:CreateDataVocabularyResponse> <infod:DataVocabularyReference> <wsa:Address>http://infod.firstrespondernetwork.com/DataVocab1 </wsa:Address> </infod:DataVocabularyReference> </infod:CreateDataVocabularyResponse> 10

Chemical Sensor - Publisher Vocabularies Registered with INFOD registry Chemical Sensor as a Publisher Publisher Entry Property Vocabulary Instance Data Source Entry Chemical Sensor with multiple sensors (producers) Data sources referenced by the publisher entry Same external EPR, different INFOD EPR Property vocabulary instances are created with reference to data source entry’s Sensor 3 Sensor 4 Chemical Sensor 1 Sensor 5 Chemical Sensor 2 Publisher Entry 2 Publisher Entry 1 Data Source Data Source Data Source Prop. Vocab. Inst. Prop. Vocab. Inst. Data Source Prop. Vocab. Inst. Prop. Vocab. Inst. Data Source Prop. Vocab. Inst. SENSOR Prop. Vocab. USER Prop. Vocab. SENSOR / Alert Data. Vocab Weather Data. Vocab INFOD Registry 11

Weather Station - Publisher Weather station returns information on request specifying a location in latitude and longitude coordinates. Weather station as a publisher Publisher Entry Property Vocabulary Instance Data Source Entry Sensor 5 Sensor 4 Sensor 3 Chemical Sensor 2 Chemical Sensor 1 Weather Station Publisher Entry 2 Publisher Entry Publisher Entry Data Source Prop. Vocab. Inst. Prop. Vocab. Inst. Prop. Vocab. Inst. Data Source Data Source SENSOR Prop. Vocab. USER Prop. Vocab. SENSOR / Alert Data. Vocab Weather Data. Vocab INFOD Registry 12

Alerting System – Consumer/Subscriber/Publisher As a Consumer of information from the sensors Consumer Entry Property Vocabulary Instance As a Subscriber for sensor information Subscriber Entry Creates subscription for data from sensors As a Publisher of Alert messages Publisher Entry Data Source Entry Weather Station Sensor 5 Sensor 4 Sensor 3 Alerting System Plume Analysis Chemical Sensor 2 Chemical Sensor 1 Subscriber Entry Publisher Entry 2 Publisher Entry Consumer Entry Publisher Entry 1 Subscription Subscription Prop. Vocab. Inst. Prop. Vocab. Inst. Prop. Vocab. Inst. Data Source Prop. Vocab. Inst. Data Source Prop. Vocab. Inst. Data Source SENSOR Prop. Vocab. USER Prop. Vocab. SENSOR / Alert Data. Vocab Weather Data. Vocab INFOD Registry 13

First Responder - Consumer Alerting System Plume Analysis Weather Station First Responder acts based on alert messages received from the Plume Analysis System Consumer Entry Property Vocabulary Instance Sensor 5 Sensor 4 Sensor 3 First Responder First Responder Chemical Sensor 2 Chemical Sensor 1 Consumer Entry Subscriber Entry Publisher Entry 2 Consumer Entry Publisher Entry 1 Consumer Entry Subscription Subscription Prop. Vocab. Inst. Prop. Vocab. Inst. Prop. Vocab. Inst. Data Source Prop. Vocab. Inst. Data Source SENSOR Prop. Vocab. USER Prop. Vocab. SENSOR / Alert Data. Vocab Weather Data. Vocab INFOD Registry 14

E911 Center - Consumer/Subscriber Alerting System Plume Analysis E911 center as a consumer of alert messages Consumer Entry Property Vocabulary Instance E911 center as a subscriber defining events and notification messages to consumers (first responders) Subscriber Entry Weather Station Sensor 5 Sensor 4 First Responder Sensor 3 First Responder First Responder Chemical Sensor 2 Chemical Sensor 1 E911 Center Subscriber Entry Subscriber Entry Publisher Entry 2 Consumer Entry Publisher Entry 1 Consumer Entry Consumer Entry Subscription Subscription Subscription Prop. Vocab. Inst. Prop. Vocab. Inst. Prop. Vocab. Inst. Data Source Prop. Vocab. Inst. Data Source SENSOR Prop. Vocab. USER Prop. Vocab. SENSOR / Alert Data. Vocab Weather Data. Vocab INFOD Registry 15

Information Dissemination Model Weather Station First Responder First Responder First Responder Sensor 5 Sensor 4 Sensor 3 Alerting System Plume Analysis E911 Center Chemical Sensor 2 Chemical Sensor 1 INFOD Registry Publisher Entry Subscriber Entry Subscription Consumer Entry Data Source Entry Property Vocabulary Instance Data Vocabulary Property Vocabulary Entry Resource – not an entry Creation of resource Reference (EPR) 16 Notification (by INFOD registry) Notification (by Publishers)

Subscription Request Message <infod:CreateSubscription> <infod:SubscriptionName> xsd:string </infod:SubscriptionName> ? <infod:SubscriptionDescription> xsd:string </infod:SubscriptionDescription> ? <infod:SubscriberEntryReference> wsa:EndPointReferenceType </infod:SubscriberEntryReference> <infod:DataConstraint > xsd:anyType </infod:DataConstraint> * <infod:PropertyConstraint> xsd:any </infod:PropertyConstraint> * <infod:DynamicConsumerConstraint> </infod:DynamicConsumerConstraint> * </infod:CreateSubscription> Response Message <infod:CreateSubscriptionResponse> <infod:SubscriptionReference> wsa:EndPointReferenceType </infod:SubscriptionReference> </infod:CreateSubscriptionResponse> 17

GetMetaData Subscribers and Consumers are not aware of data vocabulary contents. Subscriber in order to define subscription require the knowledge of data vocabulary. GetMetaData Request MetaDataQuery - XQuery expression – FLWOR Example 1 – Get the list of data vocabularies in the registry for $vocab in fn:collection(‘$$infodDataVocabularies’) return <datavocabularies> { $vocab//infodepr, $vocab//DataVocabularyName, $vocab//DataVocabularyDescription } </datavocabularies> Example 2 – Fetch the xml schema of the desired data vocabulary where $vocab//infodepr = “http://infod.firstrespondernetwork.com/DataVocab1” return $vocab <infod:GetMetaData> <infod:MetaDataQueryExpression> {xsd:anyType} </infod:MetaDataQueryExpression> </infod:GetMetadata> 18

Subscription Data Constraints and Dynamic Consumer Constraints XQuery expressions – FLWOR Subscription 1 – associating chemical sensors and alerting system <infod:CreateSubscription> <infod:SubscriptionName> Get Chemical Sensor Alerts </infod:SubscriptionName> <infod:SubscriptionDescription> On the watch for chemical spills </infod:SubscriptionDescription> <infod:SubscriberReference> <wsa:Address> http://infod.firstrespondernetwork.com/ Subscriber1 </wsa:Address> </infod:SubscriberReference> <infod:DataConstraint> for $data in fn:collection(‘$$infodDataVocabularies’) return <ChemcalSensorInformation> { $data//Substance } </ChemcalSensorInformation > </infod:DataConstraint> <infod:PropertyConstraint> for $pub in fn:collection(‘$$infodpublishers’) where $pub//ItemName=”APD2000” for $con in fn:collection(‘$$infodconsumers’) where $con//OrganizationID=”PEC101” </infod:PropertyConstraint> </infod:CreateSubscription> 19

Subscription Subscription 2 – weather information at location of the chemical sensor Property Constraint associates weather station to the alerting system Data constraint specifies the epr of the chemical sensor for weather information <infod:CreateSubscription> <infod:SubscriptionName> GetWeatherInformation</infod:SubscriptionName> <infod:SubscriptionDescription> For weather information </infod:SubscriptionDescription> <infod:SubscriberReference> <wsa:Address> http://infod.firstrespondernetwork.com/Subscriber1 </infod:SubscriberReference> <infod:DataConstraint> return <weatherinformation> { let $i= http://infod.firstrespondernetwork.com/Publisher1 where $i//Location = //Location } </weatherinformation> </infod:DataConstraint> <infod:PropertyConstraint> for $pub in fn:collection(‘$$infodpublishers’) where $pub//WSReference = http://www.weatherstation.com for $con in fn:collection(‘$$infodconsumers’) where $con//OrganizationID=”PEC101” </infod:PropertyConstraint> </infod:CreateSubscription> 20

Subscription Subscription 3 – E911 center subscribes for alert messages on behalf of first responders Property Constraint the subscription to the alerting system The dynamic consumer constraints determine the consumers at the time of an event <infod:CreateSubscription> <infod:SubscriptionName> SensorAlerts</infod:SubscriptionName> <infod:SubscriptionDescription> Need to send sensor alert information </infod:SubscriptionDescription> <infod:SubscriberReference> <wsa:Address> http://infod.firstrespondernetwork.com/ Subscriber2 </wsa:Address> /infod:SubscriberReference> <PropertyConstraint> for $pub in fn:collection(‘$$infodpublishers’) where $pub//WSReference=http://www.sensoralertingsystems.com </PropertyConstraint> <DynamicConsumerConstraints> for $con in fn:collection(“$$infodConsumers”) where $con//OrganizationCategoryAbstract=”first_responders” and //capAlertStatus = Actual and fn:distance( $con//Location , $pub//Location ) < 5 </DynamicConsumerConstraints> </infod:CreateSubscription> 21

Implementation specifics Publisher Service(s) Publisher Service Consumer Service(s) Consumer Service Notify Client Create & Monitor Subscriber Service(s) Subscriber Service Create Test Environment JAVA ORACLE PL/SQL Create/ Replace/Drop INFOD Registry Service Subscription Reasoning Component Registry Manager Component Vocabulary Manager INFOD Entry’s Manager Meta Data Manager Publisher, Subscriber and Consumers are modeled as web services 22

The Matching Procedure The matching procedure in the INFOD registry is triggered for any create/replace/drop operation. The current implementation uses expression filter to evaluate property constraints, (expression filters only support XPath expressions) The where clause of the XQuery expression is equivalent to an XPath expression, when entries are created XQuery expressions are parsed and the where clause is rewritten as XPath expressions Taking advantage of the inbuilt database features, for every subscription, constraints are drafted as a single select query and the Xpath expression is evaluated using the EVALUATE operator 23

Notification Message On evaluating subscriptions notification messages are generated Notification to Publisher <infod:PublisherNotification> <infod:SubscriptionReference> <wsa:Address> http://infod.firstrespondernetwork.com/Subscription1 </wsa:Address> </infod:SubscriptionReference> <infod:ConsumerEntryReference> http://infod.firstrespondernetwork.com/ Consumer1 </infod:ConsumerEntryReference> <infod:DataConstraint> for $data in fn:collection(‘$$infodDataVocabularies’) return <ChemcalSensorInformation> { $data//Substance } </ChemcalSensorInformation > </infod:DataConstraint> <infod:DynamicConsumerConstraint>.. </infod:DynamicConsumerConstraint> </infod:PublisherNotification> Notification to Consumer <infod:ConsumerNotification. <infod:SubscriptionReference> <wsa:Address> http://infod.firstrespondernetwork.com/Subscription1 </wsa:Address> </infod:SubscriptionReference> <infod:PublisherEntryReference> http://infod.firstrespondernetwork.com/Publisher1 </wsa:Address> </infod:PublisherEntryReference> <infod:ConsumerNotification> Notification to Subscriber <infod:SubscriberNotification> <infod:SubscriptionReference> <wsa:Address> http://infod.firstrespondernetwork.com/Subscription1 </wsa:Address> </infod:SubscriptionReference> <infod:PublisherEntryReference> http://infod.firstrespondernetwork.com/Publisher1 </wsa:Address> </infod:PublisherEntryReference> <infod:ConsumerEntryReference> http://infod.firstrespondernetwork.com/ Consumer1 </infod:ConsumerEntryReference> 24

Issues Subscribing for publisher information with reference to one other publisher’s property Need weather information at the location of the chemical sensors Subscription-1 : identifies chemical sensors Subscription-2 : requests for weather information at the location of the chemical sensors identified in the previous subscription Subscription-2 is defined on receiving the notification message as a result of subscription-1 and subscription-2 needs to be replaced as subscription-1 result set changes. Publisher Publisher Chemical Sensor INFOD Registry Weather Station Alerting System Plume Analysis Consumer/Subscriber 25

Issues Publisher’s would require metadata to evaluate constraints As a result of subscription-1 the notification message lists publisher ( chemical sensor) epr’s. Subscription-2 carries the list of epr’s for weather information. The weather station needs to do a getMetaData for the location of the chemical sensor based on the epr’s in the subscription. 26

Issues Handling Dynamic Consumers First Responder 1 INFOD Registry Alerting System Plume Analysis First Responder 2 First Responder 3 Change of entries in the registry triggers evaluation of subscriptions Alerting system is interested in first responders within a 5 mile radius of a chemical sensor As the location of the first responder changes, requires the registry to reevaluate subscriptions and generate notification messages incessantly. 27

Overview Status Steve Fisher (RAL) INFOD prototype First Responder - Use Case Scenario Implementation Issues Demo Extended specification Dieter Gawlick (Oracle) 28

Full Copyright Notice Copyright (C) Open Grid Forum (2006). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees. OGF Full Copyright Notice if necessary 29

Publisher Entry Request Message Response Message <infod:CreatePublisherEntry> <infod:WSReference> <wsa:Address>http://www.sensornetwork.com/ChemicalSensor1</wsa:Address> </infod:WSReference> <infod:PublisherName>ChemSensor1</infod:PublisherName> <infod:PublisherDescription> APD 2000 Chemical Sensor </infod:PublisherDescription < infod:PropertyConstraint> xsd:any </infod:PropertyConstraint> * <infod:Notification> TRUE </infod:Notification> </infod:CreatePublisherEntry> Response Message <infod:CreatePublisherEntryResponse> <infod:PublisherEntryReference> <wsa:Address> http://infod.firstrespondernetwork.com/Publisher1 </wsa:Address> </infod:PublisherEntryReference> </infod:CreatePublisherEntryResponse> 30

Publisher Entry Property Constraint Entry Inside the registry XQuery expression – FLWOR expression Entry Inside the registry INFOD EPR XML Entry Valid_from - SYSTIMESTAMP Valid_to – SYSTIMESTAMP The valid_from and valid_to are to facilitate replace and drop operations inside the registry. 31

Property Vocabulary Instance Request Message <infod:CreatePropertyVocabularyInstance> <infod:EntryReference> <wsa:Address> http://infod.firstrespondernetwork.com/Publisher1 </wsa:Address> </infod:EntryReference> <infod:PropertyVocabularyReference> <wsa:Address>http://infod.firstrespondernetwork.com/PropertyVocab1</wsa:Address> </infod:PropertyVocabularyReference> <infod:PropertyVocabularyInstanceBody> <?xml version="1.0"?> <xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:nc="http://niem.gov/niem/niem-core/2.0" > <xsd:sensorPropertyVocabulary> <xsd:SensorIdentification> <nc:ItemName> APD2000 </nc:ItemName> </xsd:SensorIdentification> <xsd:Location> <nc:LocationTwoDimensionalGeographicCoordinate> <nc:GeographicCoordinateLatitude> <nc:LatitudeDegreeValue>35</nc:LatitudeDegreeValue> <nc:LatitudeMinuteValue>57</nc:LatitudeMinuteValue> <nc:LatitudeSecondValue>23</nc:LatitudeSecondValue> </ nc:GeographicCoordinateLatitude> <nc:GeographicCoordinateLongitude> <nc:LongitudeDegreeValue>-83</nc:LongitudeDegreeValue> <nc:LongitudeMinuteValue>55</nc:LongitudeMinuteValue> <nc:LongitudeSecondValue>30.3</nc:LongitudeSecondValue> </ nc:GeographicCoordinateLongitude> </nc:LocationTwoDimensionalGeographicCoordinate> </xsd:Location> </xsd:sensorPropertyVocabulary> </xsd:schema> </infod:PropertyVocabularyInstanceBody> </infod:CreatePropertyVocabularyInstance> 32

Property Vocabulary Instance Response Message <infod:CreatePropertyVocabularyInstanceResponse> <infod:PropertyVocabularyInstanceReference> <wsa:Address>http://infod.firstrespondernetwork.com/PropVocabRef1 </wsa:Address> </infod:PropertyVocabularyInstanceReference> </infod:CreatePropertyVocabularyInstanceResponse> 33

Data Source Entry Request Message Response Message <infod:DataSourceEntry> <infod:DatSourceEntryName> Chemical Sensor APD 2000 </infod:DataSourceEntryName> <infod:PublisherEntryReference> <wsa:Address>http://infod.firstrespondernetwork.com/Publisher1 </wsa:Address> </infod:PublisherEntryReference> <infod:DataVocabularyReference> <wsa:Address>http://infod.firstrespondernetwork.com/DataVocab1<wsa:Address> </infod:DataVocabularyReference> </infod:DatSourceEntry> Response Message <infod:CreateDataSourceEntryResponse> <infod:DataSourceEntryReference> <wsa:Address>http://infod.firstrespondernetwork.com/DataSourceEntry1 </wsa:Address> </infod:DataSourceEntryReference> </infod:CreateDataSourceEntryResponse> 34

Data Source Entry Request Message Response Message <infod:DataSourceEntry> <infod:DatSourceEntryName> Chemical Sensor APD 2000 </infod:DataSourceEntryName> <infod:PublisherEntryReference> <wsa:Address>http://infod.firstrespondernetwork.com/Publisher2 </wsa:Address> </infod:PublisherEntryReference> <infod:DataVocabularyReference> <wsa:Address>http://infod.firstrespondernetwork.com/DataVocab1<wsa:Address> </infod:DataVocabularyReference> </infod:DatSourceEntry> Response Message <infod:CreateDataSourceEntryResponse> <infod:DataSourceEntryReference> <wsa:Address> http://infod.firstrespondernetwork.com/DataSourceEntry2a </wsa:Address> </infod:DataSourceEntryReference> </infod:CreateDataSourceEntryResponse> 35

Property Vocabulary Instance Request Message <infod:CreatePropertyVocabularyInstance> <infod:EntryReference> <wsa:Address> http://infod.firstrespondernetwork.com/DataSourceEntry2a</wsa:Address> </infod:EntryReference> <infod:PropertyVocabularyReference> <wsa:Address>http://infod.firstrespondernetwork.com/PropertyVocab1</wsa:Address> </infod:PropertyVocabularyReference> <infod:PropertyVocabularyInstanceBody> <?xml version="1.0"?> <xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:nc="http://niem.gov/niem/niem-core/2.0" > <xsd:sensorPropertyVocabulary> <xsd:SensorIdentification> <nc:ItemName> APD2000 </nc:ItemName> </xsd:SensorIdentification> <xsd:Location> <nc:LocationTwoDimensionalGeographicCoordinate> <nc:GeographicCoordinateLatitude> <nc:LatitudeDegreeValue>35</nc:LatitudeDegreeValue> <nc:LatitudeMinuteValue>57</nc:LatitudeMinuteValue> <nc:LatitudeSecondValue>23</nc:LatitudeSecondValue> </ nc:GeographicCoordinateLatitude> <nc:GeographicCoordinateLongitude> <nc:LongitudeDegreeValue>-83</nc:LongitudeDegreeValue> <nc:LongitudeMinuteValue>55</nc:LongitudeMinuteValue> <nc:LongitudeSecondValue>30.3</nc:LongitudeSecondValue> </ nc:GeographicCoordinateLongitude> </nc:LocationTwoDimensionalGeographicCoordinate> </xsd:Location> </xsd:sensorPropertyVocabulary> </xsd:schema> </infod:PropertyVocabularyInstanceBody> </infod:CreatePropertyVocabularyInstance> 36

Publisher Entry Request Message Response Message <infod:CreatePublisherEntry> <infod:WSReference> <wsa:Address> http://wwww.weatherstation.com </wsa:Address> </infod:WSReference> <infod:PublisherName> Weather Station </infod:PublisherName> <infod:PublisherDescription> Provides weather information based on latitude and longitude co-ordinates </infod:PublisherDescription> <infod:Notification> TRUE </infod:Notification> </infod:CreatePublisherEntry> Response Message <infod:CreatePublisherEntryResponse> <infod:PublisherEntryReference> <wsa:Address>http://infod.firstrespondernetwork.com/Publisher3 </wsa:Address> </infod:PublisherEntryReference> </infod:CreatePublisherEntryResponse> 37

Data Source Entry Request Message Response Message <infod:DataSourceEntry> <infod:DatSourceEntryName>Weather Station </infod:DataSourceEntryName> <infod:PublisherEntryReference> <wsa:Address> http://infod.firstrespondernetwork.com/Publisher3 </wsa:Address> </infod:PublisherEntryReference> <infod:DataVocabularyReference> <http://infod.firstrespondernetwork.com/DataVocab2 </infod:DataVocabularyReference> </infod:DatSourceEntry> Response Message <infod:CreateDataSourceEntryResponse> <infod:DataSourceEntryReference> <wsa:Address> http://infod.firstrespondernetwork.com/DataSourceEntry3 </wsa:Address> </infod:DataSourceEntryReference> </infod:CreateDataSourceEntryResponse> 38

Consumer Entry Request Message Response message would be an INFOD epr, <infod:CreateConsumerEntry> <infod:WSReference> <wsa:Address> http://www.sensoralertingsystems.com/PlumeModelling </wsa:Address> </infod:WSReference> <infod:ConsumerName> Alerting System </infod:ConsumerName> <infod:ConsumerDescription> A plume modeling system which requires information on chemical sensor and weather information at the location of the sensor for plume estimation </infod:ConsumerDescription> <infod:Notification> TRUE </infod:Notification> </infod:CreateConsumerEntry> Response message would be an INFOD epr, in this case http://infod.firstrespondernetwork.com/ Consumer1 39

Property Vocabulary Instance Request Message <infod:CreatePropertyVocabularyInstance> <infod:EntryReference> <wsa:Address> http://infod.firstrespondernetwork.com/Consumer1 </wsa:Address> </infod:EntryReference> <infod:PropertyVocabularyReference> http://infod.firstrespondernetwork.com/PropertyVocab2 </infod:PropertyVocabularyReference> <infod:PropertyVocabularyInstanceBody> <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://niem.gov/niem/niem-core/2.0" > <xsd:userPropertyVocabulary> <xsd:Organization> <nc:OrganizationID>XLABS-PMC101</nc:OrganizationID> </xsd:Organization> </xsd:sensorPropertyVocabulary> </xsd:schema> </infod:PropertyVocabularyInstanceBody> </infod:CreatePropertyVocabularyInstance> Response message would be an INFOD epr, in this case http://infod.firstrespondernetwork.com/PropVocabRef7 40

Subscriber Entry Request Message <infod:CreateSubscriberEntry> <infod:SubscriberName> Alert System </infod:SubscriberName> <infod:SubscriberDescription> Subscribes for chemical sensor and weather information </infod:SubscriberDescription> </infod:CreateSubscriberEntry> Response message would be an INFOD epr, in this case http://infod.firstrespondernetwork.com/ Subscriber1 41