You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2022/03/02 16:03:00 UTC
[jira] [Commented] (DAFFODIL-2616) End-user doc of how import/include schemaLocation resolver works
[ https://issues.apache.org/jira/browse/DAFFODIL-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500256#comment-17500256 ]
Mike Beckerle commented on DAFFODIL-2616:
-----------------------------------------
Users report this documentation needed to meet some regulatory guidlines (RTB).
> End-user doc of how import/include schemaLocation resolver works
> ----------------------------------------------------------------
>
> Key: DAFFODIL-2616
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2616
> Project: Daffodil
> Issue Type: Bug
> Components: Documentation, Website
> Affects Versions: 3.2.1
> Reporter: Mike Beckerle
> Priority: Major
> Fix For: 3.3.0
>
>
> We badly need an end-user doc/article on the daffodil.apache.org site that explains how Daffodil resolves include/import schemaLocations.
> All our larger DFDL schemas are depending heavily on this behavior now.
> The behavior of Daffodil's resolver is very sensible, reasonable, and predictable, which is why we're leaning on it so heavily now in large schemas.
> Probably should also cover packaging schemas into Jars.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)