: dev@daffodil.apache.org
Subject: Re: Help implementing schema for SISO-J
The first portion of one of these Signal PDUs is in BE+MSBF order up
to and including a header for the LINK-16 portion. Then there is the
BE+LSBF data which is a JTIDS header followed by the contents of the J
message.
The pr
implementation.
>
>
> If we implement base64 and/or compress maybe we could get you to develop the
> word-swapping pre/post processor which would would work analogously in
> Daffodil?
>
> ____________
> From: Marshall Miller
> Sent: Thursday, Januar
t you to develop the
word-swapping pre/post processor which would would work analogously in Daffodil?
From: Marshall Miller
Sent: Thursday, January 11, 2018 5:18:26 PM
To: dev@daffodil.apache.org
Subject: Re: Help implementing schema for SISO-J
Also, it occurred
h_slot3 dfdl:outputValueCalc='{ ../slot3 }'
>>
>> h_slot2MSBs dfdl:outputValueCalc="{ ../slot2 idiv dfdl:int('x8') }"
>>
>>
>> or something like that. My details here are probably off by 1 or something.
>>
>>
>> D
shift nor a bit-wise & and
> | operator. Generally it is possible to figure out how to achieve what you
> want by way of mathematical operations.
>
>
> Also note: If you want Link16 specific support we have a channel for FOUO
> email support which is daffodil-fouo-supp...@t
pport which is daffodil-fouo-supp...@tresys.com.
...mike beckerle
Tresys
____
From: Marshall Miller
Sent: Thursday, January 11, 2018 2:34:46 PM
To: dev@daffodil.apache.org
Subject: Help implementing schema for SISO-J
Hello,
I am trying to implement a schem
Hello,
I am trying to implement a schema to describe a LINK-16 message
embedded within a DIS Signal PDU as described by SISO-STD-002 [1],
paragraph 5.2.2.9 and table 5.2.3; commonly referred to as SISO-J.
The problem is that fields are packed into 32 bit words with big
endian byte order, and littl
