[jira] [Commented] (DAFFODIL-2139) unparse of unsignedLong greater than signedLong maximum gives NumberFormatException

[ https://issues.apache.org/jira/browse/DAFFODIL-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851404#comment-16851404 ] Michael Beckerle commented on DAFFODIL-2139: When this is fixed, the IPFIX

[jira] [Resolved] (DAFFODIL-1853) ipfix data format parse and unparse tests for "Schema Definition Error"

[ https://issues.apache.org/jira/browse/DAFFODIL-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Beckerle resolved DAFFODIL-1853. Resolution: Fixed Assignee: Dave Thompson (was: Michael Beckerle) Added s

[jira] [Assigned] (DAFFODIL-1853) ipfix data format parse and unparse tests for "Schema Definition Error"

[ https://issues.apache.org/jira/browse/DAFFODIL-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Beckerle reassigned DAFFODIL-1853: -- Assignee: Michael Beckerle > ipfix data format parse and unparse tests for

Re: Proposal: Add support for lookahead in DFDL expressions

Yup. This is a real situation. I think this happens in fixed length data for very mundane reasons explained in the attached slides. Practically speaking, in Link16 this comes up like twice or 3 times, so this isn't worth enhancing DFDL/Daffodil for unless this phenomenon is observed in more pl

status w.r.t. interoperability goals

We are down to exactly 2 schemas that can and should interoperate, but don't yet: * VCard - needs the unordered sequences feature to be added to daffodil * EDIFACT - not sure why not working yet. All the other schemas that can interoperate and have tests, do so including HL7, IBM4690TL

[jira] [Commented] (DAFFODIL-2139) unparse of unsignedLong greater than signedLong maximum gives NumberFormatException

[ https://issues.apache.org/jira/browse/DAFFODIL-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851346#comment-16851346 ] Michael Beckerle commented on DAFFODIL-2139: Incidently, this also blows u

[jira] [Created] (DAFFODIL-2139) unparse of unsignedLong greater than signedLong maximum gives NumberFormatException

Michael Beckerle created DAFFODIL-2139: -- Summary: unparse of unsignedLong greater than signedLong maximum gives NumberFormatException Key: DAFFODIL-2139 URL: https://issues.apache.org/jira/browse/DAFFODIL-213

Proposal: Add support for lookahead in DFDL expressions

In developing schema for link16, I have encountered a situation that I do not believe Daffodil currently has a good solutions for. It is a tagged union, where the tag comes after the union. In theory, the schema would look like: Obviously, this schema doe not work because it re

[jira] [Resolved] (DAFFODIL-1916) Properties leadingSkip alignment alignmentUnits trailingSkip should not be required by text formats.

[ https://issues.apache.org/jira/browse/DAFFODIL-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Beckerle resolved DAFFODIL-1916. Resolution: Fixed Assignee: (was: Josh Adams) Merged your changes into

[jira] [Resolved] (DAFFODIL-828) IBM Compatibility - Test out HL7 schemas

[ https://issues.apache.org/jira/browse/DAFFODIL-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Beckerle resolved DAFFODIL-828. --- Resolution: Fixed Assignee: Dave Thompson (was: Michael Beckerle)   Tresys

[jira] [Commented] (DAFFODIL-2138) Incorrect Schema Context for root path expressions

[ https://issues.apache.org/jira/browse/DAFFODIL-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850993#comment-16850993 ] Brandon Sloane commented on DAFFODIL-2138: -- Likely related problem, we see th

[jira] [Updated] (DAFFODIL-2138) Incorrect Schema Context for root path expressions

[ https://issues.apache.org/jira/browse/DAFFODIL-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Sloane updated DAFFODIL-2138: - Attachment: a2.dfdl.xsd > Incorrect Schema Context for root path expressions > ---

[jira] [Updated] (DAFFODIL-2138) Incorrect Schema Context for root path expressions

[ https://issues.apache.org/jira/browse/DAFFODIL-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Sloane updated DAFFODIL-2138: - Attachment: (was: a.dfdl.xsd) > Incorrect Schema Context for root path expressions

[jira] [Updated] (DAFFODIL-2138) Incorrect Schema Context for root path expressions

[ https://issues.apache.org/jira/browse/DAFFODIL-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Sloane updated DAFFODIL-2138: - Attachment: a.dfdl.xsd > Incorrect Schema Context for root path expressions >

[jira] [Comment Edited] (DAFFODIL-828) IBM Compatibility - Test out HL7 schemas

[ https://issues.apache.org/jira/browse/DAFFODIL-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850962#comment-16850962 ] Michael Beckerle edited comment on DAFFODIL-828 at 5/29/19 3:26 PM: -

[jira] [Created] (DAFFODIL-2138) Incorrect Schema Context for root path expressions

Brandon Sloane created DAFFODIL-2138: Summary: Incorrect Schema Context for root path expressions Key: DAFFODIL-2138 URL: https://issues.apache.org/jira/browse/DAFFODIL-2138 Project: Daffodil

[jira] [Commented] (DAFFODIL-828) IBM Compatibility - Test out HL7 schemas

[ https://issues.apache.org/jira/browse/DAFFODIL-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850962#comment-16850962 ] Michael Beckerle commented on DAFFODIL-828: --- These are mostly working with th