I actually ran into this problem with parsing a large jpeg file. I thought that
I had uncovered a bug because the file was not being parsed correctly. Once it
was pointed out to me, the problem was solved by changing the tunable to
increase the REGex search length, the file parsed as expected.
I could put the dfdl schema and schematron schema that I was using to test GIF
files somewhere if that would be helpful.
On 2020/12/18 17:21:02, John Wass wrote:
> The Embedded Schematron PR is moving along, hoping to get it out of WIP
> soon. https://github.com/apache/incubator-daffodil/pull/
I took a look at the sample xsd's with the imbedded schematron asserts. It
looks good. Does the process create SVRL files when it completes? Is there a
commandline option to direct the SVRL file to a specific path and name?
I was recently working with a modified daffodil GIF schema and schema
I’m still new at this – but I’ve found a great way to learn is to invite people
to tell me I’m wrong, so here’s my two cents.
SDE in particular is generally used to tell the parser that something has gone
wrong. This invites the parser to either back up to the most recent point of
uncertainty a
I hoping someone could give me some pointers on adding a warning message to the
Daffodil io code.
I'm looking at Daffodil-412 and want to generate a warning message when the
REGex search gets expanded and another if it exceeds the tunable for maximum
length.
I've located the code that does thes
Well, admittedly some of my observations may be dated to using Eclipse. I agree
IntelliJ does seem to just generally a better job on all forms of XML/XSD/DFDL.
The advantage of a element would be that it wouldn't matter that
the tooling is smart. Any XML-aware tool would treat these as XML docu
> If you have edited tdml in an XML aware editor, you know that the support
for embedded dfdl schemas is better than it is in xsd editors for a dfdl
schema file.
Better in what way? They looked pretty similar to me, in intellij.
On Fri, Dec 18, 2020 at 12:35 PM John Wass wrote:
> Thanks for t
Thanks for the feedback. It was in line with what I figured. There is a
chance the ambiguity I am seeing between .dfdl.xsd and .xsd is self
inflicted, but just wanted to put this out there.
On Fri, Dec 18, 2020 at 10:14 AM Beckerle, Mike <
mbecke...@owlcyberdefense.com> wrote:
> If you have e
The Embedded Schematron PR is moving along, hoping to get it out of WIP
soon. https://github.com/apache/incubator-daffodil/pull/463
The JPEG and BMP schema repos are being used for testing now, and the PNG
looks like it would provide some great coverage.. maybe too great :/ Any
other noteworthy
If you have edited tdml in an XML aware editor, you know that the support for
embedded dfdl schemas is better than it is in xsd editors for a dfdl schema
file.
For that reason I thought maybe we should use the ".dfdl" extension for a
daffodil feature which replaces the xs:schema element of a df
I think the main reason for the .xsd extension is so IDEs/editors
recognize the file as a normal XML Schema file, and so you get all the
benefits that come with that (e.g. autocompletion, syntax highlighting,
error checking), since most tools aren't going to know about a DFDL
schema, at least by de
Doing a little work with software that cares about file extensions,
resulting in a couple questions about the history and future of the dfdl
file extension.
1, Why was the extension of .dfdl.xsd used?
2. What issues would arise by dropping the xsd part?
3. Are there any other extensions being used
12 matches
Mail list logo
