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

Re: Generic Property-Value Proposal for Schema.org

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sat, 03 May 2014 09:15:58 -0400
Message-ID: <5364EC0E.7000608@openlinksw.com>
To: public-vocabs@w3.org
On 5/2/14 7:01 PM, Holger Knublauch wrote:
> On 5/3/2014 4:10, Niklas Lindström wrote:
>> My opinion, based on experience in both consuming data and working to 
>> unify disparate descriptions, is that, in the general case of needing 
>> specific properties beyond the core or schema.org 
>> <http://schema.org>, it would be quite valuable to apply the existing 
>> mechanism of mixing vocabularies, native to RDF and the enabler of 
>> decentralized vocabulary growth. It has been there from the start and 
>> proven extremely valuable in specific data integration scenarios.
>
> +1
>
> I believe Martin has raised a very important topic - on how to make it 
> easier for site owners to publish data for which no fixed schema.org 
> extension already exists. Another important topic in his proposal is 
> the handling of units and ranges. But I believe neither of these 
> necessarily require yet another extension mechanism, especially if 
> this extension mechanism breaks the integrity and simplicity of the 
> original data model and its mapping to triples.
>
> URI-based property definitions similar to RDF/OWL can already be used, 
> and anyone can very easily create their own property my:property. If 
> microdata has a problem with that because it is optimized for a single 
> namespace then the extension should be defined for microdata *syntax* 
> only, but not for the general schema.org *data model*.
>
> On the topic of units and ranges, I see no reason why these should 
> only apply to "additional" properties. They make a lot of sense for 
> existing schema.org types too, such as schema:height should also be 
> able to have values such as "10 - 500 cm". So this problem should be 
> addressed separately.
>
> I believe the original issue of making it easier for site owners to 
> publish data could be addressed by preparing suitable documentation 
> and quick start guides with the recommended design patterns. If 
> additionalProperty is still needed, then please only for microdata syntax.
>
> Holger

+1

-- 

Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen







Received on Saturday, 3 May 2014 13:16:21 UTC

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