action: open in a browser https://www.omg.org/spec/DTV/20160301/sbvr.xml
reaction: This page contains the following errors:
error on line 782 at column 3: Encoding error

The first paragraph of 11.4 contains: "the names of calendar periods are
homonyms. The multiple meanings of such names can be understood by considering that each such name can refer to a set of
time points collectively, to any member of such a set, or to a unique time point on a finite time scale." And the following example says similar things.
This is confused. A term like January refers to either the time point (Gregorian month of year 1) or to one or more time periods/intervals that are instances of it. It is never a set of time points. The January of each year is a different time interval, but the same time point.
Further, the subsequent text uses Tuesday as an example, while the subclause is about Gregorian months.

Correct the wording of 11.4 to describe named time points

The cited text of 11.4 is misleading. A named time point, like any other time point designation, is usually used to refer to the corresponding time intervals. In some usages, it refers to the time point itself. The text is corrected to say this.
Considering the placement of the text in 11.4, the example of Tuesday is replaced by April.
Note also that the title of the section is inaccurate - the section is about Gregorian months of year.

Clause 10.5 (Time zones) deals entirely with time-of-day issues and defines important time-of-day concepts. It defines time zones as distinct calendars, but that does not make the content about calendars in general. The entirety of the clause should be moved to clause 13 (time of day).

Move clause 10.5 to clause 13 and address DTV13-105

The RTF agrees that the content of clause 10.5 (time zones) is more appropriate to clause 13 (time of day). The text of 10.5 is also somewhat disorganized in presenting the concepts. The text is moved and reorganized with minor editorial changes. It was noted that one concept in the UML diagrams (time of day scale) is not documented in the text, and one concept used in the text (locale) is not in the diagram. These disalignments are also corrected.

The RTF agrees with Issue 13-105, that 'time offset' is not just a role of duration – it is the characterization of a difference between a calendar and UTC that involves a direction (ahead of or behind UTC) and a duration. The verb that introduces the term – calendar1 differs from calendar2 by time offset – actually refers to a role of 'duration' but 'differs from' is an ambiguous wording. It is replaced by 'calendar1 is duration ahead of calendar2', with the same synonymous forms using + and -. 'time offset' then characterizes the difference as 'ahead' or the inverse 'behind' together with the duration. The resolution of Issue 13-105 revises the concept ‘time offset’ and corrects the formal text that uses it.

Because Issue 13-105 modifies the text being moved, the revised text is included in the resolution of issue 13-101.

The second sentence of Clause 14.1 reads: "Many time dissemination services are available; see ftp://ftp2.bipm.org/pub/tai/scale/TIMESERVICES/timeservices.pdf."
The URI is out-of-date, but some time dissemination practices are just uses of Internet Time, and the previous sentence mentions that. The link should be to the IETF specification.

In 14.1, remove the sentence about time dissemination

The NTP reference should be to the IETF specification. Time dissemination services is not a concern of the DTV specification, and that sentence is removed.

Clause 10.5 defines standard time to be any local calendar that is specified as an offset from UTC. But British Summer Time, for example, is UTC+0100, and it is not typically considered to be a "standard time". The standard time for the UK is GMT (=UTC). Standard time is a specific local calendar that is specified as a UTC offset that is approximately consistent with local sun time.
Similarly, local time is not about whether it has an offset from UTC, but rather the calendar that is in effect for a given place at a given time.

Correct the definitions of standard time and local time

The definitions of 'standard time' and 'local time' given in clause 10.5 match the definitions given in the ISO 8601 "source". While these may not be the meanings some users expect, there is no good reason to invent other definitions for the terms.

Clause 10.5 defines time offset to be a role of 'duration'. But the intent of time offset is to describe the difference between a local time and UTC time at a given instant. That difference is only a duration if we agree that there can be negative durations. Otherwise that difference must be described as a duration and a direction. The latter is what the introductory text describes.

Merge to Issue DTV13-101

The RTF agrees that 'time offset' is not just a role of duration – it is the characterization of a difference between a calendar and UTC that involves a direction (ahead of or behind UTC) and a duration. The verb that introduces the term – calendar1 differs from calendar2 by time offset – actually refers to a role of 'duration' but 'differs from' is an ambiguous wording. It is replaced by 'calendar1 is duration ahead of calendar2', with the same synonymous forms using + and -. 'time offset' then characterizes the difference as 'ahead' or the inverse 'behind' together with the duration.

Because Issue 13-101 moves the text in question, the revised text is included in the resolution of issue 13-101.

Many of the UML classes defined in Clause 8 have several UML operations.
While it may be easy to guess the relationship between the operations and the associations, there is no text that defines these operations, or even mentions their relationship to the associations. In each case, these operations should be formally documented under the "glossary entry" for the class. (The description in clause 5.2 is helpful, but it alone does not meet the documentation requirement. It just says that each such operation is somehow related to some defined association.)

Clarify UML operations construction in 5.3

Clause 5.3 documents the derivation of the UML classes, associations, attributes, association end names, and operations from the SBVR glossary entries. The UML model is not otherwise explicitly documented at all in the text. Such documentation would be largely redundant with the glossary entry text. The RTF therefore sees no need to document the UML operations separately.

There are some minor inaccuracies in the wording of clause 5.3, and they are corrected here.

Many Date Time Vocabulary concepts have very formal definitions that are hard for one of the target audiences – business users – to understand. For example, the definition of the Allen Relationship 'time interval1 is properly before time interval2' reads:
Definition: the time interval1 is before the time interval2 and the time interval1 is before a time interval3 and the time interval3 is before the time interval2

This formal definition provides a precise meaning for use by reasoning engines, but it takes even an expert human awhile to understand. Business users have little chance of understanding it.

The solution proposed by this Issue is that this and every other Date Time Vocabulary concept should have an informal definition or description that explains the concept to the business user audience. Note that SBVR permits a concept to have multiple definitions, so adding informal definitions need not displace any existing formal definitions.

Improve wording for Allen relations

There are multiple aspects to this issue. One is whether SBVR Structured English can be used to convey the needed precision in time concepts and still be intelligible to business persons. A second is about the choice of SBVR SE phrasing in the actual Definitions – can they be made clearer to business readers? The third question is: Which of the concepts and definitions in DTV is even useful for business readers, as distinct from the “ontology” audience that uses the CLIF and OWL versions?
As stated, the issue is a recommendation for general editorial changes without guidance. The RTF agrees that the text of the definitions of the Allen relations can be improved, and the proposed text does that. But the text even says that the Allen relations are theoretical, and the more common business relationships are defined in the next section.
Specific issues should be raised for sections that are important to business persons and hard to follow.

In clause 8.2.4, in the Definition of 'time interval1 ends during time interval2', the last 'time interval' in the definition should have the subscript "2".

Replace missing subscript on 'time interval1 ends during time interval2'

Editorial repair.

The Date-Time Vocabulary has multiple concepts about amounts of time (duration, duration value), and locations in time (time interval, time point, time point set, time period, time coordinate), but very little guidance as to which of these concepts should be the basis for application business vocabularies. DTV should add a rationale section or additional commentary in Annex C to explain which concepts should be used for what purposes in business vocabularies.

Table C.1 has a reference to a concept 'date' that does not exist.

Issue does not reflect revision of Annex C

This issue was substantially addressed in v1.2 with the rewrite of Annex C as the Guidelines for Business Use. Further work on that Annex may be appropriate, but only if issues that cite specific weaknesses are raised.

In Annex D.3.2, in the entry for "base unit", the first caption should be "Definition" instead of "Concept Type".

Repair paragraph tags in D.3.2

The Issue is out of date. The paragraph tags in D.3.2 are correct in v1.2.

These errors/typos occur in Annex D.2.6 “Ordinals”, of the dtc/2015-03-02 version of DTV 1.2:

· The synonym for “eleventh member” is given as “third”; it should be “eleventh”.

· All the ordinals are given as “General Concept: thing”; they should be “General Concept: member” for consistency with the names of these ordinals. “First member” in Annex D.2. should also be “General Concept: member”. (Comment: “member” is “General Concept: thing” in D.2.2. Making the ordinals “General Concept: member”, clarifies that the ordinals only apply to things that are members of unique sequences, not to things in general.)

Clarify the "Nth member" concepts in D.2.6

'member' is a 'role', it is not a 'general concept', so it cannot be the text of a General Concept paragraph. But the concept 'second member' does specialize the (role) concept 'member', which is the point of the issue. The text is changed to state this.

The clarification concern is valid. The problem is that 'second member' itself has no Definition; and is separated in the text from the verb concept that implicitly defines it. The text is reorganized to place the role declaration immediately before the verb concept to supply a Definition.

In clause 11.2, Figure 11.1 contains a 'Gregorian week' class and Figure 11.2 contains a 'Gregorian week of year' class. These no longer exist. The corresponding 'ISO week' and 'ISO week of year' are in clause 12.

Delete all 'Gregorian week elements from the UML model

See attached file DTV13-69.docx

In clause D.4, in the entry for 'part1 overlaps part2', we find:
Synonymous Form: part2 overlaps part1
Definition: There exists a part3 that is part of the part1 and the part3 is part of the part2.

There are two problems here:
1) 'part' is not a general concept, and the range of the roles part1 and part2 is not specified. The CLIF says they are both 'thing'. So the fact type should probably be 'thing1 overlaps thing2'. Similarly, we have no idea what a 'part3' might be. The definition should read: 'there exists a thing that is part of thing1 and is part of thing2'.

2) part2 overlaps part1 is not a synonymous form of 'part1 overlaps part2'. It is the same form. The main entry defines the symbol 'overlaps' between two instances of type 'thing'. Since the placeholders do not appear in a use of 'overlaps', it makes no difference what their spelling is. What is intended here is in fact an "axiom of symmetry":
Necessity: If a thing1 overlaps a thing2, then the thing2 overlaps the thing1.

Similarly, in clause 8.2.1, in the entry for 'time interval1 overlaps time interval2', we find:
Synonymous Form: time interval2 overlaps time interval1
This is the same problem (s). 'time interval2 overlaps time interval1' is the same form as 'time interval1 overlaps time interval2' because the symbol and its context (the ranges of the roles) are the same. This should also be stated as an axiom:
Necessity: If a time interval1 overlaps a time interval2, then the time interval2 overlaps the time interval1.

Replace the synonymous forms for 'overlaps' with necessities.

As described in the Issue, x1 overlaps x2 and x2 overlaps x1 are the same form. In clause 8.2.1 replace the synonymous form: time interval2 overlaps time interval1 with a Necessity: If time interval1 overlaps time interval2 then time interval2 overlaps time interval1. And similarly for part1 overlaps part2 in D.4.

The indefinite time intervals are defined in Clause 16 in terms of occurrences that are not defined. The idea of indefinite time intervals should be in Clause 8, where it is needed for indefinite time point sequences. By defining Eternity to be the time interval that includes all time intervals, and primoridality to start Eternity and perpetuity to end Eternity, the concept can be divorced from occurrences and included in clause 8.

Define the indefinite time intervals in terms of time interval relationships and move them to Clause 8.

The RTF agrees that the indefinite time intervals should be defined in clause 8, independently of the occurrence concept. The proposed approach for ‘eternity’ is essentially correct, but the concept ‘primordiality’ should be a unique time interval that starts Eternity.

DTV v1.2 changed the model of the 'week' concept to distinguish the 'ISO week' concept. Several vestigial uses of 'week' in clause 10 should be corrected:

• In clause 10.4, in the entry for finite time scale subdivides time point kind', the Note refers to 'day of week', which should be 'ISO day of week'.

• In the introduction to clause 10.6, the example 'week 41 day 6' should be 'ISO week of year 41 ISO day of week 6' (really?, this wording has no business use).

• In 10.6.3, under atomic time coordinate, the example "calendar week 53" should probably be "ISO week of year 53".

• In 10.6.3, under 'atomic time coordinate uses index', the references to 'week of year' and 'day of week' should use "ISO".

• In clause 10.7 (Time sets), the introduction twice refers to 'week of year' and 'weekday of year', which should use "ISO"

• Clause 10.10 makes several references to the "year of weeks" and "week-based year", which should use "ISO"

Also, the concept 'ISO weekday of year' in clause 12 appears to mean 'day of ISO week-based year', but that characterization in so many words does not appear in the description of the time scale or the time point. The time coordinate may have the (compound) week/day form described in clause 18, or the ungainly form noted above, but the time point only has an index, and the term 'weekday' (without the solidus) is misleading.

Correct references to 'week' terms in Clause 10

Correct clause 10 as indicated. Revise introduction to clause 10.7. Add a Note to 'weekday of year' in Clause 12.

Specification: Date Time Vocabulary

Version: v1.2

Title: missing OCL

Summary:

The following DTV axioms have SBVR and CLIF formulations but no OCL formulation

