-
Key: DTV11-85
-
Legacy Issue Number: 19175
-
Status: closed
-
Source: General Electric ( Mark Linehan)
-
Summary:
Here's some more typos:
9. In clause 9.5, in the entry for "duration value set equals duration", the third synonymous form has the same wording as the primary form of the verb concept.
10. In clause 16.4, in the primary verb form for "occurrence1 is between occurrence2 and occurrence3", the word "and" should use verb style, rather than keyword style. In the first synonymous form, the word "and" should use verb style, rather than keyword style. The second and third synonymous forms are identical; one should be removed.
11. In Annex D.2.3, in the entry for "sequence has index origin position", the first Necessity should read "Each sequence has at most one index origin position.", rather than "Each sequence has at most one index origin value.".
-----------------------------
Mark H. Linehan
STSM, IBM Research
----- Forwarded by Mark H Linehan/Watson/IBM on 01/02/2014 04:04 PM -----From: Mark H Linehan/Watson/IBM
To: dtv-rtf@omg.org,
Date: 12/30/2013 05:06 PM
Subject: Fw: DTV typos--------------------------------------------------------------------------------
Here's another typo:
8. In clause 16.4, in the entry for "individual situation kind has occurrence interval", the Necessity "The individual situation kind has exactly one occurrence" should be "Each individual situation kind has exactly one occurrence interval".
-----------------------------
Mark H. Linehan
STSM, IBM Research
----- Forwarded by Mark H Linehan/Watson/IBM on 12/30/2013 05:00 PM -----From: Mark H Linehan/Watson/IBM@IBMUS
To: dtv-rtf@omg.org, issues@omg.org,
Date: 12/30/2013 11:29 AM
Subject: DTV typos--------------------------------------------------------------------------------
I've noticed several more typos in the DTV spec (formal-13-08-01.pdf):
1. In clause 11.2, in the entry for "Gregorian year of days scale", the first Necessity should be a Note.
2. In clause 11.2, in the entry for "Gregorian month of days scale", the first Necessity should be a Note.
3. In clause 16.7, in the entry for "time interval1 to occurrence specifies time interval2", "occurrence to time interval1 specifies time interval2", "occurrence1 to occurrence2 specifies time interval", "time interval1through individual situation kind specifies time interval2", the word "The" in the Necessity caption should have keyword style.
4. In clause 17.1, in the entry for "time table", the use of the keyword "must " in the first Necessity is not consistent with SBVR-SE style because modal keywords are not used in Necessities and Possibilities. The Necessity should read "Each time table has at least one table entry.".
5. In clause 17.2, in the entry for "schedule is for general situation kind", the first Necessity should read "Each schedule is for..." instead of "A schedule is for...".
6. In Annex D.2.1, the modal keyword "may" is used in the Possibilities for "sequence has first position" and "sequence has last position". In SBVR-SE style, modal keywords are implicit, not explicit in Possibility and Necessity statements.
7. In Annex D.2.3, the Necessity for "sequence has index origin position" should read "Each sequence has at most one index origin position." instead of "Each sequence has at most one index origin value.".
-----------------------------
Mark H. Linehan
STSM, IBM Research -
Reported: DTV 1.0 — Mon, 6 Jan 2014 05:00 GMT
-
Disposition: Resolved — DTV 1.1
-
Disposition Summary:
All identified typographical errors will be corrected. Errors in SBVR entry subtitles will also be corrected.
This issue resolution incorporates other changes that only repair typographical errors. -
Updated: Fri, 6 Mar 2015 20:58 GMT