ETSI's Bug Tracker - Part 09: Using XML with TTCN-3
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006738 | Part 09: Using XML with TTCN-3 | Editorial | public | 23-04-2014 09:23 | 26-01-2015 11:27

Reporter | Bostjan Pintar |
Assigned To |  |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | no change required |
Platform |  | OS |  | OS Version |
Product Version | v4.5.1 (published 2013-04) |
Target Version | v4.6.1 (published 2015-06) | Fixed in Version | v4.5.2 (interim 2014) |
Clause Reference(s) | 6.1.7; 6.1.8; 6.1.9; 6.1.10
For STF discussion |
Source (company - Author) | STF475

Summary | 0006738: Float values in examples are wrong due to TTCN3 standard

Description

Within ETSI ES 201 873-1(clause 6.1.0) it is written that Floating point values can be expressed by using two forms of value notations. First is the decimal notation with a dot in a sequence of numbers. To get correct transformation from XSD to TTCN3 following clauses within ETSI ES 201 873-9 should be adopted as proposed below:
clause 6.1.7
line within EXAMPLE 2
<minInclusive value="-5"/> should be changed into <minInclusive value="-5.0"/>
clause 6.1.8
line within EXAMPLE 2
<maxInclusive value="-5"/> should be changed into <maxInclusive value="-5.0"/>
clause 6.1.9
line within EXAMPLE 2:
<minExclusive value="-5"/> should be changed into <minExclusive value="-5.0"/>
<minExclusive value="-6"/> should be changed into <minExclusive value="-6.0"/>
clause 6.1.10
line within EXAMPLE 2:
<maxExclusive value="-5"/> should be changed into <maxExclusive value="-5.0"/>
<maxExclusive value="-4"/> should be changed into <maxExclusive value="-4".0/>

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
23-04-2014 09:23 | Bostjan Pintar | New Issue |
23-04-2014 13:02 | Jacob Wieland - Spirent | Note Added: 0012049 |
24-04-2014 07:35 | Bostjan Pintar | Note Added: 0012050 |
24-04-2014 07:38 | Tomas Urban | Note Added: 0012051 |
24-04-2014 07:38 | Tomas Urban | Status | new => closed
24-04-2014 07:38 | Tomas Urban | Resolution | open => no change required
24-04-2014 07:38 | Tomas Urban | Fixed in Version | => v4.6.1 (published 2015-06)
20-06-2014 11:45 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2015-06)
24-06-2014 08:59 | Gyorgy Rethy | Fixed in Version | v4.6.1 (published 2015-06) => v4.5.2 (interim 2014)
26-01-2015 11:20 | Gyorgy Rethy | Fixed in Version | v4.5.2 (interim 2014) => v4.6.1 (published 2015-06)
26-01-2015 11:27 | Gyorgy Rethy | Fixed in Version | v4.6.1 (published 2015-06) => v4.5.2 (interim 2014)

Notes

(0012049)
Jacob Wieland - Spirent
23-04-2014 13:02

for the XSD parts, only the XSD restrictions on float values apply, not the TTCN-3 restrictions. The mapping must take care to map to correct TTCN-3 float literals if the value is not a valid TTCN-3 literal (by adding .0).

(0012050)
Bostjan Pintar
24-04-2014 07:35

Issue was discussed on STF475 and we agree on the comment.

(0012051)
Tomas Urban
24-04-2014 07:38

Closing. No change in the specification required.