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

ID | Project | Category | View Status | Date Submitted | Last Update
0007100 | Part 09: Using XML with TTCN-3 | Technical | public | 06-07-2015 16:44 | 04-12-2015 15:21

Reporter | Gyorgy Rethy |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | major | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.6.1 (published 2015-06) |
Target Version | v4.7.1 (published 2016-07) | Fixed in Version | v4.7.1 (published 2016-07) |
Clause Reference(s) | 7.1.1
For STF discussion |
Source (company - Author) | L.M.Ericsson

Summary | 0007100: Mapping of XSD id attributes

Description

Today, the mapping of id attributes of XSD components is wrong.
Each id attribute is mapped to a stand-alone TTCN-3 type (see $7.1.1). Hovewer, XSD allows to assign id-s to all XSD elements (including <schema>) but <documentation> (see attached example, which is valid XSD). The mapping today is not able to bind the id attribute values to the XSD elements defining them.
Proposed solutions:
TTCN-3 with attributes can be added to any TTCN-3 definition or a field of it, thus
- either define an encoding instruction and map the id attribute value to it; this would allow to encode the id value into the XML document at sending and checking the id value at reception;
a consistent form could be
variant """ id as 'freetext' """,
where freetext contains the value of the id attribute;
- or ignore the id attributes (in principle it may cause problems when testing applications expecting the id-s in the encoded XML).

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | all.xsd (2,238) 06-07-2015 16:44 http://oldforge.etsi.org/mantis/file_download.php?file_id=3218&type=bug CR7100.docx (687,836) 02-11-2015 14:10 http://oldforge.etsi.org/mantis/file_download.php?file_id=3336&type=bug

Issue History
Date Modified | Username | Field | Change
06-07-2015 16:44 | Gyorgy Rethy | New Issue |
06-07-2015 16:44 | Gyorgy Rethy | File Added: all.xsd |
03-08-2015 11:28 | Gyorgy Rethy | Note Added: 0013024 |
03-08-2015 11:28 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
03-08-2015 11:28 | Gyorgy Rethy | Status | new => assigned
02-11-2015 10:09 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Jacob Wieland - Spirent
02-11-2015 13:52 | Jacob Wieland - Spirent | Note Added: 0013437 |
02-11-2015 14:10 | Jacob Wieland - Spirent | File Added: CR7100.docx |
02-11-2015 14:11 | Jacob Wieland - Spirent | Note Added: 0013440 |
02-11-2015 14:11 | Jacob Wieland - Spirent | Status | assigned => resolved
02-11-2015 14:11 | Jacob Wieland - Spirent | Fixed in Version | => v4.7.1 (published 2016-07)
02-11-2015 14:11 | Jacob Wieland - Spirent | Resolution | open => fixed
02-11-2015 14:11 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
04-12-2015 15:21 | Gyorgy Rethy | Note Added: 0013558 |
04-12-2015 15:21 | Gyorgy Rethy | Status | resolved => closed

Notes

(0013024)
Gyorgy Rethy
03-08-2015 11:28

STF discussion 03-08-2015: Check how id-s are used in XML encoding.

(0013437)
Jacob Wieland - Spirent
02-11-2015 13:52

as far as I understand, the id attributes in the schema definition have no bearing on the XML (not to be confused with attributes of type xsd:ID), they simply allow uniquely identifying components of a schema, probably so that these components can be referenced by some schema-referencing mechanism.
Therefore, in principle, the current definition in the standard is correct, allowing the types that the schema-components are mapped to also to be referenced by their ID-alias type. However, since these types do not really add any value in the TTCN-3 context, maybe they can be ignored in the mapping altogether (or added as variant attribute). For schema-components which are not mapped to a TTCN-3 type or field, but which are mapped to a TTCN-3 construct (like a module), a variant attribute might be the only way of preserving this information.

(0013440)
Jacob Wieland - Spirent
02-11-2015 14:11

according to STF discussion: mark feature as deprecated (see proposal)

(0013558)
Gyorgy Rethy
04-12-2015 15:21

Added to draft V4.6.3