RE: [emergency-msg] Groups - EM-Msg SC Meeting added

["Ham, Gary A" <hamg@BATTELLE.ORG>]

 Actually, I prefer to think of them as "graphic message structure
diagrams" as opposed to DOMs.  I.e., the schema is paramount.  The "DOM"
is just an illustration for clarity. None-the-less a very useful
illustration for clarity.


Gary A. Ham 
Senior Research Scientist
Battelle Memorial Institute
540-288-5611 (office)
703-869-6241 (cell)
"You would be surprised what you can accomplish when you do not care who
gets the credit." - Harry S. Truman

-----Original Message-----
From: Tim Grapes [mailto:tgrapes@evotecinc.com] 
Sent: Friday, November 17, 2006 3:57 PM
To: rexb@starbourne.com
Cc: emergency-msg@lists.oasis-open.org
Subject: RE: [emergency-msg] Groups - EM-Msg SC Meeting added

Maybe I missed something...  I didn't think DOM development for each
message was off the table; just that it would be challenging to get them
done before the FtoF.  I think it's critical that the DOMs be developed.

Thanks,
Tim


-----Original Message-----
From: rexb@starbourne.com [mailto:rexb@starbourne.com]
Sent: Friday, November 17, 2006 12:51 PM
To: emergency-msg@lists.oasis-open.org
Subject: [emergency-msg] Groups - EM-Msg SC Meeting added

I highlighted being REALISTIC about where we will be with the document
going into the F2F because I DON'T think, given recent activities, that
we will have ANY DOMs and perhaps no schemas. Without DOMs, relying
solely on schemas, I think we can expect a wide variance in
applications, which, given the number of message types, is asking for
problems. If everyone builds their own, or lets them be determined as de
facto outcomes of unstructured applications built solely on schemas and
the data dictionary, I think we court having a mess. I intensely dislike
DOM-based development, but they do enforce common structures, and that
means ongoing INTEROPERABILITY in fact, versus theory.

 -- Rex Brooks*


EM-Msg SC Meeting has been added by Rex Brooks*

Date:  Monday, 20 November 2006
Time:  04:00pm - 05:00pm ET

Event Description:
Dial-in Number:  1-641-696-6699  (Iowa)  	
Access Code 	 345450

Agenda:
1. Approve Minutes of previous meeting.
2. Review latest draft of EDXL_RM.
3. Determine goals for F2F wrt EDXL_RM, including REALISTIC asessment of
where we will be going in.
4. Mke a list of issues to be addressed as Karen noted.
5. Focus activities that leverage group participation.

Minutes:


View event details:
http://www.oasis-open.org/apps/org/workgroup/emergency-msg/event.php?eve
nt_i
d=12988

PLEASE NOTE:  If the above link does 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.


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.6/536 - Release Date:
11/16/2006
 
  

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.6/536 - Release Date:
11/16/2006