W3C home > Mailing lists > Public > public-vocabs@w3.org > May 2012

Naming Schema properties (Was: On using qualified names for properties)

From: Adrian Giurca <giurca@tu-cottbus.de>
Date: Mon, 14 May 2012 09:40:06 +0200
Message-ID: <4FB0B6D6.4010803@tu-cottbus.de>
To: Dan Brickley <danbri@danbri.org>
CC: Guha <guha@google.com>, Егор Антонов <elderos@yandex-team.ru>, public-vocabs@w3.org
Hello Dan and all,

I think the Egor's post on naming Schema properties [1] <#1_>  opens an 
interesting discussion. Let me exemplify by considering property 
"awards" defined both by classes http://schema.org/Person and 

The RDF approach defines the domain of this property as the union of 
these two classes therefore when the property is named by 
http://schema.org/awards then we get:

<http://schema.org/awards> rdfs:domain <http://schema.org/Person>.
<http://schema.org/awards> rdfs:domain <http://schema.org/CreativeWork>.

However in an object oriented approach if property naming considers the 
class  who introduced the property, e.g., 
http://schema.org/Person/awards and 
http://schema.org/CreativeWork/awards then we have two different properties

<http://schema.org/Person/awards> rdfs:domain <http://schema.org/Person>.
<http://schema.org/CreativeWork/awards> rdfs:domain 

Moreover, http://schema.org/CreativeWork/awards would be allowed to be 
used on any subclass of http://schema.org/CreativeWork/ as keeping with 
set-theoretic semantics of object orientation (class as a collection of 
all its instances).


[1] http://lists.w3.org/Archives/Public/public-vocabs/2012May/0031.html
Received on Monday, 14 May 2012 07:40:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:23 UTC