1. In clause 8.3.2, under ‘duration = duration plus duration’, in Axiom V.1

2. In clause 8.3.2, under ‘duration = number times duration’, in Axiom V.8, first Corollary

3. In clause 8.3.2, under ‘duration = number times duration’, in Axiom V.8, 2nd Corollary

4. In clause 8.3.2, under ‘duration = number times duration’, in Axiom V.8, 3rd Corollary

5. In clause 16.3, under ‘occurrence occurs for occurrence interval’

6. In Annex D.2.3, under ‘sequence has index origin value’

7. In Annex D.3.1, under ‘quantity has quantity kind’

Note: This is a follow-on to Issue 19462

Supply missing OCL Definitions and Axioms in Clauses 8, 16, Annex D

The missing OCL text is added. Some entries are reworked to align the formulations. Note that some of the CLIF Axioms only state that the arguments of particular predicates have particular types, which is conveyed by the UML signatures of the operations for OCL.

Clause 8.2.5 says it is about "time interval sum" and it introduces the concept "time interval plus time interval equals time interval" along with supporting axioms. But it apparently also introduces the concepts "time interval to time interval specifies time interval" and "time interval through time interval specifies time interval", which conceptually have nothing to do with "sum". Further, the UML diagram in Figure 8.8 only shows the 'to time interval' form.

The merger of these two topics is caused by mis-characterizing "time interval through time interval specifies time interval" as a synonymous form for "time interval plus time interval equals time interval". The two verb concepts are co-extensive, but they are different concepts. The time interval that is specified by t1 through t2 is the same time interval as the sum of t1 and t2 as the sum is defined, but its definition is more like "t1 starts t3 and t2 finishes t3". And 't1 to t2' is a relative of 't1 through t2', and its definition is not related to the sum at all.

The two concepts 't1 to t2 specifies t3' and 't1 through t2 specifies t3' should not be in 8.2.5 at all. They should be in a separate section, as another way of specifying time intervals in terms of other time intervals – one that is actually used by business people, while the verbs in 8.2.5, 8.2.6 and 8.2.7 are not.

Make 'time interval1 through time interval2 specifies time interval3' a separate concept

The task force agrees that the ‘sum’ of two time intervals, and the time interval defined by ‘time interval1 through time interval2’ are distinct. The concepts are not even co-extensive, since the latter requires time interval1 to start no later than time interval2.
At the same time, the concept ‘time interval1 to time interval2’ is unrelated to ‘sum’. Clauses 8.2.5 (sum), 8.2.6 (complement), 8.2.7 (intersection) all define means of constructing a time interval from two others. ‘time interval1 to/through time inteval2’ is a fourth means, and should be a separate section (8.2.8).

The following Synonymous Forms have incorrect character styling: although the roles appear to have ‘term’ styles, in fact they are styled in some other way:

time point2 follows time point1

time point2 is next after time point1

time point starts time interval

time point ends time interval

time scale of calendar

time scale on calendar

Repair the formatting of the cited entries

Of the cited synonymous forms, all but one were apparently corrected in the formal text of version 1.2. The exception: "time point ends time interval" is repaired here.

Note: this was corrected by in Ballot #1, but subsequently confused by inconsistencies in the v1.2 convenience documents.

In clause 8.6, in the entry for 'time interval starts on time point', the Synonymous form reads: 'time point2 starts time point1', which involves roles that are not in the primary wording. And the same error occurs in 'time interval ends on time point'.

The cited text does not appear in 8.6 in v1.2

The issue is a consequence of a discrepancy between the convenience documents for v1.2. The formal v1.2 specification (formal/15-11-02) does not contain the cited text.

The first paragraph of clause 11.2 reads: "The Gregorian calendar is standardized in ISO 8601, ..." The Gregorian calendar was standardized for international commerce by the Convention du Metre. ISO 8601 only standardizes certain representations of time coordinates.

Revise 11.2: replace ISO 8601 with the Convention du Metre

The issue is correct. In the text of 11.2, replace "ISO 8601" with "the Convention du Metre".

This issue started with a complaint about the way that misuse of Structured English in various Necessity statements that are of the form “<time point> has <number> of <class”. Then (on 1 Jan 2014) I noticed an additional problem: typically, the “<time point> of <class>” verb concept is missing, so I proposed adding a verb concept “time period has time point”.

It turns out that this solution is insufficient. It treats a Necessity such as “April has 30 of ‘Gregorian day of month‘” as though it meant “April has 30 of ‘time point‘” – which loses the semantic that the 30 time points that make up April are specifically “Gregorian day of month” time points. (Note: the fact that this is not valid Structured English is the main point of issue 19172).

To fix this, we need instead to add the following verb concepts:

· Gregorian year has Gregorian day of year

· Gregorian year has Gregorian month of year

· Gregorian month of year has Gregorian day of month

We also need to change the definitions of the Gregorian months to make clear that they are such. For example, for January, instead of the definition “time interval that has duration 31 days and that starts an instance of a Gregorian year”, we should use “Gregorian month of year that has duration 31 days and that starts an instance of a Gregorian year”. With this change, “January” is still a ‘time interval’ since a ‘Gregorian month of year’ is ultimately a ‘time interval’.

Part of the Issue is resolved by Issue 13-25; the rest is incorrect.

By substituting the actual “bindable targets” given in the Necessity for the corresponding placeholder terms in the Definition of ‘time point has number of time point kind’, the Necessity
“April has 30 of Gregorian day of month”
is defined by clause 10.4 to mean:
the time point kind ‘Gregorian day of month’ has a finite time scale (Gregorian month of days) and there is a time point sequence that is on the finite time scale and that corresponds to each instance of April, and the first time point of the time point sequence is the index origin member of the finite time scale (Gregorian day of month 1), and 30 is the cardinality of the time point sequence.
In the above, the parenthetical expressions can be inferred from other necessities for the Gregorian month of days time scale.
Thus, interpretation defined by clause 10.4 is not “April has 30 of time point”, as the issue avers. It is rather a description of the subdivision of April into Gregorian day of month time points. This text has been revised and clarified by the resolution to Issue 19172 (now 13-25), and the proposed additions are unnecessary.

The last recommendation in the issue is a consequence of a well-known problem with the SBVR-style definitions of concepts that are instances of concept types. The SBVR definition of a concept describes the properties of each of its instances, that is, the Definition of ‘January’ describes each January. The instances of the concept January are time intervals, not Gregorian months of year (as the issue proposes). So the existing definition is consistent with SBVR practice; the proposed definition is not. The concept ‘January’ is itself an instance of Gregorian month of year, and that relationship is described by the Necessity that follows the Definition.
Thus, no technical change is appropriate. It is not clear to the RTF what editorial notes could be added to avoid creating the misconceptions in the issue. Therefore, no change is proposed.

The final submission document recorded the following issue at the start of Annex F.5 "Formulating Tense and Aspect":

This section needs to be updated to reflect the term "situation model" as used in this specification, instead of "state of affairs".

Replace 'state of affairs' with 'situation kind' in E.6 and E.7

The task force agrees. Note that the Tense and Aspect section is now E.6. The first paragraph of section E.6 apparently captured this issue in the submission or the FTF and was overlooked. The use of 'corresponds to' in clause E.6 is incorrect – the SBVR verb is 'meaning corresponds to thing', not 'thing corresponds to meaning'; but here the DTV verb concept 'proposition describes situation kind' is clearer.

Many scale definitions in DTV include a Necessity that some time point "has <number> of <class>" some other time point. The issue here is that correct use of SBVR Structured English would employ the keyword "exactly", as in "has exactly <number> <class>". Examples of this problem occur in the glossary entries are listed below.

Also, most of these examples quote the <class>, using keyword-style quotes. But the entry for "Gregorian year of months scale" does not quote the <class>. If the documented SBVR-SE style is used, such quotes should not be used.
Gregorian year of months scale

common year

leap year

January (and all the month definitions, except the one for February)

week of days scale

day of hours scale

day of minutes scale

day of seconds scale

hour of minutes scale

minute of seconds scale

Replace 'time point has number of time point kind' with 'time point subdivides into time point'

The Necessities described in the issue use the verb concept ‘time point has number of time point kind’, which is defined in clause 10.4. In that usage, the <number> value plays a verb concept role, and is defined to be the cardinality of a time point sequence. The <number> is not a quantification (which would use ‘exactly’).
The RTF agrees that the verb concept ‘time point has number of time point kind’ is unusual syntax for a quantifiable relationship between time points, and that the markup of the usages is incorrect. The verb concept is really a description of the structure of a subdivision, as the existing Note for the verb concept says. This revision improves the text by replacing the strange support verb concept with a simpler one, and by correcting all the previous uses.

DTV has many verb concepts with three roles, where one particular role is the "result" of the verb concept. Examples are 'time interval1 plus time interval2 is time interval3', 'time interval1 to time interval2 specifies time interval3' (clause 8.2.5), 'time interval1 starts time interval2 complementing time interval3' (clause 8.2.6), 'duration3 equals duration1 plus duration2' and 'duration1 equals number times duration2' (8.3.2), etc.

Proposal: add to these verb concepts a new Necessity that identifies which role contains the "result". For example, "Necessity: Each number times each duration2 is exactly one duration1."

Motivations: (1) Add semantic knowledge that is currently not provided by the Date-Time Vocabulary; (2) When mapping DTV to OWL, this would provide the information needed to identify which role is the functional result of the verb concept. Specifically, the object property for the "result" role could be marked as an "functional object property" of the reified class that represents the 3-role verb concept.
-----------------------------

Add missing necessities for unique results

The verbs in question are about verbs that specify unique time intervals and durations in various ways. It is important for the UML and CLIF functions that the uniqueness is stated. The uniqueness is stated for all of the basic operations on time intervals. Stating the uniqueness for time interval1 to/through time interval2 is resolved by another issue. The remaining verbs in clause 8 and 9 are addressed here. Other minor errors in the text of clause 9.5 are corrected.

This spec should provide a simple library of datatypes for use in UML and data modeling. This is present in many physical data standards (e.g. SQL/JDBC, XML Schema) but is lacking in OMG for platform independent modeling. That would include types such as:

• Date

• DateTime

• TimeStamp

• Duration

Revise clause 18 to define datatypes

The principal DTV concepts that will be represented in software are time interval, time coordinate, duration value, occurrence, and various properties and relationships among time intervals and occurrences. The latter two are Classes and any Class implementation will be a view that incorporates only the desired associations. Time coordinate and duration value will have datatype representations. The representations of these concepts are specified in Clause 18. The text of Clause 18 is modified to describe them as 'datatypes'. In addition, the text of Clause 18 is reorganized and enhanced to reflect the 'datatype' view of representation.

In the discussion of this issue, it was noted that the Internet Time representations (described in Clause 14) are omitted from Clause 18. The corresponding text is added to clause 18 as an alternative form.

In clause 8.2.4, in the entry for 'time interval1 begins before time interval2', the Description says the start of time interval1 is before or the same as the start of time interval2, but the Definition is narrower. The Definition also requires the end of time interval1 to be before the end of time interval2. And therefore the axiom:
Each time interval begins before the time interval.
contradicts the Definition. The same problems arise with 'time interval1 ends after time interval2'

Replace 'time interval begins before time interval' with 'occurrence occurs before time interval'

The term ‘begins before’ suggests that the axiom was unintended, but the (only) uses of the verb concept in clause 16.5 and 16.10 require that the axiom is correct. So the term is misdefined and not business-friendly. The sense of the (internal) usage of ‘t1 begins before t2’ is “t1 does not start after t2”, which uses an existing verb concept, which the definitions in clause 16 can use.
The definitions in clause 16 actually rely on a verb concept ‘occurrence begins before time interval’ that does not exist, while ‘occurrence starts before time interval’ does. So, the simple solution is to rephrase the uses and delete this verb concept altogether. And the same reasoning applies to ‘ends after’.
The cited definitions in clause 16.5 also use ‘occurrence occurs before time interval’ and ‘occurrence occurs after time interval’, which are not declared, either. Those concepts have obvious business usage, and are added.
The uses of ‘begins before’ and ‘ends after’ in 16.10 are addressed by Issue DTV13-87.

Description: The "SBVR-DTV Vocabulary" in clause 4 has no namespace URI. That means it cannot be referenced across a network.

Proposed Solution: Add a "Namespace URI" caption to this vocabulary.

There is no SBVR-DTV vocabulary in DTV v1.2

The issue is long out of date. It appears to have been resolved in the FTF, and in any case, the concept 'SBVR-DTV vocabulary' was deleted in v1.2.

OMG Specification: Date Time Vocabulary

Version: 1.0

Title: Unusual use of 'that' in definitions

Summary:

In clause 8.5, the Definition of ‘time scale’ reads:

“regular sequence that each member of the regular sequence is a time point”

I see nothing in SBVR Annex C that suggests a meaning for this. I would expect:

