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] Version

The EC is a property of the service interaction, not a particular service participating in the interaction.  Service policies and contracts are part of the EC if they are agreed upon by the Consumer, but it is possible a consumer policy may be used instead of a corresponding service policy if the provider and consumer so agree.

I'm not sure if I have previously spoken of the "parts" included in the service description as service properties but I do refer to properties in section when I talk about assigning values to description.  So I don't think we have a disconnect there.

See my previous response to Duane about the service description supporting multiple versions for a single service, where here there would be a temporal chain for the service description versions, with one superseding its predecessor.


On Jun 27, 2008, at 2:54 PM, michael.poulin@uk.fid-intl.com wrote:

I have problems reading last Ken's message (looks like it is not properly formatted)...

To Duane:

just to confirm I understood you right - "Versions are usually only used for externally visible property changes"

Can we consider EC as a property of Service Description ( and related Service Contracts)? In particular, can we consider communication and execution policies (i.e. EC), mentioned in the Service Description as properties? Can we consider RWE as a property?

If answers to ALL these questions are YES, I am fine. I just would like to prevent an interpretation of properties as only belong to service interface.

To me, any changes in the public Service Description are the changes required the change in the Service version, i.e. its Service Description version.

Also, I would like to avoid anything which would benefit an approach where different elements of the Service/Service Description might be versioned separately and exposed in this way to the consumer. I hope, it is too low level of details for the RA.

- Michael


Ken Laskey

MITRE Corporation, M/S H305     phone:  703-983-7934

7515 Colshire Drive                        fax:        703-983-1379

McLean VA 22102-7508


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