Here is a good example of how an ontology is released. (01)
* Not vetted by a "Ontology Board".
* Clear statement of upwards compatibility (02)
It might be an interesting idea to think about how an automated system
would deal with this. (03)
Take the use case where retail giant "Big Store" has built an ERP where
ontologies are heavily used to define process and relationships.
It probably has several other ontologies in its mix plus its own custom
What metadata would be required to determine where this new version
interfaces with existing relationships?
How would the repository alert the development team that a new version
is one of the base ontologies is available?
What would the repository be able to tell the developer about the new
What would be the process of swapping out the old version and hooking in
the new? (05)
On 21/04/2010 5:05 AM, Martin Hepp (UniBW) wrote:
> Dear all:
> We just released a service update to the GoodRelations ontology for
> e-commerce. The update is backwards-compatible to previous releases and
> mainly adds additional properties that are important for the rental and
> accommodation business. We also redesigned the complete language reference.
> Please find the latest resources from the following URIs:
> * http://purl.org/goodrelations/v1 (RDF/XML or HTML via content negotiation)
> * http://purl.org/goodrelations/v1.owl (RDF/XML)
> * http://purl.org/goodrelations/v1.html (HTML)
> A change log is at
> * http://bit.ly/dhXqY9
> !!! Please refresh your caches !!!
> - New gr:owns property for indicating the products that you own, which
> allows exposing ownership data, e.g. to feed for future recommender
> systems. So companies and individuals can now express offers
> (gr:offers), demand (gr:seeks), and ownership (gr:owns).
> - Ordering relations for gr:QualitativeValues, which may be useful e.g.
> for modeling garment sizes (XL>L>M>S) (gr:greater, gr:lesser,
> gr:greaterOrEqual, gr:lesserOrEqual, gr:equal, and gr:nonEqual)
> - gr:validFrom and gr:validThrough can now be applied to opening hours
> and payment / delivery charge specifications. This allows for modeling
> e.g. longer opening hours in the holiday season, or free shipping in a
> certain period.
> - New properties gr:eligibleDuration, gr:eligibleTransactionVolume,
> gr:advanceBookingRequirement, gr:billingIncrement, gr:deliveryLeadTime,
> gr:availabilityStarts, and gr:availabilityEnds for being more specific
> about the offer or pricing.
> * Examples:
> o „Free shipping starting from 20 EURO“ (attached to a
> o „Minimal order volume 10 Euro“ (attached to a gr:Offering)
> o „Service fee for credit card payments below 10 Euro“ (attached to a
> - New property gr:serialNumber
> - Ordering relations between gr:DayOfWeek, useful for sorting them in
> user interfaces and for including adjacent days (gr:hasPrevious and
> - New properties gr:successorOf and gr:predecessorOf for linking newer
> product models (gr:ProductOrServiceModel) to discontinued ones.
> Backward Compatibility Issues
> The only minimal changes that may (but should not) affect existing data
> or code are the following:
> 1. We removed the rdfs:range statement for gr:legalName. It used to be
> xsd:string, but that prevented someone from indicating the natural
> language, since the language tag can only be attached to untyped RDF
> 2. We changed the domain of gr:validFrom and gr:validThrough to the
> union of gr:Offering, gr:OpeningHoursSpecification, and
> gr:PriceSpecification instead of just gr:Offering and
> gr:UnitPriceSpecification. This allows specifying the validity interval
> of offers, opening hours, payment charge specifications, and delivery
> charge specifications.
> All existing data remains valid. It is possible that you have to relax
> any domain validation heuristics that you apply.
> Special thanks go to Andreas Radinger for reviewing the specification
> and handling the deployment, and to Andreas Stolz for writing the Python
> script and templates for the language reference. Our script uses the
> RDFlib library for parsing and handling RDF and the Jinja template
> engine for generating the HTML document.
> The service update in particular and the current state of GoodRelations
> in general would have been impossible without the valuable feedback and
> suggestions from many individuals.
> In alphabetical order, we would like to thank Daniel Bingel, Andreas
> Harth, Kingsley Idehen, Jay Myers, Markus Linder, Peter Mika, Andreas
> Radinger, Martin Schliefnig, Alex Stolz, Jamie Taylor, Giovanni
> Tummarello, Jon Udell, and Andreas Wechselberger.
> Martin Hepp
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (08)