Issue 17595: 'Time Span' is defined twice (date-time-ftf) Source: International Business Machines (Mr. Mark H. Linehan, mlinehan(at)us.ibm.com) Nature: Uncategorized Issue Severity: Summary: There are two glossary entries for the concept 'time span', one in clause 16.4 and one in clause 17.2. The two glossary entries are not identical, nor do they define coextensive concepts. Resolution: Revised Text: Actions taken: September 17, 2012: received issue Discussion: End of Annotations:===== MG Issue No: 17595 Title: 'Time Span' is defined twice Source: Mark H. Linehan, IBM, mlinehan@us.ibm.com Summary: There are two glossary entries for the concept 'time span', one in clause 16.4 and one in clause 17.2. The two glossary entries are not identical, nor do they define coextensive concepts. Date: Fri, 21 Sep 2012 18:08:15 -0400 From: Ed Barkmeyer Reply-To: Organization: NIST User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: OMG DateTimeVoc FTF Subject: DTV Issue 17595: two different roles named 'time span' X-NISTMEL-MailScanner-Information: Please contact postmaster@mel.nist.gov for more information X-NISTMEL-MailScanner-ID: q8LM8K8Z026688 X-NISTMEL-MailScanner: Found to be clean X-NISTMEL-MailScanner-SpamCheck: X-NISTMEL-MailScanner-From: edbark@nist.gov X-NISTMEL-MailScanner-Watermark: 1348870104.94129@3+TNE3lPOUvdjuJQwUo5Kw X-Spam-Status: No The summary of Issue 17595 is: There are two glossary entries for the concept 'time span', one in clause 16.4 and one in clause 17.2. The two glossary entries are not identical, nor do they define coextensive concepts. Is this a problem? 16.4 defines the '_time span_ /of/ _situation model_'. 17.2 defines '_time span_ /of/ _schedule_'. The expression 'time span' is therefore a term in two different attributive namespaces. That is, it is two different terms, according to SBVR. No time interval is a 'time span'; it can only be the 'time span' /of/ something. The expression 'time span' is just part of the noun form of two different verb concepts. So I don't see a problem here. In the UML model the 'time span' term is scoped by the class (general concept) that owns it. In CLIF, the attributive role is expanded to the verb concept, just as it is in SBVR clause 9. That is, the time span of situation model xxx is rendered as "the variable ti that ranges over time interval and that is restricted by ("situation model has time span" xxx ti)". In a similar way, in OWL the reference is to the range of the objectProperty situation_model_has_time_span. (The SBVR presentation of 'attributive roles' is confusing, if not confused. Following SBVR practice, the two entries for 'time span' are actually introducing "noun forms" of the subsequent verb concepts, and calling them simply "roles" without specifying the namespaces. This was mentioned in an SBVR issue on the "noun form of a verb concept", which does not correspond to actualities!) -Ed -- 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 "The opinions expressed above do not reflect consensus of NIST, and have not been reviewed by any Government authority." From: "Barkmeyer, Edward J" To: Mark H Linehan , "sbvr-rtf@omg.org" Date: Mon, 24 Sep 2012 15:59:41 -0400 Subject: RE: DTV Issue 17595: two different roles named 'time span' Thread-Topic: DTV Issue 17595: two different roles named 'time span' Thread-Index: Ac2ZshVIOG+GYevwQSyg2kjh8ZsVwgA2ybvJ Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US I don't understand. What appears in 16.4 and 17.2 is two has verbs with the customary SBVR mechanism for defining attributive roles, i.e., defining the role in a separate entry in front of the verb concept that actually defines them. So I don't understand what 'syntax' you are proposing to change. There are two glossary entries because there are two different concepts. I think you are talking about a more general "role" ? called 'time span' that is not an attribute of anything in particular and thus cannot be very well defined. The only place SBVR does this is in defining 'minimum cardinality' and 'maximum cardinality'. And in both of those cases, the definition is exactly the same for all (both) usages, because they are both attributes of 'set' in all usages. There is only one concept, but it appears in two fact types, one of which is merely a refinement of the other. That is, 'at most n' and 'exactly n' make use of the same concept of 'maximum cardinality'. 'Exactly n' is a narrower constraint than 'at most n'. (and similarly for 'minimum cardinality') That is not the case with 'time span' -- one is an attribute of situation model and the other is an attribute of schedule, and they have no definition in common. -Ed -- Edward J. Barkmeyer Email: edbark@nist.gov National Institute of Standards & Technology Manufacturing Systems Integration Division 100 Bureau Drive, Stop 8263 Office: +1 301-975-3528 Gaithersburg, MD 20899-8263 Mobile: +1 240-672-5800 ________________________________________ From: Mark H Linehan [mlinehan@us.ibm.com] Sent: Sunday, September 23, 2012 1:37 PM To: sbvr-rtf@omg.org Subject: Re: DTV Issue 17595: two different roles named 'time span' Ed, There should be no problem with 'time span' being an attributive role of both 'situation model' and 'schedule'. The problem is that there are two glossary entries for 'time span' as concept type: role. One is in clause 16.4 just before 'situation model has time span'. The other is in clause 17.2, just 'schedule has time span'. And the two glossary entries have different definitions! My proposed solution: rework the Definition captions associated with each 'time span' glossary entry and move them to the associated 'has' verb concept, as second definitions for each. Then delete the second 'time span' glossary entry. This is just a syntactic fix. ----------------------------- Mark H. Linehan STSM, IBM Research From: Ed Barkmeyer To: OMG DateTimeVoc FTF , Date: 09/21/2012 06:09 PM Subject: DTV Issue 17595: two different roles named 'time span' ________________________________ The summary of Issue 17595 is: > There are two glossary entries for the concept 'time span', one in > clause 16.4 and one in clause 17.2. The two glossary entries are not > identical, nor do they define coextensive concepts. Is this a problem? 16.4 defines the '_time span_ /of/ _situation model_'. 17.2 defines '_time span_ /of/ _schedule_'. The expression 'time span' is therefore a term in two different attributive namespaces. That is, it is two different terms, according to SBVR. No time interval is a 'time span'; it can only be the 'time span' /of/ something. The expression 'time span' is just part of the noun form of two different verb concepts. So I don't see a problem here. In the UML model the 'time span' term is scoped by the class (general concept) that owns it. In CLIF, the attributive role is expanded to the verb concept, just as it is in SBVR clause 9. That is, the time span of situation model xxx is rendered as "the variable ti that ranges over time interval and that is restricted by ("situation model has time span" xxx ti)". In a similar way, in OWL the reference is to the range of the objectProperty situation_model_has_time_span. (The SBVR presentation of 'attributive roles' is confusing, if not confused. Following SBVR practice, the two entries for 'time span' are actually introducing "noun forms" of the subsequent verb concepts, and calling them simply "roles" without specifying the namespaces. This was mentioned in an SBVR issue on the "noun form of a verb concept", which does not correspond to actualities!) -Ed -- 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 "The opinions expressed above do not reflect consensus of NIST, and have not been reviewed by any Government authority." To: date-time-ftf@omg.org Subject: DTV Issue 17595 - 'Time Span' is defined twice X-KeepSent: CDF2D8C4:E0B516B9-85257A89:006AEAFF; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011 From: Mark H Linehan Date: Sun, 30 Sep 2012 15:29:11 -0400 X-MIMETrack: Serialize by Router on D01MC604/01/M/IBM(Release 8.5.3FP2IF1|July 25, 2012) at 09/30/2012 15:29:11 x-cbid: 12093019-5806-0000-0000-00001A1E6041 Proposed resolution: ----------------------------- Mark H. Linehan STSM, IBM Research Date-Time Issue 17595 - Time Span.doc Disposition: Resolved OMG Issue No: 17595 Title: 'Time Span' is defined twice Source: Mark H. Linehan, IBM, mlinehan@us.ibm.com Summary: There are two glossary entries for the concept 'time span', one in clause 16.4 and one in clause 17.2. The two glossary entries are not identical, nor do they define coextensive concepts. Resolution: Delete the second 'time span' entry and combine the definitions of both glossary entries into the associated 'has' verb concepts. Revised Text: In clause 16.4, replace the Definition in the 'time span' glossary entry: Definition: the smallest time interval that contains the occurrence intervals of all the occurrences in a given situation model . with: General Concept: time interval In clause 16.4, add this Description immediately after the Definition in the 'situation model has time span' glossary entry: Description: The time span is the smallest time interval that contains the occurrence intervals of all the occurrences in a given situation model. In clause 17, delete the entire glossary entry for 'time span'. In clause 17.2, add this Description and Note immediately under the Definition for 'schedule has time span': Description: The time span is the smallest time interval that includes the time intervals of all individual situation models in the schedule. Note: The time span is the .convex hull. of a schedule. Disposition: Resolved i