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


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-ra message

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

Subject: Re: [soa-rm-ra] Interaction

Title: Re: [soa-rm-ra] Interaction
First order of logic might be a good thing to start with.  You can infer a large number of things should be present in the service description based on the model.  Suss them out to the next level.

Item -> Cardinality -> Description/notes:

Policy -> 0-* -> A token or description of any policy that the service provider needs to convey to potential service consumers.  A null value is still considered a policy albeit one which imposes no special observable restrictions on the consumer.

Interaction model -> 1-* -> A token or description which relays the consumer observable patterns for interaction to the consumer.  This allows them to understand the expected behaviour on the wire.

Interaction model :: Data Model

Interaction model :: Data Model :: Structure/Syntax

Interaction model :: Data Model :: Semantics

In addition to these, you will have to start addressing things that will result from having protocol support for these.  Things like protocol version, a unique qualifying value for data elements (ei – namespaces), a metamodel, etc.


On 10/10/06 5:24 PM, "Jeffrey A. Estefan" <jeffrey.a.estefan@jpl.nasa.gov> wrote:


With respect to the metadata issue, we can probably drop the term altogether.  It is certainly abused as Cory Doctorow points out i "Metacrap: Putting the torch to seven straw-men of meta-utopia" (http://www.well.com/~doctorow/metacrap.htm).

I'd like to move the detailed discussion of the Information model elements laid out in the Interaction section currently to the Service Description section.  I have a lot more material on the message level information model and the service-level information model, but it doesn't belong in the Interaction section.  And we can drop the Metadata in Review subsection altogether.  I'm not that hung up on the term.

How would you like to proceed?  Would you like me to capture the specifics of the data-level, message-level, and service-level information models in a separate doc or Wiki for now and then let you comb through it?  I'm going to start cutting out the material in the current Interaction write-up right now.

- Jeff


Sr. Technical Evangelist - Adobe Systems, Inc.       *
Chair - OASIS SOA Reference Model Technical Committee*
Blog: http://technoracle.blogspot.com                *

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