xsd2ttcn / bug handling substitution group? [message #1798749] |
Fri, 23 November 2018 08:46  |
Eclipse User |
|
|
|
Hi XSD-Titan experts,
We at ETSI/STF160 are working developing test suites for 3GPP which require complex XSDs like the ones in
ftp://ftp.3gpp.org/specs/2018-09/Rel-13/33_series/33179-d70.zip
which use the substitution group attribute.
When working with this TS 33.179 we found following problem:
We cannot use the XSDs to generate the correct TTCN type defs. The encryption keys in the XML document should be encoded, for example as
<UserDecryptKey >
<EncryptedKey >
<EncryptionMethod Algorithm="aes256"/>
<ds:KeyInfo> <ds:KeyName>tk.12.user@example.org</KeyName>
</ds:KeyInfo> <CipherData> <CipherValue>DEADBEEF</CipherValue> </CipherData>
</EncryptedKey>
</UserDecryptKey>
The xsd2ttcn converter produces correctly
type union UserDecryptKey_group
{
KeyContentType userDecryptKey,
EncUserDecryptKey encUserDecryptKey
}
But EncUserDecryptKey resolves to simply KeyContentType instead of EncryptedKey which should be imported from module http_www_w3_org_2001_04_xmlenc.
My question: Is this an xsd2ttcn conversion issue, or the XSDs in TS 33.179 are faulty?
Attached the XSDs and the generated TTCN code.
Any hints will be appreciated.
Regards,
Olaf@ETSI-ST160
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.42149 seconds