Re: [soa-rm-ra] Disambiguating Action (Part I)

I could try to work this but I am not yet ready to relate a UDDI entry and resource. �I am wrestling with interpreting the UDDI spec for another project, and things like a business entity (or businessEntity) have too many inconsistent references to figure out what they are within UDDI, let alone how these relate to the RA.

I believe we can discuss what registries need to do in the context of the RA and let UDDI folks work the tModels. �As noted earlier, I'm more concerned with easy understanding by folks who see WSDL as end all and be all.

On May 26, 2008, at 6:01 PM, michael.poulin@uk.fid-intl.com wrote:

According to our definition (lifted from W3C) anything with an ID is a resource.

Since we can have a registry of service interfaces (e.g., UDDI) where each record has its ID, are we saying that a service interface is the resource of the service? Is a skin or a face exist as a resource of the body? I feel a bit strange now...� :-(

Are we in the position of making any changes?

We cannot talk about an abstract resource. In English, a resource assumes an object which this resource relates to as a resource. Right?�

A service may be a resource to a consumer; something, which may be accessible, may be a resource to service...

Am I lost somewhere? (I have to think faster about Ken's lists of services and lists of resources, I guess)

- Michael

-----------------------------------------------------------------------------

Ken Laskey

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

7515 Colshire Drive�� fax:�� 703-983-1379

McLean VA 22102-7508

soa-rm-ra message