W3C home > Mailing lists > Public > public-powderwg@w3.org > September 2008

Re: LC Comment Herman

From: Stasinos Konstantopoulos <konstant@iit.demokritos.gr>
Date: Tue, 23 Sep 2008 20:35:04 +0300
To: Ivan Herman <ivan@w3.org>
Cc: Public POWDER <public-powderwg@w3.org>, Phil Archer <parcher@fosi.org>
Message-ID: <20080923173504.GJ32066@iit.demokritos.gr>

Ivan, hi.

Please see Section 2.7 and Example 2-13 in the DR doc [1] and Section
3.2.4 of the Formal doc [2], where the treatment of seeAlso is
discussed. Two cases are distinguished:

If wdr:seealso points to a URL that can be resolved and downloaded
and is an RDF class, the POWDER processor MAY assert that the external
class is a super class of the descriptorset. In this case, you would
have gotten (by inference) the triples you expected to see.

If, on the other hand, wdr:seealso points to a URL that the processor
cannot or will not resolve to an RDF class, a rdfs:seeAlso annotation of
the descriptor set is asserted. This is a more-or-less arbritrary
choice, but has the advantage that if we asserted rdfs:seeAlso triples
with iriset members as subjects, we would be missing the fact that the
descritorset as a whole (and not just its iriset subset) refers to some
resource for further info. If, for example, a resource was asserted to
be in the descriptorset through a direct link, the link between this
latter resource and the resource pointed to by wdr:seealso would have
been lost.

Please comment, especially wrt whether, in the light of the above, your
comment is substantive and you have arguments in favour of asserting
rdfs:seeAlso for the iriset members or editorial and you feel that the
wdr:seealso mechanism is not adequately explained.


[1] http://www.w3.org/TR/2008/WD-powder-dr-20080815/#tags
[2] http://www.w3.org/TR/powder-formal/#furtherDs

On Mon Sep 22 14:52:45 2008 Phil Archer said:

> I've extracted this from a mail to me from Ivan.
> He wants to use POWDER to ascribe CC licenses to the SW logos. The  
> examples he's created after reading the docs have been very helpful in  
> raising issues over several months. The latest one is this:
> - The intention I
> had, when using the <seealso> was that for each resource in the resource
> set, the following triple would also appear:
> <.../logo.png> rdfs:seeAlso <http://www.w3.org/2007/10/sw-logos.html>
> but your translation (and the specification) uses the seealso to
> annotate the _Class_ and not the individuals. Ie, the triple above will
> not appear.
> I realize that there may simply be no way around that. To be more exact,
> there is, namely by defining the same restriction structure for
> rdfs:seeAlso as for all other properties, which is perfectly o.k. for
> OWL Full, but will drive you out of OWL DL. But if you know that, it is
> worth documenting it somewhere so that well prepared users would be warned.
Received on Tuesday, 23 September 2008 17:35:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:06:04 UTC