|
|
|
Re: xsd2ttcn / bug handling substitution group? [message #1798991 is a reply to message #1798944] |
Wed, 28 November 2018 11:47 |
|
Hi OLaf,
when verified with xmllint, the above XSD presents several inconsistencies:
all
<ds:KeyInfo>
<ds:KeyName>tk.12.user@example.org</KeyName>
</ds:KeyInfo>
should be changed to
<ds:KeyInfo>
<ds:KeyName>tk.12.user@example.org</ds:KeyName>
</ds:KeyInfo>
and teh final
<KeyInfo>
<KeyName>tk.12.user@example.org</KeyName>
</KeyInfo>
is maybe in the wrong namespace too.
Just my two cents
BR
Elemer
|
|
|
|
|
|
|
|
|
|
|
Re: xsd2ttcn / bug handling substitution group? [message #1799736 is a reply to message #1799690] |
Thu, 13 December 2018 08:13 |
|
Hi Olaf,
the way Titan supports XSD to TTCN-3 conversion is aligned with the standard part 9:
-the standard allows for explicit conversion , that is to generate an intermediate TTCN-3 code (instead of implicit where you can import directly the XSD)
-the only difference the -o option makes is that instead of generating a TTCN-3 file per namespace , Titan will generate a single TTCN-3 file , which is not in contradiction with the standard, which states:
"The mapping shall start on a set of valid XSD schema-s and shall result in a set of valid TTCN-3 modules. "
That being said, you will have to edit you ATS as follows:
-replace all
import from aaa.xsd all;
with
import from filegeneratedfromxsds all; //ttcn-3 file
Best regards
Elemer
[Updated on: Thu, 13 December 2018 08:55] Report message to a moderator
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05931 seconds