Handle Embedded XML and JSON in a Natural Way

[mbeckerle]

(was Action 322)

This is something that was included in the first DFDL v1.0 spec drafts but was dropped (for lack of time, to reduce complexity)

There is a need for it. Users want to use DFDL to convert data into XML (or JSON), and such data being converted will sometimes contain strings of XML (or JSON) that want to be carried into the converted data not as escapified strings, but as XML (or JSON) text.

One issue this raises is that the DFDL schema is not the XSD schema of the resulting piece of merged XML.

If properties enabled one to express the complex type/element ref of the expected XML (by name and namespace), then one could automatically create the merged XSD of the combined data in a robust way.

[mbeckerle]

From workgroup call agenda/minutes. Moved here so as to have all tracking in github issues.

| 2024-06-13 | Mike opened PR with draft document describing Daffodil experience (to be Exp Doc 9). Discussion of some points. 
SMH raised issue of possible new lengthKind based on self-delimiting length of well-formed XML (or JSON). Also need clarification 
of what it means when a DFDL processor is validating, what this means for XML (or JSON) strings. These comments added to the 
pull request. Will be incorporated into the document.

As of this comment, these changes have not been incorporated yet.