Issue 16869: UML packages don't match specification sections (dtv-rtf) Source: NIST (Mr. Edward J. Barkmeyer, edbark(at)nist.gov) Nature: Uncategorized Issue Severity: Summary: The UML packages in the supporting UML document (bmi/2011-08-01.mdzip) are not consistently aligned with the sections of the specification. In particular: Sections 8.1 and 8.2 of the specification are both in the TimeInfrastructure package, but section 8.3 is not. Section 8.3 of the specification matches the Situations package, except that 8.3.7 Schedules is in a separate Schedules package. And the Situations package also contains the Tense concepts from 10.3. Sections 9.1 to 9.4 of the specification are all in the TimeScales package, but sections 9.5 and 9.6 are not. Section 9.5 of the specification matches the Calendars package, except that Gregorian calendar (9.5.5) is a separate UML package, and Internet Time (9.5.7) is a separate UML Package. Section 9.6 of the specification (Time Tables) is in the Schedules package, along with the Schedules concepts from 8.3.7. Section 10 of the specification matches the Indexicals package, except that Tense and Aspect (10.3) is in the UML Situations package. (The UML model treats tense as a relationship of situations to time, but the time concepts involved are indexical.) Section 11 of the specification matches the DurationValues package, except that month values (11.6) and year values (11.5) are in the UML Gregorian calendar package. Section 12 of the specification matches the UML TimeCoordinates Package, except that Section 12.4 is in the Gregorian calendar package. Annex D of the specification matches the UML Packages: Sequences (D.1), Quantities (D.2), Mereology (D.4), except that D.3 Scales is included in the UML Quantities package. In sum, some reorganization of the specification did not result in a consistent reorganization of the UML model. In general, the UML packaging should be made consistent with the text. But, if the Gregorian calendar package is intended to be separable, then Gregorian elements in other parts of the specification may need to be treated as exceptions. In addition, one can argue that the 'time table' and 'schedule' concepts are closely related and should be together in the specification. I do not recommend the use of nested UML Packages. It complicates the UML model and all references to the UML concepts defined in it. Resolution: Revised Text: Actions taken: December 1, 2011: received issue April 1, 2013: transferred from FTF Discussion: End of Annotations:===== te: Thu, 01 Dec 2011 16:10:07 -0500 From: Ed Barkmeyer Reply-To: edbark@nist.gov Organization: NIST User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: issues@omg.org CC: "date-time-ftf@omg.org" Subject: Date Time Issue: UML packages don't match specification sections X-NISTMEL-MailScanner-Information: Please contact postmaster@mel.nist.gov for more information X-NISTMEL-MailScanner-ID: pB1LACU0017437 X-NISTMEL-MailScanner: Found to be clean X-NISTMEL-MailScanner-SpamCheck: X-NISTMEL-MailScanner-From: edbark@nist.gov X-NISTMEL-MailScanner-Watermark: 1323378616.08748@/RzW00/hpND3nGVgpGqHCQ 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: UML packages do not match specification sections Source: Ed Barkmeyer, NIST, edbark@nist.gov Summary: The UML packages in the supporting UML document (bmi/2011-08-01.mdzip) are not consistently aligned with the sections of the specification. In particular: Sections 8.1 and 8.2 of the specification are both in the TimeInfrastructure package, but section 8.3 is not. Section 8.3 of the specification matches the Situations package, except that 8.3.7 Schedules is in a separate Schedules package. And the Situations package also contains the Tense concepts from 10.3. Sections 9.1 to 9.4 of the specification are all in the TimeScales package, but sections 9.5 and 9.6 are not. Section 9.5 of the specification matches the Calendars package, except that Gregorian calendar (9.5.5) is a separate UML package, and Internet Time (9.5.7) is a separate UML Package. Section 9.6 of the specification (Time Tables) is in the Schedules package, along with the Schedules concepts from 8.3.7. Section 10 of the specification matches the Indexicals package, except that Tense and Aspect (10.3) is in the UML Situations package. (The UML model treats tense as a relationship of situations to time, but the time concepts involved are indexical.) Section 11 of the specification matches the DurationValues package, except that month values (11.6) and year values (11.5) are in the UML Gregorian calendar package. Section 12 of the specification matches the UML TimeCoordinates Package, except that Section 12.4 is in the Gregorian calendar package. Annex D of the specification matches the UML Packages: Sequences (D.1), Quantities (D.2), Mereology (D.4), except that D.3 Scales is included in the UML Quantities package. In sum, some reorganization of the specification did not result in a consistent reorganization of the UML model. In general, the UML packaging should be made consistent with the text. But, if the Gregorian calendar package is intended to be separable, then Gregorian elements in other parts of the specification may need to be treated as exceptions. In addition, one can argue that the 'time table' and 'schedule' concepts are closely related and should be together in the specification. I do not recommend the use of nested UML Packages. It complicates the UML model and all references to the UML concepts defined in it. -- 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 16869 - UML packages do not match specification sections X-KeepSent: 2B1CC9FB:51B0E9CF-85257A28:004F6B18; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011 From: Mark H Linehan Date: Mon, 25 Jun 2012 10:28:38 -0400 X-MIMETrack: Serialize by Router on D01MC604/01/M/IBM(Release 8.5.3 ZX853HP5|January 12, 2012) at 06/25/2012 10:28:39 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 12062514-1976-0000-0000-00000E8D6518 This is the first complete draft of the proposed reorganization of the specification. -------------------------------- Mark H. Linehan STSM, IBM Research Date-Time Issue 16869 - UML packages do not match specifications2.doc ubject: Date-Time Issue 16869 - UML packages do not match specification sections X-KeepSent: 41E2A5A1:F0514A83-85257A2D:007E5977; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011 From: Mark H Linehan Date: Sat, 30 Jun 2012 20:01:22 -0400 X-MIMETrack: Serialize by Router on D01MC604/01/M/IBM(Release 8.5.3 ZX853HP5|January 12, 2012) at 06/30/2012 20:01:24 x-cbid: 12070100-5806-0000-0000-000016D792BF Updated per last week's discussions: -------------------------------- Mark H. Linehan STSM, IBM Research Date-Time Issue 16869 - UML packages do not match specifications3.doc To: date-time-ftf@omg.org Subject: Date-Time Issue 16869 - UML packages do not match specification sections - further update X-KeepSent: 321D2B26:92C97880-85257A2E:006E52D3; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011 From: Mark H Linehan Date: Sun, 1 Jul 2012 17:07:53 -0400 X-MIMETrack: Serialize by Router on D01MC604/01/M/IBM(Release 8.5.3 ZX853HP5|January 12, 2012) at 07/01/2012 17:07:54 x-cbid: 12070121-5806-0000-0000-000016DB2B80 Sorry to hit the FTF several times with updates to the same issue resolution. This one adds URIs for each vocabulary, and 'markers' for the vocabulary ends that are required by Donald's software. We use that software to produce the machine-readable file from the text. Apparently it is up to us to pick the date within the URL, so I picked the date that the FTF report is due - 2012-09-21. -------------------------------- Mark H. Linehan STSM, IBM Research Date-Time Issue 16869 - UML packages do not match specifications4.doc