[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: [Summary] Creating a single XML vocabulary that is approp

• From: Len Bullard <len.bullard@u...>
• To: "Costello, Roger L." <costello@m...>, xml-dev@l...
• Date: Thu, 17 Jul 2008 13:28:48 -0500

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.

• Follow-Ups:
  • Re: [Summary] Creating a single XML vocabulary that is appropriately customized to different sub-groups within a community
    • From: "Fraser Goffin" <goffinf@g...>