RE: [soa-rm-ra] Questions on action model

["Poulin, Michael" <Michael.Poulin@uk.fid-intl.com>]

Title: RE: [soa-rm-ra] Questions on action model

Danny,
I take your comments as an agreement that a service descriptor has to be business domain specific and the same service may be described differently in different registry/repositories. Plus, this actually outlines that the definition of the service execution context has to be a part of the service descriptor.

- Michael

Important: Fidelity Investments International (Reg. No.1448245), Fidelity Investment Services Limited (Reg. No. 2016555), Fidelity Pensions Management (Reg. No. 2015142) and Financial Administration Services Limited (Reg. No. 1629709, a Fidelity Group company) are all registered in England and Wales, are authorised and regulated in the UK by the Financial Services Authority and have their registered offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732 361144. Fidelity only gives information on products and does not give investment advice to private clients based on individual circumstances. Any comments or statements made are not necessarily those of Fidelity. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any computer. All e-mails sent from or to Fidelity may be subject to our monitoring procedures. Direct link to Fidelity's website - http://www.fidelity-international.com/world/index.html 

-----Original Message-----
From: Danny Thornton [mailto:danny_thornton2@yahoo.com]
Sent: 15 October 2007 21:45
To: Poulin, Michael; Duane Nickull
Cc: soa-rm-ra@lists.oasis-open.org
Subject: RE: [soa-rm-ra] Questions on action model

Michael,

The question to ask is what parts of the service
description could be described in different ways in
different domains or contexts?  For example, a
provider may provide a service for a business domain
and a scientific domain.  The provider could describe
functionality different and have different contracts
associated with each domain.  Both domains could be
served by different registry/repositories.  The number
of counter examples for dictating one service
description per service are infinite.

Danny

--- "Poulin, Michael" <Michael.Poulin@uk.fid-intl.com>
wrote:

> Duane wrote:  "In an ecosystem of services, there
> could potentially be many
> service descriptions for a service.  The service
> description a consumer uses
> may be dependent on the entity the consumer
> interacts with when they use the
> service, or it could be dependent on the particular
> context the service
> description is provided.  Because of unforeseen
> possibilities for a service
> to have multiple service descriptions, I do not
> think the OASIS SOA RA can
> qualify one service to one service description."
> 
> I have a lot of concerns about underlined
> statements.
> 
> 1) Service description gets used as the service
> definition now. I agree that
> in an ecosystem not all information about the
> service is in the Service
> Descriptor. However, in this case, I prefer to
> recognise that I have
> different 'domains' in the ecosystem of services
> (voice, signs, UDDI, etc.)
> where the Service Description is the single unique
> one.
> 
> 2) To me,  the "service description a consumer uses
> may be dependent on the
> entity the consumer interacts with when they use the
> service" looks much
> more like an execution context and related Service
> Contract than a service
> description. Again, "be dependent on the particular
> context the service
> description is provided" is either services
> ecosystem domain specific
> Description or the EC and Service Contract.
> 
> 3) as I mentioned before, SOA RM states that EC is
> not a context of service
> interaction only ( though in many places it says so
> ) but also the context
> of service execution per se. If we allow "a service
> to have multiple service
> descriptions" (w/o defining concrete conditions
> where it is possible), we
> have to clearly distinguish it from a service to
> have multiple service
> descriptions in multiple service execution contexts
> - interaction and
> execution ones.
> 
> 4) I, personally, dislike the idea of "a service to
> have multiple service
> descriptions", at least, in the same Service
> Description Repository. Though
> this is a lower level technical implementation
> detail,  it is VERY important
> for practical use of SOA and quoted statement above
> can easily screw it,
> which I hate.
> 
> - Michael
> 
> Important: Fidelity Investments International (Reg.
> No.1448245), Fidelity
> Investment Services Limited (Reg. No. 2016555),
> Fidelity Pensions Management
> (Reg. No. 2015142) and Financial Administration
> Services Limited (Reg. No.
> 1629709, a Fidelity Group company) are all
> registered in England and Wales,
> are authorised and regulated in the UK by the
> Financial Services Authority
> and have their registered offices at Oakhill House,
> 130 Tonbridge Road,
> Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732
> 361144. Fidelity only
> gives information on products and does not give
> investment advice to private
> clients based on individual circumstances. Any
> comments or statements made
> are not necessarily those of Fidelity. The
> information transmitted is
> intended only for the person or entity to which it
> is addressed and may
> contain confidential and/or privileged material. If
> you received this in
> error, please contact the sender and delete the
> material from any computer.
> All e-mails sent from or to Fidelity may be subject
> to our monitoring
> procedures. Direct link to Fidelity's website -
>
http://www.fidelity-international.com/world/index.html
>
>
>
>
>
>
>
>   _____ 
>
> From: Duane Nickull [mailto:dnickull@adobe.com]
> Sent: 12 October 2007 16:49
> To: Ken Laskey; Scott Came
> Cc: soa-rm-ra@lists.oasis-open.org
> Subject: Re: [soa-rm-ra] Questions on action model
>
>
> Concur.  Look at the cardinality of WSDL. Not
> everything is mandatory
> either.  On a purely logical level, consumers can
> use only that which they
> require.  It is unlikley that any one service
> description artifact would in
> fact contain *all* the information required.
>
> At least some info is known via alternative
> mechanisms (voice, signs, UDDI,
> etc.)
>
> Duane
>
>
> On 10/11/07 6:22 PM, "Ken Laskey"
> <klaskey@mitre.org> wrote:
>
>
>
> The RM says
>
> The service description represents the information
> needed in order to use a
> service. In most cases, there is no one "right"
> description but rather the
> elements of description required depend on the
> context and the needs of the
> parties using the associated entity.  
>
> Thus, the implication is there may be overlapping
> descriptions relevant to
> different contexts.
>
> Ken
>
> On Oct 11, 2007, at 8:08 PM, Scott Came wrote:
>
>
>
> Danny:
> I don't personally have a strong feeling one way or
> the other on this
> issue.  I did sense the "one description" position
> as the subcommittee
> consensus, however...mostly from reading the RA 0.2
> draft.
> Thanks.
> --Scott
> -----Original Message-----
> From: Danny Thornton
> [mailto:danny_thornton2@yahoo.com]
> <mailto:danny_thornton2@yahoo.com]> 
> Sent: Thursday, October 11, 2007 3:55 PM
> To: Scott Came; soa-rm-ra@lists.oasis-open.org
> Subject: RE: [soa-rm-ra] Questions on action model
>
> Scott,
>
> Thank you for the summarization.  The only statement
> I
> have an exception with is 3, A service has one
> description.
>
> In an ecosystem of services, there could potentially
> be many service descriptions for a service.  The
> service description a consumer uses may be dependent
> on the entity the consumer interacts with when they
> use the service, or it could be dependent on the
> particular context the service description is
> provided.  Because of unforeseen possibilities for a
> service to have multiple service descriptions, I do
> not think the OASIS SOA RA can qualify one service
> to
> one service description.
>
> Danny
>
> --- Scott Came <scott.came@search.org> wrote:
>
> 
>
>
> Subcommittee:
>
>
>
> I'd like to take attempt a summarization of this
> thread.  Note the word
>
=== message truncated ===

      ____________________________________________________________________________________
Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, and more!
http://tv.yahoo.com/collections/3658