Issue 16872: Annex D should be Normative (date-time-ftf) Source: NIST (Mr. Edward J. Barkmeyer, edbark(at)nist.gov) Nature: Uncategorized Issue Severity: Summary: The Date/Time Annex D "Fundamental Concepts" says that it is 'informative'. But the declarations and definitions in Annex D are formally specified in SBVR and UML. Moreover, the UML classes and associations defined in Annex D are used directly in the formal normative specifications in the body of Date/Time. The 'quantities' model (D.3) is used in peripheral way in defining 'duration' and 'time unit', and might be considered informative only, since only some 'time units' are 'measurement units' (as defined in D.3). But the part/whole relationship (D.4) is used normatively in clause 8, and the sequences (D.1) and scales (D.3) concepts are critical to the formulation of definitions and necessities in clause 8 and in clause 12. So, it appears that Annex D.1, D.2 and D.4 are critical to the normative specification. It is the stated intent of the Date/Time specification that the Annex D models are outside the scope of the Date/time specification, and are used only because no appropriate formal specification of these concepts has been found. Thus a later specification with focused expertise in these areas can be expected to supplant these elements of the Date/Time specification at some future time. Nonetheless, the text of the Date/Time specification, and its formal models, depend on Annex D being interpreted normatively until some future time when it is formally replaced by a specification with wider support. Recommendation: Make Annex D 'normative', and retain the caveat that it is an interim specification. Resolution: Revised Text: Actions taken: December 1, 2011: received issue Discussion: End of Annotations:===== te: Thu, 01 Dec 2011 17:10:21 -0500 From: Ed Barkmeyer Reply-To: edbark@nist.gov Organization: NIST User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: issues@omg.org, "date-time-ftf@omg.org" Subject: Date/Time Vocabulary Issue: Annex D should be Normative X-NISTMEL-MailScanner-Information: Please contact postmaster@mel.nist.gov for more information X-NISTMEL-MailScanner-ID: pB1MAQ5e021446 X-NISTMEL-MailScanner: Found to be clean X-NISTMEL-MailScanner-SpamCheck: X-NISTMEL-MailScanner-From: edbark@nist.gov X-NISTMEL-MailScanner-Watermark: 1323382227.90704@VKCUoTP7u3sX/maa8l2vZw X-Spam-Status: No X-NIST-MailScanner: Found to be clean X-NIST-MailScanner-From: edbark@nist.gov OMG Issue Specification: Date/Time Vocabulary (DTV) Version: draft Beta-1 Title: Annex D should be Normative Source: Ed Barkmeyer, NIST, edbark@nist.gov Summary: The Date/Time Annex D "Fundamental Concepts" says that it is 'informative'. But the declarations and definitions in Annex D are formally specified in SBVR and UML. Moreover, the UML classes and associations defined in Annex D are used directly in the formal normative specifications in the body of Date/Time. The 'quantities' model (D.3) is used in peripheral way in defining 'duration' and 'time unit', and might be considered informative only, since only some 'time units' are 'measurement units' (as defined in D.3). But the part/whole relationship (D.4) is used normatively in clause 8, and the sequences (D.1) and scales (D.3) concepts are critical to the formulation of definitions and necessities in clause 8 and in clause 12. So, it appears that Annex D.1, D.2 and D.4 are critical to the normative specification. It is the stated intent of the Date/Time specification that the Annex D models are outside the scope of the Date/time specification, and are used only because no appropriate formal specification of these concepts has been found. Thus a later specification with focused expertise in these areas can be expected to supplant these elements of the Date/Time specification at some future time. Nonetheless, the text of the Date/Time specification, and its formal models, depend on Annex D being interpreted normatively until some future time when it is formally replaced by a specification with wider support. Recommendation: Make Annex D 'normative', and retain the caveat that it is an interim specification. -- Edward J. Barkmeyer Email: edbark@nist.gov National Institute of Standards & Technology Manufacturing Systems Integration Division 100 Bureau Drive, Stop 8263 Tel: +1 301-975-3528 Gaithersburg, MD 20899-8263 Cel: +1 240-672-5800 To: date-time-ftf@omg.org Subject: Date-Time Issue 16872 - Annex D Should be Normative X-KeepSent: C514D3AA:1B9F5660-85257A66:00809DA4; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011 From: Mark H Linehan Date: Sun, 26 Aug 2012 19:25:57 -0400 X-MIMETrack: Serialize by Router on D01MC604/01/M/IBM(Release 8.5.3FP2IF1|July 25, 2012) at 08/26/2012 19:25:57 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 12082623-5112-0000-0000-00000B7EA30B Proposed resolution: -------------------------------- Mark H. Linehan STSM, IBM Research Date-Time Issue 16872 - Annex D should be Normative.doc Disposition: ??? OMG Issue No: 16872 Title: Annex D should be Normative Source: Ed Barkmeyer, NIST, edbark@nist.gov Summary: The Date/Time Annex D "Fundamental Concepts" says that it is 'informative'. But the declarations and definitions in Annex D are formally specified in SBVR and UML. Moreover, the UML classes and associations defined in Annex D are used directly in the formal normative specifications in the body of Date/Time. The 'quantities' model (D.3) is used in peripheral way in defining 'duration' and 'time unit', and might be considered informative only, since only some 'time units' are 'measurement units' (as defined in D.3). But the part/whole relationship (D.4) is used normatively in clause 8, and the sequences (D.1) and scales (D.3) concepts are critical to the formulation of definitions and necessities in clause 8 and in clause 12. So, it appears that Annex D.1, D.2 and D.4 are critical to the normative specification. It is the stated intent of the Date/Time specification that the Annex D models are outside the scope of the Date/time specification, and are used only because no appropriate formal specification of these concepts has been found. Thus a later specification with focused expertise in these areas can be expected to supplant these elements of the Date/Time specification at some future time. Nonetheless, the text of the Date/Time specification, and its formal models, depend on Annex D being interpreted normatively until some future time when it is formally replaced by a specification with wider support. Recommendation: Make Annex D 'normative', and retain the caveat that it is an interim specification. Resolution: The FTF proposes to make Annex D.2 .Sequences. and Annex D.4 .Mereology. normative, and leave Annex D.3 .Quantities Vocabulary. informative. The .Sequences. and .Mereology. vocabularies are complete and self-consistent, and do not overlap with any other known standards effort. The .Quantities Vocabulary. annex deliberately addresses only the subset of the Quantities topic that is needed by the Date-Time Vocabulary. Other efforts -- the QUDV activity of SysML and the QUOMOS standards work at OASIS . are working in this area. Consequently, the FTF prefers to keep the .Quantities Vocabulary. informative. Revised Text: In clause 6.3, change the designation of Annex D from .(informative). to .(partially normative).. In clause 6.3, replace the paragraph that reads: This material is informative and is provided to illustrate how the authors think this Date-Time specification fits in a larger context. The team expects that some future effort may work on standardizing these concepts, at which time this specification should be revised to fit properly within the normative version of such concepts. . with: Annex D.2: Sequences (normative) presents a complete model of sequences that provides the formal foundation for time scales. Annex D.3 Quantities Vocabulary (informative) defines a minimal vocabulary for quantities and units of measure. This vocabulary is informative because it does not address requirements beyond those of this Date-Time Vocabulary. Annex D.4: Mereology (normative) specifies a basic model of mereology that provides the formal basis for the part-of relationship among time intervals. Change the heading of Annex D to show that it is partially normative. In Annex D.1, replace the paragraph that reads: This material is informative and is provided to illustrate how the authors think this Date-Time specification fits in a larger context. The team expects that some future effort may work on standardizing these concepts, at which time this specification should be revised to fit properly within the normative version of such concepts. . with: Annexes D.2 .Sequences. and Annexes D.4 .Mereology. are complete and consistent models of their topics and are normative. Annex D.3 .Quantities Vocabulary. is informative because it addresses only the aspects of quantities and units of measure that are required by the Date-Time Vocabulary, and because the other groups mentioned above have the charter to fully address the topic. Add the phrase .(normative). after the heading of .D.2 Sequences.. Add the phrase .(informative). after the heading of .D.3 Quantities Vocabulary.. Add the phrase .(normative). after the heading of .D.4 Mereology.. Disposition: Resolved