That's good info, thanks. Ted
On Tue, Aug 17, 2021 at 10:57 AM Steve Lawrence <slawre...@apache.org> wrote: > > Yep, it can definitely be a sizable of effort. The approach we've taken > for these large specifications is to create DFDL schema generators. We > find a machine readable specification (or scrape the PDF specification > to create a machine readable spec) and write some code to read that and > generate schemas. It's still a good amount of work, but scales much > better to the size of the specs, especially for these mil formats that > tend to have lots of repetition. > > We've found this to be pretty successful for VMF, Link16, USTMF, and > other military formats. > > > On 8/16/21 2:30 PM, Theodore Toth wrote: > > I do have a DI2E account and looked at what's available but we'll have > > to parse a number of formats (OTH-GOLD for example) for which schemas > > don't appear to exist :( My gut tells me that this will be a huge > > undertaking. > > > > Ted > > > > On Mon, Aug 9, 2021 at 10:18 AM Steve Lawrence <slawre...@apache.org> wrote: > >> > >> I'm not sure about the unable to parse "//" reference, but I do know > >> Daffodil is capable of modeling, parsing, and unparsing > >> USMTF/Link-16/JREAP and other military formats. > >> > >> If you have access to DI2E.net, there's a handful of schemas available > >> for various FOUO formats like USTMF and Link16: > >> > >> https://bitbucket.di2e.net/projects/DFDL/ > >> > >> Some schemas are more mature/tested than others, and I know some more > >> thorough variants exist that aren't on DI2E, but that should give you an > >> idea of the capabilities/approach. > >> > >> There is also a publicly available schema for MIL-STD-2045 which often > >> comes up when discussing things like UMTF/Link-16/etc. > >> > >> https://github.com/DFDLSchemas/mil-std-2045 > >> > >> - Steve > >> > >> > >> On 8/5/21 11:51 AM, Theodore Toth wrote: > >>> I've just started looking at daffodil for parsing > >>> USMTF/Link-16/JREAP/... and I'd like to know what others experience > >>> has been using this tool and schemas? One 2019 list exchange I came > >>> across discussed the inability to write schema to parse "//" was that > >>> resolved? > >>> > >>> Ted > >>> > >> >
