Aligning GoodRelations & Schema.org

PUBLIC DRAFT

Author: Martin Hepp, mfhepp@computer.org 

Skype mfhepp

Note: This may not contain all subsequent editorial changes.

The Mercurial repository at https://bitbucket.org/mfhepp/goodrelations-schema-integration

is the authoritative resource.

Overview

1 Goal

2 Prerequisites for adding GoodRelations to schema.org

2.1 Datatypes etc.

Action 1: New datatypes

Action 2: Fix problem with http://schema.org/Boolean

Action 3: Fix problem with URL values for properties

2.2 Multiple Itemtypes

Action 4: New additionalType property for http://schema.org/Thing

3 Additions to schema.org

3.1 Suggested new properties for existing classes

http://schema.org/Offer

http://schema.org/Product

http://schema.org/Place

http://schema.org/Organization

http://schema.org/Person

3.2 Suggested new classes and their properties

http://schema.org/Brand

http://schema.org/BusinessEntityType

http://schema.org/BusinessFunction

http://schema.org/DayOfWeek

http://schema.org/DeliveryMethod

http://schema.org/ParcelService as a subclass of http://schema.org/DeliveryMethod

http://schema.org/Demand (new)

http://schema.org/IndividualProduct as a subclass of http://schema.org/Product

http://schema.org/OwnershipInfo (new)

http://schema.org/OpeningHoursSpecification

http://schema.org/PaymentMethod

http://schema.org/CreditCard

http://schema.org/PriceSpecification

http://schema.org/ProductFeature  (new) subclass of http://schema.org/StructuredValue

http://schema.org/ProductModel  as a subclass of http://schema.org/Product

http://schema.org/QualitativeValue

http://schema.org/QuantitativeValue

http://schema.org/SomeProducts as a subclass of http://schema.org/Product

http://schema.org/TypeAndQuantityNode

http://schema.org/WarrantyPromise

http://schema.org/WarrantyScope

Action: Add additional classes and properties to schema.org.

3.3 Suggested new individuals

http://schema.org/BusinessEntityType

http://schema.org/BusinessFunction

http://schema.org/DayOfWeek

http://schema.org/DeliveryMethod

http://schema.org/ParcelService

http://schema.org/PaymentMethod

http://schema.org/CreditCard

http://schema.org/WarrantyScope

Action: No action needed. The enumerations remain in the GoodRelations namespace.

3.4 Other changes

3.4.1 Expand notion of a product

Action: Update textual definition of http://schema.org/Product.

3.4.2 Common superclass for organization and person

Action: Add common superclass http://schema.org/Agent

3.4.3 OWL Mapping

3.5 Changes in GoodRelations

Change Tracking

Overview

This document describes a proposal on how to extend schema.org by GoodRelations elements. It discusses only issues relevant for the schema.org sponsors as a whole. Issues about the specific support of GoodRelations by a single search engine are not included in this document but instead subject to separate, bilateral discussions.

1 Goal

• Maximize the amount and granularity of structured e-commerce data on the Web.
• Minimize Webmaster confusion about the choice between GoodRelations and Microdata.
• Preserve the expressive power of GoodRelations without raising the entrance barriers for adopters.
• Preserve backward-compatibility as much as possible, i.e. avoid major renaming of widely used, existing GoodRelations elements. In principle, however, it is possible to have a limited amount of naming differences between the schema.org version and the original version of the same GoodRelations element, so that we can maintain consistent naming conventions in both schema.org and GoodRelations.
• Avoid future divergence, as much as possible.

2 Prerequisites for adding GoodRelations to schema.org

In this section, we describe basic modifications and extensions to the schema.org specification that are needed to add GoodRelations properties. Note that due to the substantial degree of dependencies, the best approach is to implement all of them exactly as proposed, as long as there are no prohibitive compatibility issues.

Also note that implementing this will make it super-easy to build extensions for cars, tickets, real estate, jobs, etc.

2.1 Datatypes etc.

GoodRelations requires the following datatypes:

