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

ID | Project | Category | View Status | Date Submitted | Last Update
0005848 | Part 09: Using XML with TTCN-3 | Clarification | public | 10-12-2010 14:34 | 13-07-2011 14:56

Reporter | Jacob Wieland - Spirent |
Assigned To | Gyorgy Rethy |
Priority | high | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version |  | Fixed in Version |  |
Clause Reference(s) | XSD to TTCN-3 Mapping, section 7.7
For STF discussion |
Source (company - Author) | Testing Technologies - Jacob Wieland

Summary | 0005848: String content of anyAttribute values unspecified

Description

In clause 7.7 it is described that anyAttributes schema-elements shall be mapped to a record of XSD.String field named 'attr' (with additional name conversion for nameclashes). Unfortunately, it is totally unspecified what the content of the decoded strings shall be, i.e. what format it shall have, since it needs to contain both the information about WHICH attribute is set and the value.
Two solutions come to mind:
Change the definition to something more on the line of:
record of record { XSD.String name, XSD.String val } attr
or adding a type in XSD:
type record AnyAttribute { String name, String val }
and then using that type:
record of XSD.AnyAttribute attr
If, on the other hand, the intention of the standard is that the record of XSD.String shall be a flattened list of pairs of strings (i.e. for attr1="val1" attr2="val2" that you get the list { "attr1", "val1", "attr2", "val2" }, it should explicitly say so.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR5848_resolution_v1.doc (199,168) 26-05-2011 17:35 http://oldforge.etsi.org/mantis/file_download.php?file_id=2513&type=bug CR5848_resolution_v2.doc (99,840) 27-05-2011 11:49 http://oldforge.etsi.org/mantis/file_download.php?file_id=2516&type=bug CR5848_resolution_v3.doc (106,496) 27-05-2011 12:10 http://oldforge.etsi.org/mantis/file_download.php?file_id=2517&type=bug

Issue History
Date Modified | Username | Field | Change
10-12-2010 14:34 | Jacob Wieland - Spirent | New Issue |
10-12-2010 14:34 | Jacob Wieland - Spirent | Clause Reference(s) | => XSD to TTCN-3 Mapping, section 7.7
10-12-2010 14:34 | Jacob Wieland - Spirent | Source (company - Author) | => Testing Technologies - Jacob Wieland
13-12-2010 12:47 | Gyorgy Rethy | Target Version | => Edition 4.3.2 (interim)
24-05-2011 15:12 | Gyorgy Rethy | Note Added: 0010027 |
24-05-2011 15:12 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
24-05-2011 15:12 | Gyorgy Rethy | Status | new => assigned
24-05-2011 19:22 | Gyorgy Rethy | Priority | normal => high
25-05-2011 16:57 | Gyorgy Rethy | Note Edited: 0010027 |
26-05-2011 08:48 | Gyorgy Rethy | Note Edited: 0010027 |
26-05-2011 17:35 | Gyorgy Rethy | File Added: CR5848_resolution_v1.doc |
26-05-2011 17:36 | Gyorgy Rethy | Note Added: 0010092 |
26-05-2011 17:36 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Jacob Wieland - Spirent
27-05-2011 11:49 | Jacob Wieland - Spirent | File Added: CR5848_resolution_v2.doc |
27-05-2011 11:52 | Jacob Wieland - Spirent | Note Added: 0010096 |
27-05-2011 11:53 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
27-05-2011 12:10 | Gyorgy Rethy | Note Added: 0010097 |
27-05-2011 12:10 | Gyorgy Rethy | File Added: CR5848_resolution_v3.doc |
27-05-2011 12:11 | Gyorgy Rethy | Status | assigned => resolved
27-05-2011 12:11 | Gyorgy Rethy | Resolution | open => fixed
13-07-2011 14:56 | Gyorgy Rethy | Status | resolved => closed
13-07-2011 14:56 | Gyorgy Rethy | Note Added: 0010217 |
13-07-2011 14:56 | Gyorgy Rethy | Fixed in Version | => Edition 4.3.2 (interim)

Notes

(0010027)
Gyorgy Rethy
24-05-2011 15:12 (edited on: 26-05-2011 08:48)

3GPP related CR. String content has to be specified explicitly, in line with X.693.

(0010092)
Gyorgy Rethy
26-05-2011 17:36

See proposed resoltion text in CR5848_resolution_v1.doc. Jacob, pls. review.

(0010096)
Jacob Wieland - Spirent
27-05-2011 11:52

changed the ' in the element-tag part in the example to ' because to my knowledge ' can only be used in PCDATA (i.e. text between element tags) and not inside element-tags. Otherwise OK. One question, if you have the optional URI followed by whitespace, shall there be a whitespace before the name also if the URI is missing? I.e. should the whitespace not be also in the optional part?

(0010097)
Gyorgy Rethy
27-05-2011 12:10

Hi jacob, you are rigth, the whitespace shall be in the optional part. CR5848_resolution_v3.doc contains this correction, no other changes related to ~_v2.

(0010217)
Gyorgy Rethy
13-07-2011 14:56

Added to master copy.