- From: Takuki Kamiya <tkamiya@us.fujitsu.com>
- Date: Wed, 30 Sep 2015 16:45:28 -0700
- To: "Peintner, Daniel (ext)" <daniel.peintner.ext@siemens.com>, "public-exi@w3.org" <public-exi@w3.org>
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 Wednesday, 30 September 2015 23:46:14 UTC