[
https://issues.apache.org/jira/browse/DAFFODIL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652042#comment-16652042
]
Michael Beckerle edited comment on DAFFODIL-115 at 10/16/18 4:38 PM:
---------------------------------------------------------------------
For parsing this is partially implemented.
For parsing: An Infoset node for an element of simple type, if present, and
without a value, will get a value when it is accessed.
(What I can't recall is whether these nodes will get created, or will not, if
"empty representation" is found.)
The parsing uses for defaulting and the unparsing uses are really not at all
symmetrical.
For unparsing (which is more important actually) this defaulting is not at all
implemented.
The NextElementResolver class is the place where this functionality is needed.
This feature is particularly important for fixed length data - such as arises
in FINSERV and Cobol-origin data formats. There a large number of fixed length
fields always exist but applications use them sparsely. When unparsing, a small
number of them will exist in the infoset, the others must be defaulted.
Changed title to emphasize both parsing and unparsing functionality are needed.
was (Author: mbeckerle):
For parsing this is partially implemented.
For parsing: An Infoset node for an element of simple type, if present, and
without a value, will get a value when it is accessed.
(What I can't recall is whether these nodes will get created, or will not, if
"empty representation" is found.)
The parsing uses for defaulting and the unparsing uses are really not at all
symmetrical.
For unparsing (which is more important actually) this defaulting is not at all
implemented.
This feature is particularly important for fixed length data - such as arises
in FINSERV and Cobol-origin data formats. There a large number of fixed length
fields always exist but applications use them sparsely. When unparsing, a small
number of them will exist in the infoset, the others must be defaulted.
Changed title to emphasize both parsing and unparsing functionality are needed.
> Implement default values: Unparsing and Parsing
> -----------------------------------------------
>
> Key: DAFFODIL-115
> URL: https://issues.apache.org/jira/browse/DAFFODIL-115
> Project: Daffodil
> Issue Type: New Feature
> Components: Back End, Compatibility, DFDL Language, Front End,
> Middle "End"
> Reporter: Michael Beckerle
> Priority: Minor
> Labels: ForInteroperabilityTest
>
> Defaulting when parsing.
> Uses the XML Schema default and fixed properties of element declarations,
> depends on occursCountKind, minOccurs and maxOccurs.
> emptyValueDelmiterPolicy, initiator, terminator are involved as an empty
> representation is what triggers defaulting.
> Also useNilForDefault property for that specific case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
