CM Definition of Common Properties: Priority and Severity

NOTE: This is a early working draft and is subject to change frequently.

The purpose of this page is to define how some common properties such as severity and priority can be represented in OSLC-CM. They have unique characterizations in that they are typically a close choice of a configured set of values. The choices are defined by a system administrator or a specific tool instance. There is a need to be able to query on these property values, standard values and assign based on either value set as well.

Use Cases and Requirements

• Be able to have a common property
• Have standard values (enumerations)
• Be able to have custom values
• Be able to map custom values to standard ones
• Be able to provide a label (and icon) for human display

Details

Sample (option 1): Simple URIs as value

@prefix ex: <http://example.com/bugtracker> .
@prefix oslc: <http://open-services.net/ns/core#> .
@prefix cm: <http://open-services.net/ns/cm#> .
@prefix cm-x: <http://open-services.net/ns/cm-x#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix dcterms: <http://purl.org/dc/terms/> .

<http://example.com/bugs/2314>
   a oslc_cm:ChangeRequest ;
   dcterms:identifier " 00002314 " ;
   oslc:shortTitle "Bug 2314" ;
   dcterms:title " Invalid installation instructions " ;
   dcterms:type " Defect " ;
   cm-x:priority <http://open-services.net/ns/cm-x#priorityHigh> ;
   cm-x:severity <http://open-services.net/ns/cm-x#severityNormal> .

Sample (option 2): Resources for values, using Priority values as types

@prefix ex: <http://example.com/bugtracker> .
@prefix oslc: <http://open-services.net/ns/core#> .
@prefix cm: <http://open-services.net/ns/cm#> .
@prefix cm-x: <http://open-services.net/ns/cm-x#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix dcterms: <http://purl.org/dc/terms/> .

<http://example.com/bugs/2314>
   a oslc_cm:ChangeRequest ;
   dcterms:identifier " 00002314 " ;
   oslc:shortTitle "Bug 2314" ;
   dcterms:title " Invalid installation instructions " ;
   dcterms:type " Defect " ;
   cm-x:priority <http://example.com/priority/high> ;
   cm-x:severity <http://example.com/severity/low> .

<http://example.com/priority/high>
   a cm-x:PriorityHigh ;
   dcterms:title " High " ;
   ex:icon <http://example.com/priority/high.gif>.

<http://example.com/severity/low>
   a cm-x:SeverityLow ;
   dcterms:title " Low " ;
   ex:icon <http://example.com/severity/log.gif>.

Sample (option 3): Resources for values, using oslc:usage

@prefix ex: <http://example.com/bugtracker> .
@prefix oslc: <http://open-services.net/ns/core#> .
@prefix cm: <http://open-services.net/ns/cm#> .
@prefix cm-x: <http://open-services.net/ns/cm-x#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix dcterms: <http://purl.org/dc/terms/> .

<http://example.com/bugs/2314>
   a oslc_cm:ChangeRequest ;
   dcterms:identifier " 00002314 " ;
   oslc:shortTitle "Bug 2314" ;
   dcterms:title " Invalid installation instructions " ;
   dcterms:type " Defect " ;
   cm-x:priority <http://example.com/priority/high> ;
   cm-x:severity <http://example.com/severity/low> .

<http://example.com/priority/high>
   a cm-x:SeverityPriority ;
   dcterms:title " High " ;
   oslc:usage <http://open-services.net/ns/cm-x#priorityHigh>;
   ex:icon <http://example.com/priority/high.gif>.

<http://example.com/severity/low>
   a cm-x:SeverityPriority ;
   dcterms:title " Low " ;
   oslc:usage <http://open-services.net/ns/cm-x#severityLow>;
   ex:icon <http://example.com/severity/log.gif>.

To do

• How to represent label, icon and custom values: RDF reified statements (this doesn't seem to fit this model properly) or separate resource definition
• Need to check with what other tools do and have for values - 3 seems like the right minimal set of values
  • possibly use same values for both priority/severity: High, Medium, Low
• How to define property mapping: in resource shape or with the resource
  • need a way to communicate custom priorities to standard ones, for example: custom values are 1, 2, 3, ... 10 and map 1=High, 2=High, 3=High, ...., 10=Low
• Possibly just add in additional values for provider specific:

       <bugs/2314>
          cm:priority <#high>;
          rtc:priority <http://mytool/priority>.
      

• Consider how we can separate app-specific property and a standard one
• Some suggestions on how we can use owl:sameAs to help communicate: app-spec properties mapping to standard, or app-spec values to standard

Meeting Notes:

• 14 Dec 2011: SteveSpeicher, SamPadgett, DaveSteinberg, SofiaYeung, SamitMehta
  • General agreement on option 3 (priority/severity as resources and may have mappings to some standard)

References

• EvoOnt BOM http://www.ifi.uzh.ch/ddis/evoont/2008/11/bom/doc/index.html
  • Mappings http://code.google.com/p/baetle/wiki/EvoOntBomMappings
• Helios_BT http://heliosplatform.sourceforge.net/ontologies/helios_bt.html
• CmCommonProperties