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

ID | Project | Category | View Status | Date Submitted | Last Update
0003314 | Part 09: Using XML with TTCN-3 | Technical | public | 06-05-2008 13:38 | 30-10-2008 14:10

Reporter | user363 |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | major | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v3.3.1 (published 2008-04) |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version | v4.1.1 (published 2009-06) |
Clause Reference(s) | 5.3 and one to be introduced
For STF discussion |
Source (company - Author) |

Summary | 0003314: "mixed" shall be honored

Description

The XSD-type-attribute "mixed" currently is declared as "unsupported". It shall be supported in the meaning that it shall be honored and modify the mapping of the attributed element in a way so that the text content between the element content is mapped to string fields.
Proposed changes:
- Clause 5.3 shall not list the current point d) anymore.
- A new clause must be introduced to specify the following:
"Mixed content
An element which has the attribute 'mixed' may contain a starting text node before any maybe present element node it contains and a text node following each element node it contains. These text nodes (which might be the empty string) are stored in the element surrounding them in an array structure which is parallel to the array for the contained elements. Example:
<complexType name="xmpl" mixed="true">
<sequence>
<element name="elem" type="string" maxOccurs="5"/>
</sequence>
</complexType>
This will be mapped thus:
type record Xmpl
{
record length(1..5) of record
{
XSD.String elem;
} sequence_list,
record length(2..6) of XSD.String mixed_content
}
with
{
variant "name as uncapitalized";
}
Reasoning:
The current draft specifies the feature "mixed" as "unsupported" which means that this information shall be neglected. In this case the strings (which are relevant as declared by the Schema) are not stored in the resulting TTCN-3 types. At compile time, this will not raise any problem but of course during runtime this behavior cannot be considered wished as it will either raise exceptions or drop relevant information. So the current version obfuscates problems.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR3314_analysis_2008-07.ppt (69,632) 18-07-2008 09:45 http://oldforge.etsi.org/mantis/file_download.php?file_id=1561&type=bug CR3314_mixedContent_solution.doc (183,296) 15-10-2008 09:56 http://oldforge.etsi.org/mantis/file_download.php?file_id=1693&type=bug

Issue History
Date Modified | Username | Field | Change
06-05-2008 13:38 | user363 | New Issue |
06-05-2008 13:38 | user363 | Status | new => assigned
06-05-2008 13:38 | user363 | Assigned To | => Gyorgy Rethy
06-05-2008 13:38 | user363 | Clause Reference(s) | => 5.3 and one to be introduced
06-05-2008 13:38 | user363 | Source (company - Author) | =>
09-05-2008 10:38 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
18-07-2008 09:45 | Gyorgy Rethy | File Added: CR3314_analysis_2008-07.ppt |
18-07-2008 09:47 | Gyorgy Rethy | Note Added: 0006326 |
18-07-2008 09:47 | Gyorgy Rethy | Resolution | open => fixed
15-10-2008 09:55 | Gyorgy Rethy | Note Added: 0007067 |
15-10-2008 09:55 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Thomas DeiÃŸ
15-10-2008 09:56 | Gyorgy Rethy | File Added: CR3314_mixedContent_solution.doc |
15-10-2008 16:47 | Thomas DeiÃŸ | Note Added: 0007078 |
15-10-2008 16:48 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Gyorgy Rethy
30-10-2008 14:10 | Gyorgy Rethy | Status | assigned => closed
30-10-2008 14:10 | Gyorgy Rethy | Note Added: 0007222 |
30-10-2008 14:10 | Gyorgy Rethy | Fixed in Version | => Edition 4.1.1 (not yet published)

Notes

(0006326)
Gyorgy Rethy
18-07-2008 09:47

Agreed to add mapping of mixed to Part-9. Concrete mapping shall be aligned with X.694.

(0007067)
Gyorgy Rethy
15-10-2008 09:55

See proposed solution in CR3314_mixedContent_solution.doc; pls. cross-check

(0007078)
Thomas DeiÃŸ
15-10-2008 16:47

There's one typo in the first paragraph in clause 7.6.8, line 5: elemenys -> elements. Otherwise the proposal is ok.

(0007222)
Gyorgy Rethy
30-10-2008 14:10

Done in master copy (also typo corrected).