<more general concept> that <verb> <other roles>

where the ‘that’ is the subject (role 1) of the verb concept wording;

or

<more general concept> that <subject> <verb>

where the ‘that’ is the direct object (role 2) of the verb concept wording.

But in the given definition, the verb is ‘is’, the subject is ‘each member of the regular sequence’ and the direct object is ‘a time point’. What role does the ‘that’ play? How does this delimit ‘regular sequence’?

The intention is: “regular sequence such that each member of the regular sequence is a time point”

or: “regular sequence of which each member is a time point”

or: “regular sequence (all of) whose members are time points”

The first is a style that is conventional in mathematics, but perhaps not in business usage. It is not mentioned in SBVR Annex C, but neither of the others is, either. Is this an SBVR SE problem?

Note: there are several definitions in DTV with ‘that’ playing no clear role in the delimiting verb. This is just one example of the usage.

Defer for resolution of SBVR issue

The underlying issue is the apparent limitations on the expressiveness of SBVR Structured English. All of the "misuses" of 'that' could be replaced by 'such that', if it were permissible in SBVR SE. Many could be rephrased for business users by permitting qualifier clauses that begin "of which" or "the <noun form> of which" or "whose <noun form>". A corresponding issue has been raised to the SBVR RTF. This issue is Deferred until that issue is resolved.

Currently, OCL statements are created directly in the specification document, then "stripped out" of the document into a separate file via an XSLT transform. In a further step, the OCL should be integrated into the UML model so that the model includes the OCL constraints.

Merging OCL into the UML model should be automated

The Task Force agrees that the OCL should be integrated into the UML model. However, in order to avoid duplication of effort and possible inconsistency between the formal files associated with the specification, all of the OCL text in the specification, the OCL file, and the OCL elements of the UML (XMI) file should be created from a common source by an appropriate software application. But the Task Force is unaware of any such tool for modifying the UML XMI file, and lacks the resources to create one.

OMG Specification: Date Time Vocabulary

Version: 1.0

Title: Unusual use of 'that' in definitions

Summary:

In clause 8.5, the Definition of ‘time scale’ reads:

“regular sequence that each member of the regular sequence is a time point”

I see nothing in SBVR Annex C that suggests a meaning for this. I would expect:

<more general concept> that <verb> <other roles>

where the ‘that’ is the subject (role 1) of the verb concept wording;

or

<more general concept> that <subject> <verb>

where the ‘that’ is the direct object (role 2) of the verb concept wording.

But in the given definition, the verb is ‘is’, the subject is ‘each member of the regular sequence’ and the direct object is ‘a time point’. What role does the ‘that’ play? How does this delimit ‘regular sequence’?

The intention is: “regular sequence such that each member of the regular sequence is a time point”

or: “regular sequence of which each member is a time point”

or: “regular sequence (all of) whose members are time points”

The first is a style that is conventional in mathematics, but perhaps not in business usage. It is not mentioned in SBVR Annex C, but neither of the others is, either. Is this an SBVR SE problem?

Note: there are several definitions in DTV with ‘that’ playing no clear role in the delimiting verb. This is just one example of the usage.

Currently, OCL statements are created directly in the specification document, then "stripped out" of the document into a separate file via an XSLT transform. In a further step, the OCL should be integrated into the UML model so that the model includes the OCL constraints.

Specification: DTV

Version: 1.1

Source: Ed Barkmeyer, NIST, edbark(at)nist.gov

Summary:

In the Date Time Vocabulary v1.0 specification, clause 16.5 contains the following terminological entry:

individual situation kind has occurrence interval

Definition: the occurrence interval is the time span of the individual situation kind

Necessity: The individual situation kind has exactly one occurrence

...

In the Necessity, "the individual situation kind" is intended to refer to whatever plays the 'individual situation kind' role in an instance of the verb concept (wording). But that interpretation can only be made when the Necessity appears in the verb concept entry. SBVR practice is to make the meaning of the Necessity independent of where it is stated. To be consistent with SBVR practice, the above Necessity should read:

Each individual situation kind that has an occurrence interval has exactly one occurrence.

There are several Necessities in DTV that use this dubious form of reference. Each of them should be reformulated in the SBVR location-independent style.

After consultation with SBVR experts (see SBVR Issue 19361), the RTF agrees.
There is a standard pattern to the revised Necessity statements. The pattern is:
Each <subject> that <rest of verb concept wording> <rest of Necessity>.
For the example given, the result is:
Each individual situation kind that has an occurrence interval has exactly one occurrence.
This pattern is applied to binary verbs, but it does not work well for ternary verbs, and other approaches were used to phrase those Necessities correctly.
Some of the Necessities about occurrence intervals were redundant, because they were implied by the corresponding Necessities for time intervals.
Several occurrences of the problem were omitted from this resolution because another issue corrects the same text.

Specification: DTV v1.1

Title: Confusion of Axioms and Verb Concepts for Time Interval operations

Summary:

In clause 8.2.5, there are two versions of Axiom Sum, but they seem to say mostly the same thing. There is a typo: t2+t2 in the first Axiom Sum.

The two definitions of 'time interval1 to time interval2 is time interval3' conflict – the first half of each should be a condition.

In clause 8.2.6, what starts as Axiom Start-complement becomes a verb concept declaration that somehow has a corollary. Similarly Axiom End-complement, and for Axiom Intersection in 8.2.7. This seems to be primarily a text organization problem, but there is no Necessity and no OCL Constraint for each of the Axioms.

In 8.2.5, remove the duplicate Axioms, rewrite the Definition of ‘sum’ to be the first two ‘Corollaries’, and change the multiple ‘Definitions’ and ‘CLIF Definitions’ of sum to SBVR Necessities and CLIF Axioms.
In 8.2.5 merge the two partial definitions of ‘time interval1 to time interval2 specifies time interval3’ to one corrected definition.
In 8.2.6, reorganize the axioms and corollaries to follow the definition of the verb concepts, and correct the SBVR definitions of the verb concepts.
In 8.2.7, reorganize the axioms and corollaries to follow the definition of the verb concept, and correct the definitions of the verb concept.

Specification: DTV v1.1

Title: Occurrence does not specialize Situation Kind

Summary:

In clause 16.3, in the entry for ‘occurrence occurs for occurrence interval’, the verb concept is said to have

General Concept: situation kind occurs for time interval

This would require that ‘occurrence’ specializes ‘situation kind’, which is not the case. This General Concept declaration should be deleted.

Agreed. Delete the General Concept declaration.

DTV Informative Annex G contains a set of UML diagrams of the OWL mapping of DTV. There are two problems with this Annex: (1) it is out-of-date with respect to the informative OWL ontologies that were included in DTV 1.1; (2) the set is incomplete with respect to the DTV 1.1 OWL. The diagrams should be updated or the Annex should be deleted.

Since the scope of the Annex is only the supporting concepts in Annex D, as opposed to the DateTime concepts, the RTF determined that its relevance to the DTV specification is marginal. Since it is no longer accurate even for Annex D, the RTF agrees to delete the Annex.

The term 'index origin element' is used in several places in clauses 10-13.

This term is not defined. The term defined in Annex D is 'index origin member', and it should be substituted for all occurrences of 'index origin element'.

The RTF agrees

Experience with FIBO reveals two problems with the way schedules are defined in DTV:

1. DTV schedules that are based on ad-hoc time tables reference the same situation kind for all the time table entries. This is a problem because financial contracts that use ad-hoc time tables need to specify a unique situation kind for each entry.

For example a step-up bond pays different interest rates for different periods. An ad-hoc time table can adequately represent the different periods, but each interest rate needs to be a distinct situation kind – which is not possible in the current design.

The RTF agrees with the problems raised by these issues. Their resolution requires reworking both the DTV ‘schedule’ and ‘time table’ concepts, because:
• The time table concept was created to support the schedule concept but it does not properly support the business concept of ad hoc schedules. As defined, there are two kinds of ‘time table’ (‘regular’ and ‘ad hoc’) and one kind of ‘schedule’ that has a single general situation kind.
• What is needed is two kinds of ‘schedule’, one of which associates a single situation kind with a regular time table, and the other associates multiple situation kinds, each with its own time period.
• Also, the existing ‘regular time table’ is defined as a set of time periods, when what is really needed is a starting time, a repeat count, and a repeat interval.
To solve these problems, the RTF is forced to entirely replace the original ‘schedule’ design.
The resolution of issue 19653 is merged into this solution because the two issues are intimately connected. This resolution adds the ‘schedule stub’ idea.
A verb concept 'time interval1 starts after time interval1' is added to clause 8.2.4 to simplify the definition of 'schedule has earliest time'.
A synonym is added for DTV ‘situation kind’ to match the designation of the equivalent concept in FIBO.
A verb concept "set1 is set2 plus element" is added to a new Annex D.2.6 to support the definition of regular schedules.

The definition of “situation kind1 ends before situation kind2” depends upon a verb concept “time interval1 ends before time interval2” that does not exist. Probably it should use “time interval1 ends after time interval2” – and the “situation kind” version should use the same verb symbol for consistency and clarity.

The RTF agreed to create the synonymous form for “time interval1 ends before time interval2”. The situation kind verb and the related occurrence verb are parallel and both provide the corresponding synonymous form.
A typographical error in the OCL is also corrected.

In clause 12.5, the very first Necessity reads:
" Necessity: Each week of year shares the Gregorian year of days scale with each Gregorian day of year."

According to 10.9 that means that each week of year corresponds to some time point sequence in Gregorian day of year. This is not possible. The week of year scale has 53 time points and any given Gregorian year has either 52 weeks (364 days) or 53 weeks (371 days). So, in a year that has 53 weeks, there must be at least 5 days that have no counterpart.

Even in a 52-week year, the first and last weeks of the year may include days from the prior or following year. The mapping to day of year can work, but not necessarily to days of the same year; one must consider the repeating aspect, and time point sequences that wrap around the end of the finite scale. For example, week of year 1 can convert to day of year 364, 365, 1, 2, 3, 4, 5, if the year begins on Wednesday. If that is a valid 'time point sequence' on the year of days scale, then the rules given for the conversions in clause 12.5 do not support it.

The Necessity is false. The problem is not overlap; the time point sequence can wrap around the end of the Gregorian day of year scale. The problem is that there is no single time point sequence on the Gregorian year of days that corresponds to the same time intervals as any given week of year (see 10.9). Both Necessities following Figure 12.4 are false. Some of the Examples are true, but only because they fall outside the related time sets. They have nothing to do with sharing the time scale.
Similarly, the conversion to time sets on the year of days scale is misleading, because the wrap around the end of the Gregorian year of days causes the time points to refer to time periods in different Gregorian years. So, it would be necessary to add additional rules to explain the complex correspondences of the time sets to time intervals.
The intent of this section cannot be preserved. The generic relationships between the year of weeks and the Gregorian year of days are defined by the year of weeks itself. There are no others. When the Gregorian year is given, the specific correspondences can be determined from the common Gregorian days scale, on which all of them are based.

Specification: DTV

Version: 1.1

Title: Different 'time period' concept in Annex C

Source: Ed Barkmeyer, NIST, edbark(at)nist.gov

Summary:

In the Date Time Vocabulary v1.1 specification, Annex C contains the following terminological entries:

fixed period

Definition: time period that cannot be changed

...

variable period

Definition: time period that can be rescheduled

In DTV clause 8.7, a time period is defined to be: time interval that instantiates some time point sequence

No time interval can ever "be changed" , at least not in the sense of "modified". And similarly, time intervals are unlikely to be "rescheduled". One cannot alter the time interval designated July 25 into some other time interval, nor can one meaningfully reschedule it.

The intent here seems to be that some kind of schedule entry can be changed or an event can be rescheduled, so that the entry refers to a different time interval. Therefore, the term 'time period', as used in Annex C.3, does not have the meaning given in 8.7.

SBVR Annex A.2.6 discusses verbs of change and the idea of intensional roles. But in DTV Annex C, fixed period and variable period are apparently being defined as general noun concepts. (On the other hand, 'scheduled start time' is a role that is apparently declared to be a general concept.) It may be that the business use of 'time period' IS often a role of time interval, or a schedule entry that refers to a time interval, and that the DTV use of the term is not business-friendly.

In response to Issues 18990 and 19336, the RTF decided to replace the current EU Rent example in Annex C with some examples drawn from actual business experience. So this issue is moot. Formally, it can be said to be resolved via Issue 19336

In Annex D.2.2, the entry for ‘member has index in sequence’ has a main sentential form and two Synonymous noun Forms that are followed by definitions of CLIF functions and OCL operations. The first Note reads:

The primary verb concept and the synonymous form given above are “sentential forms” that yield a Boolean result.

