[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] Groups - ICS-201-draft0.2.xsd uploaded
Len, Rex, Rob, and Rick: sounds like there is at least some agreement in the group about this, which is good. For anyone who has not yet had the chance to put in some thoughts, this is a great thread to do such, so please take the time. That aside, I had a question for you Rick. Well, its not really a question, but more of a desire to stimulate some additional discussion based on what you said below. Can you elaborate on "how" you would see this manifesting itself within the scope of the TC's work? Are you thinking some normative guidelines on how to do this, some kind of XML schema/language/whatever that describes how this can be down, just some kind of note that states, "well, this is how we recommend you do this?", or maybe something else. I get your concept, but need some help visualizing how that would play out - Allen On Apr 1, 2004, at 3:21 PM, CONSULTRAC wrote: > My point is it seems more prudent to develop a standardized back-end > data-exchange specification that recognizes the organizational and > elemental > structures of common ICS elements, while remaining transparent to the > subjective nature of a particular developer's front-end format. This > should > allow us to provide near-term as well as scalable support as a > standardized > data exchange mechanism but leave room for NIMS to "guide" us further > as it > evolves. That way we won't be painting ourselves into a corner, or > appearing > to produce yet another product variant that may, or may not, be NIMS > compliant in the final analysis. -- R. Allen Wyke Chair, OASIS Emergency Management TC emergency-tc@earthlink.net
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]