[
https://issues.apache.org/jira/browse/DAFFODIL-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence reassigned DAFFODIL-2026:
----------------------------------------
Assignee: Steve Lawrence
> TDML Runner - type-sensitive comparison
> ---------------------------------------
>
> Key: DAFFODIL-2026
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2026
> Project: Daffodil
> Issue Type: Improvement
> Components: TDML Runner
> Affects Versions: 2.2.0
> Reporter: Michael Beckerle
> Assignee: Steve Lawrence
> Priority: Major
> Fix For: 2.3.0
>
>
> TDML runner needs to be able to implement type-specific comparisons when
> comparing actual and expected infosets.
> This is because there are representations of types like dates and times that
> are equivalent.
> E.g.,
> <date1>2010-12-30Z</date1>
> and
> <date1>2010-12-30+00:00</date1>
> These are entirely equivalent.
> We need to perform type-specific comparison here.
> This needs to occur based on the DFDL schema's type information.
> DFDL implementations aren't going to provide uniform (or even any) projection
> of type information into the infoset when represented in XML. So we can't
> depend on say, xsi:type information (DAFFODIL-182) functionality to tell us
> to compare as dates.
> This means the XML comparison logic must be an XML-schema-aware walk of the
> data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)