dfdl:nil* properties on xs:simpleType allowed?

In working on DAFFODIL_2096 (Add dfdlx extensions prefix), I sort of ran into issues with short form properties not being validated (DAFFODIL-598) and think I have come across a small update to the XML Schema for DFDL to re-enable schema validation of dfdl attributes, but still allow attributes

[GitHub] [incubator-daffodil] stevedlawrence commented on issue #218: Implement dfdl:choiceLength='explicit'

stevedlawrence commented on issue #218: Implement dfdl:choiceLength='explicit' URL: https://github.com/apache/incubator-daffodil/pull/218#issuecomment-499939266 +1 :+1: This is an automated message from the Apache Git

[GitHub] [incubator-daffodil] jadams-tresys commented on a change in pull request #218: Implement dfdl:choiceLength='explicit'

jadams-tresys commented on a change in pull request #218: Implement dfdl:choiceLength='explicit' URL: https://github.com/apache/incubator-daffodil/pull/218#discussion_r291613998 ## File path: daffodil-io/src/main/scala/org/apache/daffodil/io/DataOutputStream.scala ## @@

[GitHub] [incubator-daffodil] jadams-tresys merged pull request #218: Implement dfdl:choiceLength='explicit'

jadams-tresys merged pull request #218: Implement dfdl:choiceLength='explicit' URL: https://github.com/apache/incubator-daffodil/pull/218 This is an automated message from the Apache Git Service. To respond to the message,

[jira] [Resolved] (DAFFODIL-640) choiceLengthKind='explicit'

[ https://issues.apache.org/jira/browse/DAFFODIL-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Adams resolved DAFFODIL-640. - Resolution: Fixed Assignee: Dave Thompson (was: Josh Adams) Fix Version/s:

[jira] [Assigned] (DAFFODIL-1024) Property inputValueCalc should not be on element that is optional, global, or an array

[ https://issues.apache.org/jira/browse/DAFFODIL-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence reassigned DAFFODIL-1024: Assignee: Steve Lawrence > Property inputValueCalc should not be on element

[jira] [Assigned] (DAFFODIL-598) No validation of Short Form or Element Form dfdl properties

[ https://issues.apache.org/jira/browse/DAFFODIL-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence reassigned DAFFODIL-598: --- Assignee: Steve Lawrence > No validation of Short Form or Element Form dfdl

[jira] [Created] (DAFFODIL-2148) No compile time error when using nonexistent TypeCalc function

Brandon Sloane created DAFFODIL-2148: Summary: No compile time error when using nonexistent TypeCalc function Key: DAFFODIL-2148 URL: https://issues.apache.org/jira/browse/DAFFODIL-2148 Project:

[GitHub] [incubator-daffodil] mbeckerle opened a new pull request #228: WIP: Daffodil 1444 schema comp

mbeckerle opened a new pull request #228: WIP: Daffodil 1444 schema comp URL: https://github.com/apache/incubator-daffodil/pull/228 Has features to allow navigation of multiple backpointers from referenced components to the places referencing them. This enables sharing in the future

[GitHub] [incubator-daffodil] bsloane1650 opened a new pull request #229: Daffodil 2146 enum support fix1

bsloane1650 opened a new pull request #229: Daffodil 2146 enum support fix1 URL: https://github.com/apache/incubator-daffodil/pull/229 There were 2 minor bugs this fixes: 1) Enumerations assumed that any repType has a corresponding typeDef. This is not true when the repType is a

Re: dfdl:nil* properties on xs:simpleType allowed?

You are correct. The property combining logic isn't (or wasn't) enforcing that the nil-related properties are only allowed on elements. Personally I think this is a mistake. But it is what the spec says, so we should change our tests to comply. From: Steve

[GitHub] [incubator-daffodil] mbeckerle merged pull request #226: Sick of NPE. lexicalParent is now optLexicalParent and is Option type

mbeckerle merged pull request #226: Sick of NPE. lexicalParent is now optLexicalParent and is Option type URL: https://github.com/apache/incubator-daffodil/pull/226 This is an automated message from the Apache Git Service.

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue.

mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue. URL: https://github.com/apache/incubator-daffodil/pull/228#discussion_r291751451 ## File path:

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue.

mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue. URL: https://github.com/apache/incubator-daffodil/pull/228#discussion_r291751591 ## File path:

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue.

mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue. URL: https://github.com/apache/incubator-daffodil/pull/228#discussion_r291751591 ## File path:

[jira] [Updated] (DAFFODIL-1444) Performance - schema compilation

[ https://issues.apache.org/jira/browse/DAFFODIL-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Beckerle updated DAFFODIL-1444: --- Attachment: Daffodil-exponential-component-growth.xlsx > Performance - schema

[jira] [Closed] (DAFFODIL-2148) No compile time error when using nonexistent TypeCalc function

[ https://issues.apache.org/jira/browse/DAFFODIL-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Sloane closed DAFFODIL-2148. Resolution: Won't Fix > No compile time error when using nonexistent TypeCalc function

[jira] [Commented] (DAFFODIL-2148) No compile time error when using nonexistent TypeCalc function

[ https://issues.apache.org/jira/browse/DAFFODIL-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858872#comment-16858872 ] Brandon Sloane commented on DAFFODIL-2148: -- This appears to be a harder problem than I

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue.

mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue. URL: https://github.com/apache/incubator-daffodil/pull/228#discussion_r291750610 ## File path:

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue.

mbeckerle commented on a change in pull request #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue. URL: https://github.com/apache/incubator-daffodil/pull/228#discussion_r291750159 ## File path:

[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=16858894#comment-16858894 ] Josh Adams commented on DAFFODIL-2139: -- Took a look at this and noticed that it is using it's own

Outstanding issues with Enum Support

I have begun attempted to write schema to take advantage of the recent Enum feature. In doing so, I have encountered 2 quality of life issues: 1) Errors that ought to occur at compile time are defered to runtime. I discussed this at

[jira] [Commented] (DAFFODIL-1444) Performance - schema compilation

[ https://issues.apache.org/jira/browse/DAFFODIL-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858990#comment-16858990 ] Michael Beckerle commented on DAFFODIL-1444: Attached a spreadsheet to this bug, which

[GitHub] [incubator-daffodil] stevedlawrence opened a new pull request #230: Enable schema validation of attribute- and short-form properties

stevedlawrence opened a new pull request #230: Enable schema validation of attribute- and short-form properties URL: https://github.com/apache/incubator-daffodil/pull/230 - Use xs:anyAttribute and xs:any defined in the DFDL namespace to enable validation for attribute-form and

[jira] [Resolved] (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:all-tabpanel ] Josh Adams resolved DAFFODIL-2139. -- Resolution: Duplicate This is actually an issue with the schema issue (trying to unparse a

[GitHub] [incubator-daffodil] mbeckerle commented on issue #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue.

mbeckerle commented on issue #228: Incremental progress on Daffodil 1444 schema compiler space/speed issue. URL: https://github.com/apache/incubator-daffodil/pull/228#issuecomment-500033772 A thought. This change introduces 41 deprecation errors. I had to switch off the checking that

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #230: Enable schema validation of attribute- and short-form properties

mbeckerle commented on a change in pull request #230: Enable schema validation of attribute- and short-form properties URL: https://github.com/apache/incubator-daffodil/pull/230#discussion_r291768192 ## File path:

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #230: Enable schema validation of attribute- and short-form properties

mbeckerle commented on a change in pull request #230: Enable schema validation of attribute- and short-form properties URL: https://github.com/apache/incubator-daffodil/pull/230#discussion_r291768357 ## File path: