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

Re: Generic Property-Value Proposal for Schema.org

From: <martin.hepp@ebusiness-unibw.org>
Date: Sat, 3 May 2014 00:23:12 +0200
Cc: Thad Guidry <thadguidry@gmail.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
Message-Id: <7516227A-E236-4F5D-A4EC-5A71C7950498@ebusiness-unibw.org>
To: Francois-Paul Servant <francoispaulservant@gmail.com>
Francois-Paul:

On 01 May 2014, at 18:14, Francois-Paul Servant <francoispaulservant@gmail.com> wrote:

> Thad,
> 
> I've been very fast in my explanation.
> Whatever the interpretation of PropertyValue, we can write:
> 
> foo:YourBook schema:additionalProperty x:MartinHeppAsPV.
> x:MartinHeppAsPV a PropertyValue;
> 	propertyID author;
> 	value x:MartinHeppThePerson
> 
> but x:MartinHeppThePerson and x:MartinHeppAsPV are not the same thing.
> 
> Must I say that I strongly support Martin's proposal direction?
Thanks!

> My only concern is the following: it must allow to use a URI for the object of the property (the "feature") when we have one, (and minting one should be encouraged otherwise), because this allows to publish data as they are, and to lift them later.
> 

Yes, that is possible, since the new range of the value property includes another http://schema.org/PropertyValue (but I will change that to StructuredValue to give even greater flexibility).

Then you can write either

<div itemtype="http://schema.org/Product">
  <span itemprop="name">Digital Camera 123</span>
  <div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue">
	  <span itemprop="name">Interface</span>:
  	  <div itemprop="value" itemscope itemtype="http://schema.org/QualitativeValue">
	  	<span itemprop="name">RS232</span
		<link itemprop="sameAs" href="http://dbpedia.org/resource/RS232" />
       </div>   
  </div>  
</div>

which means you locally create an entity for the value "RS232" and link it to DBPedia, or directly use an external one

<div itemtype="http://schema.org/Product">
  <span itemprop="name">Digital Camera 123</span>
  <div itemprop="additionalProperty" itemscope itemtype="http://schema.org/PropertyValue">
	  <span itemprop="name">Interface</span>:
  	  <link itemprop="value" href="http://dbpedia.org/resource/RS232" />
       </div>   
  </div>  
</div>


Martin

> Best,
> 
> fps
> 
> Le 1 mai 2014 à 16:53, Thad Guidry <thadguidry@gmail.com> a écrit :
> 
>> Francois,
>> 
>> That's because this:
>> 
>> foo:YourBook schema:additionalProperty x:MartinHeppThePerson.
>> 
>> is missing the sub-property for the right context... I.E.  it's missing the word "author"
>> 
>> 1. perhaps that missing context needs to somehow use "additionalType" ?
>> 
>> 2. maybe context should just be the "scope" of the Property-Value pairing?
>> 
>> In Schema.org .. Contexts and Kinds are referred to and modeled actually as Types. ..(well, that's how we CURRENTLY have Schema.org designed).
>> 
>> But Martin's proposal presents a slight variation on the CURRENT Design...that we need, but that we need to get right...and it can be a work in progress starting at Products & Places. Agreed.
>> 
>> Martin,
>> 
>>  The new proposal looks fine to me... just wondering about how to handle missing Context, as Francois is hitting upon...would that be through the use of "additionalType" or "scope" or something else ?  Can you mock up an example for his Sunroof case ?
>> 
>> -- 
>> -Thad
>> +ThadGuidry
>> Thad on LinkedIn
> 
Received on Friday, 2 May 2014 22:23:36 UTC

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