- From: Jos De_Roo <jos.deroo.jd@belgium.agfa.com>
- Date: Mon, 11 Nov 2002 13:59:33 +0100
- To: "pat hayes <phayes" <phayes@ai.uwf.edu>
- Cc: w3c-rdfcore-wg@w3.org
[...]
>>you wrote somewhere rdfs:rest
>>I've no rdf:_n stuff in my stuff
>>I wonder why in 4.2 you don't have
>> rdfs:Class rdf:type rdfs:Class.
>> rdfs:Container rdf:type rdfs:Class.
>> rdfs:List rdf:type rdfs:Class.
>> rdfs:Property rdf:type rdfs:Class.
>
>They can all be derived from range and domain assertions elsewhere
>plus the rules. I was trying to keep the list down to a minimum.
>
>>and also why you say (also in 4.2) that
>>(some) properties are a rdf:Property
>>(why those some?
>
>Because we can derive the others, but there is no inference path to these.
right, exactly (how could I have misunderstood that)
e.g. to find that
rdf:List rdf:type rdfs:Class.
there is the argument
{
<http://www.agfa.com/w3c/euler/rdfs-rules#rule2> .
rdfs:subClassOf rdfs:domain rdfs:Class.
{
<http://www.agfa.com/w3c/euler/rdfs-rules#rule7> .
{
<http://www.agfa.com/w3c/euler/rdfs-rules#rule3> .
rdfs:domain rdfs:range rdfs:Class.
rdf:first rdfs:domain rdf:List} log:implies
{rdf:List a rdfs:Class}} log:implies
{rdf:List rdfs:subClassOf rdfs:Resource}} log:implies
{rdf:List a rdfs:Class}.
we now work with your minimal set plus
rdf:type rdfs:domain rdfs:Resource.
and also striked
rdfs:member rdfs:domain rdfs:Container.
and it works fine
-- ,
Jos De Roo, AGFA http://www.agfa.com/w3c/jdroo/
Received on Monday, 11 November 2002 08:00:12 UTC