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

ID | Project | Category | View Status | Date Submitted | Last Update
0004411 | Part 09: Using XML with TTCN-3 | Technical | public | 05-11-2008 14:18 | 20-04-2009 11:44

Reporter | Gyorgy Rethy |
Assigned To | Gyorgy Rethy |
Priority | high | Severity | major | Reproducibility | always
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version | v4.1.1 (published 2009-06) |
Clause Reference(s) | All
For STF discussion |
Source (company - Author) | L.M.Ericsson

Summary | 0004411: Use of field names in encoding instructions

Description

Currently in several examples the name of the field, to which an encoding instruction shall be associated, is included into the variant attribute; e.g.
type record E17a {
XSD.Float bar optional,
XSD.Integer foo optional
}
with {
variant "attribute 'foo', 'bar'";
variant "name as uncapitalized ";
}
TTCN-3 provides a standard mechanism to associate attributes to fields which is already implemented in tools. Therefore this standard mechanism shall be used instead of the XSD-mapping specific one. This simplifies the implementation of TTCN-3 compilers. E.g. the example above becomes:
type record E17a {
XSD.Float bar optional,
XSD.Integer foo optional
}
with {
variant "name as uncapitalized ";
variant (bar, foo) "attribute"
}

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | es_20187309v030301p_comments.doc (937,984) 26-11-2008 07:43 http://oldforge.etsi.org/mantis/file_download.php?file_id=1784&type=bug

Issue History
Date Modified | Username | Field | Change
05-11-2008 14:18 | Gyorgy Rethy | New Issue |
05-11-2008 14:18 | Gyorgy Rethy | Status | new => assigned
05-11-2008 14:18 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
05-11-2008 14:18 | Gyorgy Rethy | Clause Reference(s) | => All
05-11-2008 14:18 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
25-11-2008 10:39 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Thomas DeiÃŸ
26-11-2008 07:43 | Thomas DeiÃŸ | File Added: es_20187309v030301p_comments.doc |
26-11-2008 07:45 | Thomas DeiÃŸ | Note Added: 0007431 |
26-11-2008 07:45 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Gyorgy Rethy
10-12-2008 10:00 | Gyorgy Rethy | Note Added: 0007619 |
10-12-2008 10:00 | Gyorgy Rethy | Status | assigned => resolved
10-12-2008 10:00 | Gyorgy Rethy | Resolution | open => fixed
10-12-2008 10:01 | Gyorgy Rethy | Note Added: 0007620 |
10-12-2008 10:01 | Gyorgy Rethy | Note Added: 0007621 |
12-12-2008 11:30 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
17-12-2008 09:39 | Ina Schieferdecker | Fixed in Version | => Edition 4.1.1 (not yet published)
20-04-2009 11:44 | Ina Schieferdecker | Status | resolved => closed

Notes

(0007431)
Thomas DeiÃŸ
26-11-2008 07:45

Proposed change is ok for me. There was no solution file. I crosschecked part 9 where this change would be relevant. At least some of the occurrences are already handled by the other CRs. There are also a couple of other issues, please crosscheck in the attached commented version of part 9.

(0007619)
Gyorgy Rethy
10-12-2008 10:00

Changes to be done by cross-checking the master document after aother CRs are implemented.

(0007620)
Gyorgy Rethy
10-12-2008 10:01

Changes to be done by cross-checking the master document after aother CRs are implemented.

(0007621)
Gyorgy Rethy
10-12-2008 10:01

Changes to be done by cross-checking the master document after aother CRs are implemented.