http://www.w3.org/2001/XMLSchema#int

http://www.w3.org/2001/XMLSchema#float

http://www.w3.org/2001/XMLSchema#boolean

http://www.w3.org/2000/01/rdf-schema#Literal

http://www.w3.org/2001/XMLSchema#dateTime

http://www.w3.org/2001/XMLSchema#string

http://www.w3.org/2001/XMLSchema#time

• int/float work nicely with Float/Integer or Number
• literal/string work with Text

Action 1: New datatypes

Tracked in WebSchemas issue tracker as https://www.w3.org/2011/webschema/track/issues/15

We need

• http://schema.org/DateTime for xsd:datetime

A combination of date and time of day in the form [-]CCYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm] (see Chapter 5.4 of ISO 8601).

-> example here please :) <-

and

• http://schema.org/Time for xsd:time

A point in time recurring on multiple days in the form hh:mm:ss[Z|(+|-)hh:mm] (see http://www.w3.org/TR/xmlschema-2/#time)

-> example here please :) <-

as subtypes of http://schema.org/DataType.

xsd:time is really important for structured opening hours and other GoodRelations features.

Example:

<div itemscope itemtype="http://schema.org/Place" itemid="#store">

  <span itemprop="name">Hepp's Happy Burger Restaurant</span>

  <div itemprop="openingHoursSpecification" itemscope

       itemtype="http://schema.org/OpeningHoursSpecification">

Opening hours: Mo-Fri,

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Monday" />

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Tuesday" />

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Wednesday" />

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Thursday" />

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Friday" />

     <meta itemprop="opens" content="08:00:00">8:00 a.m. -

     <meta itemprop="closes" content="20:00:00">8:00 p.m.

  </div>

</div>

ACTION: Add these two datatypes to schema.org. DONE

Action 2: Fix problem with http://schema.org/Boolean

RESOLVED! We agree 'true' 'false' are preferred values, and seem to be the dominant usage pattern.

ACTION Dan update schema.org to make this more obvious to readers.

Tracked in WebSchemas issue tracker as https://www.w3.org/2011/webschema/track/issues/14

You have to clarify the usage of  http://schema.org/Boolean. The schema.org sponsors should clarify whether to use the RDF-compatible text (true/false) or the

URIs http://schema.org/True and http://schema.org/False.

For now, one would assume that you use the two values as individuals, e.g.

<link itemprop=”propertyname” href=”http://schema.org/True” />

<link itemprop=”propertyname” href=”http://schema.org/False” />

which is incompatible with the RDFa patterns and also less concise.

I suggest

<meta itemprop=”propertyname” content=”true” >

<meta itemprop=”propertyname” content=”false” >

A simple text amendment for http://schema.org/True, http://schema.org/False, and http://schema.org/Boolean would do the trick.:

Note: The recommended use of this datatype is with a string “true” or “false” indicating the value of the respective property.

Example:

<div itemscope itemtype="http://schema.org/Book">

<span itemprop="name">The Catcher in the Rye</span>

 Family-friendly: <meta itemprop="isFamilyFriendly" content="true"> yes

</div>

ACTION: Add this note to  http://schema.org/Boolean 

Action 3: Fix problem with URL values for properties

Resolved: we externalise GR URLs, revisit after 6 months in light of impl experience.

[let’s discuss before raising an issue -- Dan]

