W3C home > Mailing lists > Public > www-tag@w3.org > June 2012

Re: additional issue-57 use case: polysemy

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Tue, 05 Jun 2012 19:49:42 +0100
To: Pat Hayes <phayes@ihmc.us>
Cc: Jonathan A Rees <rees@mumble.net>, www-tag@w3.org
Message-ID: <f5b4nqp1tmh.fsf@calexico.inf.ed.ac.uk>
Pat Hayes writes:

> On Jun 5, 2012, at 11:23 AM, Henry S. Thompson wrote:

>> in fact uses _three_ IRIs, namely "ex:TimeDependentProperty",
>> "rdf:type" and "rdfs:Class", right?  So how do I know which of these
>> is actually _in_ the extension?
>
> All extensions extend RDF, so have the rdf: vocabulary in them. I am
> here assuming that TimeDependentProperty extends RDFS. This is a
> pretty conservative assumption.

OK, thanks.

>>  I.e. for which ones does their use in
>> a graph which inherits ex:TimeDependentProperty require appealing to
>> the constraints defined in that extension?
>
> All of them. Extensions are nested in a global DAG of
> inheritance. In this example, we have RDF <= RDFS <=
> TimeDependentProperty, where <= indicates 'is inherited by'.

Right.  So it follows that every extension graph in fact _must_
either 'own' or inherit all the URIs it contains.  And the only way to
tell which ones it 'owns' is by eliminating all the ones it inherits?

Wrt both this and my earlier use/mention comment, I was just assuming
that an extension graph would contain a bunch of triples of the form

 <> xx:owns "http://www.example.org/context#TimeDependentProperty"

or

 <> xx:ownsAll "http://www.example.org/context#"

or some such.  But I see that's not your intention at all.

Thanks,

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]
Received on Tuesday, 5 June 2012 18:52:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:33:16 UTC