W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > February 2002

Re: PRISM and multiple element concern

From: Pat Hayes <phayes@ai.uwf.edu>
Date: Thu, 7 Feb 2002 11:31:45 -0600
Message-Id: <p0510145eb88867a38608@[65.212.118.208]>
To: Brian McBride <bwm@hplb.hpl.hp.com>, Ronald Daniel <rdaniel@interwoven.com>
Cc: w3c-rdfcore-wg@w3.org
>>5) A place where I don't see a satisfactory answer: PRISM allows
>>    both
>>    <article> <prism:location> "Texas"
>>    <article> <prism:location> <iso3166-2:us-tx>
>>    One is a string, the other a term in a controlled vocabulary.

That is OK, as long as the second object isn't a literal. If that 
colonized uri is supposed to expand into a doublet:

<article> <prism:location> "Texas"
<article> <prism:location> _:x .
_:x <iso3166-2> "us-tx" .

then this is  OK;  the second use of <prism:location> does not impose 
a dtype on the "us-tx" literal. You can make <iso3166-2> into a 
datatype and then it works fine.

>>    I could declare the range of prism:location to be a location, but
>>    that is vacuous.
>
>Could you:
>
>   <prism:location> <rdfs:range>      <prism:Location> .
>   <prism:Location> <rdf:type>        <rdfs:Class> .
>   <rdf:Literal>    <rdfs:subClassOf> <prism:Location> .
>   <iso:Location>   <rdfs:subClassOf> <prism:Location> .
>
>Danbri?

Or:
<prism:isolocation> <rdfs:subPropertyOf> <prism:location> .
<prism:isolocation> <rdfs:range> <iso3166-2> .

Pat
-- 
---------------------------------------------------------------------
IHMC					(850)434 8903   home
40 South Alcaniz St.			(850)202 4416   office
Pensacola,  FL 32501			(850)202 4440   fax
phayes@ai.uwf.edu 
http://www.coginst.uwf.edu/~phayes
Received on Thursday, 7 February 2002 12:31:11 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 3 September 2003 09:45:07 EDT