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

Although contract != contract metadata, a contract will consist of various
sections of structured and unstructured text/data: certain structured
contractual *terms* (order size, deliver by, unit price, etc...) can be
considered also as metadata, but other parts of the contract (the legal
blurb, conditions, etc.) would not, unless they too can be modelled as
structured data...The key question is not whether something in the contract
is metadata or not; but rather what extent of metadata do we want in the
reference model?


-----Original Message-----
From: Duane Nickull [mailto:dnickull@adobe.com] 
Sent: 25 April 2005 16:32
To: Breininger, Kathryn R
Cc: Rex Brooks; Francis McCabe; Gregory A. Kohring; Ken Laskey;
Subject: Re: [soa-rm] Architectural Scope of Reference Model


Thank you - this clarification is very useful.  May I impose upon you to
take a look at the glossary definitions and add some comments if we should
make the changes?

I think this also justifies and answers one outstanding question that we had
on our position paper regarding whether or not the contract is part of the
metadata.  It appears that it is logically separate given this definition.
The same question exists for data model.  Is a data model conceptually part
of a larger set of metadata that includes things like semantics, policies
(including security policies), etc.?


Breininger, Kathryn R wrote:

>From work I have done in the realm of metadata, classification, 
>categorization, etc., The purpose of metadata is to provide a 
>description or information about something; in this case it is not the 
>contract, and not the offer.  There may be metadata that describes the 
>offer; there may also be a separate set of metadata that describes the 
>contract.  In both cases, metadata is still providing information about 
>the data (definition of metadata = data *about* data) e.g., contract, 
>offer, service, schema, brownie recipe, etc. etc. are all things that 
>may be described by metadata.
>Kathryn Breininger
>Boeing Library Services
>425-965-0182 phone
>-----Original Message-----
>From: Rex Brooks [mailto:rexb@starbourne.com]
>Sent: Thursday, April 21, 2005 9:46 PM
>To: Duane Nickull; Rex Brooks
>Cc: Breininger, Kathryn R; Francis McCabe; Gregory A. Kohring; Ken 
>Laskey; soa-rm@lists.oasis-open.org
>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  - 

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  -

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