- From: Charles McCathie Nevile <chaals@yandex-team.ru>
- Date: Wed, 20 Nov 2013 18:31:27 +0100
- To: "Dan Brickley" <danbri@google.com>, "Liddy Nevile" <liddy@sunriseresearch.org>, "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
- Cc: "<public-vocabs@w3.org>" <public-vocabs@w3.org>, "a11y-metadata-project@googlegroups.com" <a11y-metadata-project@googlegroups.com>
On Tue, 19 Nov 2013 22:22:53 +0100, Peter F. Patel-Schneider <pfpschneider@gmail.com> wrote: > You mean like "emergency" is likely to make you think of "A specific > branch of medical science that [...] deals with the evaluation and > initial treatment of medical conditions caused by trauma or sudden > illness."? > > I think that the non-general purpose name genie is firmly out of the > schema.org bottle. RIght. But changing the "prefix" in this case (unlike medicalEmergency which would probably still produce the wrong association) is probably a reasonable solution to the problem. cheers Chaals > peter > > On 11/19/2013 06:48 AM, Dan Brickley wrote: >> On 19 November 2013 00:07, Liddy Nevile <liddy@sunriseresearch.org> >> wrote: >>> I note that everything now has a prefix accessibility eg >>> accessibilityFeature. Does this solve the problem with accessHazard ie >>> is accessibilityHazard going to be OK?? >> There was a problem having a property called 'accessControl'. In a >> purely accessibility-oriented setting that might be intuitive. However >> schema.org is a general purpose flat namespace, and so the phrase >> "access control" is likely to make people think more of passwords, >> openid, etc. >> >> Dan >> > -- Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex chaals@yandex-team.ru Find more at http://yandex.com
Received on Wednesday, 20 November 2013 17:32:06 UTC