W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > April 2003

danc-04 add a triviallyTrue predicate

From: Jeremy Carroll <jjc@hpl.hp.com>
Date: Sat, 26 Apr 2003 21:19:18 +0300
To: w3c-rdfcore-wg@w3.org
Message-Id: <200304262119.18618.jjc@hpl.hp.com>

DanC suggests:
Consider adding to RDFS a triviallyTrue predicate;

  ?S rdfs:triviallyTrue ?O.

is true for all ?S and ?O.


(1) jeremy's digital signature application needs
to number bnodes

(2) folks are asking for all uses of rdfs:comment
to be vacuously true. This would provide that


DanBri says:
Can you make a case for including triviallyTrue in the RDF Core specs,
rather than (for eg) in a utility vocabulary of some kind published (eg)
as a Note? There are lots of neat things we _could_ add if we had the time,
eg. conventions for XHTML markup in comments, modelling of versioning etc.
Is there something about triviallyTrue that jumps it to the top of the 

I argue that, at least for my application, there is not such a case.
I currently quite happily follow DanBri's advice of defining it in a utility 
If I wish to use a standard, the following will do me:

<owl:DatatypeProperty rdf:ID="triviallyTrue">
  <rdfs:range rdf:resource="&xsd;long"/>

      <owl:onProperty rdf:resource="#triviallyTrue"/>

which makes triviallyTrue hold between all resources and all longs, which in 
practice will be enough.

The rdfs:comment use case (in which we would declare

triviallyTrue rdfs:subPropertyOf rdfs:comment .

to turn comments into true comments) is not addressable in this fashion.

Received on Saturday, 26 April 2003 15:19:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:54:05 UTC