Re: Schema.orgAaron Bradley <> Product Info

Dear all:

IMO, the recommended way of adding more granular product type and product feature information to markup is to use

1. the additionalType property in combination with an a product type identifier from an external vocabulary, be it, eClass or the UNSPSC 
2. use the mechanism for representing the product features as property-value pairs. For examples, see

Properties for product characteristics cannot be part of unless they are very, very generic due to the sheer number of such properties. eClass for instance defines more than 5000 product properties and the eOTD more than 20,000 (albeit some are redundant).

Note that as soon as you can establish a common prefix and a set of unique identifiers for externally defined product properties, using schema:additionalProperty is as good as hard-wired properties in

Example: Using properties from eClass:

<!-- Product: Property ID for clarifying the meaning of a property: Code from eCl@ss Standard -->
<!-- The Property code 02-AAM226 is for "USB interface present" in eCl@ss 8.1 -->
<div itemscope itemtype="">
  <img itemprop="image" src="camera123.jpg" />
  <span itemprop="name">Digital Camera 123</span>
  <div itemprop="additionalProperty" itemscope itemtype="">
      <span itemprop="name">USB Interface</span>:
      <meta itemprop="value" content="True">Yes
      <meta itemprop="propertyID" content="eclass81:02-AAM226">

For a bit of background on the problems of modeling product features and product types in Web vocabularies, you might find the following publications useful:

A Quantitative Analysis of Product Categorization Standards: eCl@ss, UNSPSC, eOTD, and RNTD, in: Knowledge and Information Systems (KAIS), Springer, Vol. 13, No. 1, pp. 77-114, September 2007. PDF from

E-Business Vocabularies as a Moving Target: Quantifying the Conceptual Dynamics in Domains, Proceedings of the 16th International Conference on Knowledge Engineering and Knowledge Management (EKAW2008), September 29 - October 3, 2008, Acitrezza, Italy, Springer LNCS, Vol. 5268, pp. 388-403. PDF from

Products and Services Ontologies: A Methodology for Deriving OWL Ontologies from Industrial Categorization Standards, in: Int'l Journal on Semantic Web & Information Systems (IJSWIS), Vol. 2, No. 1, pp. 72-99, January-March 2006. PDF from


martin hepp          @mfhepp

> On 23 Mar 2016, at 09:32, AUDRAIN LUC <> wrote:
> Hi,
> Sorry for the question, but could you tell me what ‘DYI' means?
> Luc Audrain
> De : Eric Kauz <>
> Date : mardi 22 mars 2016 20:57
> À : Aaron Bradley <>, Russell Pruitt <>
> Cc : " Mailing List" <>
> Objet : RE: Schema.orgAaron Bradley <> Product Info
> Renvoyer - De : <>
> Renvoyer - Date : mardi 22 mars 2016 20:57
> Hi Aaron and Russel,
> The GS1 Vocabulary as currently defined has a limited number of properties that relate purely to DYI products but there is interest from our community to start building out the Vocabulary to cover these types of products.  Our community includes many suppliers and retailers in the DYI space.
> We are very open to working with you or anyone else on this effort. 
> Best Regards
> Eric
> From: Aaron Bradley [] 
> Sent: Tuesday, March 22, 2016 3:16 PM
> To: Russell Pruitt <>
> Cc: Mailing List <>
> Subject: Re: Schema.orgAaron Bradley <> Product Info
> Hi Russell,
> Without going into a great deal of detail here, the Product schema is fundamentally generic, whereas the properties you're exploring are very much domain-specific.  So depending on what benefit you hope to derive from declaring such properties, you may indeed well wish to explore building your own external extension.
> Alternately and/or additionally, you'll definitely want to take a look at the GS1 Web Vocabulary [1], which is a far more products-focused external extension, and accordingly has a much broader range of properties available for use. [2]
> Finally, also check out the The Product Types Ontology [3].  While this won't necessarily make more product categories available for your use, through the use of additionalType you can at least make much more granular product declarations.
> [1]
> [2]
> [3]
> On Tue, Mar 22, 2016 at 9:35 AM, Russell Pruitt <> wrote:
>> Hi Everyone,
>> I have been looking at the current product schema that are in the product item scope of property, but they are not very robust for the itemtypes/itemprops that are offered. 
>> I have around 150 different itemprops I'd like to propose, but wanted to understand if there are any suggestions or rules around this?
>> I could always build a proprietary extension of types, but would much rather do this so that it benefits everyone in the product schema (
>> Here are some examples I believe could be useful to add - I have many more based on our current use:
>> Abrasion Resistance
>> Additional Protection Features
>> Adhesion to Foam
>> Adhesive Color
>> Adhesive Content
>> Adhesive Controltac/Comply
>> Adhesive Features
>> Adhesive Type
>> Alternative Sale Availability
>> Application / Industry
>> Application Category
>> Application Method
>> Application Surface
>> Application Temperature (Celsius)
>> Applications
>> Aspect Ratio
>> Attachment Type
>> Any insight would be great.
>> Thanks.
>> Russell
>> -- 
>> Russell Pruitt
>> 763.200.1418
>> @koffephilosophy
>> The creative thinker is flexible and adaptable and prepared to rearrange his thinking.
>> - A.J. Cropley
> CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. GS1 may monitor communications. Third party rights acknowledged. (c) 2016.

Received on Wednesday, 23 March 2016 10:51:35 UTC