W3C home > Mailing lists > Public > public-lod@w3.org > June 2011

Re: Schema.org in RDF ...

From: Pat Hayes <phayes@ihmc.us>
Date: Sat, 11 Jun 2011 16:33:17 -0700
Cc: Linked Data community <public-lod@w3.org>, Michael Hausenblas <michael.hausenblas@deri.org>
Message-Id: <1DEB9B2A-F3AB-4610-AC02-AA796A0957F0@ihmc.us>
To: Richard Cyganiak <richard@cyganiak.de>

On Jun 11, 2011, at 9:55 AM, Richard Cyganiak wrote:

> All,
> Thanks for the thoughtful feedback regarding schema.rdfs.org, both here and off-list.
> This is a collective response to various arguments brought up. I'll paraphrase the arguments.

>> Nothing is gained from the range assertions. They should be dropped.
> They capture a part of the schema.org documentation: the “expected type” of each property. That part of the documentation would be lost. Conversely, nothing is gained by dropping them.

Let me respectfully disagree. Range assertions (in RDFS or OWL) do *not* capture the notion of "expected type". They state a strict actual type, and cannot be consistently be "over-ridden" by some other information. Which has the consequence that these are liable to be, quite often, plain flat wrong. Which in turn has the consequence that there is something to be gained by dropping them, to wit, internal consistency. They are not mere documentation; they have strictly entailed consequences which many actual reasoners can and will generate, and which to deny would be to violate the RDFS specs. If you don't want these conclusions to be generated, don't make the assertions that would sanction them. For documentation, use the structures provided in RDFS for documentation, such as rdfs:comment.


IHMC                                     (850)434 8903 or (650)494 3973   
40 South Alcaniz St.           (850)202 4416   office
Pensacola                            (850)202 4440   fax
FL 32502                              (850)291 0667   mobile
phayesAT-SIGNihmc.us       http://www.ihmc.us/users/phayes
Received on Saturday, 11 June 2011 23:33:50 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:29:54 UTC