- From: Dan Brickley <danbri@danbri.org>
- Date: Tue, 4 Jun 2013 10:31:44 -0700
- To: Max Froumentin <Max.Froumentin@digital.justice.gov.uk>
- Cc: "<phil.barker@hw.ac.uk>" <phil.barker@hw.ac.uk>, "<public-vocabs@w3.org>" <public-vocabs@w3.org>
On 4 June 2013 09:49, Max Froumentin <Max.Froumentin@digital.justice.gov.uk> wrote: > On 4 Jun 2013, at 14:49, Phil Barker <phil.barker@hw.ac.uk> wrote: > >> On 04/06/13 07:13, Dave Pawson wrote: >>> Max was looking for a refinement (phone number to 'home phone number') >>> Is there any convention for doing this in schema.org? >>> >> Extensions? http://schema.org/docs/extension.html > > I have two problems with the Extensions section. > > 1. It says "schema.org uses the '/' character to create extensions that are specializations of existing schema.org vocabulary" > Where do you use the '/' character? http://schema.org/Person/Engineer/ElectricalEngineer isn't a valid URI, nor is > musicGroupMember/leadGuitar2 a valid attribute value for itemprop I think we can do better than that /-based mechanism, and we should probably get extension.html updated to suggest mechanisms like: <div vocab="http://schema.org/" prefix="ep: http://example.org/2013/person-extras123#" typeof="Person ep:ElectricalEngineer"> <span property="name">John Smith</span> <span property="ep:engCode" content="MATHLESS"></span> </div> ...using a real schema elsewhere plus rdfa multiple typing allows basic schema.org consumers to ignore the extension, but smarter tools to understand that an ElectricalEngineer is a specialization of Person (and perhaps of Engineer). Plus it gives you a real page to document (eg. rdfa+rdfs) in English/Russian/Chinese etc. The /-based mechanism doesn't do that. > 2. I guess I should design an extension vocabulary for my own purposes, in particular for applications consuming my data who want to differentiate an ElectricalEngineer from a MechanicalEngineer, for instance. But if I do that, it doesn't help me with search engines who don't know about my extensions. In other words, why use the specialised Place/photo and not the general Thing/image, if search engines don't know Place/photo ? I'm not a big fan of using /, but the basic idea is they can 'dumb down' to the parent path. Dan > Max. >
Received on Tuesday, 4 June 2013 17:32:15 UTC