|Eclipse Titan statement of compliance [message #1734814]
||Mon, 13 June 2016 08:25
|| Elemer Lelik
Registered: January 2015
if you were curious enough to look through the documentation supplied with Titan, you may have discovered a new document,
namely a statement of compliance, describing in detail conformance to the TTCN-3 standard.
This statement of compliance(or statement of conformity, if you prefer) is based on the form and test suites published by ETSI at
There are two such form and suites published,
TS 102 950 1.5.1 Covering Core Language (ES 201 873-1 V4.7.1)
TS 103 255 1.2.1 Covering XML schema (ES 201 873-9 V4.6.1)
one for the core language and one for XML.
ASN.1 and the rest of the standards and extensions to the standard are not covered.
The aforementioned document
extends to the core language only; we are currently working on the XML part , and this will be published in the next release.
Using this document anyone can verify which parts of the implementation are not adhering to the standard.
In our approach non-confomities fall into one of the following categories:
-implementation errors: for instance , the compiler delivers a warning instead of a compiler error when "*" is used for mandatory field;
these should be documented with a trouble report and fixed with the highest priority
-features not yet implemented, e.g. "select union" (typically features introduced in later revisions of the standard)
these should be documented with a change request and should be implemented with their specific priorities and as resources permit
-deliberate non-conformities: for example, a number of test cases fail as Titan does not support selective import
and we don't have an intention to change this, as visible benefits are not so great, but the required changes are resource-intensive.
All such non-confomities should be documented in the reference guide Ch.2 "TTCN-3 Limitations in this version"
Our ambition is that all non-conformites referring to the core language part will be documented and possibly fixed as above in the next release, due
towards the end of the year.
[Updated on: Mon, 13 June 2016 14:17]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01613 seconds