XSLT Processors and the TDD_to_openEHR.xsl

Technical (archive)
1

Hi everybody,

I got a question regarding the TDD_to_openEHR.xsl. So far I used the XSLT processor of altova which works great. Nevertheless, to achieve a better integration into Microsoft SSIS, I would like to use a .net based processor. I tried to use recent versions of Saxon and XMLPrime but failed (the created target document is blank). I guess those processors are more complient with w3c specs than altova but I still have not found the point of failure.

Do you have any experience concerning this issue?

Thanks and have great week,

2

Hi Birger,

Using Oxygen I have found that the transform works with

MSXML.net 4.0
Saxon 6.5
Saxon PE 9.5.1.2

but not Saxon EE 9.5.1.2

The problem seems to be that the latter does an initial validation
check which fails (expected) because we are overriding a DV_TYEXT with
a DV_CODED_TEXT i.e the data contains defining_code etc. The override
is valid in openEHR but breaks the TDS schema - this is expected and
we just ignore these validation errors.

If you email your TDD privately I would be happy to test it here.

Ian

3

Hi Ian,

thank you very much for pointing out the issues with Saxon EE. It really freaked me out :slight_smile: In the meantime I was lucky to find a copy and get a workaround with AltovaXML 2008. I'm not sure if it will be the final solution but it works smoothly so far. Nevertheless, I will give Saxon another try and will provide feeback about my experiences!

Thanks for your help!

Birger