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] DOM?


Regarding the model, I suggest "Resource Messaging Reference Schema" (or
Reference Model).  What it really contains is the superset of all possible
Resource messaging elements, with message segment cardinality (aka like a
DOM).   I agree that we should refer to the definition of each message type
for specification of optionality.

I'll take a look at the hybrid model again before the Thursday meeting.

Thanks,

Tim 

-----Original Message-----
From: Rex Brooks [mailto:rexb@starbourne.com] 
Sent: Tuesday, August 22, 2006 12:33 AM
To: Renato Iannella; Emergency_Mgt_Msg_SC
Subject: Re: [emergency-msg] DOM?

We can discuss it Thursday, but the more we can hash it out on the 
list here, the better. I am not opposed to this, but I would like to 
hear more opinions.

Cheers,
Rex

At 1:57 PM +1000 8/22/06, Renato Iannella wrote:
>The "DOM" needs some fixing:
>
>1 - since the cardinality is defined per message type, there should 
>not be any mandatory/conditional fields
>on the generic model
>
>2 - DOM is not the correct term to use, as a DOM is an "API to 
>parsing structured information"
>Can we just call it the "Resource Messaging Model" ?
>
>3 - We had previous discussion on the 'hybrid-model" - there is not 
>that much difference now, only the schedule info
>are all group together and the response has explicit 
>accept/decline/reason elements.
>
>Comments?
>
>Cheers...  Renato Iannella
>National ICT Australia (NICTA)
>
>
>--------------------------------------------------------------------------
>This email and any attachments may be confidential. They may contain
legally
>privileged information or copyright material. You should not read, copy,
>use or disclose them without authorisation. If you are not an intended
>recipient, please contact us at once by return email and then delete both
>messages. We do not accept liability in connection with computer virus,
>data corruption, delay, interruption, unauthorised access or unauthorised
>amendment. This notice should not be removed.


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

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.3/423 - Release Date: 8/18/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.3/423 - Release Date: 8/18/2006
 



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