About rdfs:member and rdf:_nnn

Comments on rdfs:member and rdf:_nnn.

1. About rdfs:member
 
Why not constraint the rdfs:domain of rdfs:member to be rdfs:Container? 
   (3.3 RDFS interpretations of the RDF Semantics spec)

    Consider adding an axiomatic triple as follows:
    rdfs:member rdfs:domain rdfs:Container

Why not specify rdfs:member to be an instance of rdfs:ContainerMembershipProperty?
   (3.3 RDFS interpretations of the RDF Semantics spec)

    Consider adding an axiomatic triple as follows:
    rdfs:member rdf:type rdfs:ContainerMembershipProperty

By so doing, we have:
* rdfs:member is an instance of rdfs:ContainerMembershipProperty (not just rdf:Property) that is a super-property of all the container membership properties.
* Container membership properties must be applied to containers.

These reflects most of the intended meanings or use cases. Of course, the current treatment is not wrong. (See section 5.1.5, section 5.1.6  and Appendix A of the RDF Schema Spec, section 3.3 of the RDF Semantics spec)

2. About rdf:_nnn  (section 3.2.2 of the RDF Semantics spec)

Please consider adding one more example to clarify the meaning of rdf:_nnn, such as the following:

_:xxx rdf:type rdf:Seq.
_:xxx rdf:_2 <ex:a> .
_:xxx rdf:_2 <ex:c> .

<ex:a> and <ex:c> should denote the same thing? In other words, the property rdf:_nnn should be a functional property? (I haven't found any explanation about this issue in the spec) 

Considering there are two RDF graphs, the first one contains:

<foo:aContainer> rdf:type rdfs:Container.
<foo:aContainer> rdf:_1 <ex:a> .
<foo:aContainer> rdf:_2 <ex:b> .

The second one contains:
<foo:aContainer> rdf:_1 <ex:b> .
<foo:aContainer> rdf:_2 <ex:a> .

How about merging the two RDF graphs?


Thanks for your concern!


Yuzhong Qu
--------------------------------------------------
Dept. of Computer Science and Engineering
Southeast University, Nanjing 210096, P. R. China
Home Page: http://cse.seu.edu.cn/People/yzqu/en
Research Group: http://xobjects.seu.edu.cn
--------------------------------------------------

Received on Sunday, 16 February 2003 11:02:00 UTC