ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0005994 | Part 06: TTCN-3 Control Interface | Technical | public | 21-12-2011 17:26 | 12-07-2012 13:38

Reporter | Anthony Baire |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.3.1 (published 2011-06) |
Target Version | v4.5.1 (published 2013-04) | Fixed in Version | v4.5.1 (published 2013-04) |
Clause Reference(s) | 11.3.3.20 B.3
Source (company - Author) |

Summary | 0005994: AddressValue allows multiples values in the XML mapping
Description | The XML mapping for AddressValue may contain multiple values. This is kind of strange. <xsd:complexType name="AddressValue"> <xsd:choice minOccurs="0" maxOccurs="unbounded"> ... -> <xsd:complexType name="AddressValue"> <xsd:choice minOccurs="0"> ...
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
21-12-2011 17:26 | Anthony Baire | New Issue |
21-12-2011 17:26 | Anthony Baire | Clause Reference(s) | => 11.3.3.20 B.3
21-12-2011 17:26 | Anthony Baire | Source (company - Author) | =>
10-07-2012 14:15 | Gyorgy Rethy | Note Added: 0010758 |
10-07-2012 14:15 | Gyorgy Rethy | Assigned To | => Ina Schieferdecker
10-07-2012 14:15 | Gyorgy Rethy | Status | new => assigned
10-07-2012 14:15 | Gyorgy Rethy | Target Version | => Edition 4.5.1
12-07-2012 10:34 | Ina Schieferdecker | Note Added: 0010864 |
12-07-2012 10:35 | Ina Schieferdecker | Note Added: 0010866 |
12-07-2012 10:36 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Tomas Urban
12-07-2012 10:36 | Ina Schieferdecker | Resolution | open => fixed
12-07-2012 12:04 | Tomas Urban | Note Added: 0010880 |
12-07-2012 12:04 | Tomas Urban | Assigned To | Tomas Urban => Ina Schieferdecker
12-07-2012 13:37 | Ina Schieferdecker | Status | assigned => resolved
12-07-2012 13:37 | Ina Schieferdecker | Status | resolved => closed
12-07-2012 13:38 | Ina Schieferdecker | Fixed in Version | => Edition 4.5.1

Notes

(0010758)
Gyorgy Rethy
10-07-2012 14:15

STF discussion 2012-07-10: we may need several addresses for multicasting. To be checked in the standard.

(0010864)
Ina Schieferdecker
12-07-2012 10:34

It should even be resolved into:
-->
<xsd:complexType name="AddressValue">
<xsd:choice>
meaning that there needs to be an element - if no address value is present, the null element is to be used instead, if it is explicitly omitted, then omit is to be used.
The same fix should be done for AnytypeValue:
<xsd:complexType name="AddressValue">
<xsd:choice minOccurs="0" maxOccurs="unbounded">
-->
<xsd:complexType name="AddressValue">
<xsd:choice>
Please check.

(0010866)
Ina Schieferdecker
12-07-2012 10:35

PS: The addresses in multicasting operations are represented as value lists.

(0010880)
Tomas Urban
12-07-2012 12:04

I agree with the proposed changes, just in the fix for AnytypeValue, AddressValue was accidentally used. The correct text would be: --> <xsd:complexType name="AnytypeValue"> <xsd:choice> With this correction, it can be added to the TCI specification.