W3C home > Mailing lists > Public > public-ws-semann@w3.org > July 2006

Re: [issue10] what about multiple categories ?

From: Jacek Kopecky <jacek.kopecky@deri.org>
Date: Tue, 04 Jul 2006 17:43:55 +0200
To: Pierre.CHATEL@fr.thalesgroup.com
Cc: public-ws-semann@w3.org
Message-Id: <1152027835.10081.69.camel@localhost>

Hi Pierre, 
this is a reply to both your [issue 10] questions.

First, there can be multiple modelReference values (one attribute, the
value is a whitespace-separated list of URIs) so you can still have
multiple categorizations.

As for the question of UDDI mapping - the interface model reference can
be a URI to a particular category, if a taxonomy provides such URIs, or
it can be a structured piece of information like <category> was.

We have decided to drop the XML structure of <category> because it would
be hard to agree on what exact pieces of information it should contain
and also because in an ideal world, all categories should have URIs so a
single piece of information would be required for categorization (the
URI), and that can fit within modelReference.

Since we don't live in an ideal world, we decided to provide a
non-normative small ontology (in OWL or RDFS) that will define class
"Category" with properties pointing to a taxonomy and a particular code,
a hopefully useful subset of the information we had in <category>.

We use an ontology instead of an XML construct so that the resulting
data can easily be pointed to by modelReference and processed by
semantic processors.

Hope this clarifies and justifies our decision on issue 10,


On Fri, 2006-06-23 at 15:00 +0200, Pierre.CHATEL@fr.thalesgroup.com
> Hi,
> It was possible to have multiple category elements under one
> interface, but there's only one modelReference attribute for a given
> xml element. How can a single interface can now be associated to
> multiple taxonomies ? Should we have an other RDF classe capable of
> handling multiple taxonomies and codes ?
> Also, when mapping interface categories to UDDI, using the deprecated
> Category element I was able to associate a given taxonomy to a
> specific taxonomy tModel (such as NAICS) and use the uuid of this
> tModel to categorize my interface tModel. Now that this information is
> hidden behind an RDF instance of the Category class the only thing I
> can do is associate the value of the modelReference attribute (an URI)
> to the interface.... less useful !
> Pierre
> --
> Pierre Chatel
> SC2 - Software Core for Computer-based systems
> 1-5, Avenue Carnot / BC4
> 91883 Massy CEDEX
> Tel 01 69 75 30 57
Received on Tuesday, 4 July 2006 15:51:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:45 UTC