RE: [uddi-dev] RE: Representing Hierarchical Value Sets (for example for uddi:uddi.org:categorization:types)

["Daniel Feygin" <feygin@unitspace.com>]

Mirek,

Thanks for you help, I found the file on Systinet's site.  I was wrong in my
assumption that I had the latest version.

Regards,
Daniel

> -----Original Message-----
> From: Mirek Novotny [mailto:mirek.novotny@systinet.com] 
> Sent: Tuesday, April 15, 2003 12:15 AM
> To: Daniel Feygin; 'Paul Denning'
> Cc: uddi-dev@lists.oasis-open.org
> Subject: Re: [uddi-dev] RE: Representing Hierarchical Value 
> Sets (for example for uddi:uddi.org:categorization:types)
> 
> 
> Hi Daniel and Paul
> 
> Taxonomy.xsd schema describes the persistent format our 
> taxonomies. Try to browse our latest Systinet WASP UDDI, 
> 4.5.1 documentation accessible at 
> http://www.systinet.com/uddi/web/doc/ or use 
> http://www.systinet.com/uddi/web/doc/uddi/taxonomymanagement.h
> tml for taxonomy management description. The requested 
> taxonomy schema is also accesible at 
> http://www.systinet.com/uddi/web/doc/uddi/taxonomy.xsd
> 
> You can also try taxonomies on our live WASP UDDI registry at 
> http://www.systinet.com/uddi/web.
> 
> Taxonomy schema is also located in WASP UDDI distribution at 
> WASP_UDDI_HOME/etc/uddi/taxonomy.xsd.
> If you want to explore our Taxonomy API you can try our 
> taxonomy demos located at 
> WASP_UDDI_HOME/demos/advanced/taxonomy or browse our Systinet 
> WASP UDDI Client API javadoc at 
> http://www.systinet.com/uddi/web/doc/api/index.html
> 
> If you will have any troubles please feel free to contact me.
> 
> Regards
> 
> Mirek
> 
> --
> Mirek Novotny
> WASP UDDI Project Leader
> Systinet  (formerly Idoox)
> http://www.systinet.com
> 
> 
> ----- Original Message -----
> From: "Daniel Feygin" <feygin@unitspace.com>
> To: "'Paul Denning'" <pauld@mitre.org>
> Cc: <uddi-dev@lists.oasis-open.org>
> Sent: Monday, April 14, 2003 7:31 PM
> Subject: RE: [uddi-dev] RE: Representing Hierarchical Value 
> Sets (for example for uddi:uddi.org:categorization:types)
> 
> 
> I could not find the file 
> WASP_UDDI_HOME/etc/uddi/taxonomy.xsd referred to in 
> http://www.systinet.com/doc/wasp_uddi/uddi/taxonomymanagement.
> html.  I looked in WASP UDDI 4.0.  Microsoft (as, I'm sure, 
> other registry vendors) provides similar file-based taxonomy 
> representation functionality and tools, while going somewhat 
> further with an extension API get_relatedCategories: 
> http://msdn.microsoft.com/library/default.asp?url=/library/en-
> us/dnuddi/html
> /travtreeuddi.asp.
> 
> Daniel
> 
> > -----Original Message-----
> > From: Paul Denning [mailto:pauld@mitre.org]
> > Sent: Wednesday, April 09, 2003 9:07 PM
> > To: Pranav Parekh; Wai-Kwong Sam LEE
> > Cc: uddi-dev@lists.oasis-open.org
> > Subject: Re: [uddi-dev] RE: Representing Hierarchical Value 
> Sets (for 
> > example for uddi:uddi.org:categorization:types)
> >
> >
> > UDDI Spec TC is looking into "external taxonomies": 
> > http://lists.oasis-open.org/archives/uddi-spec/200303/msg00000.html
> >
> > Systinet WASP-UDDI has nice support for taxonomy download 
> and upload 
> > using XML. 
> > http://www.systinet.com/doc/wasp_uddi/uddi/taxonomymanagement.html
> >
> > Paul
> >
> >
> > At 04:58 PM 2003-03-18, Pranav  Parekh wrote:
> > >Thanks for the response Sam.
> > >
> > >
> > >Some follow-up comments and questions..
> > >
> > >In my original question, when I mentioned that I was unable
> > to find any
> > >details in the spec. as to how the hierarchical value set is 
> > >represented.. I meant to say I was unable to find the XML 
> > >representation of the hierarchical value set.
> > >
> > >Also, since there are no APIs for users of the registry to
> > retrieve the
> > >hierarchical value set (that a category scheme or identifier
> > scheme is
> > >bound to have), any vendor who thinks it is important or
> > necessary to
> > >expose this functionality for end users will have a custom 
> > >implementation.  In light of that, is there a preferred
> > approach that
> > >the UDDI committee has recommended which might become part
> > of a future
> > >specification?
> > >
> > >Thanks,
> > >- Pranav
> > >
> > >-----Original Message-----
> > >From: Wai-Kwong Sam LEE [mailto:Sam.Lee@oracle.com]
> > >Sent: Monday, March 17, 2003 4:37 PM
> > >To: Pranav Parekh
> > >Cc: uddi-dev@lists.oasis-open.org
> > >Subject: Re: Representing Hierarchical Value Sets (for example for
> > >uddi:uddi.org:categorization:types)
> > >
> > >
> > >The complete hierarchy of the value set 
> > >uddi:uddi.org:categorization:types tModel is detailed in the spec 
> > >section 11.1.1.4:
> > >
> > >http://uddi.org/pubs/uddi_v3.htm#UDDITypes
> > >
> > >There is no API for users of the registry to retrieve this 
> value set.
> > >
> > >In general, in UDDIv3, there are APIs (such as the
> > get_allValidValues
> > >you mentioned) to allow a *registry* (rather than the users of the
> > >registry) to retrieve valid values of a value set from a value set 
> > >provider.
> > >
> > >The API set was created to allow a registry implementation
> > to cache the
> > >valid values for spell-check type of validation, rather 
> than for end 
> > >users to retrieve the values and the structure (such as
> > hierarchy) of a
> > >value set.
> > >
> > >
> > >- sam
> > >
> > >Pranav Parekh wrote:
> > > > Folks,
> > > >
> > > > For UDDI Version 3, the UDDI specs. provides the
> > hierarchical value
> > >set
> > > > for the uddi:uddi.org:categorization:types TModel.
> > However, I was
> > > > unable to find any details in the spec. as to how this value set
> > >itself
> > > > is represented.  Additionally, I was unable to find any APIs 
> > > > relevant
> > >to
> > > > the retrieval or management of this hierarchical value 
> set (or any
> > >other
> > > > hierarchical value set for some other categorization 
> scheme).  The
> > >only
> > > > API relevant to value sets is the get_allValidValues but
> > using that
> > >API
> > > > how would information regarding a hierarchical value set be 
> > > > retrieved?
> > > >
> > > > Any insight would be greatly appreciated.
> > > >
> > > > Best Regards,
> > > > - Pranav J. Parekh
> > > >
> >
> >
> >
> 
> 
>