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/05/22 20:18:00 UTC
[jira] [Updated] (DAFFODIL-2278) Rewrite example schemas to use
choiceDispatchKey, not discriminators
[ https://issues.apache.org/jira/browse/DAFFODIL-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Beckerle updated DAFFODIL-2278:
------------------------------------
Description:
Lots of example schemas are written using discriminators, because they predated the choiceDispatchKey feature.
These schemas should be revised to use choiceDispatchKey, which is a tighter more declarative specification of a format, and also more efficient.
See issue: [https://github.com/DFDLSchemas/PCAP/issues/4](DONE!) also, which is about rewriting discriminators for PCAP specifically
was:
Lots of example schemas are written using discriminators, because they predated the choiceDispatchKey feature.
These schemas should be revised to use choiceDispatchKey, which is a tighter more declarative specification of a format, and also more efficient.
See issue: [https://github.com/DFDLSchemas/PCAP/issues/4] also, which is about rewriting discriminators for PCAP specifically
> Rewrite example schemas to use choiceDispatchKey, not discriminators
> --------------------------------------------------------------------
>
> Key: DAFFODIL-2278
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2278
> Project: Daffodil
> Issue Type: Bug
> Components: Usability
> Affects Versions: 2.5.0
> Reporter: Mike Beckerle
> Priority: Major
> Fix For: 3.0.0
>
>
> Lots of example schemas are written using discriminators, because they predated the choiceDispatchKey feature.
> These schemas should be revised to use choiceDispatchKey, which is a tighter more declarative specification of a format, and also more efficient.
> See issue: [https://github.com/DFDLSchemas/PCAP/issues/4](DONE!) also, which is about rewriting discriminators for PCAP specifically
--
This message was sent by Atlassian Jira
(v8.3.4#803005)