fodil CLI tool can kill 2 birds with one stone in that we will be
> adding support for EXI as well as demonstrating how to pass in your own SAX
> ContentHandler.
> >
> > Josh
> > ____________________
> > From: Mike Beckerle
> > Sent: Monday, July 11,
m: Mike Beckerle
Sent: Monday, July 11, 2022 3:19 PM
To: dev@daffodil.apache.org
Subject: CLI -I sax feature - remove?
In the CLI, there is the -I option to specify infoset-type.
One of the choices is 'sax'.
This is a mistake I think. This is really "XML text by way of calling the
SAX API"
By this argument, should we also remove JDOM, W3CDOM, and Scala XML
infoset outputters from the CLI? These are also effectively API's as
well. The CLI just takes the results and converts them to a string for
output.
Maybe the CLI only cares about outputting to XML using the XML Text
Infoset
Roger that.
From: Mike Beckerle
Sent: Monday, July 11, 2022 4:52 PM
To: Thompson, Dave
Cc: dev@daffodil.apache.org; Adams, Joshua
Subject: Re: CLI -I sax feature - remove?
(I'd swear I replied to this already, but not in the thread so... rinse, repeat)
I do realize we didn't add
To: dev@daffodil.apache.org; mbecke...@apache.org
> Subject: Re: CLI -I sax feature - remove?
>
> Funnily enough I was just having a conversation with Dave Thompson about
> this very thing. When I mentioned that we will have a "-I exi" option for
> the command line tool
dil CLI
tool can kill 2 birds with one stone in that we will be adding support for EXI
as well as demonstrating how to pass in your own SAX ContentHandler.
Josh
From: Mike Beckerle
Sent: Monday, July 11, 2022 3:19 PM
To: dev@daffodil.apache.org
Subject: CLI -I sax
tool can kill 2 birds with one stone in that we will be adding support for EXI
as well as demonstrating how to pass in your own SAX ContentHandler.
Josh
From: Mike Beckerle
Sent: Monday, July 11, 2022 3:19 PM
To: dev@daffodil.apache.org
Subject: CLI -I sax
+1 from me. Sounds like the right way to go.
-Original Message-
From: Mike Beckerle
Sent: Monday, July 11, 2022 3:19 PM
To: dev@daffodil.apache.org
Subject: EXT: CLI -I sax feature - remove?
WARNING: This email originated from outside of GE. Please validate the sender's
email address
In the CLI, there is the -I option to specify infoset-type.
One of the choices is 'sax'.
This is a mistake I think. This is really "XML text by way of calling the
SAX API". It's effectively a testing mode for us.
SAX usage is inherently an API.
I believe we should remove this feature from the
