Changelog/20090718

= Changelog: Service Update July 18, 2009 =

Summary: The most significant change in this update is the introduction of the gr:seeks property. This allows representing both the sales and the buy side with no additional changes to the vocabulary.

Note: The usage of this property requires either additional queries or non-standard reasoning e.g. in the form of the SPARQL CONSTRUCT shown above.
 * Changed the domain of gr:hasStockKeepingUnit from the union of gr:ProductOrServiceModel and gr:Offering to the union of gr:ProductOrService and Offering, since also products or services that have no Product Or Service Model may have this property. Also slightly updated the text.
 * Changed the comment field for gr:priceType to indicate that the absence of this property indicates the actual sales price.
 * Changed the domain of gr:hasManufacturer from gr:ProductOrServiceModel to gr:ProductOrService, since also products or services that have no Product Or Service Model may have this property. Also slightly updated the text
 * Added a new gr:PaymentMethod http://purl.org/goodrelations/v1#DirectDebit
 * Added a new gr:PaymentMethod http://purl.org/goodrelations/v1#COD
 * Added a gr:includes property as shortcut with the following semantics:

"This links a Business Entity to the Offerings it is offering (i.e., the sales side). If you want to express interest in receiving offers, use gr:seeks instead." This is necessary because the new gr:seeks property requires such a clarification. "This links a Business Entity to the Offerings that describe what the Business Entity is interested in (i.e., the buy side). If you want to express interest in actually offering something, use gr:offers instead. Note that this substitutes the former Business Function gr:Buy, which is now deprecated." "This property specifies the current approximate inventory level of the Product Or Service Some Instance Placeholder. The unit of measurement and the point value or interval are indicated using the attached gr:QuantitativeValueFloat instance."
 * Changed the range of http://purl.org/goodrelations/v1#typeOfGood from gr:ProductOrService to the union of
 * gr:ActualProductOrServiceInstance and
 * gr:ProductOrServiceSomeInstancesPlaceholder
 * Changed the rdfs:comment for gr:offers to
 * Added a new object property http://purl.org/goodrelations/v1#seeks. This allows expressing interest in offers by others. It replaces the former Business Function gr:Buy.
 * Updated the rdfs:comment text for all gr:BusinessFunctions to be compatible with the new gr:seeks property.
 * Deleted the two obsolete classes
 * http://purl.org/goodrelations/v1#AcceptedPaymentMethods
 * http://purl.org/goodrelations/v1#AvailableDeliveryMethods
 * Added an object property http://purl.org/goodrelations/v1#hasInventoryLevel
 * Added mutual disjointsWith axioms between all siblings.
 * Added isDefinedBy to all new elements manually:
 * http://purl.org/goodrelations/v1#DirectDebit
 * http://purl.org/goodrelations/v1#COD
 * http://purl.org/goodrelations/v1#includes
 * http://purl.org/goodrelations/v1#seeks
 * http://purl.org/goodrelations/v1#hasInventoryLevel
 * Since individuals cannot be set deprecated, http://purl.org/goodrelations/v1#Buy can only be marked deprecated by means of rdfs:label and rdfs:comment. --&gt; DONE
 * Removed range xsd:float at gr:hasMinValue Note that this property is a shortcut only!
 * Added domain and range to hasValueFloat and hasValueInteger This was formerly implicit via the subpropertyOf relationship, but since some annotation tools don't do reasoning, we added them in here explicitly. Note that these properties are shortcuts only! a) hasValueFloat --&gt; # rdfs:domain  -- #QuantitativeValueFloat # rdfs:range -- http://www.w3.org/2001/XMLSchema#float  b) hasValueInteger --&gt; #  rdfs:domain  -- #QuantitativeValueInteger # rdfs:range -- http://www.w3.org/2001/XMLSchema#int