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

["Tom Merkle" <TMerkle@capwin.org>]

I can ask around DHS and NIJ for clarification on their views and plans
for the current ICS forms with respect to XML. My initial reluctance
stems for the same "ownership and turf issues" that Allen mentioned. The
only way I would recommend TC involvement is by having close
coordination with the "owner" of the forms and assurances that the TC
would not be used as a weapon in any turf battle. I certainly understand
the need to review this area, but only as a fact finding group at this
time. Any other approach may produce unexpected results. 


Regards,
 
Tom Merkle
 
CapWIN:        www.capwin.org 
Phone:        (301) 614-3720
Cell Phone:   (240) 375-1966
Fax:          (301) 614-0581
e-mail:        tmerkle@capwin.org
 
CapWIN
6305 Ivy Lane Suite 300
Capital Office Park
Greenbelt, MD 20770

-----Original Message-----
From: Rex Brooks [mailto:rexb@starbourne.com] 
Sent: Thursday, April 01, 2004 4:11 PM
To: R. Allen Wyke; rexb@starbourne.com
Cc: emergency@lists.oasis-open.org
Subject: Re: [emergency] Groups - ICS-201-draft0.2.xsd uploaded

We can do that in XForms, but before we do anything, we need to find out
if DHS thinks we should, and in fact, having worked on it, and having
looked through the NIMS-90 document, I'm not at all sure we should take
on this work unless asked. But as for the XSD v. XForms issue, I would
recommend compatible versions of both within the same spec for a couple
of reasons, mainly that it is almost guaranteed that there will be a
need to dynamically update the information using a telephonic and/or
wireless connection so conversion/translation into VXML and/or WML seems
inevitable and ought to be included in the overall plan from the outset.
That overall plan is for DHS to set forth, so I think we need to get in
touch with Steve Cooper or someone at DHS on this. We have both a
history with them, and a need for an ongoing connection/liaison with
them. The question is what is the most appropriate approach to make
contact and who should do this. 
That's both a personal contact and/or organizational jurisdiction
question. I don't have an answer for that, but I suggest asking Jamie
Tuesday, and also seeing if either Tom Merkle or Gary Ham can suggest a
good approach.

Ciao,
Rex

At 2:09 PM -0500 4/1/04, R. Allen Wyke wrote:
>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/59
>>15/ICS-201-draft0.2.xsd
>>
>>View Document Details:
>>http://www.oasis-open.org/apps/org/workgroup/emergency/document.php?do
>>cument_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_w
orkgroup.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


--
Rex Brooks
GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth
W3Address: http://www.starbourne.com
Email: rexb@starbourne.com
Tel: 510-849-2309
Fax: By Request

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_wor
kgroup.php.