Issue 17541: Inconsistent Use of ‘Concept Type’ (date-time-ftf) Source: International Business Machines (Mr. Mark H. Linehan, mlinehan(at)us.ibm.com) Nature: Uncategorized Issue Severity: 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 Resolution: Revised Text: Actions taken: August 6, 2012: received issue Discussion: End of Annotations:===== sposition: ??? OMG Issue No: 17541 Title: Inconsistent Use of .Concept Type. Source: Mark H. Linehan, IBM, mlinehan@us.ibm.com 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 <> 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 <> 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 <> hour of day minute of day Figure 14.1 shows the following class .internet time point. that should be marked <>, but that is missing from the text Resolution: Revised Text: Disposition: ???