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

ID | Project | Category | View Status | Date Submitted | Last Update
0005340 | Part 09: Using XML with TTCN-3 | Technical | public | 09-09-2009 17:07 | 23-03-2010 09:11

Reporter | Gyorgy Rethy |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.2.1 (published 2010-07) | Fixed in Version | v4.2.1 (published 2010-07) |
Clause Reference(s) | 6.4.3
For STF discussion |
Source (company - Author) | L.M.Ericsson

Summary | 0005340: Incorrect mapping of the XSD double type
Description | The XSD float type is converted today to a specific subset of the TTCN-3 float type (IEEE754float). However, this is not correct, as XSD also allows three specific values, positive and negative infinity and not-a-number. TTCN-3 float does not contain value notation for these 3 special values. The conversion shall be changed to allow these special values as well.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

related to | 0005339 | closed | Gyorgy Rethy | Part 09: Using XML with TTCN-3 | Incorrect translation of the XSD float type
related to | 0005507 | closed | Ina Schieferdecker | Part 01: TTCN-3 Core Language | Infinity is a real value
child of | 0005344 | closed | Ina Schieferdecker | Part 01: TTCN-3 Core Language | Introduce range subtyping boundaries excluding the boundaries themselves

Attached Files | CR5340_resolution_P1_v3.doc (259,072) 11-12-2009 09:22 http://oldforge.etsi.org/mantis/file_download.php?file_id=2317&type=bug CR5340_resolution_P7_v4.doc (161,280) 11-12-2009 09:26 http://oldforge.etsi.org/mantis/file_download.php?file_id=2318&type=bug CR5340_resolution_P9_v3.doc (136,192) 12-12-2009 17:24 http://oldforge.etsi.org/mantis/file_download.php?file_id=2320&type=bug

Issue History
Date Modified | Username | Field | Change
09-09-2009 17:07 | Gyorgy Rethy | New Issue |
09-09-2009 17:07 | Gyorgy Rethy | Status | new => assigned
09-09-2009 17:07 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
09-09-2009 17:07 | Gyorgy Rethy | Clause Reference(s) | => 6.4.3
09-09-2009 17:07 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
09-09-2009 17:07 | Gyorgy Rethy | Relationship added | related to 0005339
11-09-2009 11:59 | Gyorgy Rethy | Relationship added | related to 0005344
11-09-2009 12:00 | Gyorgy Rethy | Relationship deleted | related to 0005344
11-09-2009 12:00 | Gyorgy Rethy | Relationship added | child of 0005344
11-09-2009 12:08 | Gyorgy Rethy | Note Added: 0008997 |
11-09-2009 12:08 | Gyorgy Rethy | File Added: CR5340_resolution_P1_v1.doc |
11-09-2009 12:09 | Gyorgy Rethy | File Added: CR5340_resolution_P7_v1.doc |
11-09-2009 12:09 | Gyorgy Rethy | File Added: CR5340_resolution_P9_v1.doc |
11-09-2009 12:16 | Gyorgy Rethy | Note Edited: 0008997 |
13-09-2009 17:03 | Gyorgy Rethy | File Added: CR5340_resolution_P1_v2.doc |
13-09-2009 17:03 | Gyorgy Rethy | File Deleted: CR5340_resolution_P1_v1.doc |
13-09-2009 17:10 | Gyorgy Rethy | File Deleted: CR5340_resolution_P1_v2.doc |
13-09-2009 17:11 | Gyorgy Rethy | File Added: CR5340_resolution_P1_v2.doc |
07-12-2009 14:38 | Ina Schieferdecker | Target Version | => Edition 4.2.1 (not yet published)
09-12-2009 17:13 | Gyorgy Rethy | File Deleted: CR5340_resolution_P7_v1.doc |
09-12-2009 17:14 | Gyorgy Rethy | File Added: Backup of CR5340_resolution_P7_v2.wbk |
09-12-2009 17:17 | Gyorgy Rethy | File Deleted: Backup of CR5340_resolution_P7_v2.wbk |
09-12-2009 17:17 | Gyorgy Rethy | File Added: CR5340_resolution_P7_v2.doc |
09-12-2009 17:51 | Gyorgy Rethy | File Deleted: CR5340_resolution_P1_v2.doc |
09-12-2009 17:51 | Gyorgy Rethy | File Deleted: CR5340_resolution_P9_v1.doc |
09-12-2009 18:05 | Gyorgy Rethy | File Added: CR5340_resolution_P1_v3.doc |
10-12-2009 08:39 | Gyorgy Rethy | File Deleted: CR5340_resolution_P7_v2.doc |
10-12-2009 08:40 | Gyorgy Rethy | File Added: CR5340_resolution_P7_v3.doc |
11-12-2009 09:20 | Gyorgy Rethy | File Deleted: CR5340_resolution_P1_v3.doc |
11-12-2009 09:21 | Gyorgy Rethy | File Added: CR5340_resolution_P7_v4.doc |
11-12-2009 09:21 | Gyorgy Rethy | File Deleted: CR5340_resolution_P7_v3.doc |
11-12-2009 09:22 | Gyorgy Rethy | File Added: CR5340_resolution_P1_v3.doc |
11-12-2009 09:24 | Gyorgy Rethy | File Deleted: CR5340_resolution_P7_v4.doc |
11-12-2009 09:26 | Gyorgy Rethy | File Added: CR5340_resolution_P7_v4.doc |
12-12-2009 17:23 | Gyorgy Rethy | File Added: Backup of CR5340_resolution_P9_v3.wbk |
12-12-2009 17:23 | Gyorgy Rethy | File Deleted: Backup of CR5340_resolution_P9_v3.wbk |
12-12-2009 17:24 | Gyorgy Rethy | File Added: CR5340_resolution_P9_v3.doc |
12-12-2009 17:28 | Gyorgy Rethy | Note Added: 0009149 |
12-12-2009 17:29 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Ina Schieferdecker
04-01-2010 12:04 | Ina Schieferdecker | Note Added: 0009151 |
04-01-2010 12:04 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Gyorgy Rethy
01-02-2010 13:44 | Gyorgy Rethy | Note Added: 0009178 |
01-02-2010 15:13 | Gyorgy Rethy | Note Added: 0009184 |
01-02-2010 15:13 | Gyorgy Rethy | Status | assigned => closed
01-02-2010 15:13 | Gyorgy Rethy | Resolution | open => fixed
01-02-2010 15:13 | Gyorgy Rethy | Fixed in Version | => Edition 4.2.1 (not yet published)
23-03-2010 09:11 | Ina Schieferdecker | Note Added: 0009250 |
29-06-2010 09:35 | Ina Schieferdecker | Relationship added | related to 0005507

