On Nov 20, 2007 2:33 AM, Basil Gasser <[EMAIL PROTECTED]> wrote: > thanks for the answers. This point is clear,however it brought up some > new questions. > The Hex Format still is not clear. Especially not for arrays. > What must the xml encoding of an array in Hex format look like, i.e. are > they grouped into blocks of 4 separated by spaces? If so, what about > padding? For example, if we have a byte array in hex format. One needs > two hex digits to represent a byte. But what if a byte's value is > smaller than 16 (-> value can be decoded by a single hex digit). Do we > add a leading zero to the xml encoding? > For example: > Having a byte array with two elements: [255,1]. Now, if we encode this > as xml in hex format, do we have <element>FF1</element> or > <element>FF01</element> or should be group it by byte using spaces, > giving us <element>FF 1</element> or possibly <element>FF 01</element>? > <element>FF01</element>would make the most sense to me. > > best. > Basil
The LTK-XML schema is implied by the 'def file but to answer questions like this you need to look at both side. Bit arrays are represented as xs:hexBinary so they must be two nibbles. That is, they will always be at least two characters. The way we've been treating Byte arrays is to generate xs:hexBinary values, no spaces. For all other integer arrays we space separate the hex values. -- John. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
