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] Resource Description (4.1.1.1) and Policies - bis


Title: Re: [soa-rm-ra] Resource Description (4.1.1.1) and Policies - bis
Being I'm the culprit behind section 4.1, let me give this a shot.  

First, as Danny noted, service description was built off the RM so on first pass things stayed together.  I agree that moving it up to general description would not be a problem.

But I actually did give this some additional thought long ago and my rationale was that in a SOA ecosystem, we would make use of resources through SOA services.  While I may have a policy about an individual, that's extraneous unless that individual tries to do something with my resource using a SOA service, and at that point, it is the service that reflects the policy.  If the individual tries doing something with my resource outside of SOA, then that's out of scope for the RA.  So I kept policy with service as a simplification rather than making it more general and having the service description inherit it.

Make any sense?

Ken

P.S.  Jim: Note, you'll find me often making the distinction between business services as a way of doing business things and a SOA service as an IT mechanism to make use of business services and realize their real world effects.  Otherwise, the various meanings of service get conflated and, if that's not the way to madness, it is the way to long, frustrating meetings.

On Jan 29, 2009, at 5:27 PM, Danny Thornton wrote:

Yes I am in agreement with your suggestion since we have included resource in the RA.

Danny


-------- Original Message --------
Subject: Re: [soa-rm-ra] Resource Description (4.1.1.1) and Policies -
bis
From: James Odell <email@jamesodell.com>
Date: Thu, January 29, 2009 2:23 pm
To: Danny Thornton <danny.thornton@scalablearchitectures.com>
Cc: OASIS-RA <soa-rm-ra@lists.oasis-open.org>

Hi again Danny,

Or, did I just misunderstand: you are agree with my suggestion?  (Just read your last sentence.)  Sorry.

-Jim



------ Forwarded Message
From: James Odell <email@jamesodell.com>
Date: Thu, 29 Jan 2009 17:20:48 -0500
To: Danny Thornton <danny.thornton@scalablearchitectures.com>
Cc: OASIS-RA <soa-rm-ra@lists.oasis-open.org>
Conversation: [soa-rm-ra] Resource Description (4.1.1.1) and Policies
Subject: Re: [soa-rm-ra] Resource Description (4.1.1.1) and Policies

Hi Danny,

In this case, I do not understand why Resource Description is in the spec.  I assume it is to provide the general Description class from which other more specialized classes can be derived (e.g.Service Description, Participant Description, and so on).  By having Policy & Contract at a more general, makes it available to the subclasses?  Does that make sense?  Or, am I a confused newbie, still.  :-)

-Jim



On 1/29/09 5:09 PM, "Danny Thornton" indited:

Figure 21 or 22, Service Description, in the OASIS SOA RA is expanding on Figure 9, Service Description, in the OASIS SOA RM.

OASIS SOA RM PDF Link: http://www.oasis-open.org/committees/download.php/19679/soa-rm-cs.pdf

The focal point of the RM is Service and thus the equivalent association in the RA to Service Description.  

Since Service Description is a Description, relating Policies and Contracts to the general Description would still be equivalent.   This update makes sense to me.

Danny


-------- Original Message --------
Subject: [soa-rm-ra] Resource Description (4.1.1.1) and Policies
From: James Odell <email@jamesodell.com>
Date: Thu, January 29, 2009 1:28 pm
To: OASIS-RA <soa-rm-ra@lists.oasis-open.org>

 Resource Description (4.1.1.1) and Policies   Hi all,
 
 The Resource Description in 4.1.1.1 is very important, IMO — mainly because most of my SOA systems are really Resource Oriented.  So, I congratulate the team for inserting this.  This is great.
 
 My issue is this: Why is the Policy & Contract class under the Service Description and not the Resource Description?  When the consumers and providers negotiate at the resource level, Policies & Contracts are very important concepts in that negotiation.  In other words, whether I am negotiating for a service or an asset, contracts and policies are part of the discussion.  Therefore, my question is: is there any reason why Policies & Contracts cannot be moved from the Service Description and placed at a more general level: the Resource Description?
 
 Certainly, this will only need 5 minutes of discussion.  ;-)
 
 
 Best regards,
 
 Jim   


------ End of Forwarded Message
<bottom.letterhead>

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