[
https://issues.apache.org/jira/browse/DAFFODIL-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828049#comment-17828049
]
Steve Lawrence commented on DAFFODIL-2671:
------------------------------------------
DAFFODIL-2877 adds "error", "ignore", and "validate" options for how to handle
DFDL-invalid restrictions. "error" and "ignore" are pretty trivial to implement
in this case, but "validate" might be hard for date/time min/maxInclusive
because the current implementation is tied pretty heavily to numbers. If it's
too difficult to implement validation for a specific restriction (like maybe
this one) how should we handle it? Maybe we warn that the
invalidRestrictionPolicy says to "validate", but we can't validate this
specific restriction?
> support minInclusive maxInclusive on date/time/dateTime
> -------------------------------------------------------
>
> Key: DAFFODIL-2671
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2671
> Project: Daffodil
> Issue Type: New Feature
> Components: Back End
> Affects Versions: 3.2.1
> Reporter: Mike Beckerle
> Assignee: Mike Beckerle
> Priority: Minor
>
> I am trying to use this simple type:
> {code:java}
> <simpleType name="msDateTime">
> <restriction base="xs:dateTime">
> <maxInclusive value="2094-12-31T23:59:59"/>
> <minInclusive value="1995-01-01T00:00:00"/>
> </restriction>
> </simpleType>{code}
> I get this diagnostic message:
> {code:java}
> Schema Definition Error: Failed to parse (1995-01-01T00:00:00) to dateTime
> (uuuu-MM-dd'T'HH:mm:ss.SSSSSSxxx) due to Character array is missing "e"
> notation exponential mark. (after Unparseable date:
> "1995-01-01T00:00:00").{code}
> The other facets (minExclusive, maxExclusive), and the other calendar types
> (date, time) should also be tested.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