Note: If we use all enumerated values from GoodRelations as external enumerations from their original namespace (e.g. http://purl.org/goodrelations/v1#UPS instead of http://schema.org/UPS, then the proposal for external enumerations described at http://www.w3.org/wiki/WebSchemas/ExternalEnumerations should be sufficient and this issue could be closed. We would just need pointers in the description of the properties to the respective values, e.g. “Use with GoodRelations enumerations like http://purl.org/goodrelations/v1#UPS”.

Such schema.org elements that are actually instances of a schema.org class, e.g.

    http://schema.org/InStock 

should be listed with matching properties and not as a subtype.

A possible solution is to change the last delimiter to indicate that this is a different form of an isA relationship, e.g. a colon:

So change the pattern from

Thing > Intangible > Enumeration > ItemAvailability > InStock

to

Thing > Intangible > Enumeration > ItemAvailability :: InStock

This is of general relevance, but since GoodRelations uses predefined individuals frequently, it should be fixed before GoodRelations elements are added to schema.org

Action: Change pattern for individuals in the HTML version of schema.org. Solved for the moment (not critical for GoodRelations integration).

2.2 Multiple Itemtypes

Action 4: New additionalType property for http://schema.org/Thing

Add a property "additionalType" with a range of URI to http://schema.org/Thing so that additional types for items can be signaled without breaking the frame-based model of schema.org and Microdata. The cardinality should be 0..*.

<div itemscope itemtype="http://schema.org/Product">

    <link itemprop="additionalType" href="http://www.productontology.org/id/Hammer" />

    <link itemprop="additionalType" href="http://www.productontology.org/id/Sledgehammer" />

    <!-- other schema.org properties go in here -->

</div>        

For GoodRelations and www.productontology.org, this will mostly be needed for http://schema.org/Product, but I think a generic property attached to http://schema.org/Thing makes far more sense.

So add this property to http://schema.org/Thing

Action: Add additionalType property to http://schema.org/Thing. DONE - included in the 0.96 release

3 Additions to schema.org

3.1 Suggested new properties for existing classes

http://schema.org/Offer 

Action: Add additional properties to http://schema.org/Offer. 

http://schema.org/Product

Also, the range for the model property of http://schema.org/Product must be changed to allow either text or http://schema.org/ProductModel.

Add the following three specializations of http://schema.org/Product:

http://schema.org/IndividualProduct

A single, identifiable product instance (e.g. a laptop with a particular serial number).

Position in the schema.org hierarchy: Thing > Product > IndividualProduct

http://schema.org/ProductModel 

A datasheet or vendor specification of a product (in the sense of a prototypical description)

Position in the schema.org hierarchy: Thing > Product > ProductModel

http://schema.org/SomeProducts 

A placeholder for multiple similar products of the same kind.

Position in the schema.org hierarchy: Thing > Product > SomeProducts

Action: Add additional properties to http://schema.org/Product. 

Action: Change range of brand to http://schema.org/Brand.  

Action: Tolerate additional properties from specializations of GoodRelations when using full URIs, e.g.

• http://purl.org/vso/ns#engineDisplacement
• http://purl.org/vvo/ns#torque

Action: Add three subclasses  http://schema.org/IndividualProduct, http://schema.org/ProductModel, and http://schema.org/SomeProducts  to http://schema.org/Offer. 

http://schema.org/Place 

Action: Add additional properties to http://schema.org/Place 

http://schema.org/Organization 

Action: Add additional properties to http://schema.org/Organization.

http://schema.org/Person 

Action: Add additional properties to http://schema.org/Person. 

3.2 Suggested new classes and their properties

http://schema.org/Brand

A brand is a name used by an organization or business person for labeling a product, product group, or similar.

Position in the schema.org hierarchy: Thing > Intangible > Brand

http://schema.org/BusinessEntityType 

A business entity type is a conceptual entity representing the legal form, the size, the main line of business, the position in the value chain, or any combination thereof, of an organization or business person.  

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > BusinessEntityType

http://schema.org/BusinessFunction 

The business function specifies the type of activity or access (i.e., the bundle of rights) offered by the organization or business person through the offer. Typical are sell, rental or lease, maintenance or repair, manufacture / produce, recycle / dispose, engineering / construction, or installation.

Proprietary specifications of access rights are also instances of this class.

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > BusinessFunction

gr:License (Special Case)

For legal reasons, schema.org cannot contain elements for modeling licensing conditions, because site-owners may try to use them to express complex licensing terms for the use of their content by search engines, which cannot be properly handled by Web-scale crawlers. Thus, the class gr:License from GoodRelations is not available from the schema.org namespace. If you want to use gr:License, use GoodRelations in its original namespace or use the additionalType property in combination with the full URI http://purl.org/goodrelations/v1#Licenseand the main itemtype http://schema.org/BusinessFunction.

http://schema.org/DayOfWeek 

The day of the week, e.g. used to specify to which day the opening hours of a http://schema.org/OpeningHoursSpecification refer.

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > DayOfWeek

http://schema.org/DeliveryMethod 

A delivery method is a standardized procedure for transferring the product or service to the destination of fulfilment chosen by the customer. Delivery methods are characterized by the means of transportation used, and by the organization or group that is the contracting party for the sending organization or person.

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > DeliveryMethod

http://schema.org/ParcelService as a subclass of http://schema.org/DeliveryMethod 

A private parcel service as the delivery mode available for a certain offer.

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > DeliveryMethod > DeliveryMethodParcelService

http://schema.org/Demand (new)

A demand entity represents the public, not necessarily binding, not necessarily exclusive, announcement by an organization or person to seek a certain type of goods or services. For describing demand using this type, the very same properties used for http://schema.org/Offer apply.

Position in the schema.org hierarchy: Thing > Intangible > Demand

Note: Replicate all properties (existing and those coming from GoodRelations above) from http://schema.org/Offer for this type; omitted in here for brevity. Exceptions are

• price
• priceCurrency
• priceValidUntil
• review
• reviews
• aggregateRating

which are omitted for the Demand type, since they will rarely be useful for this type. The reason for these omissions are as follows:

• price, priceCurrency, and priceValidUntil: The more advanced price modeling using the new priceSpecification property is more suited for modeling demand.
• review, reviews, aggregateRating: These properties may be useful for describing the products sought, but will then be added to the http://schema.org/Product and not the demand type.

http://schema.org/IndividualProduct as a subclass of http://schema.org/Product

A single, identifiable product instance (e.g. a laptop with a particular serial number).

Position in the schema.org hierarchy: Thing > Product > Individual

Note: Replicate all properties (existing and those coming from GoodRelations above) from http://schema.org/Product for this type; omitted in here for brevity.

http://schema.org/OwnershipInfo (new)

A structured value providing information about when a certain organization or person owned a certain product.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > OwnershipInfo

http://schema.org/OpeningHoursSpecification 

A structured value providing information about the opening hours of a place or a certain service inside a place.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > OpeningHoursSpecification

Example:

<div itemscope itemtype="http://schema.org/Place" itemid="#store">

  <span itemprop="name">Hepp's Happy Burger Restaurant</span>

  <div itemprop="openingHoursSpecification" itemscope

       itemtype="http://schema.org/OpeningHoursSpecification">

Opening hours: Mo-Fri,

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Monday" />

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Tuesday" />

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Wednesday" />

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Thursday" />

     <link itemprop="dayOfWeek"

           href="http://purl.org/goodrelations/v1#Friday" />

     <meta itemprop="opens" content="08:00:00">8:00 a.m. -

     <meta itemprop="closes" content="20:00:00">8:00 p.m.

  </div>

</div>

http://schema.org/PaymentMethod 

A payment method is a standardized procedure for transferring the monetary amount for a purchase. Payment methods are characterized by the legal and technical structures used, and by the organization or group carrying out the transaction.

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > PaymentMethod

http://schema.org/CreditCard 

A credit or debit card type as a standardized procedure for transferring the monetary amount for a purchase.

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > PaymentMethod > CreditCard

http://schema.org/PriceSpecification 

A structured value representing a monetary amount. Typically, only the subclasses of this type are used for markup.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > PriceSpecification

http://schema.org/UnitPriceSpecification as a subclass of http://schema.org/PriceSpecification

The price asked for a given offer by the respective organization or person.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > PriceSpecification > UnitPriceSpecification

Properties: All properties from http://schema.org/PriceSpecification plus the following:

http://schema.org/DeliveryChargeSpecification as a subclass of http://schema.org/PriceSpecification

The price for the delivery of an offer using a particular delivery method.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > PriceSpecification > DeliveryChargeSpecification

Properties: All properties from http://schema.org/PriceSpecification plus the following:

http://schema.org/PaymentChargeSpecification as a subclass of http://schema.org/PriceSpecification

The costs of settling the payment using a particular payment method.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > PriceSpecification > PaymentChargeSpecification

Properties: All properties from http://schema.org/PriceSpecification plus the following:

http://schema.org/ProductFeature  (new) subclass of http://schema.org/StructuredValue

A property-value pair representing a product feature.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > ProductFeature

Note: This new approach is strategically very promising, since it allows shops and vendor pages to expose rich product data without cleansing it completely as simple property-vTalue pairs.

http://schema.org/ProductModel  as a subclass of http://schema.org/Product

A datasheet or vendor specification of a product (in the sense of a prototypical description)

Position in the schema.org hierarchy: Thing > Product > ProductModel

Note: Replicate all properties (existing and those coming from GoodRelations above) from http://schema.org/Product for this type; omitted in here for brevity.

Additional properties:

http://schema.org/QualitativeValue

A predefined value for a product characteristic, e.g. the the power cord plug type "US" or the garment sizes "S", "M", "L", and "XL".

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > QualitativeValue (DISCUSS)

Note: This element will be very important for future fashion use-cases!

http://schema.org/QuantitativeValue 

A point value or interval for product characteristics and other purposes

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > QuantitativeValue

http://schema.org/SomeProducts as a subclass of http://schema.org/Product

A placeholder for multiple similar products of the same kind.

Position in the schema.org hierarchy: Thing > Product > SomeProducts

Note: Replicate all properties (existing and those coming from GoodRelations above) from http://schema.org/Product for this type; omitted in here for brevity.

Also, the inventoryLevel property from http://schema.org/Offer should include http://schema.org/SomeProducts as a compatible domain type to be in sync with GoodRelations.

http://schema.org/TypeAndQuantityNode 

A structured value indicating the quantity, unit of measurement, and business function of goods included in a bundle offer.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > TypeAndQuantityNode

http://schema.org/WarrantyPromise

A structured value representing the duration and scope of services that will be provided to a customer free of charge in case of a defect or malfunction of a product.

Position in the schema.org hierarchy: Thing > Intangible > StructuredValue > WarrantyPromise

http://schema.org/WarrantyScope 

A range of of services that will be provided to a customer free of charge in case of a defect or malfunction of a product.

Position in the schema.org hierarchy: Thing > Intangible > Enumeration > WarrantyScope

Action: Add additional classes and properties to schema.org.

3.3 Suggested new individuals

http://schema.org/BusinessEntityType 

http://schema.org/Business - Business entity type: Business

http://schema.org/Enduser - Business entity type: End-user

http://schema.org/PublicInstitution - Business entity type: Public Institution

http://schema.org/Reseller - Business entity type: Reseller

http://schema.org/BusinessFunction 

http://schema.org/ConstructionInstallation - Business Function: Construction and installation

http://schema.org/Dispose - Business Function: Disposal

http://schema.org/LeaseOut - Business Function: Rental

http://schema.org/Maintain - Business Function: Maintenance

http://schema.org/ProvideService - Business Function: Service

http://schema.org/Repair - Business Function: Repair

http://schema.org/Sell - Business Function: Sell

http://schema.org/DayOfWeek 

http://schema.org/Monday - Day of the week: Monday

http://schema.org/Tuesday - Day of the week: Tuesday

http://schema.org/Wednesday - Day of the week: Wednesday

http://schema.org/Thursday - Day of the week: Thursday

http://schema.org/Friday - Day of the week: Friday

http://schema.org/Saturday - Day of the week: Saturday

http://schema.org/Sunday - Day of the week: Sunday

http://schema.org/PublicHolidays - Day of the week: Public Holidays

http://schema.org/DeliveryMethod 

http://schema.org/DirectDownload - Delivery Mode: Direct download (gr:DeliveryModeDirectDownload)

http://schema.org/Freight - Delivery Mode: Freight(gr:DeliveryModeFreight)

http://schema.org/Mail - Delivery Mode: Mail / Postal service (gr: DeliveryModeMail)

http://schema.org/OwnFleet - Delivery Mode: By own fleet (gr: DeliveryModeOwnFleet)

http://schema.org/PickUp - Delivery Mode: In-store pick-up (gr: DeliveryModePickUp)

http://schema.org/ParcelService 

http://schema.org/DHL - Delivery Mode: DHL (tm)

http://schema.org/FederalExpress - Delivery Mode: Federal Express (tm)

http://schema.org/UPS - Delivery Mode: UPS (tm)

http://schema.org/PaymentMethod 

http://schema.org/DirectDebit - Payment method: Direct debit

http://schema.org/ByBankTransferInAdvance - Payment method: By bank transfer in advance

http://schema.org/ByInvoice - Payment method: By invoice

http://schema.org/Cash - Payment method: Cash

http://schema.org/CheckInAdvance -  Payment method: Check in advance

http://schema.org/COD - Payment method: Cash on delivery

http://schema.org/GoogleCheckout - Payment method: Google Checkout (tm)

http://schema.org/PayPal - Payment method: PayPal (tm)

http://schema.org/PaySwarm - Payment method: Payswarm (tm)

http://schema.org/CreditCard 

http://schema.org/AmericanExpress - Payment method: American Express (tm)

http://schema.org/DinersClub - Payment method: Diners Club  (tm)

http://schema.org/Discover - Payment method: Discover (tm)

http://schema.org/VISA - Payment method: VISA (tm)

http://schema.org/JCB - Payment method: JCB (tm)

http://schema.org/MasterCard - Payment method: MasterCard (tm)

http://schema.org/WarrantyScope 

http://schema.org/PartsAndLabor-BringIn - Warranty scope: Parts and labor, bring-in service.

http://schema.org/PartsAndLabor-PickUp - Warranty scope: Parts and labor, pick-up service.

http://schema.org/Labor-BringIn - Warranty scope: Labor, bring-in service.

Action: No action needed. The enumerations remain in the GoodRelations namespace.

3.4 Other changes

3.4.1 Expand notion of a product

The definition of http://schema.org/Product should be updated to include commodity services, e.g.

A product is anything that is made available for sale—for example, a pair of shoes, a concert ticket, or a car. Commodity services, like haircuts, can also be represented using this type.

Action: Update textual definition of http://schema.org/Product.

3.4.2 Common superclass for organization and person

It would be useful to have a common superclass like http://schema.org/BusinessEntity or http://schema.org/Agent that combines http://schema.org/Organization and http://schema.org/Person, because in some cases, the data sources may not support that distinction (e.g. a list of eBay member of which you do not know whether they are a company or a private seller).

Action: Add common superclass http://schema.org/Agent. This is a separate issue with no direct dependecies to the GoodRelations integration.

3.4.3 OWL Mapping

It may be useful to add mapping axioms to the OWL version of schema.org, but this is secondary. We can also provide the mapping axioms in GoodRelations or as a separate file for interested audiences.

3.5 Changes in GoodRelations

The respective work will be done directly in a GoodRelations service update once the integration into schema.org is final.

Change Tracking

1. After a discussing between Martin Hepp and Dan Brickley, we now propose to use the original GoodRelations namespace for the enumerations, i.e. the individuals of certain value or type classes. So the whole section 3.3. can be omitted. For an example, see http://wiki.goodrelations-vocabulary.org/Cookbook/Schema.org#Offer_with_Delivery_Charges_and_Business_Function
2. Changed all property names from plural to singular so that we will be consistent with the preferred naming pattern in schema.org
3. Added model / modelLink property to http://schema.org/Product
4. New property releaseDate for http://schema.org/Product. The release date of a product or product model. This can be used to distinguish the exact variant of a product. Range: Date
5. The range of eligibleRegion is now "Text or GeoShape".
6. condition vs. itemCondition: I consolidated the two properties into one by expanding the range from OfferItemCondition to "Text or OfferItemCondition" and expanding the domain from http://schema.org/Offer to http://schema.org/Offer, http://schema.org/Demand, and http://schema.org/Product
7. Changed range of brand property: The range of the brand property has been changed from http://schema.org/Organization to http://schema.org/Brand, because organizations and their brands are distinct entities - often, the Webmaster will not know the legal entity behind a certain brand.
8. The open issue on whether to extend the model property or to implement a modelLink property for http://schema.org/Product has been solved by extending the range for the existing model property to allow either text or http://schema.org/ProductModel. This achieves compatibility with GR without introducing another property.
9. Renamed http://schema.org/Individual to http://schema.org/IndividualProduct and http://schema.org/SomeItems to http://schema.org/SomeProducts
10. Renamed http://schema.org/DeliveryModeParcelService to http://schema.org/ParcelService
11. Renamed http://schema.org/PaymentMethodCreditCard  to http://schema.org/CreditCard
12. Polished the wording for price and priceCurrency, since they can appear in multiple contexts. New wording is "The offer price of a product or a price component, when attached to <code>PriceSpecification</code> and its subtypes." and "The currency (in 3-letter ISO 4217 format) of the offer price or a price component, when attached to <code>PriceSpecification</code> and its subtypes."
13. Implemented minPrice and maxPrice as proposed. Note: Schema.org has a similar property lowPrice / highPrice, but I think the meaning is narrower than this one, so I would keep them separate.
14. Fixed minor bug: gr:billingIncrement corrected to billingIncrement
15. Changed text for http://schema.org/ProductFeature. The new text is "A property-value pair representing a product feature."
16. Updated the text for businessFunction so that is matches the agreed usage of GR elements from the purl.org namespace: "The default is http://schema.org/Sell." --> "The default is http://purl.org/goodrelations/v1#Sell."
17. Fixed inconsistent text for typeOfGood: The new text is "The product that this structured value is referring to."
18. Changed durationOfWarrantyInMonths with a range of Number to durationOfWarranty with a range of QuantitativeValue. This allows using year, months and day as the unit of measurement, e.g. for "30-day money back guarantee"
19. Added missing text for the class http://schema.org/QuantitativeValue in the Google Docs document
20. Renamed property purchasedFrom to acquiredFrom, because one can acquire products also by other means than purchase (e.g. as a gift)
21. Simplified the pattern for http://schema.org/ProductFeature: Dedicated properties propertyName and propertyValue for the name and value of the property-value pair.  If the value is a range, simply use propertyValue as text ("3 - 5") instead of overloading minValue and maxValue from http://schema.org/QuantitativeValue.
22. Added http://schema.org/SomeProducts to the domain of the inventoryLevel property
23. Extended the range of the seller property to include individuals (http://schema.org/Person), as e.g. in eBay scenarios
24. Polished the text for gtin8, gtin13, gtin14, and mpn properties
25. Fixed the domain and range for eligibleTransactionVolume. The domain is now Offer, Demand, or PriceSpecification. The range is PriceSpecification. Note that for constraints on the quantity of a good, use eligibleQuantity.
26. Consolidated the text of multiple occurrences of the eligibleQuantity property
27. Added the missing http://schema.org/License type to the domain of validThrough and validFrom
28. Fixed text for the billingIncrement property
29. Fixed text for the eligibleRegion property in the documentation
30. Changed the text for http://schema.org/Product to also allow commodity services: "A product is anything that is made available for sale—for example, a pair of shoes, a concert ticket, or a car. Commodity services, like haircuts, can also be represented using this type."
31. Fixed text and superclass for http://schema.org/WarrantyPromise
32. Renamed the property warrantyPromise to warranty in order to avoid the name class with the type http://schema.org/WarrantyPromise.
33. Removed gr:License from the proposal.