Re: [soa-rm] Architectural Scope of Reference Model

[Rex Brooks <rexb@starbourne.com>]

That would work. Vague in this sense means non-specific as to the 
service, which is, I believe the level of abstraction we are aiming 
to maintain, yes?

Ciao,
Rex

At 8:41 PM -0700 4/21/05, Duane Nickull wrote:
>Rex Brooks wrote:
>
>>I think one can have metadata about a contract or contracts as a 
>>class, but I don't think contracts are metadata in themselves.
>
>I had originally shared this view. That is why the contract was 
>separate from the "service Description" in our posiion paper.  The 
>contract offer is perhaps a bit more vague and could be part of the 
>metadata.
>
>Perhaps the Lawyer amongst us can give us his PoV (Jamie????)
>
>Duane
>
>--
>***********
>Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
>Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
>Adobe Enterprise Developer Resources  - 
>http://www.adobe.com/enterprise/developer/main.html
>***********


-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-849-2309