OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [emergency-msg] Meeting Next Week?

Thanks Gary, Patti,

Sounds like we're slogging through it as best we can. We should be 
able to make a bit more progress by next Thursday and hopefully the 
home stretch will be in sight by then.


At 1:01 PM -0500 1/3/07, Ham, Gary A wrote:
>Regarding the schema.
>I built the reference schema from the matrix and it was designed to
>remain faithful to the matrix we approved in the meeting.  The big
>change was to abstract out as types the elements that did not change
>across the matrix. I was actually planning to wait on the individual
>message schemas until the matrix is complete.
>(So I guess that I agree with you!)
>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: Aymond, Patti [mailto:Patti.Aymond@iem.com]
>Sent: Wednesday, January 03, 2007 12:22 PM
>To: Rex Brooks; emergency-msg@lists.oasis-open.org
>Subject: RE: [emergency-msg] Meeting Next Week?
>I'm available. I spent some time last week trying to synch the matrix
>with the schema, but it's slow going. I guess that's why I like to do
>the schema last.
>Patti Iles Aymond, PhD
>Senior Scientist, Research & Development Innovative Emergency
>Management, Inc.
>Managing Risk in a Complex World
>8555 United Plaza Blvd.   Suite 100
>Baton Rouge, LA 70809
>(225) 952-8228 (phone)
>(225) 952-8122 (fax)
>-----Original Message-----
>From: Rex Brooks [mailto:rexb@starbourne.com]
>Sent: Wednesday, January 03, 2007 9:43 AM
>To: emergency-msg@lists.oasis-open.org
>Subject: [emergency-msg] Meeting Next Week?
>Hi Folks,
>We should have a meeting next week to get back in synch after the
>holidays. The TC , the IF SC and the Adoption SC are all meeting next
>Tuesday morning, so it would be crowded to squeeze our meeting into that
>set of timeslots, plus we need to include Karen and Renato, if he can
>manage it.
>So I suggest scheduling our next meeting for Thursday Jan 11 at 4:00 to
>5:00 p.m. EST.
>If that doesn't work for you, please pipe up here and we can discuss it.
>If we don't hear from anyone with conflicts for this, I would appreciate
>it if Tim could schedule it for us.
>Also, I would appreciate it if anyone has a recollection of any other
>message elements where the ContactInformation package needs to be added
>other than the top level Resource Message unit for each message type and
>in the ResponsibleParty in OwnershipInformation.
>In the top level I used the form Contact:ContactInformation but I am
>wondering if it should just be ContactInformation: char since we don't
>have a message element: Contact?
>I hesitated to call it ContactRole, (the previous name for the
>relationship between the top level unit and the Contact Information
>I did that to avoid repeating an element from further downstream in the
>element chain.
>We may need a new label for the person sending the message, or
>responsible for sending the message (like MessageContact or
>MessageContactRole) to avoid having a term that is used in its own
>definition which would have if we used either
>ContactInformation:ContactInformation or ContactRole:ContactInformation
>(in which Contact Role is a defining characteristic with a specific list
>of types).
>   I have attached my update of the main Element Reference Model so you
>can see what I have done. I didn't want to update all of the rest of the
>models until I am sure that this much is correctly aligned.
>I would also appreciate any discussion about whether we should consider
>adding the ContactInformation package to the ResponseInformation unit.
>My question is to those with more practical on-the-ground experience
>than I have as to whether or not a person other that the person sending
>a response type message would be the contact for that information. I
>certainly don't want to add wrinkles where we could get out of synch
>between the data dictionary, schema and models on the basis of my own
>Rex Brooks
>President, CEO
>Starbourne Communications Design
>GeoAddress: 1361-A Addison
>Berkeley, CA 94702
>Tel: 510-849-2309

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-849-2309

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]