I'd appreciate your views on an issue my dev org is running into. At Rational we are planning to use rdfs:member as a generic membership predicate, e.g. to indicate membership of resources in any set, not necessarily an RDF Container. However, the default behavior of ARQ is to compute rdfs:member using inference rules applied to the container membership predicates rdf:_1, rdf:_2, etc. and it in fact ignores explicit rdfs:member triples.
RDF Schema inference rules should always add triples. However, the default behavior of ARQ ignores explicit rdfs:member triples. This seems like a bug. I understand we can turn off this ARQ behavior in Java code. Is there a way to do this using command line args to tdb.tdbquery? What do you think is the intended use of rdfs:member, and how is it used in practice? Thx. Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 Twitter | Facebook | YouTube