A verb concept is not a sentential form and it does not “yield a boolean result”. What is meant is that the verb concept wording is a sentential form, and the corresponding CLIF predicate and the OCL operation yield a boolean result. This pattern must be true of many other verb concepts in the vocabulary. It is strange that it first appears in an Annex.

The Definition can be simplified to: Some sequence position of the sequence has an index that is equal to the index and has a member that is the member.

In addition, one of the synonymous forms has inconsistent type setting.

Reword the Note to say that the CLIF predicate and the UML/OCL operation derived from the primary wording yield a Boolean result, while those derived from the noun forms return the index value or the member.
The CLIF and OCL relations for index of member in sequence, however, have no corresponding function. The only things that have indices in a sequence are those that are members of exactly one sequence position in the sequence. So the would-be ‘function’ is not defined on ‘thing’. This ‘noun form’ is therefore deleted. The only use of it is in the definition of ‘time point has index’. That definition is corrected. All the rest of the uses in the text are as ‘index of time point’.
The wording of an introductory paragraph to Section D.2 (Sequences) is somewhat misleading about the relationship of time points and time intervals to indices. It is revised.

Clause 7.17 is an overview of the specification structure. It is incorrectly placed at the end of Clause 7 (Rationale). It should be in Clause 6, following 6.3, which gives an overview of the specification.

The issue is correct. The clause was inadvertently separated from Clause 6 when the Rationale section was added. It is moved back to follow 6.3.
Note: Issue 19483 revises the Figure in clause 7.17 and some of the descriptive text. So, that revision is merged with this Issue.
Note: Issue 19574 renames the ‘Week Calendar’ package to ‘ISO Week Calendar’ and that change is included in Figure 6.1 below.

In clause 8.7, the definition of time point sequence corresponds to time interval assumes that each time point sequence has a first time point and a last time point. Further, v1.1 introduced the “time points” primordial and perpetuity to provide the means for specifying indefinite time periods. That creates time points to be the first and last time points of the time point sequences that correspond to indefinite time periods.

We must either redefine the correspondence concept or remove the possibility that there is no first/last time point. The latter simplifies the model. (Note also that most indefinite time periods DO have a last time point, we just don’t know what it is.)

The RTF agrees that indefinite time point sequences are problematic. The text should recommend the use of ‘primordial’ and ‘perpetuity’ when those are explicitly intended. But when the first or last time point of a time point sequence is simply “unknown”, that is not clearly appropriate. In any case, however, every time point sequence has a first time point and a last time point, and the text is revised to eliminate features and wording that suggest otherwise.

The final submission document recorded this issue in clause 11.6 "Mixed-Base Arithmetic":
Need to add a paragraph discussing arithmetic involving weeks and years because these are incommensurable. This depends upon defining a concept that computes the number of weeks in any particular year.

The current clause 10.10 (Mixed Base Time Arithmetic) does not address arithmetic on the weeks calendars. The revised text provides guidance. It also repairs minor typos in the text.
The text below uses terms and concepts adopted by the resolution to Issue 19645 and Issue 19574

The concepts 'time coordinate' and 'duration value' serve similar purposes: one defines how time points are represented in terms of calendars, and the other addresses how durations are represented in terms of measurement units. 'Time Coordinate' is defined as a "representation of a time point" in clause 10.6.1, which is fine. In contrast, 'duration value' is defined in clause 9.2 as being either an 'atomic' or 'compound' duration value, with the former having a number and a unit. So 'duration value' is NOT a representation.

I believe the final design of 'time coordinate' was decided late in the FTF phase after considerable discussion – and the FTF overlooked converting 'duration value' to a similar design. This should be fixed.
-----------------------------

This issue is identical in text to Issue 18991. See the resolution to Issue 18991.

In the beta-2 document, clause 10.8 defines a verb concept 'time point converts to time point sequence on time scale'. A typical use is 'Gregorian month converts to time point sequence on the Gregorian days scale', which is given as a specialization. The 'time scale' role is redundant in the main verb concept, and the use of individual concepts in the derived verb concepts is poor practice.

The RTF agrees that “on time scale” is redundant in the two conversion verb concepts. It is removed, the text preceding the verb concept entry, and the other elements of the entry, are revised to match. There is a corresponding Necessity (which is not stated): Each time point converts to at most one time point sequence/time set on any given time scale. Text in this section that refers to specializations for the Gregorian calendar is revised to refer to clause 11.
'Gregorian month converts to time point sequence on the Gregorian days scale' is a binary verb concept whose definition should be a use of 'time point converts to time point sequence'. The Definition given is a means of stating a Necessity. And this is also the case with the other two uses of ‘converts to’ in 11.8 and 11.9. Most of the perceived problem is resolved by restating the binary verb concepts more simply, e.g., Gregorian month has Gregorian days sequence, using the ‘converts to’ verb concept in the Definition, and stating the computations as Necessities.
The currently informal mechanism for relating month-of-year to day-of-year in 11.7 is formalized and used in converting a Gregorian month to Gregorian days.
Tables 11.1 and 11.2 incorrectly identify the columns as properties of Gregorian month – they are properties of Gregorian month-of-year. The table headings are corrected.
While the concepts in Section 11.8 and 11.9 are unchanged, the formulations are modified to use the simplified verbs and separate the Necessities.

The concepts 'time coordinate' and 'duration value' serve similar purposes: one defines how time points are represented in terms of calendars, and the other addresses how durations are represented in terms of measurement units. 'Time Coordinate' is defined as a "representation of a time point" in clause 10.6.1, which is fine. In contrast, 'duration value' is defined in clause 9.2 as being either an 'atomic' or 'compound' duration value, with the former having a number and a unit. So 'duration value' is NOT a representation.

I believe the final design of 'time coordinate' was decided late in the FTF phase after considerable discussion – and the FTF overlooked converting 'duration value' to a similar design. This should be fixed

The RTF agrees that neither a duration value nor a time coordinate is a ‘representation’ in the SBVR sense. Each can have more than one ‘expression’. Rather, the instances of both are “conceptual structures of meaning”. A duration value is the instantiation of a reference scheme for duration. It is a structure of meaning that is interpreted as a definite description of a duration. A time coordinate is a structure of meaning that ‘indicates’ (is interpreted as) a concept that is a category of time interval. The text and the UML model are revised to state these characterizations.
A reference scheme for the concept ‘time point’ that is actually used in Gregorian calendar time coordinates is (time point kind, index), and this is added to the reference schemes for time point.
Issue 19547 identifies additional problems with the same sections of clause 10.6. It modifies many of the same diagrams and entries. Therefore the revised text of this issue resolution is merged with that of Issue 19547.

Spec: DTV

Version: 1.0 and 1.1

Source: Ed Barkmeyer, NIST

Summary:

In Annex D.2.4 of DTV, the CLIF Definition of ‘consecutive sequence’ is:
(forall (s) (iff ("consecutive sequence" s)

(and

(sequence s)

(forall (sp1)

(if

(and

("sequence has sequence position" s sp1)

(exists (sp2)

("next sequence position succeeds sequence position" sp2 sp1)) )

(forall (x1 x2)

(if

(and

("sequence position has index" sp1 x1)

("sequence position has index" sp2 x2))

(= x2 (+ x1 1)) ))

)) )))

This is clearly incorrect. The scope of the quantification “exists (sp2)” ends with the right paren before “(forall (x1 x2))”. So the last occurrence of sp2 is not associated with the quantified variable.

The correct formulation is:

(forall (s) (iff ("consecutive sequence" s)

(and

(sequence s)

(forall (sp1 sp2 x1 x2)

(if

(and

("sequence has sequence position" s sp1)

("next sequence position succeeds sequence position" sp2 sp1)

("sequence position has index" sp1 x1)

("sequence position has index" sp2 x2))

(= x2 (+ x1 1)) ))

)))

The English definitions might also be improved by adding a Description:

A consecutive sequence is a sequence in which consecutive sequence positions have consecutive indices.

Accept the text correction

DTV 1.1 clause 4 has several errors:

1. “set includes thing”, “set has element” and “thing is in set” are listed as separate concepts. In SBVR, the first two are synonymous forms of the third.

2. “intensional definition” is misspelled “intentional definition”.

3. Many of the glossary entries have leading underscores – a minor typo.

4. The only definition given for each concept is “

”, which is not described anywhere. At least the generalization relationships among the clause 4 concepts should be captured since these relationships affect the meaning of the DTV terms that use them. Furthermore, the lack of these generalization relationships impacts the translation of DTV to OWL. Recommend adding “General Concept:” captions to the following: Concept General Concept
-------------------------------------------------------------------------------
categorization type concept type
characteristic verb concept
concept type general concept
definite description intensional definition
definition representation
extensional definition definition
general concept noun concept
intensional definition definition
meaning thing
noun concept concept
role noun concept
unitary concept noun concept
verb concept concept
verb concept role role

Issue 19463 rewrites Clause 4 to change the form to an ISO style, as opposed to an SBVR vocabulary. The list of additional terms above is incorporated in that revision.

I am concerned that the sheer size of the Date-Time Vocabulary – the number of concepts – may be a barrier to its use. So I propose that we introduce a distinction between concepts that are intended for business use, and concepts that are defined solely to support other concepts. Examples of these “internal” concepts are the various time scales (e.g. weeks scale), concepts that support calendar computations (e.g. months remainder of month value), supporting concepts (e.g. time set, time point sequence), and the Annex D fundamental concepts of sequences, quantities, and mereology. For someone coming new to the Vocabulary, I think the significant number of these internal concepts detracts from goals such as picking the right concept to use for a particular purpose, or understanding the overall design.

Specifically, I propose a new caption called “Intended Use:”, with two possible values “business” and “internal”. By default, concepts would be “business use”, so we need only add this new caption to concepts that we decide are “internal use”. This choice of default fits with the SBVR philosophy that business vocabularies should define business concepts.

When I brought up this idea during last Thursday’s phone call, Donald suggested using Notes. This is certainly possible, but I think there’s value in making this a little more formal. I think tools could use this to simplify things for business users by optionally limiting what is shown to them. Introducing an explicit caption and restricting the possible values used with the caption will work better for that purpose than free-form text in the existing Note caption. The downside of introducing a new caption is an implied need to extend the SBVR XMI format.

This resolution incorporates the resolution for issue 18990 (business users need better guidance for applying DTV concepts). The resolution adopts these measures to address these issues:
1. Adds new convenience concepts with the intent of better supporting "calendar expressions". These convenience concepts build on existing DTV infrastructure.
2. Replaces informative Annex C ("EU-Rent Date-Time Example") with a new version that:
a. Adds a discussion of how to formulate complex calendar expressions, such as "the third Tuesday of each month".
b. Provides a table of DTV concepts recommended for business use.
3. Separates Annex C into a stand-alone document intended to enable business users to apply DTV without referencing the main normative document.
Rather than identifying the intended use of business concepts within the normative text, the new table in Annex C provides a comprehensive list of business-oriented DTV concepts.

Clause 16.4 has a pair of verb concepts: “situation kind has first/last occurrence. Distinguishing between uses of these verb concepts is impossible, since they have the same verb symbol and role types. For example, does a rule that refers to “the time interval of the launching of the SpaceX Dragon” mean the first occurrence of the launching or the last occurrence?

Suggestion: make the keywords “first” and “last” part of the verb symbols rather than the role names.

The example “the time interval of the launching of the SpaceX Dragon” does not use the verb concept wording ‘situation kind has first/last occurrence’ at all. The normal use will be in the noun form: “the first/last occurrence of launching the SpaceX Dragon”, and there is no ambiguity.
Technically, the words ‘first occurrence’ and ‘last occurrence’ are part of the verb symbols. In the SBVR notation, the role ‘first occurrence’ is shown as a noun concept, but it is not a placeholder – the role term will appear verbatim in every use of the verb concept wording (in either form). The SBVR notation is confusing, but there is no ambiguity in the usage, just as there is no ambiguity between ‘set has cardinality’ and ‘set has element’. This is an SBVR notation issue, not a DTV issue.
Revised Text:
none
Disposition: Closed, No Change

The table at the end of clause 16.9 should have a caption.

The caption is supplied and the reference is corrected.

The concept ‘time of day’ in clause 10.3 is supposed to be a ‘time point kind’ per the resolution of issue 19319. If that’s correct, ‘time of day’ is missing “Concept Type: concept type”. But ‘time point kind’ has a Necessity “Each time point kind has at most one time scale” – and ‘time of day’ has multiple time scales.

It is not at all obvious, from their definitions, that clause 10.3 ‘calendar year’ and its siblings, are ‘time point kinds’. Either the definitions should make that clear, or Notes should be added to clarify these concepts.

DTV v1.1 says that ‘time point kind’ is a categorization type and thus a concept type.
The intent of ‘time point kind’ is ‘category of time point that characterizes exactly the time points on some time scale. ‘time of day’ has no time scale –not all of its instances are on any given time scale. But it also has no granularity, which violates the second Necessity in the section. All of the uses of ‘time point kind’ intend that it is associated with exactly one time scale. The definition and the verb concept should be modified to convey that intent.
With this narrower definition, ‘calendar day’ and its siblings are not ‘time point kinds’.

