ontolog-forum
[Top] [All Lists]

Re: [ontolog-forum] Legacy systems

To: "[ontolog-forum] " <ontolog-forum@xxxxxxxxxxxxxxxx>
From: Rex Brooks <rexb@xxxxxxxxxxxxxx>
Date: Mon, 19 Nov 2007 05:50:37 -0800
Message-id: <a0624080fc3673c32b170@[192.168.15.2]>
Hi Paola, Sean,    (01)

We ran into exactly this problem with the first 
EDXL specification, EDXL-DE, the Distribution 
Element, where the different kinds of "events" 
initially led us to attempt what you are 
describing, with the same result, and before we 
came up with "a" solution, I actually wrote a 
small "event ontology" in Protégé to illustrate 
how this would, in theory, work and then put it 
into practice in a few example scenarios.    (02)

Later our Semantic Interoperability Architecture 
Pilot group ( formerly referred to as SIA-Pilot6 
& separate from the OASIS Emergency Management 
Technical Committee) settled on a data set from 
EPA incident management of a train derailment 
with a chlorine tank car rupture and release in 
Graniteville, South Carolina in January 2005 to 
use as a basis of an alerting demonstration.    (03)

In the EM TC we eventually arrived at a solution 
we named a "ValueListType." What this refers to 
is the citation of a keyword that is associated 
with a (namespaced) list of string values 
(names/labels) that is publicly published and 
maintained by some organization or entity for a 
specific category of information, such as 
sender/recipient types or roles, event types, 
command structure position titles, etc. This 
mechanism is now used consistently in EDXL 
specifications.    (04)

Obviously, we need the various global 
jurisdictions, local, state, provincial, 
national, international to publish and maintain 
these lists, and, in the US we are working with 
the IPAWS effort for this. IPAWS stands for 
"Integrated Public Alert and Warning System."    (05)

I/we suggest that these lists be published using 
the eXtended MetaData Registry (XMDR) which is 
based on ISO 11179. XMDR provides freely 
available software for this purpose.    (06)

IPAWS is being architected by Sandia National 
Labs by David Ellis who has worked with both the 
EM TC and the SIA-Pilot6 group, that was recently 
renamed "Integrated Response Services Consortium 
(IRSC). IPAWS will be handling security for 
trusted networks.    (07)

We are working on new demonstrations using 
EDXL-DE, CAP, and the newer EDXL specifications 
EDXL-HAVE (Hospital AVailability Exchange now in 
its second 60-Day Public Review) and EDXL-RM 
(Resource Messaging, which I'm editing and is 
about two months from being ready for its second 
60-Day PR).    (08)

IRSC welcomes any interested parties to explore 
joining our effort. Just send me an email and I 
will add you to our email list and you will be 
notified about upcoming meetings as we work on 
these demonstrations and on organizing our 
Consortium.    (09)

Our EM TC EDXL-RIM effort (Reference Information 
Model which will be expressed in RDFS and OWL as 
well as XSD) will specifically gather up such 
mechanisms as the ValueListType, our use of OASIS 
CIQ standard for "Contact Information" and the 
geo-oasis profile of GML we are working on with 
the OpenGeospatial Consortium.    (010)

In addition, I am working with a fellow 
participant from the OASIS SOA Reference Model 
TC's Reference Architecture Subcommittee (OASIS 
SOA-RM-RA SC) (in which David Ellis has also 
participated) to implement a federated two-domain 
set of ebXML-UDDI Web Service Registries within 
the IRSC effort to demonstrate an example OASIS 
SOA-RM-RA . These domains are Emergency 
Management and Health Informatics.    (011)

Cheers,
Rex    (012)

At 6:53 PM +0700 11/19/07, paola.dimaio@xxxxxxxxx wrote:
>Sean
>
>  I would be interested in capturing such an interesting scenario
>for research purposes - and evaluate feasibility of mapping the
>different legacy system you are referring to identify  where
>interoperability may be possible, and where not
>
>Ultimately, it is like translating between different languages and
>cultures, this today is done routinely in many other domains, using
>different frameworks
>
>Do you have some documentation/reference that I can look up?
>
>PDM
>
>
>
>
>
>
>On Nov 19, 2007 5:47 PM, Barker, Sean (UK) <Sean.Barker@xxxxxxxxxxxxxx> wrote:
>>
>>
>>  Rex,
>>
>>      I tried to get a similar approach going in the EU project OASIS (no
>  > relation) for a tactical situation object for emergency response, but
>>  although we agreed on using a sort-of-taxonomy, an ontology was a step to
>>  far.
>>
>>      I say sort-of-taxonomy. It was clear that with some twenty different
>>  sorts of emergency responder to inform, and with different breakdowns of
>>  responsibility between the member countries (there are some 20+ to
>>  consider), that no classification single system would be used consistently
>>  and even basic categories vary between service, location and country.
>>  Consequently, in several areas, particularly that for identifying the type
>>  of incident, we used an "anti-taxonomy", which identified multiple classes
>>  of classification factors and provided a classification system for each
>>  factor, but which did not identify an overall class. Consequently, there is
>>  no classification "major-warehouse-fire", but separate classifications for
>>  scale, site, and incident type (fire/flood/earthquake...).
>>
>>      One of the problems is that each responder has their own "legacy"
>>  classification system, which cannot be easily replaced, since it is built
>>  into the procedures and culture of the responding organization. Rather like
>>  the Edison problem, the best we can do is pipe emergency situation messages
>>  to each responder, and let them convert it into something that they can
>>  consume. The critical problem is to ensure that the conversion process does
>>  not lose too much of the original - in the case of emergency situation
>>  messages, misunderstand does not create a significant risk to the lives or
>>  health of the responders.
>>
>>  Sean Barker
>>  Bristol, UK
>>
>>  This mail is publicly posted to a distribution list as part of a process of
>>  public discussion, any automatically generated statements to the contrary
>>  non-withstanding. It is the opinion of the author, and does not represent an
>>  official company view.
>>  ********************************************************************
>>   This email and any attachments are confidential to the intended
>>   recipient and may also be privileged. If you are not the intended
>>   recipient please delete it from your system and notify the sender.
>>   You should not copy it or use it for any purpose nor disclose or
>>   distribute its contents to any other person.
>>   ********************************************************************
>>
>>
>>
>>  _________________________________________________________________
>>  Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
>>  Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
>>  Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
>>  Shared Files: http://ontolog.cim3.net/file/
>>  Community Wiki: http://ontolog.cim3.net/wiki/
>>  To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
>>
>>
>>
>
>
>
>--
>Paola Di Maio
>School of IT
>www.mfu.ac.th
>*********************************************
>
>_________________________________________________________________
>Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/ 
>Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/ 
>Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
>Shared Files: http://ontolog.cim3.net/file/
>Community Wiki: http://ontolog.cim3.net/wiki/
>To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
>    (013)


-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670    (014)

_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx    (015)

<Prev in Thread] Current Thread [Next in Thread>