From c36d2ea9474fc160be02da5bc2b2ed85af4da086 Mon Sep 17 00:00:00 2001 From: Michael Beckerle Date: Thu, 14 Nov 2024 12:38:08 -0500 Subject: [PATCH] Add minutes and update actions --- calls/2024/2024-11-14_DFDL-WG-Call.md | 59 +++++++++++++++++---------- 1 file changed, 38 insertions(+), 21 deletions(-) diff --git a/calls/2024/2024-11-14_DFDL-WG-Call.md b/calls/2024/2024-11-14_DFDL-WG-Call.md index 0261c88..7776841 100644 --- a/calls/2024/2024-11-14_DFDL-WG-Call.md +++ b/calls/2024/2024-11-14_DFDL-WG-Call.md @@ -5,17 +5,16 @@ ### Attendees * Mike Beckerle - + ### IPR statement "I acknowledge that participation in this meeting is subject to the OGF Intellectual Property Policy" ### Meeting closed -xx:xx EST.US (UTC-5) +11:57 EST.US (UTC-5) ### Next regular call (Normally, monthly on 2nd Thursday) @@ -31,7 +30,20 @@ xx:xx EST.US (UTC-5) ## Minutes -* TBD +* prefixLengthType - redistribute as email not received. +* decimalSigned - implementations need to check and report back on whether a decimalSigned="no" + xs:decimal is unparsing a negative value - is this error detected. Because this will dictate + whether specifying this requirement is a breaking change. Note that DFDL on IBM ZSeries does + not implement dfdl:decimalSigned="no", so can't have the issue. Daffodil and IBM DFDL need to + check. +* decimalSigned property definition should use "signed number" and "unsigned number" terminology. + Create issue to track. + +* action items review: + * action 338 (Pathological DFDL behavior) to be closed, and recorded as a github + issue, but there is no specific action to take to further this (it's a research topic). + * action 341 to be moved to deferred + * other actions - no progress ## Actions @@ -62,16 +74,8 @@ Next action: **344** | 2024-06-13 | Mike opened PR with draft document describing Daffodil experience (to be Exp Doc 9). Discussion of some points. SMH raised issue of possible new lengthKind based on self-delimiting length of well-formed XML (or JSON). Also need clarification of what it means when a DFDL processor is validating, what this means for XML (or JSON) strings. These comments added to the pull request. Will be incorporated into the document. | 2024-09-12 | No progress reported. Updates to the document per above have not been made yet. | 2024-10-10 | No progress reported. Updates to the document per above still pending. +| 2024-11-14 | No progress reported. Ditto. -| 338 | Pathological DFDL behavior (Non-linear) -|------------|---| -| 2024-02-07 | Created to address this issue. Bradd K mentioned that customers use the transformation capabilities of DFDL to create and populate structures that are different from the input format, and in unparsing to populate the output from structures that are different. So any solution to the pathological DFDL behavior problem can't prevent these kinds of transformations since users are depending on them. However, there is nothing that requires creation of non-linearly larger structures. -| 2024-03-14 | Briefly discussed. No concrete proposals yet. -| 2024-04-18 | No progress reported. -| 2024-05-09 | No progress reported. Needs more research. -| 2024-06-13 | No progress reported. -| 2024-09-12 | No progress reported. -| 2024-10-10 | No progress reported. Observation: this isn't stopping anyone from using DFDL successfully. | 340 | DFDL 2.0 feature priority |------------|---| @@ -79,29 +83,42 @@ Next action: **344** | 2024-06-13 | The "in use" labels added. High-priority labels still TBD. | 2024-09-12 | No progress reported. | 2024-10-10 | No progress on the "high priority" labels. Apache Daffodil project has created a new-feature request to implement the experimental offset/pointer (aka "indirection") feature (https://issues.apache.org/jira/browse/DAFFODIL-2941) - -| 341 | Convert DFDL spec to XML and create ISO formatted document -|------------|---| -| 2024-06-13 | Action created. Emails from Jim Melton (ISO SQL workgroup) and materials in email thread titled "Topic: Creating ISO document from XML source". -| 2024-09-12 | Discussed and conclusion from discussion is until a new version of the DFDL spec is needed, it seems there is not enough motivation to dig into this task. -| 2024-10-10 | Reviewed discussion. Consensus remains that this be deferred until a new version is needed. +| 2024-11-14 | No progress reported. +| 2024-11-14 | No progress reported. | 342 | complex types with element properties |------------|---| | 2024-06-13 | Action created to consider this improvement to the DFDL language. This was in reaction to recent email threads on XSD Element References which are the only way to reuse complex elements with their DFDL properties currently. A way to do this that reuses the complex type is desirable. By keeping the properties on the complex type distinct from those of the model group of that type perhaps the previously feared drawbacks of properties on complex types can be avoided. Worth consideration for DFDL 2.0. | 2024-09-12 | No progress reported. | 2024-10-10 | No progress reported. +| 2024-11-14 | No progress reported. + | 343 | Simplified non-XSD syntax for DFDL |------------|---| | 2024-06-13 | Action created. The world has moved on from XML/XSD and some developers who would otherwise be interested in DFDL are put-off by the XML/XSD complexities. A non-XML syntax, along with a simplification of language features should be considered as an available alternative for a future version of DFDL. | 2024-09-12 | No progress reported. | 2024-10-10 | Discussed this need. It was observed that ASN.1 ECN is such a notation. Non-XML data structures, format annotatinos. The annotations are not at all like DFDL, but the syntax supports those annotations, so this is at least a precedent for some sort of notation like this. +| 2024-11-14 | No progress reported. + ### Closed actions -* none +| 338 | Pathological DFDL behavior (Non-linear) +|------------|---| +| 2024-02-07 | Created to address this issue. Bradd K mentioned that customers use the transformation capabilities of DFDL to create and populate structures that are different from the input format, and in unparsing to populate the output from structures that are different. So any solution to the pathological DFDL behavior problem can't prevent these kinds of transformations since users are depending on them. However, there is nothing that requires creation of non-linearly larger structures. +| 2024-03-14 | Briefly discussed. No concrete proposals yet. +| 2024-04-18 | No progress reported. +| 2024-05-09 | No progress reported. Needs more research. +| 2024-06-13 | No progress reported. +| 2024-09-12 | No progress reported. +| 2024-10-10 | No progress reported. Observation: this isn't stopping anyone from using DFDL successfully. +| 2024-11-14 | Closed. See: https://github.com/OpenGridForum/DFDL/issues/63 ### Deferred actions -* none +| 341 | Convert DFDL spec to XML and create ISO formatted document +|------------|---| +| 2024-06-13 | Action created. Emails from Jim Melton (ISO SQL workgroup) and materials in email thread titled "Topic: Creating ISO document from XML source". +| 2024-09-12 | Discussed and conclusion from discussion is until a new version of the DFDL spec is needed, it seems there is not enough motivation to dig into this task. +| 2024-10-10 | Reviewed discussion. Consensus remains that this be deferred until a new version is needed.