Issue 13413: In B.3.3.7, the first rule allows defining bounds of different type, This should be forbidden (marte-ftf)
Source: Fundacion Tecnalia Research and Innovation (Mr. Huascar Espinoza Ph.D., Huascar.Espinoza(at)tecnalia.com)
Nature: Revision
Severity: Significant
Summary: In B.3.3.7, the first rule allows defining bounds of different type. This should be forbidden. The first two rules must be changed by: <interval> ::= ('[' | ']') <interval-bounds> ('[' | ']') <interval-bounds> ::= <number-interval-bound> '..' <number-interval-bound> | <datetime-interval-bound> '..' < datetime -interval-bound> | <tuple-interval-bound> '..' <tuple-interval-bound> | <choiceinterval-bound> '..' <tuple-interval-bound> | <expression-interval-bound> '..' <tuple-interval-bound>
Resolution: See issue 13408 for disposition
Revised Text: 
Actions taken:
February 2, 2009: received issue
October 16, 2009: closed issue
Discussion: 

End of Annotations:=====
s is issue # 13413

In B.3.3.7, the first rule allows defining bounds of different type, This should be forbidden

In B.3.3.7, the first rule allows defining bounds of different type. This should be forbidden. The first two rules must be changed by: <interval> ::= ('[' | ']') <interval-bounds> ('[' | ']') <interval-bounds> ::= <number-interval-bound> '..' <number-interval-bound> | <datetime-interval-bound> '..' < datetime -interval-bound> | <tuple-interval-bound> '..' <tuple-interval-bound> | <choiceint


From: webmaster@omg.org
Date: 02 Feb 2009 14:41:37 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Huascar Espinoza
Company: CEA
mailFrom: huascar.espinoza@cea.fr
Notification: Yes
Specification: MARTE
Section: Annex B
FormalNumber: 08-06-09
Version: Beta 2
RevisionDate: 08-06-09
Page: 411-419
Nature: Revision
Severity: Significant
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1; MS-RTC LM 8)
Description
A number of small (but important) issues were identified in the VSL grammar: 1. Literals terminal rule has not been defined for its elements, in Section B.3.3.1 in p. 412. 2. In Section B.3.3.12 (Variables, p 416), the text is not aligned with the grammar. A variables begins by a .direction. and not by a .$. symbol. Yet, the direction is optional, and so a default value must be defined. 3. Section B.3.3.3 is duplicated. 4. In Section B.3.3.4., the DateTimeLiteral rule can be optimized by removing the first alternative and letting optional date-string in the third alternative. 5. In B.3.3.7, literal-interval-bound should be separated in two interval bounds: number-interval-bound and a datetime-interval-bound. 6. In B.3.3.7, the first rule allows defining bounds of different type. This should be forbidden. The first two rules must be changed by: <interval> ::= ('[' | ']') <interval-bounds> ('[' | ']') <interval-bounds> ::= <number-interval-bound> '..' <number-interval-bound> | <datetime-interval-bound> '..' < datetime -interval-bound> | <tuple-interval-bound> '..' <tuple-interval-bound> | <choiceinterval-bound> '..' <tuple-interval-bound> | <expression-interval-bound> '..' <tuple-interval-bound> 7. In Section B.3.3.8, remove the .unlimited-natural. term (not longer valid). 8. Properties of TupleType and ChoiceType should be constrained to be DataType only. 9. In Section B.3.3.12, in the last line, the examples should refer to variable call expr, and not property call expr. 10. In Section B.3.3.12, second rule, it is missing the .:. symbol in variable declaration. 11. Variable call expression and property call expression are ambiguous. We should define a context for property call expression, or define some keywords for making difference. 12. In B.3.3.14, first rule, parentheses are not optional. (already solved in other Issue number!). 13. In B.3.3.13, namespace must be replaced by: <namespace> ::= <body-text> ['.' <namespace>] 14. In B.3.3.15, the parentheses in the rules: if-true-expr and if-false-expr are not required. 15. In B.3.3.15, if-false-expr should be optional. Also, the metamodel in page 402: must be updated. 16. In B.3.3.16, namespace must be replaced by (or removed because the rule already exists): <namespace> ::= <body-text> ['.' <namespace>] 17. In B.3.3.16, jitter(t1,t2) should be clarified (description of the t2 term). Should be jitter(t2-t1)??