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


I agree completely.  Sorry I haven't read the rest of this thread and this 
just caught my eye.  I was going to add a definition of metadata to the 
glossary last week but it seemed to be locked when I tried.  I'll give it 
another try when I can.

Ken

At 08:05 PM 4/24/2005, 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?
>
>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

--
      ---------------------------------------------------------------------------------
   /   Ken 
Laskey                                                                \
  |    MITRE Corporation, M/S H305    phone:  703-983-7934   |
  |    7515 Colshire Drive                    fax:      703-983-1379   |
   \   McLean VA 22102-7508                                              /
     ----------------------------------------------------------------------------------

*** note: phone number changed 4/15/2005 to 703-983-7934 ***





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