GoodRelations Issues List

From Wiki of the E-Business and Web Science Research Group
Jump to: navigation, search

This page lists open and fixed issues regarding the Goodrelations ontology.

Contents


Open Issues

Issue: Include links to other vocabularies

It was suggested to include links to other existing vocabularies, e.g. FOAF, DC, etc. The problem with that is the candidate vocabularies are defined in different ontology languages or language fragments, e.g. RDF-S, OWL DL, and OWL Full. Including such links in GoodRelations directly will turn GoodRelations into OWL Full, which is something we want to avoid as much as we can.

The reason is that there are applications for GoodRelations both

  • in the "open, wild Web", where OWL Full will anyway be the likely language fragment, and incomplete, lightweight reasoning be suffcient, and
  • in controlled, corporate settings, where staying withing OWL DL is an important feature for consistent DL reasoning.

Solution: We will maintain a page at which recommended links & mappings will be described which can be included when they help and don't hurt.

STATUS: PLANNED

Issue: Product models may include accessories

Often, a product model includes a particular set of accessories. It is currently unclear how this can be represented.

Example: We have the cell phone Siemens 1234. This model includes an earphone and a remote control.

Since gr:ProductOrServiceModel instances cannot be further decomposed, a query for an offering that includes a cell phone and an earphone will not return an offering that includes one piece of that model.

STATUS: POSTPONED. Since it is now possible to attach an EAN and GTID also to an gr:Offering, one can simply model the parts includes as a regular product bundle. Also, the exact amount of accessories included often varies by country or merchant, which also recommends to express that explicitly at the offering level.

Issue: Links between eClassOWL and GoodRelations properties

Some attributes in the GoodRelations vocabulary are also defined at the level of eClassOWL. We have to spot these and link them when updating eClassOWL.

Two candidates are

  • 1. gr:EAN
  • 2. gr:description

Solution: The links will be included in eClassOWL 5.1.4, but the eClassOWL properties will be subproperties (problem that the domain of those includes now Offering and ProductOrService; a Product or Service will then be inferred to belong to the Union of Offering and ProductOrService;that is a bit akward but will likely not hurt)

STATUS: PLANNED, this will be included in the official eClassOWL 5.1.4. release

Issue: UN/LOCODE for Country and Region

For country and region, UN / LOCODE http://www.unece.org/cefact/locode/service/main.htm may be a better alternative; see United Nations Economic Commission for Europe (UN/CEFACT), 2004

This is a low priority issue for the moment.

STATUS: POSTPONED

Closed Issues

Issue: Ordering relation for gr:QualitativeValue

In some applications, it may be useful to express an ordering relation between instances of gr:QualitativeValue.

Example: If one has the garment sizes S,M,L, and XL, one may want to express that S<M<L<XL, both for querying and for user interfaces.
At the moment, we have decided against that because

  • OWL2 may support rdf:List or a similar feature
  • We cannot populate that feature easily for eClassOWL

STATUS: IMPLEMENTED in the 2010-04-12 service update

Older Issues

  • EANs / GTIN-14 for product bundles(solved by including gr:Offering in the domain of those two properties)
    1. Discuss whether there should be a Unit Of Measurement for Price specifications. Basically, this seems redundant, as the Unit Of Measurement is already specified by the components of the offering and their quantities (these quantities have Uoms, too). So the Uom for the Price Specification is by definition always "pieces of this set of items". TBD.
    • ==> solved: recommended is "C62" for "Unit or piece", but others are possible. Justification: For all offerings that contain one item only, it should be possible to use arbitrary units of measurement in the price spec.
    • The usage of timezones for various date and time elements must be incorporated (mainly in the documentation).
      SNIP from http://www.w3schools.com/Schema/schema_dtypes_date.asp

"Time Zones

To specify a time zone, you can either enter a dateTime in UTC time by adding a "Z" behind the time - like this:

2002-05-30T09:30:10Z

or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this:

2002-05-30T09:30:10-06:00

or

2002-05-30T09:30:10+06:00"

1. Base URI changed to http://purl.org/goodrelations/v1
2. Project home page URI changed to http://purl.org/goodrelations/
3. Price Ranges for Unit Price, Shipping Charge, Payment Charge added

  • hasCurrencyValueMin
  • hasCurrencyValueMax
  • hasCurrencyValue

1. List Price support added: isListPrice yes/no for Unit Price only
2. Properties for EAN/UPC and GTIN-14 added

  • hasEAN_UCC-13
  • hasGTID-14

1. Properties identifying businesses added

  • hasGlobalLocationNumber for BusinessEntity and LocationOfSalesOrServiceProvisioning
  • hasDUNS for BusinessEntity only
Retrieved from "http://www.ebusiness-unibw.org/wiki/GoodRelations_Issues_List"
Personal tools
Navigation