[jira] [Commented] (DAFFODIL-2788) Huge number of unneccessary namespace bindings in XML output

["Steve Lawrence (Jira)" <ji...@apache.org>]

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

Steve Lawrence commented on DAFFODIL-2788:
------------------------------------------

I can't find the schema with excessive namespaces. Maybe namespace clutter was fixed by changes to the schema?

I suggest we close this ticket and we can reopen if we find what schema it is or can create a reproducible test. 

Note that we have other tickets related to broken namespace minimization like DAFFODIL-2550 and DAFFODIL-2282

> Huge number of unneccessary namespace bindings in XML output
> ------------------------------------------------------------
>
>                 Key: DAFFODIL-2788
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2788
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.4.0
>            Reporter: Mike Beckerle
>            Priority: Critical
>             Fix For: 3.5.0
>
>
> On a large commercial DFDL schema project, the XML documents being produced by the parse have truly excessive numbers of entirely unnecessary namespace bindings in them. 
> The file size of XML infoset files is dominated by the namespace bindings. 
> Technically the XML is "correct" and tests don't fail, but the volume of these bindings has first order impact on:
>  * developer productivity - can't see what's going on in the XML data because it is so cluttered with bindings. What's worse, pretty printing gets very indented and ends up inserting whitespace around simple values (which breaks comparison) just due to these bindings.
>  * performance - the XML output is vastly bigger than it needs to be. XML is already big and slow, but this is just piling on!
> If this fix is reasonably localized, I might request we make a patch for 3.4.0 (ex: 3.4.1) as this issue is very important. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)