[
https://issues.apache.org/jira/browse/DAFFODIL-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740320#comment-17740320
]
Mike Beckerle commented on DAFFODIL-813:
----------------------------------------
I suggest that to avoid excessive XML clutter that no attribute means valid,
and we only add the validation attribute at the root element, and for any
element that is invalid we put daf:valid="false" at the deepest level where it
holds.
> Infoset valid member (a boolean indicating if the item is valid or not)
> should be set by Validation
> ---------------------------------------------------------------------------------------------------
>
> Key: DAFFODIL-813
> URL: https://issues.apache.org/jira/browse/DAFFODIL-813
> Project: Daffodil
> Issue Type: New Feature
> Components: Back End, DFDL Language
> Affects Versions: s10
> Reporter: Mike Beckerle
> Priority: Minor
>
> An alternative to turning on validation and having to deal with warning
> messages is to build the valid/not-valid information into the infoset.
> Turns out the DFDL Spec allows for this. Infoset Items have a 'valid' member
> which is a boolean indicating whether the item is valid or not. (See DFDL
> Spec section 4.1.2).
> When validation is enabled, we should populate this member.
> Hopefully there are standard ways to represent the information of a PSVI,
> that are settable/accessible from JDOM/DOM.
> (If not we can invent one like: dafext:valid="true", or similar).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
