Added rdfs:label properties for all elements. For reasons of consistency, they are identical with the element identifiers (e.g. "BusinessEntity"). Ontologically significant individuals (e.g. days of the week) also contain the name of their superclass in parentheses (e.g. "Friday (DayOfWeek)").
Removed unused protege namespace prefix
Expanded the descriptions of hasMaxValue and hasMinValue to indicate that hasMaxValueFloat/hasMaxValueInteger, haxMinValueFloat/hasMinValueInteger, or hasValueFloat/hasValueInteger should be used when specifying values.
Set description to deprecated; use rdfs:comment now instead. This provides better tooling support.
Added PayPal as a PaymentMethod.
Added DeliveryModePickUp as a DeliveryMethod
Added DeliveryModeFreight as a DeliveryMethod
Added DeliveryModeOwnFleet as a DeliveryMethod
Added PublicHolidays as a DayOfWeek; This is a placeholder for all official public holidays at the LocationOfSalesOrServiceProvisioning. It allows specifying the opening hours on public holidays. If a given day is a public holiday, this specification supersedes the opening hours for the respective day of the week.
Added hasPOS ObjectProperty. This property states that the respective LocationOfSalesOrServiceProvisioning is a point of sale for the respective BusinessEntity. It allows linking those two types of entities without the need for a particular Offering.
Added note that the return format of the ontology specification is determined by content negotiation - in order to get a particular format, append .owl or .html to the ontology URI.
Added hasNAICS datatype property for attaching NAICS codes to BusinessEntities
Addes hasISICv4 datatype property for attaching ISIC Rev. 4 codes to BusinessEntities.
Added cardinality recommendations (constraints) to datatype and object properties by extending the rdfs:label elements.
Added isVariantOf object property for modeling product model variants. This states that a particular ProductOrServiceModel instance is a variant of another ProductOrServiceModel. It is pretty safe to infer that the variant inherits all quantitativeProductOrServiceProperties, qualitativeProductOrServiceProperties, and datatypeProductOrServiceProperties that are defined for the first ProductOrServiceModel.
Set isListPrice to DEPRECATED. Use the new gr:priceType property instead. This boolean attribute indicated whether a UnitPriceSpecification is a list price (usually a vendor recommendation) or not. TRUE indicates it is a list price, FALSE indicates it is not. It is safe to assume by default that a UnitPriceSpecification that lacks this attributes is not list price.
Added new datatype property priceType: This attribute can be used to distinguish multiple different PriceSpecifications for the same Product or Service. It supersedes the former isListPrice property. The following values are recommended: SRP: "suggested retail price" - applicable for all sorts of a non-binding retail price recommendations, e.g. such published by the manufacturer or the distributor. This value replaces the former gr:isListPrice property. INVOICE: The invoice price, mostly used in the car industry - this is the price a dealer pays to the manufacturer, excluding rebates and charges.
Added explicit namespace prefix "gr" in addition to the default (xmlns:gr="http://purl.org/goodrelations/v1#). This may make life easier for ontologies that import GoodRelations.
Added business function ConstructionInstallation. This Business Function indicates that the Business Entity offers to construct and/or install the specified Product at the customers location.
Changed cardinality constraints (recommendation) for gr:hasOpeningHoursDayOfWeek from 1..1 to 1..*. This allows using a single OpeningHoursSpecification instance for multiple Days of Week, as long as the opening hours are the same. This is an important simplification for RDFa markup.
Fixed several spelling mistakes and inconsistencies in capitalization and usage of camel word (BusinessEntity etc.). Now, identifiers for classes and instances are camel words with a starting capital letter (BusinessEntity). Properties use camel words with an initial lower caps (hasPOS). In rdfs:comment fields etc., the camel words of classes and instances are split up into multiple words by inserting white space, but the capitalization remains (Type And Quantity Node); this indicates that we are talking about an entity defined in the ontology. For properties, the camel words as used as identifiers are also used in rdfs:comment fields ("We recommend the hasPOS property to link a Business Entity to a Location of Sales").
Improved the XHTML rendering - now, the ontologically significant instances (e.g. values) are indicated as links under the respective class definition.
Changed cardinality constraints (recommendation) for gr:hasBusinessFunction from 1..1 to 1..*. This allows using a single Offering instance for multiple business functions, as long as there are no price specifications. For incomplete / lightweight descriptions, this simplifies RDFa markup. Note 1: This shortcut can only be used if the terms and conditions and all details of the offering are the same for different business functions. This is highly unlikely as soon as prices are given (the price for leasing out and selling a boat is unlikely to be the same).
Added list of predefined individuals to class definitions in XHTML file.
Added list of suitable predefined individuals for the range of object properties in the XHTML file.