-
When I install the extension (version 0.0.6), I don't yet know how to start a debug session. I guessed that I need to make a launch configuration, so I added
```json
{
"type": "dfdl",
…
-
Have the Daffodil debugger backend zip added to the VSIX and have the extension use this file instead of trying to download the zip file from the releases url of the repo
-
While testing edifact example, there is an error on building the D03B EDIFACT-Interchange6125501674812409972.dfdl.xsd in temp.
When I look to the file it is not xml valid. (I used xerces validation i…
-
I need to parse INVOIC 95B EDIFACT document but UNOC syntax version is 1. Simple hack might be change version before processing the document but is there anyway I can allow Smooks to process version 1…
-
Thanks for many stellar efforts on DFDL specification and implementations.
Attached please find DFDL Specification review comments. If you prefer these can be separated into individual issues.
…
-
I have the use-case where I have to convert a D.01B Invoice which uses EAN011 extensions, i.e. a `IMD+C++CU::9'` segment (https://www.gs1.org/sites/default/files/docs/eancom/ean02s4/part2/invoic/0541.…
-
I am trying to figure out how to create document syntax exception when processing EDIFACT data.
I noticed you can get assert exception when it is defined in dfdl.xsd file. At the moment, I only get…
-
(Moved from redmine tracker 339)
Pre-decoding will cause a processing error when encodingErrorPolicy is 'error'. Some useful libraries will inevitably pre-decode and we don't want to make DFDL impl…
-
My requirement is to parse and validate a JSON document received from a remote source against a JSON schema, and to report all the validation failures in the document. In other words, do not quit whe…
-
For positive tests, the TDML runner gets the root element name and namespace from the infoset XML.
For negative tests, the root attribute of the test case is used to get the name. If the DFDL schem…