OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

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

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

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?


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 
>Perhaps the Lawyer amongst us can give us his PoV (Jamie????)
>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  - 

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

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