W3C home > Mailing lists > Public > public-vocabs@w3.org > December 2014

Re: Automotive, EXIF, Property-Values

From: <chaals@yandex-team.ru>
Date: Wed, 17 Dec 2014 22:31:14 +0300
To: "mfhepp@gmail.com" <mfhepp@gmail.com>
Cc: W3C Web Schemas Task Force <public-vocabs@w3.org>, Dan Brickley <danbri@google.com>, Guha Guha <guha@google.com>
Message-Id: <33611418844674@webcorp01g.yandex-team.ru>


17.12.2014, 16:57, "mfhepp@gmail.com" <mfhepp@gmail.com>:
> Hi Chaals, all:
>
> On 17 Dec 2014, at 14:23, chaals@yandex-team.ru wrote:
>>  A few tiny comments…
>>
>>  17.12.2014, 13:03, "mfhepp@gmail.com" <mfhepp@gmail.com>:
>>>  In effect, it adds the following elements:
>>>
>>>  1. Types for common vehicle categories
>>>  --------------------------------------
>>>
>>>      http://sdo-property-value.appspot.com/Bike
>>  I'd really like this to be called "Bicycle".
>
> If this is consensual, I am happy to change it

Well, so far it is just me…

>>>  2. Properties for common, vendor-independent car features
>>>  ---------------------------------------------------------
>>>  For a list, see here:
>>>
>>>      http://www.w3.org/wiki/WebSchemas/Vehicles#New_Properties
>>  transmission, gears, payload, speed, airbags, doors, damages all seem like terms that could *easily* get confused, and should should probably be disambiguated by making them longer and more specific.
>
> We have conflict between ease for use for the main case and potential conflicts due to the "global property notion" in schema.org.
>
> I am fine to prefix them all to
>
> vehicleTransmission
> vehicleGears
> vehicleAirbags etc.
>
> if this is consensual - Dan, Guha what is your take?
>
> From a Web developers perspective, I think the shorter names are more appealing because the typing effort will be much lower, and also an auto-complete feature in an editor will not work as well if 20+ properties have the same prefix.
>
> Due to the examples in three syntaxes, I would like to know the consensual opinion among the sponsors of schema.org prior to implementing the change.

Fair enough. And you point about this becoming a bigger problem if schema keeps growing is a sensible one. We either end up namespacing by adding words into names and maintain the flat schema, or we do something to structure it and break what we said before. In the former case, we start relying on tools to help out more… which puts an onus on us to help them out more…

cheers

Chaals

> Martin
>>  cheers
>>
>>  --
>>  Charles McCathie Nevile - web standards - CTO Office, Yandex
>>  chaals@yandex-team.ru - - - Find more at http://yandex.com

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Wednesday, 17 December 2014 19:31:45 UTC

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