You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@daffodil.apache.org by "Costello, Roger L." <co...@mitre.org> on 2018/12/19 13:54:52 UTC
Summary of what is and isn't impacted by dfdl:byteOrder
Hello DFDL community,
I want to be sure that I understand what is and isn't impacted by dfdl:byteOrder.
Below is my summary. Is it correct?
* xs:unsignedInt and xs:unsignedLong are affected by the value of dfdl:byteOrder
* xs:hexBinary and xs:string are not affected by the value of dfdl:byteOrder
* Suppose the input file has this value (as viewed in a hex editor): 48 69
* The input is read into the <field> element.
* If field is declared to be of type xs:unsignedInt and dfdl:byteOrder="littleEndian" then here is the value of the element: 26952
* If field is declared to be of type xs:unsignedInt and dfdl:byteOrder="bigEndian" then here is the value of the element: 18537
* If field is declared to be of type xs:string then here is the value of the element: Hi
* If field is declared to be of type xs:hexBinary then here is the value of the element: 4869
Re: Summary of what is and isn't impacted by dfdl:byteOrder
Posted by Mike Beckerle <mb...@tresys.com>.
I didn't double check your base 2 to base 10 conversions, but what you've said below sounds right.
However, until a recent fix to Daffodil, xs:hexBinary IS affected by byte order, so if you are using the released v2.2.0 of daffodil, you will see xs:hexBinary show sensitivity to byte order.
________________________________
From: Costello, Roger L. <co...@mitre.org>
Sent: Wednesday, December 19, 2018 8:54:52 AM
To: users@daffodil.apache.org
Subject: Summary of what is and isn't impacted by dfdl:byteOrder
Hello DFDL community,
I want to be sure that I understand what is and isn’t impacted by dfdl:byteOrder.
Below is my summary. Is it correct?
* xs:unsignedInt and xs:unsignedLong are affected by the value of dfdl:byteOrder
* xs:hexBinary and xs:string are not affected by the value of dfdl:byteOrder
* Suppose the input file has this value (as viewed in a hex editor): 48 69
* The input is read into the <field> element.
* If field is declared to be of type xs:unsignedInt and dfdl:byteOrder="littleEndian" then here is the value of the element: 26952
* If field is declared to be of type xs:unsignedInt and dfdl:byteOrder="bigEndian" then here is the value of the element: 18537
* If field is declared to be of type xs:string then here is the value of the element: Hi
* If field is declared to be of type xs:hexBinary then here is the value of the element: 4869