RE: Support for Canonical EXI interoperability test in TTFMS

Hi Daniel,

I fixed a bug in the TTFMS framework.

Next time you compile the framework and run the test,
you will be able to see schema-informed EXI files generated
when the test case provides one and schema use is enabled.

Thank you,

Takuki Kamiya
Fujitsu Laboratories of America


-----Original Message-----
From: Peintner, Daniel (ext) [mailto:daniel.peintner.ext@siemens.com] 
Sent: Wednesday, October 14, 2015 6:50 AM
To: Takuki Kamiya; public-exi@w3.org
Subject: AW: Support for Canonical EXI interoperability test in TTFMS

Hi Taki,

I uploaded a revised EXIficient library but I agree, I do still see some issues.
(in my test run 20 files out of 115 are still different)

Maybe this has to do with whitespace handling (will send separate email...)

Moreover, I am currently able to run schema-less test runs only by calling
ant run-iot-c14n-classes -DtestCases=config/testCases-restricted/all-v1.xml

Maybe someone can point me to the configuration how to call schema-informed test runs or byteAligned test runs to facilitate debugging.

Thanks,

-- Daniel



________________________________
Von: Takuki Kamiya [tkamiya@us.fujitsu.com]
Gesendet: Dienstag, 13. Oktober 2015 03:23
An: Peintner, Daniel (ext); public-exi@w3.org
Betreff: RE: Support for Canonical EXI interoperability test in TTFMS

Hi Daniel,

I also modified openexi driver so that it always output header options.

However, I still see many differences between exificient and openexi
outputs. We will need to further investigate this.

Thank you,

Takuki Kamiya
Fujitsu Laboratories of America


-----Original Message-----
From: Peintner, Daniel (ext) [mailto:daniel.peintner.ext@siemens.com]
Sent: Thursday, October 01, 2015 5:50 AM
To: Takuki Kamiya; public-exi@w3.org
Subject: AW: Support for Canonical EXI interoperability test in TTFMS

Hi Taki,

Thank you for pointing me to the parameter "measure" which indicates the type of the test run.

I also uploaded a first snapshot of the EXIficient library supporting Canonical EXI. Additional updates may be necessary.
When comparing the encoded files with OpenEXI I do see mostly diffs. I think it is because OpenEXI at the moment does not always include the EXI Options.

Please let me know if you encounter other issues.

Thanks,

-- Daniel

________________________________
Von: Takuki Kamiya [tkamiya@us.fujitsu.com]
Gesendet: Donnerstag, 1. Oktober 2015 01:45
An: Peintner, Daniel (ext); public-exi@w3.org
Betreff: RE: Support for Canonical EXI interoperability test in TTFMS

Hi Daniel,

You should be able to get the test mode by accessing:
measure field (of class MeasureParam) that is in _driverParams (of class DriverParameters)

When it is iot_c14n_encode, you should change the behavior of the
processor to comply with c14n rules.

Do you plan to check-in new EXIficient jar to TTFMS soon?

Thank you,

Takuki Kamiya
Fujitsu Laboratories of America


-----Original Message-----
From: Peintner, Daniel (ext) [mailto:daniel.peintner.ext@siemens.com]
Sent: Wednesday, September 30, 2015 8:28 AM
To: Takuki Kamiya; public-exi@w3.org
Subject: AW: Support for Canonical EXI interoperability test in TTFMS

Hi Taki,

I did check out the new code and it worked as expected.
Thank you for your work!

The only thing I miss is a testCase option that informs about whether the EXI processor is required to produce canonical EXI.

Did I miss anything with that regard?

Thanks,

-- Daniel



P.S. EXIficient does not sort attributes in schema-less mode


________________________________
Von: Takuki Kamiya [tkamiya@us.fujitsu.com]
Gesendet: Dienstag, 29. September 2015 02:20
An: public-exi@w3.org
Betreff: Support for Canonical EXI interoperability test in TTFMS

Hi,

I added support for Canonical EXI interoperability test in TTFMS.

You need to invoke target " run-iot-c14n-classes" in order to run the
encoding process.

After that, diff tools such as WinMerge (on windows) can be used to
compare the encoded files output by various implementations.

Initial experimental run showed quite a lot of differences in encodings
between EXIficient and OpenEXI.

I found at least some of the diffs are due to the attribute orders in
schema-less setting. Is it true that EXIficient sorts attributes whether
it is schema-less or schema-informed?

Thank you,

Takuki Kamiya
Fujitsu Laboratories of America

Received on Tuesday, 20 October 2015 22:06:45 UTC