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
0005838Part 09: Using XML with TTCN-3Technicalpublic01-12-2010 14:5902-12-2010 08:07
ReporterGyorgy Rethy 
Assigned ToGyorgy Rethy 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Versionv4.3.1 (published 2011-06)Fixed in Versionv4.3.1 (published 2011-06) 
Summary0005838: Specify encoding and decoding processes for anyElement and anyAttribute
DescriptionThe encoding instructions anyElement and anyAttribute are defined but it is not clear how they effect the encoding and the decoding processes.
Additional InformationIt is proposed to add the text to B.3.2 (B.3.3 references B.3.3, therefore no text has to be added to B.3.3):
In the encoding process the content of the TTCN-3 value shall be handled transparently, except when maxOccurs is greater than 1: in this case the elements of the TTCN-3 record of value (corresponding to the any XSD element), shall be concatenated transparently to produce the encoded XML value.
In the decoding process, the decoder shall check if the fragment of the received XML document corresponding to the TTCN 3 field with the "anyElement" encoding instruction fulfils the namespace specification in the encoding instruction and is a well-formed XML (i.e. the content shall be assessed according to XML Schema Part 1 [8] clause 3.10.1, assesment level skip. The failure of the namespace checking or the content assessment shall cause a decoding failure.
TagsNo tags attached.
Clause Reference(s)B.3.2 and B.3.3
For STF discussion
Source (company - Author)L.M.Ericsson
Attached Filesdoc file icon CR5838_resolution.doc [^] (68,608 bytes) 02-12-2010 08:06

- Relationships

-  Notes
(0009899)
Gyorgy Rethy (reporter)
01-12-2010 15:02

 Proposed to accept according to the proposal.
(0009900)
Jacob Wieland - Spirent (reporter)
01-12-2010 15:10

 agreed
(0009911)
Gyorgy Rethy (reporter)
02-12-2010 08:06

 resolution text uploaded.
(0009912)
Gyorgy Rethy (reporter)
02-12-2010 08:07

 Done.

- Issue History
Date Modified Username Field Change
01-12-2010 14:59 Gyorgy Rethy New Issue
01-12-2010 14:59 Gyorgy Rethy Clause Reference(s) => B.3.2 and B.3.3
01-12-2010 14:59 Gyorgy Rethy Source (company - Author) => L.M.Ericsson
01-12-2010 15:02 Gyorgy Rethy Assigned To => Gyorgy Rethy
01-12-2010 15:02 Gyorgy Rethy Status new => assigned
01-12-2010 15:02 Gyorgy Rethy Target Version => Edition 4.3.1 (not yet published)
01-12-2010 15:02 Gyorgy Rethy Additional Information Updated
01-12-2010 15:02 Gyorgy Rethy Note Added: 0009899
01-12-2010 15:03 Gyorgy Rethy Assigned To Gyorgy Rethy => Jacob Wieland - Spirent
01-12-2010 15:10 Jacob Wieland - Spirent Note Added: 0009900
01-12-2010 15:10 Jacob Wieland - Spirent Assigned To Jacob Wieland - Spirent => Gyorgy Rethy
01-12-2010 15:20 Gyorgy Rethy Status assigned => closed
01-12-2010 15:20 Gyorgy Rethy Resolution open => fixed
01-12-2010 15:20 Gyorgy Rethy Fixed in Version => Edition 4.3.1 (not yet published)
02-12-2010 08:06 Gyorgy Rethy Status closed => feedback
02-12-2010 08:06 Gyorgy Rethy Resolution fixed => reopened
02-12-2010 08:06 Gyorgy Rethy Note Added: 0009911
02-12-2010 08:06 Gyorgy Rethy File Added: CR5838_resolution.doc
02-12-2010 08:07 Gyorgy Rethy Status feedback => closed
02-12-2010 08:07 Gyorgy Rethy Note Added: 0009912
02-12-2010 08:07 Gyorgy Rethy Resolution reopened => fixed

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