Re: [emergency] Groups - ICS-201-draft0.2.xsd uploaded

["CONSULTRAC" <rcarlton@consultrac.com>]

Allen,

I think that our attempting to define a "holistic" XML-based ICS 201 is a
flawed approach and beyond our scope. Perhaps we should prepare an XML-API
process spec that acknowledges the specific elements and name types
referenced in the ratified NIMS-construct, but leave the front end
formatting to the marketplace. In my view this places us where we belong; at
the "standardized data exchange protocol" level rather than the
"applications/forms development" level. The latter posture suggests certain
product biases that I do not think we want attached to the committee's work.

Rick
----- Original Message ----- 
From: "R. Allen Wyke" <emergency-tc@earthlink.net>
To: <rexb@starbourne.com>
Cc: <emergency@lists.oasis-open.org>
Sent: Thursday, April 01, 2004 11:09 AM
Subject: Re: [emergency] Groups - ICS-201-draft0.2.xsd uploaded


> You know, I have been thinking more and more about this - about how we
> are approaching it. Being that our TC, nor anyone here, gave birth to
> ICS nor the 201 form, I am a little concerned that we might be
> overstepping our bounds to consider creating an XML schema
> representation of it.
>
> Perhaps a more politically correct approach would be to defined an
> XForms (http://www.w3.org/MarkUp/Forms/) model of the form and maybe
> even suggest that implementations should use the XForms UI vocabulary
> to "draw" the actual form in a browser, in an app, on a phone, etc.?
> Something just doesn't feel right about us defining an actual XML
> schema, BUT using XML for us to describe a form....well, that may
> result in not only better work on our part, because of the power of
> XForms, but also in something that gives credit where credit is due
> (and doesn't claim credit for something that isn't ours).
>
> Anyone else have an opinion on this one way or the other? Its possible
> we can't do what we need in XForms, but it couldn't hurt to check.
>
> On Mar 13, 2004, at 9:58 AM, rexb@starbourne.com wrote:
>
> > The document ICS-201-draft0.2.xsd has been submitted by Rex Brooks
> > (rexb@starbourne.com) to the OASIS Emergency Management TC document
> > repository.
> >
> > Document Description:
> >
> >
> > Download Document:
> > http://www.oasis-open.org/apps/org/workgroup/emergency/download.php/
> > 5915/ICS-201-draft0.2.xsd
> >
> > View Document Details:
> > http://www.oasis-open.org/apps/org/workgroup/emergency/document.php?
> > document_id=5915
> >
> >
> > PLEASE NOTE:  If the above links do not work for you, your email
> > application
> > may be breaking the link into two pieces.  You may be able to copy and
> > paste
> > the entire link address into the address field of your web browser.
> >
> >
> >
> > To unsubscribe from this mailing list (and be removed from the roster
> > of the OASIS TC), go to
> > http://www.oasis-open.org/apps/org/workgroup/emergency/members/
> > leave_workgroup.php.
> >
> >
> --
> R. Allen Wyke
> Chief Technology Officer
> awyke@blue292.com
> 919.806.2440
>
>
> --
> R. Allen Wyke
> Chief Technology Officer
> awyke@blue292.com
> 919.806.2440
>
>
> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php.
>
>
>