Notes

(0008997)
Gyorgy Rethy
11-09-2009 12:08 (edited on: 11-09-2009 12:16)

CR5340_resolution_Px_v1.doc: first drafts for the resolution for part-1, 7 and 9.
Open: how to handle exclusive range boundaries of constrained float types?
1) introduce exclusive boundaries in TTCN-3 as well (CR5344)
2) refer to some " minimal distinguishable real value", that is a) platform dependent; as the converter and the TTCN-3 tool may be used on different platforms, this may lead to different behaviours of different TTCN-3 tools b) not as exact as TTCN-3 should be.
3) define the "minimal distinguishable real value"; the real behaviour of tools still may be platform dependent and in some specific cases behaviours of all tools may be wrong (if the received value less by delta than the boundary but this delta is less than the "minimal distinguishable real value";

(0009149)
Gyorgy Rethy
12-12-2009 17:28

Ready for review. Solution relies upon the new exclusive boundary feature in the core for float, double and decimal types. Mapping of integer do not change. Also handling of date/time types is added, though the bounding facets applied to date/time types are ignored (but this is explicit now). Also text is extended to cover the different cases more precisely and explicitly, though technical change effects only the float/double/decimal types.

(0009151)
Ina Schieferdecker
04-01-2010 12:04

For sake of simplicity, I propose to use also for XML one rule for handling of exclusive boundaries and not to differentiate between float and integer types for that, i.e.
Instead of
<simpleType name="e12a">
<restriction base="positiveInteger">
<maxExclusive value="100"/>
</restriction>
</simpleType>
// Is mapped in TTCN-3 to:
type XSD.PositiveInteger E12a (1 .. 99)
with {
variant "name as uncapitalized"
}
we may define
<simpleType name="e12a">
<restriction base="positiveInteger">
<maxExclusive value="100"/>
</restriction>
</simpleType>
// Is mapped in TTCN-3 to:
type XSD.PositiveInteger E12a (1 .. !100)
with {
variant "name as uncapitalized"
}
The proposals for Part 1 and Part 7 are ok.

(0009178)
Gyorgy Rethy
01-02-2010 13:44

Implemented in Part-9, according to Ina's proposal on the unified handling of integer and float/double types.

(0009184)
Gyorgy Rethy
01-02-2010 15:13

Implemented in Part-7 acc. to CR5340_resolution_P7_v4.doc.

(0009250)
Ina Schieferdecker
23-03-2010 09:11

Part 1 changes implemented with minor changes: In 7.1.3: "minus zero is less than plus zero, which represents zero" In 6.1.1: "NOTE 2: - not_a_number (i.e. minus not a number) is not to be used." In BNF: FloatValue ::= FloatDotNotation | FloatENotation | NaNKeyword --> FloatValue without InfinityKeyword as this is already part of the range definition