Logo etsi

ETSI's Bug Tracker
Main | My View | View Issues | Change Log | Roadmap | Monitor project
  
Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005164Part 09: Using XML with TTCN-3Clarificationpublic08-05-2009 15:4201-02-2010 09:37
ReporterGyorgy Rethy 
Assigned ToIna Schieferdecker 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Versionv4.2.1 (published 2010-07)Fixed in Versionv4.2.1 (published 2010-07) 
Summary0005164: useorder and untagged should not be used together
DescriptionX.693 amd1, 35.2.8 excludes using the useorder and the untagged encoding instructions together. In the last example in $7.9 they are used together. This has to be clarified in the text and the example has to be corrected.
TagsNo tags attached.
Clause Reference(s)7.9
For STF discussion
Source (company - Author)L.M.Ericsson
Attached Filesdoc file icon CR5164_resolution_v1.doc [^] (152,064 bytes) 02-09-2009 17:28
doc file icon CR5164_resolution_v2.doc [^] (155,648 bytes) 08-12-2009 12:26

- Relationships

-  Notes
(0008967)
Gyorgy Rethy (reporter)
02-09-2009 17:43

 CR5164_resolution_v1.doc: first draft for resolution: description of the untagged encoding instruction (missing in published versions).

The original question still needs to be clarified: are the useOrder and untagged instructions allowed together? When converting XSD Schemas, they may be used together in one case: both attached to the record type generated for a model group definition with the compositor <all>.

ASN.1 forbids the joint use of USE-ORDER and UNTAGGED (in X.693) but X.694 ignores model groups with compositor <all>, therefore their combination simply never needed. TTCN-3 Part-9 differs in this from X.694.

Generating a type for model groups with compositor <all> would be incorrect in the case if XSD allowed referencing more than one such model group within a single ComplexType content. In this case the order field (which is an additional record of enumerated) should combine all elements from all referenced groups. But it still needs to be checked if XSD allows this or not.
(0009084)
Gyorgy Rethy (reporter)
07-12-2009 16:25
edited on: 08-12-2009 12:26

 CR5164_resolution_v2.doc: clarified and updated: useOrder and untagged can be used together but name as and untagged should not (the rule to handle such cases is defined, thus should not cause an error); ready for review

- Issue History
Date Modified Username Field Change
08-05-2009 15:42 Gyorgy Rethy New Issue
08-05-2009 15:42 Gyorgy Rethy Status new => assigned
08-05-2009 15:42 Gyorgy Rethy Assigned To => Gyorgy Rethy
08-05-2009 15:42 Gyorgy Rethy Clause Reference(s) => 7.9
08-05-2009 15:42 Gyorgy Rethy Source (company - Author) => L.M.Ericsson
30-06-2009 10:28 Ina Schieferdecker Target Version => Edition 4.2.1 (not yet published)
02-09-2009 11:41 Gyorgy Rethy File Added: CR5164_resolution_v1.doc
02-09-2009 17:28 Gyorgy Rethy File Deleted: CR5164_resolution_v1.doc
02-09-2009 17:28 Gyorgy Rethy File Added: CR5164_resolution_v1.doc
02-09-2009 17:43 Gyorgy Rethy Note Added: 0008967
07-12-2009 16:21 Gyorgy Rethy File Added: CR5164_resolution_v2.doc
07-12-2009 16:25 Gyorgy Rethy Note Added: 0009084
08-12-2009 12:24 Gyorgy Rethy File Deleted: CR5164_resolution_v2.doc
08-12-2009 12:26 Gyorgy Rethy File Added: CR5164_resolution_v2.doc
08-12-2009 12:26 Gyorgy Rethy Note Edited: 0009084
08-12-2009 12:27 Gyorgy Rethy Assigned To Gyorgy Rethy => Ina Schieferdecker
01-02-2010 09:37 Gyorgy Rethy Status assigned => closed
01-02-2010 09:37 Gyorgy Rethy Resolution open => fixed
01-02-2010 09:37 Gyorgy Rethy Fixed in Version => Edition 4.2.1 (not yet published)

MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker