[ 
https://issues.apache.org/jira/browse/DAFFODIL-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323898#comment-17323898
 ] 

Mike Beckerle commented on DAFFODIL-2490:
-----------------------------------------

Feature request withdrawn.

This feature is hard, and complex to implement within Daffodil.

It is easy to implement as a data pre/post processor on XML text or a SAX event 
processor.

This is preferable than a change of this complexity to Daffodil requiring a 
DFDL extension feature that is specialized to when the infoset is being 
represented as XML. 

> Feature to treat string of data as XML
> --------------------------------------
>
>                 Key: DAFFODIL-2490
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2490
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End, Front End
>    Affects Versions: 3.0.0
>            Reporter: Mike Beckerle
>            Priority: Major
>
> More than once the need has arisen to convert binary data to XML where the 
> binary data contains a string of data that is already XML.  That XML is not 
> escapified XML, it's regular XML.
> The surrounding binary data needs to be parsed and converted to XML, but the 
> string of XML needs to simply be slammed into the XML text coming out of 
> Daffodil.
> The inverse needs to happen on unparsing - the XML corresponding to the 
> string has to be written out as a string (without escaping) and  incorporated 
> into the binary data.
> Note that such XML isn't necessarily adhering to DFDL's subset of XML schema. 
> E.g., it may use attributes, etc.
> Nevertheless, the combined XML - the XML you get corresponding to the binary 
> data part, along with the string of XML embedded in it, the resulting 
> complete XML document does have an XSD and could be validated (if not by 
> Daffodil, then by a separate validator)
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to