[
https://issues.apache.org/jira/browse/DAFFODIL-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742207#comment-17742207
]
Olabusayo Kilo commented on DAFFODIL-2732:
------------------------------------------
So do we also want to remove the prefix as well, for example instead of:
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<ex:seq_11 xmlns:ex="http://example.com";>
<ex:e1>3</ex:e1>
</ex:seq_11> {code}
We would output:
{code:java}
<seq_11>
<e1>3</e1>
</seq_11> {code}
> trace output has namespace prefix binding clutter
> -------------------------------------------------
>
> Key: DAFFODIL-2732
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2732
> Project: Daffodil
> Issue Type: Bug
> Components: Debugger
> Affects Versions: 3.3.0
> Reporter: Mike Beckerle
> Assignee: Olabusayo Kilo
> Priority: Minor
> Fix For: 3.5.1
>
>
> When using the trace output of the debugger you see infoset dumps like this:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <comments>
> <FRI xmlns="" xmlns:vmfc="urn:mil-std-6017c-DFDL"
> xmlns:vmfbase="urn:mil-std-6017base-DFDL" xmlns:vmfa="urn:mil-std-6017a-DFDL"
> xmlns:tns="urn:mil-std-6017a-DFDL"
> xmlns:nocvmf="urn:noc-milstd2045-vmf">0</FRI>
> <value>This is a Test</value>
> </comments>{code}
> In my terminal window all those namespace bindings require scrolling to the
> right.
> There is no reason for namespace prefix bindings at all in this context. We
> should strip them before we present this to the user.
> Note that the XML processing instruction slug-line at the top of the infoset
> is also not needed in this context, and should be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
