- From: Charles McCathie Nevile <chaals@yandex-team.ru>
- Date: Wed, 05 Jun 2013 01:57:19 +0500
- To: "<phil.barker@hw.ac.uk>" <phil.barker@hw.ac.uk>, "Max Froumentin" <Max.Froumentin@digital.justice.gov.uk>
- Cc: "<public-vocabs@w3.org>" <public-vocabs@w3.org>
On Tue, 04 Jun 2013 21:49:16 +0500, 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, In what sense? That you can't find anything there? (As a URI it seems valid to me...) > 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 ? The dumb-down principle is not brilliant, because your case shows where it might or might not work depending on your goal. But at least where it does, it's pretty straightforward to make it happen... cheers Chaals -- Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex chaals@yandex-team.ru Find more at http://yandex.com
Received on Tuesday, 4 June 2013 23:58:16 UTC