DTV 1.0b2 FTF Avatar
  1. OMG Issue

DTV — Inconsistent Use of ‘Concept Type’

  • Key: DTV-45
  • Legacy Issue Number: 17541
  • Status: closed  
  • Source: General Electric ( Mark Linehan)
  • Summary:

    Each kind of time point is a ‘concept type’. That is, the instances of each kind of time point are themselves concepts.

    The specification is inconsistent about this. Referring to the beta 2 document:

    Figure 10.2 shows the following as <<concept type>> but the text does not:
    calendar day
    calendar week
    calendar month
    calendar year
    Figure 11.1 and the associated text do not mark these concepts as ‘concept type’, but should:
    Gregorian day
    Gregorian week
    Gregorian month
    Gregorian year
    Figure 11.3 and the associated text do not mark these concepts as ‘concept type’, but should:
    common year
    leap year
    centennial year
    quadricentennial year
    Gregorian day of year
    Gregorian day of month
    Gregorian month of year
    Figure 11.7 shows the following concepts that should be marked <<concept type>>
    Gregorian year
    Gregorian day
    Figure 12.1 and the associated text do not mark these concepts as ‘concept type’, but should:
    calendar week
    week of year
    day of week
    weekday of year
    Figure 13.1 and the associated text do not mark these concepts as ‘concept type’, but should:
    hour of day
    minute of day
    second of day
    leap second
    minute of hour
    second of minute
    Figure 13.3 shows the following concepts that should be marked <<concept type>>
    hour of day
    minute of day
    Figure 14.1 shows the following class ‘internet time point’ that should be marked <<concept type>>, but that is missing from the text

  • Reported: DTV 1.0b1 — Mon, 6 Aug 2012 04:00 GMT
  • Disposition: Resolved — DTV 1.0b2
  • Disposition Summary:

    Every specialization of ‘time point’ is marked ‘concept type’. The text and the figures are aligned wherever required.

  • Updated: Fri, 6 Mar 2015 20:58 GMT