[
https://issues.apache.org/jira/browse/DAFFODIL-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168154#comment-17168154
]
Mike Beckerle commented on DAFFODIL-2350:
-----------------------------------------
This change would require a tunable, or perhaps even a daffodil-specific
property in the schema to enable this behavior.
The specific set of features to be allowed needs to be defined. Right now it's
* XSD key and unique constraints
* pattern facets on hexBinary
* pattern facets on numbers
Other types than hexBinary and numbers is tbd.
Daffodil's internal validation would ignore these things, but they would be
allowed to be on the schema without issuing errors/warnings so that these
features could be used by Xerces validation when run by Daffodil, or other XSD
validation run by a separate validator using the DFDL schema as the XSD for
validation.
> Allow XSD key and unique constraints in DFDL schemas
> ----------------------------------------------------
>
> Key: DAFFODIL-2350
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2350
> Project: Daffodil
> Issue Type: Bug
> Components: Front End
> Affects Versions: 2.6.0
> Reporter: Mike Beckerle
> Priority: Major
> Fix For: 3.0.0
>
>
> DFDL uses only a subset of XSD features.
> That subset doesn't include xs:key and xs:unique constraints.
> However, those are very useful for integrity checking once data has be
> converted from native format into XML.
> So Daffodil should simply ignore these xs:key and xs:unique features thereby
> allowing them to be in the DFDL schema when it is used only as an XML schema
> for validation purposes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