Please register a DTV issue for this. All of these errors show up in dtc/2014-06-02, the June 10 version of the RTF 1.1 convenience document:

1. In clause 8.2.4, under “time interval1 begins before time interval2” and “time interval1 ends after”, the OCL after the Necessity should be labelled “OCL Constraint” rather than “OCL Definition”.

2. In clause 8.2.5, under “time interval1 plus time interval2 is time interval3”, the fourth CLIF definition does not match the fourth SBVR definition.

3. In clause 8.3.3, under “time interval has particular duration”, the OCL for the first and second Corollaries of Axiom D.4 both have “OCL Definition” sections that are complete rubbish and should be removed. The “OCL Constraint” paragraphs for each of these are correct, but are missing “inv:”.

4. In clause 16.6, the OCL Definitions for ‘situation kind1 starts before situation kind2’ and ‘situation kind1 ends before situation kind2’ have the correct content, but are for ‘situation kind1 precedes situation kind2’. The first line of each definition should be reworded.

5. There are numerous places that have CLIF Definitions or Constraints without corresponding OCL Definitions or Constraints. The whole document should be reviewed to ensure consistency between the CLIF and OCL.

These entries in 8.2.4 are modified by Issue 19431.
2. Section 8.2.5 is modified by Issue 19628
3. The OCL under “time interval has particular duration” is corrected below.
4. The OCL in clause 16.6 is corrected by Issue 19714.
5. Some missing OCL is not supplied by this resolution. A separate issue is raised to address specific instances.

Specification: DTV v1.1

Title: DTV SBVR Profile is not formally applied

Source: Pete Rivett, Adaptive (for the AB)

Summary:

In order for the SBVR Profile elements to be applied to model elements in the UML model, the containing package must Apply the Profile. The DTV UML model (DTV/v1.1/dtv-uml.xml) does not include any Profile Application for the SBVR Profile

Correct the UML model. Replace Figure 7.3 to show the profile application. Add text to 7.17 to describe it.
Clause 7.17 is moved into Clause 6 by the resolution to Issue 19573. Accordingly, the revised diagram and text for this issue is merged into the text moved to clause 6.

None of the concepts listed in Clause 4 have any semantics other than “

” has no semantics. Note that the symbol “

”.

2. Duplicate the entire glossary entries of the adopted concepts from SBVR.

3. Add “General Concept” captions to these adopted concepts to capture the primary SBVR type hierarchy.

The RTF agrees that the form of Clause 4 is unsatisfactory.
SBVR does not specify what the form of an excerpt from another vocabulary, including selective adoption of terms should be. Further, the SBVR RTF does not agree that the form of Clause 4 is an appropriate form for a vocabulary. Therefore, the RTF determined that the form of Clause 4 should be consistent with ISO practice, which is to identify the source standard and cite the terms adopted from it. This requires the reader to be familiar with the source standard (SBVR), and that is not an unreasonable requirement for a reader of DTV.
Clause 4 is rewritten in ISO style, and not as an SBVR vocabulary.
Issue 19445 identifies a number of missing concepts in Clause 4, and those are incorporated in the revised text below.
The RTF also notes that the term ‘business designation’ is not an SBVR term. The title of the DTV Index should be Index of Date Time Designations.

In clause 9.3, in the entry for 'duration value equals number times duration value', we find the Necessity:

Necessity: If duration value1 is a nominal duration value and the number is fractional then the time unit of each atomic duration value of the duration value is not ‘month’ and the fractional part of the number is ¼, ½, 2/4, or ¾.

This Necessity, the four Necessities that follow, and the Note that follows them, are constraints on the number part of a nominal duration value. They are not necessities about scalar multiplication. At best all of this should be moved to 9.2.3.

This necessity, however, is unnecessarily restrictive, and appears to be utterly inappropriate. 1/3 year is 4 months, 1/6 year is 2 months, and 1/12 year is 1 month, and their multiples are multiples of months, but they are apparently "not common in business usage". Moreover, in estimating a contract, why couldn’t one multiply a standard duration estimate stated in months by 1.2 to allow for some delaying factor? And similarly, if we average seven durations stated in years, the multiplier is 1/7. Business analytics will generate fractional multiples of months and years. Why should DTV disallow them?

The Note provides the underlying motivation:

Note: This specification defines only the fractional nominal duration values ¼ year, ½ year, 2/4 year, and ¾ year because these are in common business use and they equal an integral number of months. This specification does not support any fractional 'month' duration values

because such fractions are not in common use [which is false] and because they are not equal to an integral number of years or days [which is the real reason].

Integral number of months or years are not equal to an integral number of days, either. But, per 9.2.3, they correspond to time sets (in days), while a fractional number of either does not. How important is this?

The RTF agrees that the cited Necessity is an unnecessary constraint. It is deleted, and the subsequent Note is revised.

DTV schedules that are based on regular time tables need a way to model “stubs” at the beginning and end of a regular time table. These stubs are time periods that fall immediately before or after the time span of the regular time table. They capture any special handling that is required before the start or after the end of the regular portion of the schedule.

A typical financial example is a home mortgage where payments are due at the start of each calendar month. If the mortgage is initiated in the middle of a calendar month, then there will be an initial payment, covering the period to the beginning of the next calendar month. Similarly, there may be a final payment for the days after the last monthly payment. As currently defined, a DTV schedule that uses a regular time table can model the regular monthly mortgage payments. But DTV has no provision for the “stub” initial and final payments.

These two problems should be fixed in order to make DTV schedules usable for typical financial contracts.

The RTF agrees to add the requested feature. The resolution is merged with that of issue 19652 since the latter replaces the affected clause.

Disposition: Merged (see Issue 19652)

Specification: Date Time Vocabulary v1.1

Title: what is the year of weekdays?

Summary:

In clause 12.2, the year of weekdays is defined as:

Definition: the finite time scale that has granularity 1 day and that has cardinality 366 and that repeats over the year of days scale

Since the year of days also has 366 time points, it is impossible that the year of weekdays can repeat over it. The intent must be that it repeats over the Gregorian days scale. But that also describes the year of days scale. So it is inadequate.

The Necessity provides the real delimiting characteristic:

Necessity: Each time interval that is an instance of the first time point of the year of weekdays is a Monday and is an instance of a day of year that has an index that is less than 8.

Now, if the intent is that the year of week days goes from the first Monday of one year to the Sunday before the first Monday of the following year (which is not at all clear from the above), then the scale must have 371 (7 x 53) time points, because a year that starts on a Monday ends on a Monday, and the first Monday of the following year is 6 days later.

This structure has no relationship to the year of weeks calendar, because the year of weeks starts with the Monday of the week that contains the first Thursday, and 3 times in 7 years, the year of weekdays will begin in week of year 2.

So, what (and why) is the 'year of weekdays'?

The year of weekdays is intended to provide a subdivision of the “week-based year” that is defined by the year of weeks time scale, in order to support relative time coordinates of the week-day form. For that intent, the existing Definition and Necessity are incorrect.
The ISO week-based year concept is introduced in parallel to the Gregorian year, and the weekday of year concept is then defined as a “day of ISO week-based year”.
The revised text below incorporates terms from the resolution to Issue 19574.

DTV defines the indefinite 'weeks scale' in clause 12.2 as follows:

Definition: indefinite time scale of granularity 'week' and of 'calendar week' time points

Note: No special meaning is assigned to the indices of calendar weeks on the week scale. Therefore, no index origin element or index origin value is specified for this time scale.

It then defines calendar week as follows:

Definition: time point that is on the weeks scale and that is defined by a given calendar as 7 consecutive calendar days

Note: ISO 8601 adds “starting on a Monday” to this definition. This vocabulary drops that phrase because it is culture-specific.

The net effect of these is that weeks are some sequences of 7 days that are determined by a calendar. We don’t know where any such sequence begins, or what day-of-week it begins with. There is no significance to the indices because none of them is defined to refer to any particular point in time. So, DTV does not define a specific ' weeks scale' at all.

Now, clause 12.1 says: "References to specific weeks are by week of year coordinate. This specification follows [ISO 8601] in defining 'Monday' as the first day of the week." This contradicts the above. But it does confirm that the finite 'year of weeks' scale is the only well-defined scale whose granularity is a week.

Then in 12.4 we find this entry:

year week coordinate indicates time point sequence

Definition: the Gregorian year coordinate and the week of year coordinate of year week coordinate jointly specify a time point sequence of Gregorian days

Note: Unlike other time coordinates, this one indicates a time point sequence, not a time point. This is because a year week coordinate means a sequence of calendar days rather an individual time point on some time scale.

So a 'year week coordinate' does not refer to a 'week' on any 'weeks scale' . Now, since it does not indicate any time point, a year-week coordinate is NOT a time coordinate.

The presented model is incomplete and inconsistent. The underlying model anchors a weeks scale to Gregorian days – every instance of a Gregorian day instantiates a particular day-of-week; and the relationship to Gregorian years is dependent on choosing Monday as the first day of week. It is absolutely necessary to anchor some day-of-week to some event or time interval, in order to have any idea which Gregorian days are Mondays. Somewhere in the text, it is mentioned that January 1, 2000 is a Saturday. (More useful is the fact that January 1, 1601 is a Monday.) And that, together with the assertion that Monday is the first day of a week-of-year, defines a weeks scale, except for assigning an index to the week containing January 1, 2000 (or 1601).

The underlying problem here was the unwillingness of the FTF to commit to Monday as the first day of the week, as indicated in the cited Note. The assertion in 12.1 did not represent consensus of the RTF. As a consequence, the Week Calendar Vocabulary, and most of the terms introduced in the section, are now prefixed by “ISO” to distinguish them from weeks calendars that choose other conventions for the first day of the week. At the same time, the neutral concepts ‘calendar week’ and ‘week period’ are retained and moved to Clause 10 to support the original purpose of allowing other choices for first day of week.
Establishing Monday as day of week 1 enables the specification of a reference time period for an index origin member for the indefinite weeks scale, choosing Monday, January 3, 2000, with an index consistent with the Gregorian day numbering.
Aligning the Gregorian calendar with the weeks calendar eliminates the need for the verb concept ‘year week coordinate indicates time point sequence’ and the related ‘starting week day’ idea, which are deleted. In its place, we create the ‘starting week’ concept, which is parallel to ‘starting day’. This enables the correct axioms (Necessities) for the year of weeks and year of weekdays scales.
Some related errors in terminology or arithmetic are also corrected.
The RTF determined in resolving Issue 19525 that the definition of ‘starting day’ should be functional and the calculation should be a Necessity. The same idea is applied to ‘starting week’.
Issue 19034 recommended editorial corrections to the terms for day of week time points. These are included in the modifications to the (ISO) day of week entry below.
Issue 19526 asked for corrections to the description of ‘starting weekday’, which this resolution deletes. But the definition of ‘starting week’ requires the notion ‘first Thursday’, which was embedded in the ‘starting week day’ concept. So the revised text carries the intent of Issue 19526 forward.
The resolution to Issue 19645 modifies the entry for the year of weekdays scale and incorporates text changes related to this issue. It also adds the concept ISO week-based year, which is mentioned in the revised introductory text below.
The resolution to Issue 19650 deletes section 12.5. Nomenclature changes in 12.5 that are related to this issue are therefore omitted below.

In clause 10.5, Figure 10.7 is titled Time Zones, and it shows a verb concept: “time scale differs from time scale by time offset”. This verb concept is in the UML model (in Time Infrastructure), but does not appear anywhere in the text of DTV v1.1. It appears to have been replaced by ‘calendar1 differs from calendar2 by time offset’ in Figure 10.8. But Figure 10.7 shows several other concepts that are defined in clause 10.5, and the definition of ‘local calendar’ refers to a time scale that “differs from the UTC day-of-hours time scale by a given time offset”, which appears to use the phantom verb concept.

The UML diagram will be realigned with the text. The definition of ‘local calendar’ and the definitions of time coordinates ‘with time offset’ are modified to use the documented verb concept ‘calendar1 differs from calendar2 by time offset’.

In DTV clause 11.2, the entry for Convention du Métre contains:

Definition: time interval of the signing of the Convention du Métre

Necessity: The Convention du Métre is at 20 May 1875.

These are inconsistent. The Necessity uses an undefined verb concept 'time interval is at time interval'.

It was intended that the Necessity uses 'occurrence is at (during) time interval'. The signing of the treaty is not a time interval; it is an event, an occurrence. The important fact is that the signing event occurred within the day, month and year denoted by 20 May 1875.

