RE: [emergency-msg] Brief note

[Rex Brooks <rexb@starbourne.com>]

Thanks, Tim,

This table is useful. It is good to see the 
overall set of messages we have at a glance and 
also shows that the notion I had of overall 
categories may be useful as regards grouping per 
the DE DistributionType. My thought is still just 
a thought. It is more a case of handiness in the 
data dictionary than for schema or DOM purposes. 
I just want it to be easy to get to the message 
types, because, as with the Oct. f2f, I suspect a 
great deal of our work is likely to be in the 
nature of ironing out the wrinkles of those 
specific message types to make sure we understand 
how they fulfill the requirements.

It does help.

Ciao,
Rex

At 2:40 PM -0500 1/31/06, Tim Grapes wrote:
>Rex and all,
>
>On the one extreme we have the complete reference schema that addresses all
>16 required Resource Messages.  On the other we have the idea of addressing
>each individually, and Rex is thinking about something in between.  I tend
>to believe we need to end up with an instance for each specific resource
>message, but this is a good discussion to have.
>
>The attached one-pager may help as a reference to further discuss this.  We
>used a concept we called "RMContentType" in our original DOM which specified
>the "type" of resource message being utilized, and mapped that concept to DE
>Distribution types (we pulled the concept out for political reasons to for
>the submission - can explain that later if needed).
>
>At any rate, this is an easy one-pager to use as a reference if it helps...
>
>Tim
>
>-----Original Message-----
>From: Rex Brooks [mailto:rexb@starbourne.com]
>Sent: Tuesday, January 31, 2006 1:32 PM
>To: emergency-msg@lists.oasis-open.org
>Subject: [emergency-msg] Brief note
>
>Hi Again, Folks,
>
>I naturally neglected my own issue, such as it is. I wanted to
>suggest we give some thought to making a couple of large categories
>of RM, specifically Requests and Responses. It might make it somewhat
>easier to find specfic requests and responses rather than having each
>one stand on its own, or perhaps having one of each for every
>specific resource message type, especially in the data dictionary.
>Let me make it clear that this is just a thought that I haven't
>followed through with any kind of test, but I suspect it just might
>make our job a tad easier. I could easily be wrong, but I think this
>may have been something along the lines of what Art was trying to
>suggest at our last meeting.
>
>Regards,
>Rex
>--
>Rex Brooks
>President, CEO
>Starbourne Communications Design
>GeoAddress: 1361-A Addison
>Berkeley, CA 94702
>Tel: 510-849-2309
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.375 / Virus Database: 267.14.23/243 - Release Date: 1/27/2006
>
>
>--
>No virus found in this outgoing message.
>Checked by AVG Free Edition.
>Version: 7.1.375 / Virus Database: 267.14.23/243 - Release Date: 1/27/2006
>
>
>
>
>Attachment converted: Macintosh HD:RMmessages&Distr.doc (WDBN/«IC») (000E375B)


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