Issue 13408: Literals terminal rule has not been defined for its elements, in Section B.3.3.1 in p. 412 (marte-ftf)
Source: Fundacion Tecnalia Research and Innovation (Mr. Huascar Espinoza Ph.D., Huascar.Espinoza(at)tecnalia.com)
Nature: Revision
Severity: Significant
Summary: Literals terminal rule has not been defined for its elements, in Section B.3.3.1 in p. 412
Resolution: Since Issues 13408 to 13424 are all related to mistakes in the grammar of VSL
(Annex B), we merge them all in this issue resolution. For convenience, we copy
below the formulation of each issue.
This resolution proposes to fix all these issues as proposed by the Issue source.
Revised Text: see ptc/2009-05-12 pages 358 - 364
Actions taken:
February 2, 2009: received issue
October 16, 2009: closed issue
Discussion: 

End of Annotations:=====

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


This is issue # 13408

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. 
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: <names ??)1t-2t(rettij eb dluohS .)mret 2t eht fo noitpircsed( deifiralc eb dluohs )2t,1t(rettij ,61.3.3.B nI .71 ]>ecapseman< '.'[ >txet-ydob< =:: >ecapseman< :)stsixe ydaerla elur eht esuaceb devomer ro( yb decalper eb tsum ecapseman ,61.3.3.B nI .61 .detadpu eb tsum :204 egap ni ledomatem eht ,oslA .lanoitpo eb dluohs rpxe-eslaf-fi ,51.3.3.B nI .51 .deriuqer ton era rpxe-eslaf-fi dna rpxe-eurt-fi :selur eht ni sesehtnerap eht ,51.3.3.B nI .41 ]>ecapseman< '.'[ >txet-ydob< =:: >ecap
terals terminal rule has not been defined for its elements, in Section B.3.3.1 in p. 412