The conventions for establishing which time interval was named 20 May 1875 were established at that time by observation of noon at the Greenwich observatory. That was used as the basis for definition of Gregorian days until 1972, when it was replaced by Universal Coordinated Time (UTC). By convention, 24-hour periods with a midpoint at Greenwich noon might also be used to define Gregorian days before 1875, although actual approaches were different. Without specifying these conventions as well, the concept Gregorian day is not defined by the date of the Convention du Métre. There are several thousand distinct time intervals that encompass the signing of the treaty and have a duration of 86400 seconds.

The Convention du Mètre is intended to be an occurrence. Inaccurate references should refer to the Gregorian day of the signing, which is properly defined as the 24 hours beginning at midnight as determined by Greenwich Mean Time from 1884 to 1972 and by UTC thereafter.

In clause 8.2.5, the verb concept 'time interval1 plus time interval2 is time interval3'

has 4 CLIF Definitions. Actually, each of these is an Axiom and together they make up a definition of sorts.

Further , each of them uses 'iff' incorrectly. The first has the form:

(forall (t1 t2 t3)

(if

(or

("time interval1 is before time interval2" t1 t2)

("time interval1 properly overlaps time interval2" t1 t2))

(iff

("time interval1 plus time interval2 is time interval3" t1 t2 t3)

(and

("time interval1 starts time interval2" t1 t3)

("time interval1 finishes time interval2" t2 t3))

)))

It should be:

(forall (t1 t2 t3)

(if

(and

("time interval1 plus time interval2 is time interval3" t1 t2 t3)

(or

("time interval1 is before time interval2" t1 t2)

("time interval1 properly overlaps time interval2" t1 t2)))

(and

("time interval1 starts time interval2" t1 t3)

("time interval1 finishes time interval2" t2 t3))

))

and similarly for the others.

The suggested text is no improvement; the Definition remains fragmented, and it loses the conditional equivalences. The OCL Definition is a definition. The others aren’t. As the issue says, the 4 “CLIF Definitions” are axioms. They should be identified as such.

Annex D.3.2 contains the following axiom for 'system of units is for system of quantities':

Necessity: Each system of units is for exactly one system of quantities.

CLIF Axiom:

(forall (("system of units" "system of units"))

(= (count ("system of units is for system of quantities" "system of units")) 1))

I'm not sure what this is supposed to mean. The conventional form would be:

(forall ((sou "system of units"))

(exists ((soq "system of quantities"))

(and

("system of units is for system of quantities" sou soq)

(forall (soq2)

(if ("system of units is for system of quantities" sou soq2)

(= soq2 soq) ))

)))

Note also that there is no OCL form of this axiom.

Replace the text as suggested. Add the OCL form.

The weekday definitions in clause 12.4 have incorrect definitions. They say that "Monday", etc., are kinds of "day of week 1", etc. But there is no object type called "day of week 1" – the styling is wrong. "Day of week" should be styled "term", and "1" should be styled "name". The intended meaning is "day of week" number 1.

In resolving Issue 18991, the RTF decided that notations of the form
<time point kind><index>, such as ‘day of week 1’,
are abbreviations of definite descriptions of the form
“<time point kind> that has index <index>”, such as
“day of week that has index 1”. These abbreviations are complex expressions used as designations for the time points defined by the definite descriptions. The notation is used in many places in the specification, and is explained in the revised text for Issue 18991.
Accordingly, the styling recommended in the issue is correct.
The day of week definitions are modified by the resolution to Issue 19574, which also corrects the formatting of the notation.

Clause 8.2.4 contains two verb concepts that make no sense, and the descriptions added by issue 18253 do not match their definitions. These verb concepts should be removed, since there are others that address the requirements:

· time interval1 begins time interval2

· time interval1 ends time interval2

The RTF agrees that these verb concepts were left from a misunderstanding of business requirements. Other issues involve additions and modifications to verb concepts that eliminate any value of these. They will be deleted.

Clause 16.4 has two verb concepts that appear to mean the same thing: ‘occurrence1 precedes occurrence2’ and ‘occurrence1 ends before occurrence2’.

Clause 16.6 has two verb concepts that appear to mean the same thing: ‘situation kind1 precedes situation kind2’ and ‘situation kind1 ends before situation kind2’.

Suggest making one of each pair a synonymous form of the other.

[NOTE: This replaces the resolution of this issue in Ballot 8]
This is a misunderstanding. An occurrence A precedes an occurrence B if A ends before B starts. But A could start before or after B starts and end before B ends. The verb concept only compares the two ending times. The existing example reflects this, The text is clarified.

The only OCL Constraint in DTV clause 8.2.1 reads:

context: _'time interval'

inv: 'time interval'.'time interval1 is proper part of time interval2'-->notEmpty()

It should be:

context: _'time interval'

inv: self._'time interval1 is proper part of time interval2'-->notEmpty()

(The first word after the “inv:” in the second line should be “self”, not “_’time_interval’”.)

The RTF agrees that the OCL is incorrect. Interpretation of the corrected OCL, however, seems to require any conforming M0 population of the UML/MOF model to be infinite, in that each ‘time interval’ object must have different ‘proper part’ time interval. The intent of the Axiom is that no time interval can be declared or assumed to be atomic, but in any given model population there will be time intervals that have no proper part in the population. The proposed OCL constraint would make such a population invalid.

First, the notation introduced in Annex F is used nowhere in the DTV v1.1 specification. It was formerly used in Annex that was revised in DTV v1.0. The title of Annex F is confusing for DTV, since DTV provides normative logical formulations in CLIF and OCL. The intent is to describe SBVR logical formulations, for which DTV provides normative expressions in SBVR Structured English.

Second, the Annex specifies a notation for SBVR logical formulations. If it is to have value, the notation should be specified in the SBVR specification. In any case, this Annex should be considered for adoption by the SBVR RTF (as the DTV FTF recommended). Indeed, the SBVR Logical Representation of Meaning clause might well profit from the ability to express examples in this form. There are some technical defects in the Annex F specification, but these could be remedied by the SBVR RTF, whereas specifications for the representation of SBVR are out of scope for the DTV RTF.

Finally, the text of Annex F begins: “The table below is kindly provided by Don Baisley of Microsoft Corp.” This sentence is entirely inappropriate, and raises intellectual property concerns. If the Annex is retained, this sentence must be deleted. Don Baisley is properly included in the acknowledgements in 6.4, but the specification is the work of the submitters and the editing Task Forces, and this Annex is presumably not intended to be an exception.

The RTF agrees that the Annex should not be a part of the Date Time Vocabulary. The Issue of incorporating in SBVR has been raised to the SBVR RTF, noting that the specification in Annex F was formally adopted by the OMG.

Specification: DTV v1.1

Title: misplaced Synonymous Forms on 'time set'

Summary:

In DTV v1.1, clause 10.7, the two synonymous forms under ‘time set’

Synonymous Form: time set1 equals time set2

Synonymous Form: time set1 = time set2

should be under ‘time set1 is equivalent to time set2’

Agree. Editorial repair

In clause 10.6.3, the definition of 'compound time coordinate' is:

Definition: time coordinate that combines more than one time coordinate

and the definition of 'compound time coordinate combines atomic time coordinate' is:

Definition: the atomic time coordinates jointly specify the compound time coordinate

That makes them both circular. Prefer something like:

compound time coordinate

Definition: time coordinate that is a set of atomic time coordinates that jointly indicate a time point

compound time coordinate combines atomic time coordinate

Definition: the atomic time coordinate is an element of the compound time coordinate (set)

These definitions match the first Necessity under the verb concept.

The 'set' makes the second Necessity redundant.

The third Necessity is misstated: it compares a time coordinate to a time scale.

The circular definitions are resolved more or less as suggested, and the related Necessities are revised.
Because of other changes to the descriptions of compound time coordinates that affect the same definitions, and related changes to the UML diagrams, the revised text for this issue is merged with Issue 19547.
Revised Text:
See Issue 19547.

Specification: DTV v1.1

Title: Starting week day is a number

In clause 12.4, the entry for starting week day has the Definition:

the index of the Gregorian day of year that is 3 days before the first Thursday of some Gregorian year

It is at least unexpected that any category of ‘day’ would be a integer. The definition appears to be that of ‘starting Monday index’, or something the like. The expected concept would be “Gregorian day that is three days before the Gregorian day that corresponds to the first Thursday of the Gregorian year.’ In either case, one would have to define: Gregorian year has first Thursday. This suggests that the useful concept is in fact, Gregorian year has starting Thursday (or starting Monday).

The verb concept is ‘starting week day of Gregorian year’ rather than ‘Gregorian year has starting week day’, and there is a Necessity that only Gregorian years after 1600 have starting week days, which is clearly wrong.

This whole concept appears to be an artifice for determining which week of the ‘weeks calendar’ is the ‘first week’ of a Gregorian year. So there is no intended business use of these terms, but the entries should be corrected.

The last paragraph of the Issue Summary correctly indicates that the function of ‘starting week day’ is to support interpretation of ‘week of year’ and ‘year week coordinates’. The resolution of Issue 19574 restructures that interpretation by creating a fixed relationship between the Gregorian calendar and the weeks calendar. That restructuring eliminates the use of ‘starting week day’ per se, although it makes a similar concept ‘first Thursday’ necessary.
The resolution of this issue is therefore merged with that of 19574.
Revised Text:
none. See Issue 19574

Clause 8.7 includes two verb concepts:

time point1 through time point2 specifies time period

time point1 to time point2 specifies time period

The definitions of these concepts describe the construction of a time point sequence followed by the correspondence to time period. Several of the Necessities in these entries restate Necessities for time point sequences. At least one Necessity for time point sequences in general is stated here but not in the entry for time point sequences:

If the time scale of time point1 is an indefinite time scale then time point1 through time point2 specifies exactly one time period.

That is, each time point sequence that is on an indefinite time scale corresponds to exactly one time period.

By creating companion verb concepts:

time point1 through time point2 defines time point sequence

time point1 to time point2 defines time point sequence

the redundancies can be eliminated and the Definitions and Necessities for the two verb concepts specifying time periods can be greatly simplified.

E.g. for

time point1 through time point2 specifies time period

Definition: time point1 is the first time point of a time point sequence and time point2 is the last time point of the time point sequence and the time point sequence corresponds to the time period

the Definition is replaced by:

Definition: the time point sequence that is defined by time point1 through time point2 corresponds to the time period

The RTF agrees that Necessities about time point sequences in general should be moved to the entry for time point sequence or the related verb concepts.
The RTF notes that the UML diagram in Figure 8.25 is inconsistent with the existing text, and includes the two proposed intermediate verb concepts.
The proposed verb concepts are added, the definitions and necessities for the cited concepts are revised accordingly, and the UML model is re-aligned with the text.
Text is added to explain that ‘time point sequence’ is overall an artificial construct used to describe references to time periods.

Specification: DTV v1.1

Title: Gregorian years before 1600 have no starting day

Summary:

In clause 11.7, in the entry for ‘Gregorian year has starting day’, the Definition is a formula for calculating the index of the ‘starting day’, as distinct from a definition of the verb concept (which is actually carried in the definition of the role ‘starting day’). The Definition is followed by the Necessity:

Necessity: The index of Gregorian year is greater than 1600.

We must conclude that either there are no Gregorian years before 1600, or the ones before 1600 have no starting day. The real intent is probably that the formula given in the Definition is not correct for Gregorian years before 1600.

The correct definition is: The starting day is the Gregorian day that is the first calendar day of the Gregorian year.

Necessity: Each Gregorian year has exactly one calendar day.

Necessity: The starting day of Gregorian year 1875 is Gregorian day 684606.

This relates the concept to the index origin for the Gregorian days scale. The rest are determined by the rules for the length of Gregorian years.

How to compute the index of the starting day from 1601 on should be a Note. One would expect the rule to be how to calculate from the index origin, and there may be other such algorithms. The concept is not the computation algorithm.

The RTF agrees that the definition should be corrected, and the first Necessity should be added.
The Gregorian calendar algorithm is, however, a Necessity not a Note, and the starting day of 1601 is important to it. The second proposed Necessity is irrelevant – the index origin of the Gregorian days calendar is not the starting day of any Gregorian year, and is not useful to the calendar algorithm.
Note also that there are no Gregorian years before 1582. That Necessity is corrected

Specification: DTV

Version: 1.1

Source: Ed Barkmeyer, NIST, edbark(at)nist.gov

Summary:

Examination of some business usages of time concepts has led to the observation that several regulations use the concept:

time interval1 starts during time interval2

or

occurrence starts during time interval

These verb concepts can easily be phrased in terms of existing DTV concepts, but the phrasing is cumbersome. It would be useful to add these to the DTV business vocabulary.

The RTF agreed to add these, in order to simplify business usage.

Specification: DTV v1.1

Title: Unspecified Relationship of OWL files to DTV

Source: Sridhar Iyengar, IBM (for the AB)

