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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-regrep message

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


Subject: RE: UDDI Classification vs. ebXML RR Classification


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





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

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC