Re: UDDI Classification vs. ebXML RR Classification

[Matthew MacKenzie <matt@xmlglobal.com>]

Krishna,

Yes, the adhoc query mechanism solves a part of the problem, but not all.  Along
with adhoc queries on
the registry, we need drill down support for taxonomies, for instance, I might
make the following string of queries:

req:    oqm.getTaxonomyList();
resp:  UNSPC, NAICS, AUTO_TAXON

req: oqm.getTaxonomyMap(AUTO_TAXON); // Or there is a copy locally...this is for
dynamic use of arbitrary taxonomies.
resp: {10 => Cars, 11 => Trucks, 12 => "Sport Utilities"}

req: oqm.submitAdhocQuery("find all businesses classified AUTO_TAXON=10");
resp: {Ford, General Motors, Toyota, Renault, ...}

req: oqm.submitAdhocQuery("find all products made by Ford");
resp: ...

I propose that a default set of taxonomies be supported in the Registry, and an
extension mechanism or
policy be expected for the addition of specialized taxonomies.  A client would be
able to dynamically select
a taxonomy to use.

-Matt


Krishna Sankar wrote:

> Hi,
>
>         I thought Farrukh's adHoc query proposal addresses the second method -
> query based on known attributes/classification. Can you check it out ?
>
> cheers
>
> -----Original Message-----
> From: Matthew MacKenzie [mailto:matt@xmlglobal.com]
> Sent: Wednesday, November 22, 2000 3:56 PM
> To: ebxml-regrep@lists.ebxml.org
> Subject: UDDI Classification vs. ebXML RR Classification
>
> It seems that in ebXML RR, classification trees are requested and traversed
> without
> any prior knowledge of the classification taxonomies, the classification is
> given to
> the user dynamically.  This approach is certainly very flexible for allowing
> arbitrary
> taxonomies to be introduced in certain industries, but presents a problem
> when an
> attempt is made to integrate with UDDI.
>
> UDDI expects the browser to know about the classification taxonomies.  At
> UDDI.microsoft.com, if I wanted to find businesses that are associated with
> Apparel,
> Luggage and Personal Care Products, I would need to do
> search that essentially says: find businesses with a UNSPC code of 53.
>
> Should ebXML RR support a number of taxonomies such as UNSPC, NAICS, SIC and
> GeoWeb,
> as UDDI does, and have an option of supplying the classification tree based
> on a list
> of taxonomies that the
> client is interested in, for instance:
>
> ObjectQueryManager->getClassificationTree("UNSPC")
>
> ??
>
> Comments??
>
> -Matt