[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency] Tactical Situation Object
I've provided a couple of HTML reports in the ZIP that help understand their data model. Plus I provided comments on specific elements - see text below - and their data model - which overall - IMHO is somewhat "Fisher Price" XML. I provide an Excel spreadsheet of their dictionary.
Also - I used the renamer tool to fix their short uppercase names into new camel case names that are fully NIEM term reference compliant - and build a dictionary of those new terms.
Then I rewrote their existing schema using XSD export - and this actually wrote their XSD back out better than their original (IMHO!) - a scary "first" for CAM - I've not seen it write schema better than humans before!
Overall I see that XML maturity wise the OASIS team here just is way better than CEN!?!? But we would say that wouldn't we?
-------- Original Message --------
Subject: [emergency] Tactical Situation Object
From: Rex Brooks <rexb@starbourne.com>
Date: Tue, April 06, 2010 9:20 am
To: emergency TC lists Oasis <emergency@lists.oasis-open.org>,
emergency-msg@lists.oasis-open.org, EM GIS SC
<emergency-gis@lists.oasis-open.org>,
"emergency-if@lists.oasis-open.org" <emergency-if@lists.oasis-open.org>,
"emergency-rim@lists.oasis-open.org"
<emergency-rim@lists.oasis-open.org>
Hi Everyone,
I tried to send the main presentation on the Tactical Situation Object
(TSO) yesterday, but it was too large for the OASIS Server's limit, so I
am sending out the url for the presentation which I hope you will all
take the time to look at because i think we must take this effort into
account, and use it as best we can.
TSO Org: http://www.tacticalsituationobject.org/
TSO Presentation:
http://www.tacticalsituationobject.org/docs/Shared-Situation-Awareness-the%20TSO-15Dec2008.pdf
Since it specifies aspects of interoperability with CAP and used
EDXL-DE, I believe it may also be adaptable to some of the gaps in our
current set of EDXL specifications.
I will be incorporating it into the NCOIC All Hazards Alert and Warning
(AHAW) Capabilities Pattern, and it will also be the subject of one of
two specific AHAW Technical Patterns.
Cheers,
Rex
--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]