Summary:

The DTV v1.1 inventory formally includes a ZIP file that contains OWL ontologies for the DTV vocabularies, but no text in the specification refers to this file, or to these ontologies. Also, the text of the CLIF and OCL elements associated with vocabulary elements is contained directly in the specification, but the relationship between the OWL elements and the vocabulary elements is nowhere described. Some text should describe what the OWL ontologies are, and how the OWL model elements are derived from the vocabulary elements.

A brief description of the relationship of the OWL files to the specification is added to Clause 5.

Following the entry for ‘compound time coordinate combines atomic time coordinate’, the following paragraph appears:

Calendar scales (i.e., those involving calendar years, calendar months, calendar weeks, and calendar days) use index origin value 1, while time-of-day scales (i.e., those involving hours of day, minutes of hour and seconds of minute) use index origin value 0. In all cases other than the Gregorian years scale, the index original element is the first element of the time scale. For clarity, the index origin value and index origin element of each time scale is included with the time scale.

The paragraph has nothing to do with the nature of time coordinates, which is the topic of 10.6. It may belong in 10.8 or at the end of 10.1.

The paragraph is out of place, but it is most relevant to atomic time coordinates that involve the index of the time point. It is reworded to make that clear, and to clarify the forward references to clauses 11 and 13.
The text revision is in the area modified by issues 19547 and 18991, and the corresponding text changes are merged with Issue 19547.
Revised Text:
see Issue 19547.

Disposition: Merged (see Issue 19547)

In clause 10.7 (time sets), Figure 10.15 is followed by text that relates time sets to time point sequences, but time point sequences do not appear in the Figure. Similarly, Figure 10.16 is the same diagram, but it is followed by text that relates time sets to time periods, and time periods do not appear in the diagram.

Both of these diagrams are out-of-date. They are replaced with the correct diagrams.
Note also that Figure 10.15 correctly shows that ‘time point sequence matches time set’ specializes ‘thing is in set’. The entry is modified to capture this.

Specification: DTV v1.1

Title: Missing and incorrect text in clause 10.6

Summary:

In clause 10.6 (Time Coordinates), the introduction suggests that a time coordinate can represent more than one time point. This is false. A time coordinate represents exactly one time point (which is nowhere stated). It can only combine time point identifiers to refer to a different time point.

The verb concept 'time coordinate has time scale' appears in the UML diagram and in one of the definitions, but nowhere in the text.

In the entry for 'time coordinate', the two dichotomies are stated as possibilities in the Notes. They should be stated as Necessities.

The definitions of absolute and relative time coordinates refer to their "corresponding to" time intervals. The time points correspond, but the coordinates only "refer to" them.

Upon examination, the RTF determined that an atomic time coordinate indicates exactly one time point. A compound time coordinate, and therefore time coordinates in general, indicates at most one time point, and may not indicate any (documented) time point. For example, March 3 does not indicate any documented time point. This necessitates a number of minor changes to the model, and to the wording of many definitions in 10.6.
With this understanding, only an atomic time coordinate has a time scale, and that concept is added.
The dichotomies are restated as Necessities, and shown in the UML diagrams. The definitions of absolute and relative time coordinates are modified as recommended, and other inconsistencies are also repaired.
There is a significant overlap of the changes associated with this issue and the changes associated with Issues 18989, 18991, 19529, and 19635.
Issue 18989 and 18991 (duplicates) were resolved to determine that a time coordinate is a conceptual structure of meaning rather than a representation of a time point. This affects the UML diagrams in 10.6, the wording of the introductory text, and the wording of many of the definitions being altered by Issue 19547. In particular this results in elaborating the model of atomic time coordinate.
Issue 18991 also makes parallel changes to the wording of Clause 9.1 and 9.2.
Issue 19529 points out that the definitions of ‘compound time coordinate’ and ‘compound time coordinate combines atomic time coordinate’ are circular. The resolution of that issue is to define a compound time coordinate to be a set of atomic time coordinates, but to ‘combine’ time coordinates in general. The revised definitions must also take into account the fact that compound time coordinates do not necessarily indicate time points. Those changes are therefore merged into the Revised Text below.
Issue 19635 requires an editorial change to move a misplaced paragraph in 10.6.3. In addition, the revised entry for ‘compound time coordinate includes atomic time coordinate’ is moved to follow the entry for ‘compound time coordinate’.

The Date-Time Vocabulary has multiple concepts about amounts of time (duration, duration value), and locations in time (time interval, time point, time point set, time period, time coordinate), but very little guidance as to which of these concepts should be the basis for application business vocabularies. DTV should add a rationale section or additional commentary in Annex C to explain which concepts should be used for what purposes in business vocabularies.

Table C.1 has a reference to a concept 'date' that does not exist.

The RTF recognizes the need to provide guidance to business analysts and other users. After some discussion, the RTF decided not to try to distinguish concepts that are “infrastructural” from “application concepts” within the body of the various vocabularies. Instead the need will be addressed by a revision of Annex C that provides the guidance. This issue is closely related to Issue 19336, and resolutions are merged into a single revision of Annex C.

Specification: DTV v1.0

Title: 'date time' associations

Source: Ed Barkmeyer (for the RTF), NIST, edbark@nist gov

Figure 10.17 has the wrong association names on 'date time' has 'date' and 'date time' has 'time'.

Should be: 'date time combines calendar date' and 'date time combines time of day coordinate'. And 'time' should be 'time of day coordinate'.

The business term 'date' should be a synonym for 'calendar date'.

We already have "of" as a synonymous form for 'combines' in 10.6.3. But the SynonymousForm 'compound time coordinate of atomic time coordinate' should be 'compound time coordinate has atomic time coordinate'.

SBVR experts:

In the Date Time Vocabulary v1.0 specification, clause 16.5 contains the following terminological entry:

individual situation kind has occurrence interval

Definition: the occurrence interval is the time span of the individual situation kind

Necessity: The individual situation kind has exactly one occurrence

Note: The time span of an individual situation kind is exactly the occurrence interval of its only occurrence.

Example: The occurrence interval of the Great Fire of London was 2 September 1666 through 5 September 1666 (English old style calendar).

The technical aspects of this are not at issue. An ‘individual situation kind’ (state of affairs) can have at most one occurrence. An occurrence (actuality) has exactly one ‘occurrence interval’ – the time interval during which it is occurring. And any situation kind can have a ‘time span’ – the smallest time interval that includes all occurrences of the situation kind. (If it never occurs, it may have No time span.)

There are two SBVR “style” problems here.

First, the Definition of the verb concept is (appropriately) a sentence involving the placeholders, but the first character of the sentence is not capitalized. By convention in SBVR, the first character of a Definition is not capitalized, and this is also true of example sentences in SBVR v1.2, e.g., in clause 8.2.2. The question is: Which convention – English or SBVR – is appropriate here? Or do we even care?

Second, and more importantly, the intent of the above Necessity is: If an individual situation kind has an occurrence interval, the individual situation kind has exactly one occurrence. But the text above omits the antecedent. Instead, it assumes that ‘the individual situation kind’ refers to whatever plays the ‘individual situation kind’ role in an instance of the verb concept (wording). Is it the intent of SBVR that such an omission is valid in this context (the terminological entry)? Or is the antecedent required (to establish the context of an instance of the verb concept)?

The considered opinion of the SBVR RTF will dictate the nature of any related changes to this entry in the DTV.

No Data Available

The glossary entry for Time Axis has a ‘General Concept:’ entry that reads “mathematical representation of the succession in time of instantaneous events along a unique axis”. The caption is wrong; it should be a ‘Definition:’.

Correct the caption in the ‘Time Axis’ glossary entry. Also, correct the wording of the definition to avoid the terms ‘representation’ and ‘instantaneous’ since the former could be confused with SBVR’s ‘representation’, and the latter is not true of the model we use.

The description for "Properly overlaps" in this section is as follows:

"The ‘properly overlaps’ relation distinguishes the case in which there is a part of each time interval that is not a part the other from all the cases in which one time interval is entirely a part of the other. The general ‘overlaps’ relation subsumes all of them. ‘Properly overlaps’ describes the first time interval as starting and ending earlier than the second, whereas ‘is properly overlapped by’ describes the first time interval as starting and ending later."

Problem:

In the phrase "‘Properly overlaps’ describes the first time interval as starting and ending earlier than the second," the sense which is intended is in fact "‘Properly overlaps’ describes the first time interval as starting earlier than the second starts and ending earlier than the second ends"

That is, a word was left implied in this phrase, but no one word would, when inserted here, have carried the correct meaning. For example "starting and ending earlier than the second [starts]" would be incorrect, as would "starting and ending earlier than the second [ends]". So when the reader parses this surface-level syntax and inserts any implied words for a deeper level cognitive representation of the meaning, any such representation would be incorrect compared to the intended sense of this term.

Similarly in the phrase which follows:
"... whereas ‘is properly overlapped by’ describes the first time interval as starting and ending later."

should then (presumably) be:
"... whereas ‘is properly overlapped by’ describes the first time interval as starting later than the second starts, and ending later than the second ends."

Proposed Solution:
Rewrite the offending paragraph as follows:

"The ‘properly overlaps’ relation distinguishes the case in which there is a part of each time interval that is not a part the other from all the cases in which one time interval is entirely a part of the other. The general ‘overlaps’ relation subsumes all of them. ‘Properly overlaps’ describes the first time interval as starting earlier than the second starts and ending earlier than the second ends, whereas ‘is properly overlapped by’ describes the first time interval as starting later than the second starts, and ending later than the second ends."

Replace text as described below.

In clause 9.5.3, 'calendar day' is defined as: 'time point that is defined by a given calendar and during which approximately one revolution of the earth occurs on its axis'. Clause 9.3 defines 'time point' as 'scale point that is in a time scale and that specializes the concept 'time interval'. Fortunately, 9.3 also says 'time point' is a concept type, so the idea of specialization makes sense. That is, the definition in 9.3 means: a time point is a scale point on a time scale, and a time point is a concept that specializes 'time interval'. A concept that specializes time interval is not a time interval during which the earth rotates – its instances are.

Recommendation:

In clause 9.5.3, change the definition of calendar day to 'time point that is defined by a given calendar and that corresponds to time intervals during which approximately one revolution of the earth on its axis occurs'.
In clause 9.3 reword the definition of time point to 'concept that specializes the concept time interval and that is a scale point on a time scale.

The recommendation is adopted as given.

(The change to the definition of ‘time point’ is accomplished by the resolution to issue 16665.)

Clause 12.4 contains the following:
"The concept “time point converts to time period on time scale” enables conversion of a time point on some time scale1, to a time period on the given time scale. The target time scale always is finer, meaning that it has a granularity that is less than or equal to the granularity of time scale1. This means that time point is equivalent to a time period on time scale2.
"For example, the Gregorian month that is indicated by “January” (on the Gregorian year of months scale) is the time period from Gregorian day of year 1 through Gregorian day of year 31 on the Gregorian year of days scale."

In all of this text, the term 'time period' should probably be replaced by 'time point sequence'.

Clause 12.4 then contains this entry:

"time point converts to time period on time scale
"Definition: time point converts to a time point sequence on the time scale and the time period
instantiates the time point sequence"

The verb concept 'time point converts to time point sequence' appears in diagram 12-12, but is not defined anywhere, and 'time point converts to time period on time scale' does not appear on the diagram. So the obvious interpretation is that 'time period' should be replaced by 'time point sequence' in the verb concept entry. But then the definition is circular.

Replace the glossary entry for 'time point converts to time period on time scale' with 'time point converts to time point sequence on time scale'. Also for clarity, add 'time point converts to time set on time scale'. Include these verb concepts in figure 12-2. Add "General Concept" captions to each specialization of these verb concepts to relate the specializations to the general concepts

The Date Time Vocabulary provides verb concepts that relate the time order of any two time intervals (e.g. 'time interval1 is before time interval2'), any two situation models ('situation model1 precedes situation model2'), and any two occurrences ('occurrence1 precedes occurrence2'). Another common ordering relationship is among three time intervals, situation models, or occurrences, as in 'time interval1 is between time interval2 and time interval3', 'situation model1 is between situation model2 and situation model3', and 'occurrence1 is between occurrence2 and occurrence3'. These ternary verb concepts should be added to the Date Time Vocabulary.

Add the suggested verb concepts to the vocabulary. Use "and" in the primary form of the verb concepts (even though it is also a keyword for conjunction), and provide an alternate synonymous form that does not use 'and'.

The Date-Time Vocabulary (DTV) document FTF beta 1 draft Mike sent on Dec. 8, 2011 shows a concept of 'time unit' specialized as:

• 'precise time unit', a specialization of 'measurement unit'
• 'nominal time unit'

It is understood that in DTV, a 'precise time unit' is a kind of ISO 80000 measurement unit (i.e., 3.8 in ISO-80000-1):

