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 2020/09/23 20:20:00 UTC

[jira] [Commented] (DAFFODIL-1633) Implement unionMemberSchema and schema members of Infoset

    [ https://issues.apache.org/jira/browse/DAFFODIL-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201070#comment-17201070 ] 

Mike Beckerle commented on DAFFODIL-1633:
-----------------------------------------

Challenge here is anonymous types. If the xsi:type is to be used, it must name an actual XSD type declaration. There's no way a QName can become an SCD magically.

So if the type is a defined type, then xsi:type could be used, but if it is an anonymous simple type, perhaps we should take the base type, (which will always have a QName).

If it is an anonymous complex type, then we would need a different way to deal with this. like daf:unionMemberSchema="...scd...". But it would be fine to just not have this for complex types initially, and split that out to be a separate issue.

> Implement unionMemberSchema and schema members of Infoset
> ---------------------------------------------------------
>
>                 Key: DAFFODIL-1633
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1633
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End, DFDL Language
>            Reporter: Mike Beckerle
>            Priority: Minor
>
> These infoset members are needed to navigate back from an infoset element to the corresponding schema component. This is needed so as to access other annnotations (not DFDL annotations) on that schema component which may be needed by the application - enhanced diagnostic messages, etc. As an example, the units-of-measure of a numeric element may be stored on an appinfo annotation, but these may want to be used in error messages.
> Implementing these requires implementing SCID (Schema Component Identifiers), and an API by which they can be used to access the schema component.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)