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

ID | Project | Category | View Status | Date Submitted | Last Update
0006379 | Part 09: Using XML with TTCN-3 | Editorial | public | 05-12-2012 09:46 | 19-12-2012 13:11

Reporter | Thilo Lauer |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.4.1 (published 2012-04) |
Target Version | v4.5.1 (published 2013-04) | Fixed in Version | v4.5.1 (published 2013-04) |
Clause Reference(s) | ETSI ES 201 873-9 V4.4.1 (2012-04) - Section 7.1.4 MinOccurs and maxOccurs Table 7
For STF discussion |
Source (company - Author) | Devoteam - Thilo Lauer

Summary | 0006379: Add case "minOccurs not present and maxOccurs=unbounded" to Table 7
Description | Add this case to section 7.1.4, Table 7: column: content: ======================= minOccurs: not present, //i.e. default value = 1 maxOccurs: unbounded in...: TTCN-3: record length (1..infinity) of <initial type> Comment: The table row starting with: "<x> â‰¥ 1" covers the case above only implicitly. But imho it should be contained explicitly in Table 7.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR6379_resolution_v1.doc (89,088) 10-12-2012 15:07 http://oldforge.etsi.org/mantis/file_download.php?file_id=2759&type=bug

Issue History
Date Modified | Username | Field | Change
05-12-2012 09:46 | Thilo Lauer | New Issue |
05-12-2012 09:46 | Thilo Lauer | Clause Reference(s) | => ETSI ES 201 873-9 V4.4.1 (2012-04) - Section 7.1.4 MinOccurs and maxOccurs Table 7
05-12-2012 09:46 | Thilo Lauer | Source (company - Author) | => Devoteam - Thilo Lauer
05-12-2012 11:10 | Thilo Lauer | Note Added: 0011202 |
05-12-2012 11:36 | Thilo Lauer | Note Edited: 0011202 |
10-12-2012 13:47 | Gyorgy Rethy | Status | new => assigned
10-12-2012 13:47 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
10-12-2012 14:59 | Gyorgy Rethy | Note Added: 0011206 |
10-12-2012 14:59 | Gyorgy Rethy | File Added: CR6379_resolution_v1.doc |
10-12-2012 15:01 | Gyorgy Rethy | File Deleted: CR6379_resolution_v1.doc |
10-12-2012 15:07 | Gyorgy Rethy | File Added: CR6379_resolution_v1.doc |
10-12-2012 15:08 | Gyorgy Rethy | Status | assigned => resolved
10-12-2012 15:08 | Gyorgy Rethy | Resolution | open => fixed
10-12-2012 15:08 | Gyorgy Rethy | Fixed in Version | => Edition 4.5.1
10-12-2012 15:08 | Gyorgy Rethy | Target Version | => Edition 4.5.1
19-12-2012 13:11 | Gyorgy Rethy | Status | resolved => closed
19-12-2012 13:11 | Gyorgy Rethy | Note Added: 0011286 |

Notes

(0011202)
Thilo Lauer
05-12-2012 11:10 (edited on: 05-12-2012 11:36)

The following cases should also be added to section 7.1.4, Table 7 for clarification reasons: column: content: ======================= minOccurs: 0 maxOccurs: <y> > 1 in...: TTCN-3: record length (0..<y>) of <initial type> column: content: ======================= minOccurs: not present // i.e. default value = 1 maxOccurs: <y> > 1 in...: TTCN-3: record length (1..<y>) of <initial type>

(0011206)
Gyorgy Rethy
10-12-2012 14:59

See resolution proposal in CR6379_resolution_v1.doc.
The case minOccurs is missing, maxOccurs is unbounded has been added to the column where minOccurs >= 1, because, as the CR also mentions, this is not a separate case just a different way of specifying minOccurs ="1".
The case minOccurs: 0 and maxOccurs: <y> > 1 has been solved by replacing <x> not equals 0 by <x> >= 0
The case minOccurs: 1 or not present maxOccurs: <y> > 1 has been added as a new row

(0011286)
Gyorgy Rethy
19-12-2012 13:11

Implemented in draft V4.4.2