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


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

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

Subject: RE: [uddi-spec] Groups - Strawman Proposal - Representing Property Information (uddi-spec-tc-proposal-strawman-representing-property-information-20050320.doc) uploaded


Here are my comments:

1. General

I agree with the general approach in laying out a set of
guidelines and usage patterns in capturing property meta
data for UDDI entities. Further, I agree to expand the
formalism of doing so into a UDDI technical note.

2. Technical

I would recommend capturing the relationship between
the tModel definitions for each property (name, email, dn,
etc) with the its enclosing categorizationGroup tModel. The
purpose is to give some hint/guidelines as to how to use
the categorizationGroup, what can go in such a
keyedReferenceGroup. Furthermore, user interfaces (and
tooling) can use such meta data to do validation.

One way this can be implemented is to use categorization on
the categorizationGroup tModel definition to include
keyedReferences to the set of property tModel keys as
keyValues, using keyNames to hold property
names/comments. We may need to define a special tModel for
the key of such keyedReferences. This approach is similar to
what is in the "Property In UDDI" proposal in [1].

3. Editorial

* Page 3, line 111
  "... The xxx-org:yy...servicetype" category system will
  be used for this purpose."

  You probably meant the categorizationGroup tModel

* Page 7 to page 8, section "Representing Contact
  The introduction and definition of
  categorization system seems to trump previous mentions of
  categorization system (see the first keyedReference in
  the "organizationalcontact" keyedReferenceGroup in "all"
  examples.) Did you mean to define the same categorization

* Page 8, line 312-313
  Where did the XXXX:BrokeredServicesITService
  (categorization) come from and where was it used?

* Throughout the document, the naming and UDDI keys of all
  the relevant tModels need to be consistent, for example,
  search and replace all "xxx" with "xxxx".


Jin Tong
Phone 703-917-2839      ||  Booz | Allen | Hamilton
Fax   703-902-3457      ||  8251 Greensboro Drive
Email Tong_Jin@bah.com ||  McLean VA 22102

> -----Original Message-----
> From: luc.clement@systinet.com [mailto:luc.clement@systinet.com] 
> Sent: Sunday, March 20, 2005 3:56 PM
> To: uddi-spec@lists.oasis-open.org
> Subject: [uddi-spec] Groups - Strawman Proposal - 
> Representing Property Information 
> (uddi-spec-tc-proposal-strawman-representing-property-informat
ion-20050320.doc) uploaded
> The document named Strawman Proposal - Representing Property 
> Information
> (uddi-spec-tc-proposal-strawman-representing-property-informat
> has been submitted by Luc Clement to the OASIS UDDI 
> Specification TC document repository.
> Document Description:
> This document describes how to represent property information 
> in registry.
> Specifically, it describes how to represent contacts and 
> their relationship with entities.
> The problem and the motivating use cases are described at [1] 
> and [2]. In addition to these at numerous other occasions the 
> author has been asked and has worked with vendors and 
> practitioners to address this specific need.
> What is required in essence is agreement on the methodology 
> to use to describe property information. This document does 
> so using an example specifically, the representation of 
> contact information associated with an entity of the UDDI data model. 
> [1] 
> http://lists.oasis-open.org/archives/uddi-spec/200503/msg00005.html
> [2] 
> http://lists.oasis-open.org/archives/uddi-dev/200503/msg00001.html 
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/uddi-spec/documen
> t.php?document_id=11942
> Download Document:  
> http://www.oasis-open.org/apps/org/workgroup/uddi-spec/downloa
> PLEASE NOTE:  If the above links do not work for you, your 
> email application may be breaking the link into two pieces.  
> You may be able to copy and paste the entire link address 
> into the address field of your web browser.
> -OASIS Open Administration

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