OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-if message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Groups - DE_RoutingWithReasoning_Example_Components.zip (DE_RoutingWithReasoning_Example_Components.zip) uploaded


This zip file represents some progress in creating an example which begins
to illustrate how the DE enables "smart" routing of messages.  The key is
the importance of the DE value list to reference an externally-managed
ontology of terms. The goal is to show that emergency messages can be
routed based on role to ensure that the messages get to all those who need
them. We can discuss this example at our upcoming meeting of the IF
subcommittee. Thanks.

 -- Jeff Waters

The document named DE_RoutingWithReasoning_Example_Components.zip
(DE_RoutingWithReasoning_Example_Components.zip) has been submitted by Jeff
Waters to the EM Infrastructure Framework SC document repository.

Document Description:
The attached zip file contains the basic files needed to understand a
simple example of utilizing Hermit and Camel and the DE to perform
"smart" routing of messages where an ontology is used to infer
the recipients
based on recipientRole specified in the DE.  The files are:
(1) MyMessageRouter.java is a toy program which shows how to route a DE
Message based on a recipientRole where an ontology is used to infer the
recipients that satisfy that role. 
(2) DE_WithHazMatRole.xml is a sample DE message where the first value of
the recipientRole is utilized for routing, namely
"hazMatResponderForIncidentABC".
(3) DE2_Example_SR1_Manchester.owl and DE2_Example_SR1.owl are the
same simple ontology (the former in a format that is a little easier for a
human to read).  The ontology identifies two individuals, Joe and Marie.
Joe has a role (hazMatSupportForIncident) for an OASISIncident ABC, whereas
Marie has a role (hazMatSupportForEvent) for a TSOEvent DEF.  Both the
TSOEvent and the OASISIncident are assumed for this example to be the same
event, e.g. a hazmat spill.  The goal is to show that if a message is
routed to all those who have the OASIS role, that the messages will also
get to those who have the TSO role because the ontology says they
are equivalent roles. (NOTE: These particular OASIS and TSO roles 
are fictitious.)
(4) To actually run this example, you need to install Maven and then
put (install) HermiT.jar in your local Maven repository (since it doesn't
seem to be directly accessible from a URL) and setup your Camel context
to reference the bean for routing.


View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=42621

Download Document:  
http://www.oasis-open.org/committees/download.php/42621/DE_RoutingWithReasoning_Example_Components.zip


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]