Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] [Summary] Creating a single XML vocabulary that is appropriately customized to different sub-groups within a community

From: Len Bullard <len.bullard@---.--->
To: "Costello, Roger L." <costello@-----.--->, xml-dev@-----.---.---
Date: 7/17/2008 6:29:00 PM
Let me see if I can make this more tangible with a real world messaging
community.   In public safety, there is the concept of an incident.  Seems
well-bounded?  Is it?

How many community types are there?  Just to start:

O Advisory
O Aviation
O Fire
O Police
O EMA
O EMS
O Geophysical
O Hazmat
O Health
O Infrastructure
O Meteorological
O Security
O Structural
O Terrorism
O Transportation

Do they all share a single vocabulary for incidents?  Do they share an
incident class with subtypes?  Do they use different incidents which are
subtypes in name only?  Do they use a message type with generic boxes for
information which human analysts sift with automated tools and out of which
they sift it into just a few reports or a dashboard?

HINT:  The answer is yes to all of the above.  It varies by procurement.

By the way, sometimes they say 'event' for 'incident' and sometimes they say
'incident' for 'event'.  The difference is not content but the way time is
used as a qualifier.  What should one abstract away to make that converge?

len                                                                  
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent