1. OMG Mailing List
  2. Commons Ontology Library (Commons) 1.0 Finalization Task Force mailing list

Open Issues

  • Issues not resolved
  • Name: cmns-ftf
  • Issues Count: 8

Issues Descriptions

The constraint on a classifier that says it must classify something is too restrictive

  • Key: COMMONS-9
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    Classification schemes should be able to be defined without necessarily referring to all of the things that they classify. For example, one should be able to encode industry classifiers without having to know exactly what those classifiers apply to. Thus, the constraint that a classifier classifies some thing should be loosened to be min 0, meaning 'may'.

    This issue affects the Classifiers ontology, only

  • Reported: COMMONS 1.0a1 — Thu, 14 Jul 2022 21:44 GMT
  • Updated: Sun, 7 Aug 2022 00:00 GMT
  • Attachments:

The use of rdfs:isDefinedBy is inconsistent in the annotation vocabulary

  • Key: COMMONS-1
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    In the annotation vocabulary machine-readable file, the use of rdfs:isDefinedBy is inconsistent. For reified elements for Dublin Core annotations, we use the Qname / abbreviated IRI to link to the source. For reified elements for the Simple Knowledge Organization System (SKOS), we use the full IRI. And, we have not included rdfs:isDefinedBy for any of our local annotation declarations.

    The latter is probably ok, but we should normalize the references for Dublin Core and SKOS to all use the same approach.

    This issue was raised by Richard Beatch in his AB review.

  • Reported: COMMONS 1.0a1 — Fri, 1 Jul 2022 18:25 GMT
  • Updated: Sun, 7 Aug 2022 00:00 GMT
  • Attachments:

Some of the commons ontologies include double spaces in annotations


Need to be able to indicate whether or not something can only be classified by a single classifier from a specific scheme

  • Key: COMMONS-11
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    This is not expressible in OWL, easily. One option would be to create a boolean that indicates this is the case, which perhaps a rule engine for data quality, or sparql, or a SHACL shape could then test. What you really want to be able to say is that 'is classified by' can only have one value from a given classification scheme when applied to something.

    This is a change to the Classfiers ontology, which may impact that section of the specification.

  • Reported: COMMONS 1.0a1 — Fri, 5 Aug 2022 18:37 GMT
  • Updated: Fri, 5 Aug 2022 18:37 GMT

Examples are needed to help explain to Commons users how to use the ontologies

  • Key: COMMONS-5
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    There are no examples in the specification itself, which are needed to assist both library implementers and users of the ontologies.

  • Reported: COMMONS 1.0a1 — Fri, 1 Jul 2022 19:03 GMT
  • Updated: Fri, 1 Jul 2022 19:03 GMT

Some of the diagrams in Clause 8 are difficult to read

  • Key: COMMONS-4
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    All these diagrams, with the exception of Figure 9, have too small symbols and text. It would be very easy to reduce the width of those diagrams by reorganizing the content a little, this would allow larger magnification of the images.

  • Reported: COMMONS 1.0a1 — Fri, 1 Jul 2022 18:47 GMT
  • Updated: Fri, 1 Jul 2022 18:47 GMT

The format of the tables throughout the specification needs improvement

  • Key: COMMONS-3
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    (1) Different fonts: I can understand why you are using a fixed-width font in the metadata tables to identify the right-hand columns as the actual values of the terms listed in the left column.
    In the Properties tables I suggest to use a sans-serif font (e.g. Ariel) for the Axioms column to clearly distinguish the Axioms from the Annotations
    (2) The Properties tables are too cramped. It is not clear what the purpose of the name repetitions in parentheses in the Name column is. However, these repetitions take up unnecessarily much horizontal space. This could be solved by always moving them in a line under the bold camel-case name. The recovered horizontal space should be then allocated to the Axioms column, which is way too narrow. Many axioms are mutilated by inappropriate line breaks.
    (3) Since you are not using vertical separators (which is ok), you should extend the gutter whitespace between columns to improve readability, in particular between Annotation and Axiom columns.
    (4) Clause 6 should contain good explanations regarding the fonts and the table layouts [and the parenthesis names].

  • Reported: COMMONS 1.0a1 — Fri, 1 Jul 2022 18:45 GMT
  • Updated: Fri, 1 Jul 2022 18:45 GMT

The terms and definitions section of the Commons Ontology Library is incomplete

  • Key: COMMONS-2
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    This section defines ontology, but none of the other key terms that are present in any of the ontologies. It should be revised to incorporate at least some of the basic definitions that are present in the ontology files.

  • Reported: COMMONS 1.0a1 — Fri, 1 Jul 2022 18:40 GMT
  • Updated: Fri, 1 Jul 2022 18:40 GMT