real scalar quantity, defined and adopted by convention, with which any other quantity of the same kind can
be compared to express the ratio of the second quantity to the first one as a number

The DTV names for 'time unit' and 'nominal time unit' are misleading because in the Dec. 2011 DTV FTF 1 beta document,
these terms are not defined as kinds of ISO 80000 measurement units.

From the DTV FTF perspective, the objection against defining 'time unit' and 'nominal time unit' as ISO 80000 measurement units is that 'month',
a kind of 'nominal time unit', varies between 28 and 31 days and therefore does not exactly fit the definition of measurement unit per ISO 80000.
In pure ISO 80000 terms, this would suggest that 'month' would be a measurement unit with a variable conversion factor from 'day', which is defined as a normative measurement unit in ISO 80000-3, item 3-7.d.

I believe that the DTV interpretation of ISO 80000 measurement unit is too restrictive and should be changed such that a DTV 'time unit' is in fact a kind of ISO 80000 'measurement unit'.

There is compelling evidence to support this change in ISO 80000 itself:

1) The definition of year as a non-SI measurement unit in ISO 80000-3, Annex C, item 3-7 shows an example where the conversion factor is variable:

a := 365d or 366d

One tropical year is the duration between two
successive passages of the Sun through the mean
vernal equinox.

This duration is related to the corresponding difference
in mean longitude of the Sun, which depends on time in
a not exactly linear form; i.e. the tropical year is not
constant but decreases at a rate of nearly per
century. The tropical year is approximately equal to
365,242 20 d ≈ 31 556 926 s.

2) The value of a quantity can be expressed in three ways according to ISO 80000-1, item 3.19:

• a product of a number and a measurement unit
• a number and a reference to a measurement procedure
• a number and a reference material

3) 'month' could be defined as an ISO 80000 'conventional reference scale', that is, a quantity-value scale defined by formal agreement.

This could facilitate defining that 'month' is a 'conventional reference scale' varying between 28 and 31 'days'.
Specializations of 'month' could be made for 28-days months, 29-days months, 30 days months, 31 days months where such specializations can be defined as ISO 80000 derived units of 'days' with a precise conversion factor.

4) 'amount of substance', one of the 7 base quantities in the International System of Quantities, ISQ, is intrinsically context-dependent:
See the remarks in ISO-80000-9, 9-1:

Amount of substance of a pure
sample is that quantity that can
often be determined by
measuring its mass and
dividing by the molar mass of
the sample.

Amount of substance is
defined to be proportional to
the number of specified
elementary entities in a
sample, the proportionality
constant being a universal
constant which is the same for
all samples.

The name “number of moles”
is often used for “amount of
substance”, but this is
deprecated because the name
of a quantity should be
distinguished from the name of
the unit.

In the name “amount of
substance”, the words “of
substance” could, for
simplicity, be replaced by
words to specify the substance
concerned in any particular
application, so that one may,
for example, talk of “amount of
hydrogen chloride, HCl”, or
“amount of benzene, C6H6”.
It is important to always give a
precise specification of the
entity involved (as emphasized
in the second sentence of the
definition of the mole); this
should preferably be done by
giving the molecular chemical
formula of the material
involved.

Just like 'amount of hydrogen chloride' is a specialization of 'amount of substance',
'January' is a specialization of 'month.
All are measurement units in the sense of ISO 80000.

The DTV specification should clearly indicate the correspondence between the DTV vocabulary and the corresponding ISO 80000 vocabulary.
These correspondences are important to clarify the relationship between the use of ISO 80000 vocabulary in DTV and SysML's QUDV.

The FTF consulted with NIST authors of VIM and ISO 80000-3, who confirmed that 'month' and 'year' are not defined by SI and do not fit the VIM definition of 'measurement unit'. Therefore, the proposal made above is not adopted. Instead, a Rationale section is added to discuss the issue.

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.

The FTF decided to reorganize the document itself, and then repackage the UML model to match the new document organization. The goals of this reorganization are:

• To modularize the document, the vocabulary, and the UML model so that users do not need to accept the entire design in order to adopt parts.
• To reconcile dependencies among the parts of the specification, so that each concept is introduced before any dependencies upon that concept.
• To create an individual SBVR vocabulary and UML package matching the content of each top-level Clause of the specification.
• To clearly show the dependencies among the Clauses, and correspondingly among the SBVR vocabularies and UML packages.
• To separate the generic time and calendar concepts from the definitions of the Gregorian, week, time of day, and Internet calendars so that users can model other calendars using the generic concepts without dependencies on these calendars.

See the new text for clause 6.3 (below) for a summary of the new organization.

The definition of ‘nominal time unit’ is updated to resolve a forward dependency from ‘nominal time unit’ to ‘duration value sets’.

(This comment came from the Architecture Board's review of the final submission.)

On p100 it is stated that "the Gregorian Calendar was introduced in
1582" and corrected calendar drift by "skipping over the dates between
October 5-15, 1582". This is true, but it's worth noting that only Spain, Portugal, the Polish-Lithuanian Commonwealth, and parts of Italy implemented the new calendar on Friday 15 October 1582 (following Julian Thursday 4 October 1582). Other countries stayed with the Julian calendar, so those "lost dates" (e.g. 10th October 1582) are valid in those countries. France adopted the Gregorian calendar on Monday 20 December 1582 (following Sunday 9 December 1582). Other countries followed over the centuries, with the UK and East-Coast American colonies not switching until 1752 (Wednesday 2 September 1752 was followed by Thursday 14 September 1752). Russia didn't change until 1918. The last countries to change seems to have been Greece, where Thursday 1 March 1923 followed Wednesday 15 February 1923, and Turkey, which switched in 1926.

(Yes, I got all those dates from Wikipedia .

Hence I think this section would benefit from a comment saying that although the Gregorian Calendar begins in 1582, various countries switched on various later dates, so that to be completely unambiguous, dates after October 1582 should really state which calendar they use. (For instance, today, Sunday 11th September 2011 in the Gregorian Calendar is Monday 29th August 2011 in the Julian calendar).

Similarly, at the top of page 121 it says that the Gregorian calendar was "introduced in 1582". It might be more accurate to say it was "first defined" in 1582 (or some similar wording), and "introduced" in different countries at different later dates.

Remove the extraneous text under ‘nominal time unit’ that discusses the history of the Gregorian Calendar.

Add Notes to the definition of ‘Gregorian Calendar’ explaining when this calendar was adopted in various countries, and cautioning that some historical dates may not use this calendar.

(This comment came from the Architecture Board's review of the final submission.)
This comment on page 16 [now Annex A.3 jarred somewhat:
"These variations are accounted for by incorporating intercalary leap days and leap seconds into some calendar and timekeeping schemes. This specification chooses to support leap days, but not leap seconds, because leap days are significant to business while leap seconds are insignificant."
It seems a bit arrogant to assert that "leap seconds are insignificant to
business". If (for instance) your company's Telephone PABX were to crash at
midnight on New Year's Eve because its software couldn't cope with
leap-seconds, I suggest that would be "significant to business".

Currently, the Date-Time Vocabulary describes the Gregorian Calendar in terms of the UTC time scale. To support leap seconds, add definitions of the TAI time scale and leap seconds, and add text saying that leap seconds add discontinuities in the UTC time scale. These discontinuities affect use cases that are sensitive to leap seconds.
Per ISO 80000-3, the definition of the 'day' time unit remains as a fixed 86 400 seconds.

The final submission document recorded this issue regarding figure 80 "Scales" in clause Annex E.3:
The "black diamond" and

on the "scale has scale point" association are wrong.

The resolution of issue 16665 deleted this Annex. Therefore this issue is moot.
Revised Text:
Disposition: Merged: See issue 16665

• The fact type form “months centennial quotient of month value” is used in two different glossary entries in clause 10.6, “Duration Values”. The second entry should be “months quadricentennial quotient of month value”. Both the glossary entry and the definition should be updated.
• The fact type form “years centennial quotient of year value” in clause 10.5 has the same error as above and needs the same fix.

In clause 11.5 on page 135, there are two glossary entries named “years centennial quotient of year value”. Rename the second one to “years quadricentennial quotient of year value”. Correct the definition of this entry to read:

Definition: the years quadricentennial quotient is the remainder produced by dividing the number of the year value by 400

In clause 11.6 on page 138, there are two glossary entries named “months centennial quotient of year value”. Rename the second one to “months quadricentennial quotient of year value”. Correct the definition of this entry to read:

Definition: the months quadricentennial quotient is the remainder produced by dividing the number of the month value by 4 800

Regarding the "monogamy" example in clause 7.3
> “Consider the law of monogamy as it exists in some countries:”
> “It is prohibited that a person1 is married to person2, if that person1 is married to another person3 and person2 is different from person3.”
> “This rule is not entirely correct….”
I cannot imagine a country with the law of monogamy stated like that. It is not proper English nor is it proper SBVR SE. How about this: “A person must not be married to more than one person.” This section argues that the rule statement is “not entirely correct” because it doesn’t say “at the same time”. But that is nonsense. Based on that argument, every rule would need to explicitly tie every relation it uses to time. E.g.:
Rule A: It is prohibited that a drunk driver operate a EU-Rent vehicle.
Rule B: It is prohibited that there exists a time interval such a driver is drunk throughout that time interval and the driver operates a vehicle throughout that time interval and the vehicle is a EU-Rent vehicle throughout that time interval.
It would be better to point out that in any situation there is at most one present time. Therefore, the law of monogamy stated as “A person must not be married to more than one person” is perfectly correct and it logically implies that “A person must not be married to more than one person at the same time.”

“occurrence” is defined in the introduction to be a possible state of affairs. This is OK, if that’s what is intended. But “occurrence” is defined differently later.

Proposed Resolution:
Change the text at the start of the clause from:
Consider the law of monogamy as it exists in some countries:
It is prohibited that a person is married to more than one person.
This rule is correct only on the understanding that the rule is evaluated at a point in time, as specified in this document. A version of the rule that uses the concepts defined in this section to make this understanding explicit is:
If a person1 is married to some person2 occurs for some time interval, it is prohibited that person1 is married to another person3 during the time interval.

to:
Consider the law of monogamy as it exists in some countries:
It is prohibited that a person is married to more than one person.
This rule is correct only on the understanding that the rule is evaluated at a point in time, as specified in this document. A version of the rule that uses the concepts defined in this section to make this understanding explicit is:
If a person1 is married to some person2 occurs for some time interval, it is prohibited that person1 is married to another person3 during the time interval.

Chose a different example from EU-Rent that illustrates the point. Add a new Rationale section that discusses in more detail different techniques for writing rules that refer to situations and time. Add new verb concepts 'occurrence1 overlaps occurrence2' and 'situation model1 overlaps situation model2' to simplify rules that talk about two situation models occurring at the same time.

The definition of "situation model" should be clarified to make it clear that it "may or may not occur".

Proposed Resolution:
(At it's conference call on September 9, the submission team agreed to the following change. Since this change was after the final submission, it is recorded here for consideration by the FTF.)

Change the Definition of "situation model" to read:

Definition: res that is an abstract model or conceptualization of an event, activity, situation, or circumstance that may or may not occur in some possible worlds

Clarify that a situation model may or may not occur

The term "granularity" has two glossary entries, one in clause 8.2, and another in D.4. One should be renamed to avoid confusion, although they mean almost the same thing.
Proposed Resolution:
(The submission team adopted this resolution after the final submission. The change is recorded here as an Issue so that it can be considered by the FTF.)

Under "time scale has granularity" in clause 8.2, add a new Necessity:

Necessity: The scale of the time scale is the granularity of the time scale if and only if the granularity of the time scale is a precise time unit.
In Annex E.3:

• rename the glossary entry "granularity" to "scale granularity"
• rename the glossary entry "scale has granularity" to "scale has scale granularity"
• reword the Necessity under " scale has scale granularity" to read:

Necessity: Each scale has at most one scale granularity.
• Add 1 note and 2 examples:
Note: Time scales are kinds of scales, but time scales of nominal time units (which are not true measurement units) do not have true scale granularities (which are always measurement units).
Example: The Gregorian years scale has a granularity of 'year'. This granularity is the scale granularity of the scale.
Example: The Gregorian months scale has a granularity of 'month'. This scale does not have a scale granularity because 'month' is a nominal time unit, not a precise time unit.

(The submission team adopted this resolution after the final submission. The change is recorded here as an Issue so that it can be considered by the FTF.)

Under "time scale has granularity" in clause 8.2, add a new Necessity:

Necessity: The scale of the time scale is the granularity of the time scale if and only if the granularity of the time scale is a precise time unit.
In Annex E.3:

• rename the glossary entry "granularity" to "scale granularity"
• rename the glossary entry "scale has granularity" to "scale has scale granularity"
• reword the Necessity under " scale has scale granularity" to read: