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

ID | Project | Category | View Status | Date Submitted | Last Update
0006685 | Part 09: Using XML with TTCN-3 | Clarification | public | 06-02-2014 13:39 | 04-11-2015 09:34

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.5.1 (published 2013-04) |
Target Version | v4.6.1 (published 2015-06) | Fixed in Version | v4.6.1 (published 2015-06) |
Clause Reference(s) | 6.8
For STF discussion |
Source (company - Author) | Elvior

Summary | 0006685: Splitting rules for xsd:anyType

Description

According to 6.8, xsd:anyType content is mapped to a record of strings. However, the specification doesn't provide any guideline on how to split received XML content into individual strings which makes matching of these fields nearly impossible.
There's of course a possibility that it is a tool-dependent feature, but in such a case, it should be explicitly stated in the specification so that developers don't include fields of this type in matching patterns of test suites meant for public use (such as the test suites developed in ETSI STFs).
However, I would prefer if binding rules were added to the specification. When creating those rules, all possible content types should be considered, especially:
- primitive data
- nested complex content
- sequence of elements
- mixed content
The clause 6.8 should contain an example on each of the above mentioned data contents too.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

has duplicate | 0006842 | closed | Gyorgy Rethy | Rule for anyType shall not be a comment
has duplicate | 0006869 | closed | Gyorgy Rethy | AnyType in XSD module is missing embed_values field

Attached Files | CR6685_resolution_v1.doc (192,512) 08-12-2014 16:46 http://oldforge.etsi.org/mantis/file_download.php?file_id=3193&type=bug CR6685_resolution_v2.doc (208,896) 12-12-2014 11:31 http://oldforge.etsi.org/mantis/file_download.php?file_id=3196&type=bug CR6685_resolution_v3.doc (210,432) 15-12-2014 09:22 http://oldforge.etsi.org/mantis/file_download.php?file_id=3198&type=bug

Issue History
Date Modified | Username | Field | Change
06-02-2014 13:39 | Tomas Urban | New Issue |
06-02-2014 13:39 | Tomas Urban | Clause Reference(s) | => 6.8
06-02-2014 13:39 | Tomas Urban | Source (company - Author) | => Elvior
07-04-2014 14:10 | Jens Grabowski | Assigned To | => Gyorgy Rethy
07-04-2014 14:10 | Jens Grabowski | Status | new => assigned
07-04-2014 14:10 | Jens Grabowski | Note Added: 0011940 |
08-04-2014 17:06 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2015-06)
07-11-2014 12:38 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Tomas Urban
07-11-2014 12:40 | Gyorgy Rethy | Note Added: 0012493 |
08-12-2014 16:46 | Gyorgy Rethy | File Added: CR6685_resolution_v1.doc |
08-12-2014 16:49 | Gyorgy Rethy | Note Added: 0012536 |
08-12-2014 16:50 | Gyorgy Rethy | Status | assigned => confirmed
10-12-2014 09:39 | Tomas Urban | Note Added: 0012537 |
10-12-2014 09:39 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
11-12-2014 13:34 | Gyorgy Rethy | Relationship added | parent of 0006842
11-12-2014 13:36 | Gyorgy Rethy | Relationship replaced | has duplicate 0006842
12-12-2014 11:31 | Gyorgy Rethy | File Added: CR6685_resolution_v2.doc |
12-12-2014 11:33 | Gyorgy Rethy | Note Added: 0012544 |
12-12-2014 11:34 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Tomas Urban
15-12-2014 09:22 | Tomas Urban | File Added: CR6685_resolution_v3.doc |
15-12-2014 09:25 | Tomas Urban | Note Added: 0012549 |
15-12-2014 09:25 | Tomas Urban | Status | confirmed => resolved
15-12-2014 09:25 | Tomas Urban | Resolution | open => fixed
15-12-2014 09:25 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
30-12-2014 20:03 | Gyorgy Rethy | Note Added: 0012592 |
30-12-2014 20:03 | Gyorgy Rethy | Status | resolved => closed
30-12-2014 20:03 | Gyorgy Rethy | Fixed in Version | => v4.6.1 (published 2015-06)
04-11-2015 09:34 | Gyorgy Rethy | Relationship added | has duplicate 0006869

Notes

(0011940)
Jens Grabowski
07-04-2014 14:10

György, will investigate the problem.

(0012493)
Gyorgy Rethy
07-11-2014 12:40

We shall look at ASN.1, X.695 if they have a rule on using the RECORD OF. If yes, and technically sound, we should take it over, if not, we need to define a technically sound way.

(0012536)
Gyorgy Rethy
08-12-2014 16:49

Please find and review the proposed solution in CR6685_resolution_v1.doc. I still have to look at, if the case when the <element> of type anyType is nillable, does it need any additional text or just a note refering to the nillable clause.

(0012537)
Tomas Urban
10-12-2014 09:39

The proposed changes are fine by me. For nillable elements, I think a note would be sufficient.

(0012544)
Gyorgy Rethy
12-12-2014 11:33

OK, thinking further, I cannot see a reason even for a note (equally we could add notes to take into account other facets influencing the mapping, e.g. minOccurs/maxOccurs), but I have added an example. Pls. check, and if correct, set the CR to resolved.

(0012549)
Tomas Urban
15-12-2014 09:25

Apart from one cosmetic problem with quotes (corrected in the 3rd version of the resolution), the proposed changes solve the CR and the resolution can be added to the new version of the TTCN-3 specification.

(0012592)
Gyorgy Rethy
30-12-2014 20:03

Added to draft V4.5.3