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

Re: On using qualified names for properties

From: Dan Brickley <danbri@danbri.org>
Date: Thu, 10 May 2012 12:34:04 +0200
Message-ID: <CAFfrAFo9KPx_Hkn+QTq46ErEHoNMu17w392m0st2y9+GNLiX1A@mail.gmail.com>
To: Егор Антонов <elderos@yandex-team.ru>
Cc: Adrian Giurca <giurca@tu-cottbus.de>, "public-vocabs@w3.org" <public-vocabs@w3.org>
On 10 May 2012 12:26, Егор Антонов <elderos@yandex-team.ru> wrote:
> No, there must be only http://schema.org/Thing/name I think
> As an option, http://schema.org/CreativeWork/name can redirect to the parent
> type, which owns this property

I would call it http://schema.org/name, but yes, it's a single
property, not two properties.

> If we think in terms of multiple itemtypes on a single object, adding a type
> prefix is an organic way to avoid collisions and distinguish different types
> properties

The classic example is (addressbook contact) 'title' versus (document)
'title'. Schema.org simply has 'name' instead of (document)'title'.
Some contact schemas have 'honorificPrefix' for (contact)title. It's
usually possible to find an alternative word or phrase. This can be
annoying for vocabulary managers and sometimes the word is not
perfect, but it simplifies the data model.


Received on Thursday, 10 May 2012 10:34:37 UTC

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