- From: James M Snell <jasnell@gmail.com>
- Date: Thu, 2 Aug 2012 10:58:26 -0700
- To: Egor Antonov <elderos@yandex-team.ru>
- Cc: "public-vocabs@w3.org Vocabs" <public-vocabs@w3.org>
- Message-ID: <CABP7RbfhzVTCSrTSDqcirDOEMzX780KhMdM0u_wUDuByqZ2BAw@mail.gmail.com>
The way it's defined, developers could continue using simple names as well.. for example... <div itemscope itemtype="http://schema.org/Person"> <div itemprop="name">Joe Smith</div> </div> <div itemscope itemtype="http://schema.org/Person"> <div itemprop="commonName" itemscope itemtype="http://schema.org/Name"> Joe Smith </div> </div> etc.. - James On Thu, Aug 2, 2012 at 10:51 AM, Egor Antonov <elderos@yandex-team.ru>wrote: > Hi James, > > I fully agree that a name is a compex and culture dependent construct, but > it's not so easy for me to imagine websites which would like to maintain > people names in such a complex way. > There are many developers using just a simple 'string' (or 'varchar') > column to store somebody's name. > Removing support for plain text means they must complicate their db (and > they surely won't change anything). > I think we should leave this complexity to more specialized ontologies > > -- > Egor > > 02.08.2012, 21:27, "James M Snell" <jasnell@gmail.com>: > > Hello all, > > I've recently been exploring the possible integration of schema.orgmetadata with the OpenSocial API ( > http://opensocial.org). OpenSocial defines it's own schema for various > objects like Person, Groups, Albums, etc. Eventually, I would like to see > this model brought in line with things like the schema.org model but > there are a number of existing gaps that would need to be addressed. As an > experiment, I decided to take one single aspect of the OpenSocial model and > visualize what that would look like as a schema.org Type... > > Within OpenSocial, a "Person" object [ > http://opensocial-resources.googlecode.com/svn/spec/trunk/Social-Data.xml#Name > ] has a fairly rich collection of metadata elements. The person's name, > for instance, is represented by a structured Name object, and the person > can have a common name, a native name, a nickname, and an optional > collection of "alternate names", each of which can be richly structured. > Within the schema.org Person object, however, there is only a single set > of unstructured text properties like "givenName" and "alternativeName". > This definitely would not work within OpenSocial applications. > > So here's the idea: create a new schema.org intangible object called > "Name", with a subtype of "PersonalName", with the following basic > definition: > > |-- Intangible > | > |-- Name > | > |-- PersonalName ( > honorific, > honorificPrefix, > honorificSuffix, > byname, > givenName, > middleName, > familyName, > generationName, > patronymic, > matronymic, > diminutive, > pronunciation, > pronunciationExample > ) > Then, let's add the following new properties to the schema.org/Personobject ... > * alternateName, > * formerName, > * nativeName, > * commonName, > * nickname, > * preferredName, > * professionalName, > * psuedonym > And remove / deprecate the following from schema.org/Person... > * additionalName > * familyName > * honorificPrefix > * honorificSuffix > * givenName > Several examples... > <div itemscope itemtype="http://schema.org/Person"> > <div itemprop="nativeName" > itemscope > itemtype="http://schema.org/PersonalName"> > <span itemprop="givenName"> > Лев > </span> > <span itemprop="patronymic"> > Никол > а́еви > ч > </span> > <span itemprop="familyName"> > Толст > о́й > </span> > </div> > <div itemprop="commonName" > itemscope > itemtype="http://schema.org/PersonalName"> > <span itemprop="givenName">Lev</span> > <span itemprop="patronymic">Nikolayevich</span> > <span itemprop="familyName">Tolstoy</span> > </div> > <div itemprop="alternateName" > itemscope > itemtype="http://schema.org/PersonalName"> > <span itemprop="givenName">Leo</span> > <span itemprop="familyName">Tolstoy</span> > </div> > </div> > <div itemscope itemtype="http://schema.org/Person"> > <div itemprop="commonName" > itemscope > itemtype="http://schema.org/PersonalName"> > <span itemprop="byName"> > Custodian of the Two Holy Mosques > </span>, > <span itemprop="honorific">King</span> > <span itemprop="givenName">Abdullah<span> > <span itemprop="patronymic">bin Abdulaziz</span> > <span itemprop="familyName">al Saud</span> > </div> > <div itemprop="nativeName" > itemscope > itemtype="http://schema.org/PersonalName" dir="rtl"> > <span itemprop="byName"> > خادم ال > حرمينا > لشريفي > ن</span>, > <span itemprop="honorific">ملك</span> > <span itemprop="givenName">عبد > الله<span> > <span itemprop="patronymic">بن عبد > العزيز</span> > <span itemprop="familyName">آل سع > ود</span> > (<span itemprop="pronunciation"> > Abd ullāh ibn ‘Abd al-‘Azīz > Āl Su‘ūd</span>) > </div> > </div> > <div itemscope itemtype="http://schema.org/Person"> > <div itemprop="name" > itemscope > itemtype="http://schema.org/PersonalName"> > <span itemprop="givenname">Hideo</span> > <span itemprop="familyname">Tanaka</span> > <span itemprop="honorificSuffix">-san</span> > </div> > <div itemprop="nativename" > itemscope > itemtype="http://schema.org/PersonalName"> > <span itemprop="givenname">英夫</span> > <span itemprop="familyname">田中</span> > <span itemprop="honorificSuffix">さん</span> > (<span itemprop="pronunciation"> > ひでお たなか > </span>) > </div> > </div> > Thoughts and opinions are always welcome... > - James > > -- > Egor Antonov > Department of secured search, > Yandex >
Received on Thursday, 2 August 2012 17:59:16 UTC