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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-dev message

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


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


I think the biggest problem is that there isn't a lot of "real" information
registered in the UBR.

> -----Original Message-----
> From: Jaime Tarquino [mailto:jtarquino@tutopia.com]
> Sent: Tuesday, March 18, 2003 5:01 PM
> To: uddi-dev@lists.oasis-open.org
> Cc: pparekh@digev.com
> Subject: RE: [uddi-dev] RE: Representing Hierarchical Value Sets (for
> example for uddi:uddi.org:categorization:types)
>
>
> In my project of grade I am making crawl from UDDI and in the current
> state I observe that very little people are following the UDDI
> recommendations for example the best practice for wsdl
> http://www.uddi.org/pubs/wsdlbestpractices-V1.05-Open-20010625.pdf
>
> In this doc says that every tmodel that uses a WSDL as its overview doc
> must use a keyed reference
> Example:
> <keyedReference tModelKey="uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4"
> keyName="uddi-org:types"
> keyValue="wsdlSpec"/>
> </categoryBag>
>
> But the only way that I found to know when a tmodel reffers a WSDL doc
> was mading a parse of the overviewdoc searching the word wsdl.
>
> In other businessServices the tmodel are empty and the WSDL is in the
> Accespoint of the BusinessService (I believe that is not correct the
> Accesspoint must be the address when the Web Service attends the
> requests)
>
> I am trying to crawl UDDI searching the WSDLs and later download the
> WSDL to index his content to offers trhought a search engine but I am
> starting to think that will be impractical because the information in
> UDDI is not enouht clean
>
> For example
>  Some statistics about the official UDDI registry based in my crawl
>  Near of 13.000 BusinessEntity Only 5096 have BusinessEntity
>  And from this 5096 are many without a WSDL document this means
>  that not are Web Services or not was well registered.
>
> What think you?
>
> -----Original Message-----
> From: Tom Bellwood [mailto:bellwood@us.ibm.com]
> Sent: Martes, 18 de Marzo de 2003 04:43 p.m.
> To: Pranav Parekh
> Cc: Wai-Kwong Sam LEE; uddi-dev@lists.oasis-open.org
> Subject: Re: [uddi-dev] RE: Representing Hierarchical Value Sets (for
> example for uddi:uddi.org:categorization:types)
>
>
>
>
>
>
> Pranav,
>
> You are correct.  There is currently no spec. defined mechanism for
> defining the structure of a value set, nor are there any APIs defined
> for
> saving and querying the content of a value set.   Maintaining this data
> has
> been deemed beyond the scope of the UDDI registry up through the V3
> specification, defering to the referential nature of UDDI.
>
> The topic you raise has, however, been the topic of discussion for
> sometime
> now in the UDDI TC.   Work in this area will be considered as a
> candidate
> item in V4.
>
> Thanks,
> Tom Bellwood       Phone:  (512) 838-9957 (external);   TL:  678/9957
> (internal)
> Co-Chair, OASIS UDDI Specification TC
>
>
> "Pranav Parekh" <pparekh@digev.com> on 03/18/2003 02:58:59 PM
>
> To:    "Wai-Kwong Sam LEE" <Sam.Lee@oracle.com>
> cc:    <uddi-dev@lists.oasis-open.org>
> Subject:    [uddi-dev] RE: Representing Hierarchical Value Sets (for
>        example for uddi:uddi.org:categorization:types)
>
>
>
> 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
> >
>
>
>



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