- From: Jarno van Driel <jarno@quantumspork.nl>
- Date: Tue, 29 Apr 2014 13:12:35 +0200
- To: "martin.hepp@ebusiness-unibw.org" <martin.hepp@ebusiness-unibw.org>
- Cc: W3C Web Schemas Task Force <public-vocabs@w3.org>
- Message-ID: <CAFQgrbaohU94x135LBv4fv6zGvZcTsN-uXa7OQQaTMqCBxJnDA@mail.gmail.com>
Let me first say I like the generic extension mechanism as a whole as well as the property name 'additionalProperty'. It seems obvious in regards to how to use. Having quite some experience with eCommerce sites myself though, I also see a some disadvantages for website owners. Especially for those who have a site which sells many different types of products and get their product info from supplier feeds or datasheets that generally don't contain this type of data. Meaning that if a site-owner would want publish this type of data, quite a lot of code development (and thus resources) would be needed. And I suspect quite a lot of daily man hours as well, since it's the type of data that's difficult to markup automated within a template system. If a corporation with tens of thousands of products on their site(s) would contemplate doing this, what would there to gain for them? And from the perspective of data-consumers, e.g. schema.org's sponsors or price-comparison sites: what are the advantages of having access to this type of non-standardized data. Doesn't the fact that it's non-standardized also mean it's data that's hard to process, especially when comparing specific product specifications? On Tue, Apr 29, 2014 at 11:42 AM, martin.hepp@ebusiness-unibw.org < martin.hepp@ebusiness-unibw.org> wrote: > Dear all: > > I have just finalized a proposal on how to add support for generic > property-value pairs to schema.org. This serves three purposes: > > 1. It will allow to expose product feature information from thousands of > product detail pages from retailers and manufacturers. > 2. It will simplify the development of future extensions for specific > types of products and services, because we do no longer need to standardize > and define all relevant properties in schema.org and can instead defer > the interpretation to the client. > 3. It will serve as a clean, generic extension mechanism for properties in > schema.org > > The proposal with all examples is here: > > https://www.w3.org/wiki/WebSchemas/PropertyValuePairs > > Your feedback will be very welcome. > > Best wishes / Mit freundlichen Grüßen > > Martin Hepp > ----------------------------------- > martin hepp http://www.heppnetz.de > mhepp@computer.org @mfhepp > > > > > >
Received on Tuesday, 29 April 2014 11:13:03 UTC