Re: [VOTE] Release Apache Daffodil 3.2.0-rc1

Updating vote to +1 The issues I identified appear to be present in the 3.1.0 as well, so no reason for them to hold up this release. From: Interrante, John A (GE Research, US) Sent: Monday, December 6, 2021 11:25 AM To: dev@daffodil.apache.org Subject: RE:

Re: [VOTE] Release Apache Daffodil 3.2.0-rc1

e (see daffodil/BUILD.md at main * apache/daffodil > (github.com)<https://github.com/apache/daffodil/blob/main/BUILD.md>). > > John > > From: Sloane, Brandon > Sent: Sunday, December 5, 2021 5:25 PM > To: dev@daffodil.apache.org > Subject: EXT: Re: [VOTE] Release

Re: [VOTE] Release Apache Daffodil 3.2.0-rc1

-1 I tried verifying the release candidate and ran into numerous failures on the unit tests (full output attached). This is the first time in a while I have tried Daffodil on this particular system (Linux Mint 19.1), particularly, this is the first time I have used this system since we added

Re: Possible road map for GUI debugger

idea of what it is we are building. From: John Wass Sent: Tuesday, February 16, 2021 7:31 AM To: Sloane, Brandon Cc: dev@daffodil.apache.org Subject: Re: Possible road map for GUI debugger > I am conceiving of it as a standalone utility. I'm interes

Re: Possible road map for GUI debugger

_ From: John Wass Sent: Monday, February 15, 2021 7:39 AM To: dev@daffodil.apache.org Subject: Re: Possible road map for GUI debugger Is the gui envisioned to be an ide plugin or a standalone application (ie swing, fx, ...)? On Sun, Jan 24, 2021 at 2:08 PM Sloane, Brandon wrot

Re: [VOTE] Contributors - Graduate Apache Daffodil (Incubating) to a top-level project

+1 -- Brandon From: Mike Beckerle Sent: Thursday, January 28, 2021 6:08 PM To: dev@daffodil.apache.org Subject: [VOTE] Contributors - Graduate Apache Daffodil (Incubating) to a top-level project One of the first steps in graduating from the Apache incubator to

Possible road map for GUI debugger

Following up on the recent discussion about the Daffodil debugger, I would like to propose a roadmap for creating graphical debugger. Organizationally, the GUI debugger is a separate application (maintained in the normal Daffodil repository) that may include any of the current Daffodil

Re: The future of the daffodil DFDL schema debugger?

analysis in cases where it is not practical to attach a debugger while Daffodil is running. From: Sloane, Brandon Sent: Thursday, January 7, 2021 1:21 PM To: dev@daffodil.apache.org Subject: Re: The future of the daffodil DFDL schema debugger? I've been thinking

Re: The future of the daffodil DFDL schema debugger?

I've been thinking about a tool along similar lines (although more integrated with Daffodil than post-processing the trace output). One thing to keep in mind is that, although the trace output is presented as a linear log (since we do not have much choice), the actual process is more of a

Re: The future of the daffodil DFDL schema debugger?

I agree with Steve that "ideal" debugger would involve a rich multi-pane GUI; and like the idea of establishing a well defined protocol to isolate the GUI from the main codebase. Using a protocol would also give us scritability for nearly free, as users could leverage normal shell tools to

Re: Daffodil-1300

I've used dynamic tests in a couple of schema projects I was working on. My recollection is that the IDE integration made it difficult to run a single test, as you first need to generate all the tests; and there was not a good way to cache the results. In the case of Daffodil, we also take

Re: Subproject names proposed for discussion

+1 From: Beckerle, Mike Sent: Monday, October 5, 2020 10:23 AM To: dev@daffodil.apache.org Subject: Re: Subproject names proposed for discussion +1 from me. From: Interrante, John A (GE Research, US) Sent: Monday, October 5,

Re: Large dfdl:length values on complex types

of a SAX API. It won't affect how we handle the data at all. On 9/11/20 3:04 PM, Sloane, Brandon wrote: > We should be careful about making the cache too big due to the memory > overhead. I'm not sure where we are with support for streaming parses (beyond > the --stream option in the CLI,

Re: Large dfdl:length values on complex types

e even try to read it in? ________ From: Sloane, Brandon Sent: Friday, September 11, 2020 1:53 PM To: dev@daffodil.apache.org Subject: Re: Large dfdl:length values on complex types 256MB doesn't strike me as that big. We haven't ad filesize limits measured in GB since fat32 a

Re: Large dfdl:length values on complex types

256MB doesn't strike me as that big. We haven't ad filesize limits measured in GB since fat32 and ext1 (depending on settings; even ext4 can have a limit as low as 16gb). All it takes is such a file to have a length prefix, and we can very easily run into the limit. Combined with our support of

Re: Large dfdl:length values on complex types

(Resending after updating my subscribed address) 256MB doesn't strike me as that big. We haven't ad filesize limits measured in GB since fat32 and ext1 (depending on settings; even ext4 can have a limit as low as 16gb). All it takes is such a file to have a length prefix, and we can very

Re: Points of Uncertainty and Unordered Sequences

Since occursCountKind=parsed, there is a point of uncertainty at the element X. However, because the sequence is set initiatedContent=yes, it should not be able to backtrack after it matched the "X:" initiator. >From the spec: > If the child is optional then it is deemed to have been found

Re: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

+1 Verified the following: * Testsuite passes * Signatures verify * Version number updated to 2.7.0 From: Adams, Joshua Sent: Thursday, July 2, 2020 11:27 AM To: dev@daffodil.apache.org Subject: Re: [VOTE] Release Apache Daffodil (incubating)

Re: Incorrect delimiter scanning when mixed encodings?

Without looking at the spec, I would expect that delimiters be defined by the encoding the the element that defines the delimeter; so Daffodil is buggy in the case you describe. However, there are a couple of complications we have to consider: 1) What if instead of a terminator, we had a

Re: Using Scala 2.12.11

I'm not too familiar with how Scala version compatibility works, but I get the sense it is pretty strict. Would we risk breaking things for people running 2.12.11? From: Beckerle, Mike Sent: Monday, April 6, 2020 10:10 AM To: dev@daffodil.apache.org Subject:

Re: Hey!

Hi, I don't think there will be issues with a PR bumping the version to 2.10.2; particularly with a known CVE reported against the current version. Regarding other tickets you could look at, we have several open under the "beginner" label.

Re: [DRAFT] Daffodil Podling Report - March 2020

What's the status with Runtime2? Is Julian still contributing to that effort? From: Steve Lawrence Sent: Friday, February 28, 2020 10:20 AM To: dev@daffodil.apache.org Subject: [DRAFT] Daffodil Podling Report - March 2020 Apache Daffodil is an implementation of

Re: One DataProcessor handle more than one message format...

A DataProcessor corresponds to a single DFDL schema. If you have two different schemas, then you will need 2 different DataProcessors. There is no issue having multiple DataProcessors loaded in the same JVM. From: Rob Rose Sent: Thursday, January 16, 2020 4:28

Re: [DISCUSS] release tag naming scheme

Unless you routinely keep the tags on your personal remote updated, you will need to run 'git push --tags' before deleting them. Otherwise, the delete command seems to fail entirely. From: Steve Lawrence Sent: Monday, January 6, 2020 2:41 PM To:

Re: [VOTE] Release Apache Daffodil (incubating) 2.5.0-rc2

+1 I checked: * 'daffodil --version' output * Builds locally * Passes test suite locally * Non publically available schema (MDA); produces same output as under 2.4.0 * Current bugs in Jira for 2.4.0 (nothing that strikes me as blocking).

Re: [VOTE] Release Apache Daffodil (incubating) 2.5.0-rc1

-1 Given the recent bugs that have been found and fixed, I think another release candidate is warranted. From: Steve Lawrence Sent: Monday, December 23, 2019 11:14 AM To: dev@daffodil.apache.org Subject: [VOTE] Release Apache Daffodil (incubating) 2.5.0-rc1 Hi

Re: [DISCUSS] Daffodil 2.5.0 Release

+1 From: Steve Lawrence Sent: Friday, December 20, 2019 9:42 AM To: dev@daffodil.apache.org Subject: Re: [DISCUSS] Daffodil 2.5.0 Release Yeah, I'm assuming there's going to be some wrinkles with the new container release process, and since I'm most familiar

Inconsistent CI results

After merging in my DataValue PR, I noticed some inconsitent results in our automated testing. Prior to merging, all tests passed. After merging, there was an error in 2 of the configurations: * Java 11, Scala 2.11, Windows-latest

Re: DataValue compiler bug under 2.11

To: Sloane, Brandon ; dev@daffodil.apache.org Subject: Re: DataValue compiler bug under 2.11 Seems reasonable to me. +1 On 12/17/19 2:36 PM, Sloane, Brandon wrote: > This is the option I think I am settling on. > > SBT allows us to provide a seperate implementation of a file based on

Re: DataValue compiler bug under 2.11

modifications. From: Steve Lawrence Sent: Tuesday, December 17, 2019 2:11 PM To: Sloane, Brandon ; dev@daffodil.apache.org Subject: Re: DataValue compiler bug under 2.11 So this seems a bit hacky, but doing some simple testing I think wrapping the byte array works, e.g

Re: DataValue compiler bug under 2.11

believe this is scala bug 7521: https://github.com/scala/bug/issues/7521 Skimming the comments and other referenced issues, I don't see anyone mentioning a workaround. Appears the fix was added in 2.12, which makes sense based on the behavior you're seeing. On 12/17/19 1:19 PM, Sloane, Brandon

DataValue compiler bug under 2.11

While debugging my latest DataValue PR under 2.11, I came across what I believe to be a compiler bug. Recall that we have source code along the lines of: ... @inline implicit def toDataValue(v: DFDLTime): DataValueTime = new DataValue(v) @inline implicit def toDataValue(v: Array[Byte]):

Re: Developing against Scala 2.11

for this went away some time ago, not sure why but may have been associated with the 2.11 to 2.12 move. That's the theory I'm suggesting here anyway. From: Sloane, Brandon Sent: Tuesday, December 17, 2019 10:53 AM To: dev@daffodil.apache.org Subject: Developing against Scala

Developing against Scala 2.11

I am trying to debug issues that arrise under Scala 2.11. To this end, I regenerated my eclipse project for 2.11 by updating build.sbt to have 2.11 as the primary target and running 'sbt eclipse', followed by setting the scala instalation to 2.11 withing eclipse. This led to a micro version

Junit Logger

While running the Daffodil-test JUnit tests, I noticed that the new UDF feature is spamming the console. with INFO messages. I assume that this is because the UDF stuff is correctly sending these messages to the logger, which then defaults to sending them to stdout. I would think that for the

Commit spam

Having just completed a review of my latest PR, I notice that the commit mailing list recieves a message for each individual comment, even if they are all submitted at the same time. Is it possible to configure the bot to consolidate such messages? Brandon T. Sloane Associate, Services

Github build issues

On my latest PR, many of these automated tests are failing almost immidiatly on the "install dependencies" step with errors such as: E: Repository 'https://packages.microsoft.com/repos/microsoft-ubuntu-bionic-prod bionic InRelease' changed its 'Origin' value from 'microsoft-ubuntu-bionic-prod

DFDL spec "Known to Exist"

Following the recent discussion on the user-list, I read through some of the spec, and came across this section of 9.3.1.1: If none of those hold because they are not applicable then the occurrence is still known-to-exist if ALL of the following hold, and no processing error occurs during

Re: 2.5.0 branch performance looks problematic currently (2019-12-02)

Do we have an easy to run performance test suite? Going forward, it would be nice to integrate performance testing in our normal workflow. Particularly if we are going to be focusing optimizing. It would be much easier to do so with the quick feedback on an integrated performance test-suite.

Re: [DRAFT] Daffodil Podling Report - December 2019

1) Are we still in the "potential collaboration" stage wrt code generation? My understanding is work has already begun here. 2) The most recent commiter elected is Lola at this point. From: Steve Lawrence Sent: Monday, December 2, 2019 11:35 AM To:

Re: CLI Performance usage...

Second question: The "parse time" time vaue, is that measured as the amount of time it takes to compile the parser, parse the data according to the schema, and output the data to the console or file? Thanks so much again! Rob -Original Message- From

Re: CLI Performance usage...

I am not familiar with how daffodil's performance stats are reported (particularly how the average rate is faster then the max rate). However, the biggest bottlenecks for Daffodil performance is schema compilation. If performance is a concern, I would recommend pre-compiling your parser using

Re: [DISCUSS] Release Daffodil 2.4.0

, Sloane, Brandon wrote: > I am working on DAFFODIL-2165 now. The solution I am pursuing changes the > proposed functions for typeCalcs (instead of a seperate String/Int function, > there is just a single function that automatically infers its return type). > > > This involves a fa

Re: SDE during pre-serialization

. From: Sloane, Brandon Sent: Wednesday, June 26, 2019 4:32:01 PM To: dev@daffodil.apache.org Subject: SDE during pre-serialization I am working on moving much of the typeCalc logic to compile time (notably for this email, I am moving much of the error detection to compile time

Justification for seperate DPathCompileInfo object

The comment on DPathCompileInfo says: " What makes the circularity is that the runtime data structures (ElementRuntimeData in particular), are not lazy. Everything part of them is forced to be evaluated when those are constructed. So anything that needs even one member of an ERD is

SDE during pre-serialization

I am working on moving much of the typeCalc logic to compile time (notably for this email, I am moving much of the error detection to compile time). To avoid circular depdencies, I am trying to use the same pass-by-name trick we use for the runtime data structures: class

Re: [DISCUSS] Release Daffodil 2.4.0

I am working on DAFFODIL-2165 now. The solution I am pursuing changes the proposed functions for typeCalcs (instead of a seperate String/Int function, there is just a single function that automatically infers its return type). This involves a fair bit of plumbing to get information to where it

Re: Missing typecalc functions

(identity) Might be worth a shot. On 6/25/19 2:39 PM, Sloane, Brandon wrote: > Related to below "other issues", I appear to be having an issue wit > serializing typeCalcMap now: > > > java.lang.ClassCastException: cannot assign instance of > scala.collection.immutable.HashMap

Re: Missing typecalc functions

ypeCalcMap, defined by: type TypeCalcMap = Map[GlobalQName, TypeCalculator[AnyRef, AnyRef]] --Brandon ____ From: Sloane, Brandon Sent: Tuesday, June 25, 2019 1:37:11 PM To: dev@daffodil.apache.org Subject: Re: Missing typecalc functions I picked up where I left off on m

Re: Missing typecalc functions

dependency on every other thing that goes into that runtime data object, and these are what trip us up often. ____ From: Sloane, Brandon Sent: Tuesday, June 25, 2019 12:33:42 PM To: dev@daffodil.apache.org Subject: Re: Missing typecalc functions I thin

Re: Missing typecalc functions

g > binary date/times. > > > That said. I have exactly and only 1 use case. Not sufficient IMHO to > motivate adding date/time support. > > > From: Sloane, Brandon > Sent: Tuesday, June 25, 2019 11:44:03 AM > To: dev@daffodil

Missing typecalc functions

The typeCalc functions are all specialized by their return type; and currently support only Integer and String. It appears that there is a need to at least add Double to this list. (My use-case here is VMF/Link-16 where, for example, "degrees" is specified in units of 360/2^n making an

Re: Character Encodings - No Statement

t without committing to some element name. I have the same complaint about dimensionality - tied to elements therefore to element names. From: Sloane, Brandon Sent: Monday, June 17, 2019 5:43:23 PM To: dev@daffodil.apache.org Subject: Re: Character Encodings - No Sta

Using tns: prefix in tdml files

I am working on a tdml file and noticed that I am unable to set the targetNamespace attribute on the root element. When I look at other tdml files, I see that they are able to use the "tns:" prefix without specifying either a targetNamespace, or a xmlns:tns attribute anywhere. Any explanation

Re: Proposal: Add choiceBranchKeyRanges annotation

support. Suggest you update the design note on the wiki to add this capability to the "proposal". ____ From: Sloane, Brandon Sent: Monday, June 17, 2019 4:23:10 PM To: dev@daffodil.apache.org Subject: Re: Proposal: Add choiceBranchKeyRanges annotation I

Re: Character Encodings - No Statement

re context. ____ From: Sloane, Brandon Sent: Monday, June 17, 2019 4:55:09 PM To: dev@daffodil.apache.org Subject: Character Encodings - No Statement I am going through link16 (mil-std-6016e, not publically available) to add support for some of the special character

Character Encodings - No Statement

I am going through link16 (mil-std-6016e, not publically available) to add support for some of the special character encodings to Daffodil (simmilar to dfi264:dui001 that has already been added). While doing so, I came across DFI 311 DUI 002. Several bitcodes are "UNDEFINED", which I intend

Re: Proposal: Add choiceBranchKeyRanges annotation

urse if we want. I want to understand vis a vis influencing the DFDL standard in the future, how many cases there are of this situation. ____ From: Sloane, Brandon Sent: Wednesday, June 12, 2019 11:16:53 AM To: dev@daffodil.apache.org Subject: Proposal: Add choiceBranc

Proposal: Add choiceBranchKeyRanges annotation

The DFDL specification only allows for a choice branch to specify a single key value. Daffodil has expanded this to allow for a space delimiated list of keys. However, this does not support the case where a large number of contiguous integers are the key. Are standard advice there is to use a

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

Scala is broken?

While investigating issue DAFFODIL-2146, I discovered that dstate.currentValue was taking on the value of "One(0)". My first instinct is to attribute the to a bug in my enumeration support code (which it probably is), however my second instinct is to note that dstate.currentValue is declared

Re: Proposal: Add support for lookahead in DFDL expressions

_____ From: Sloane, Brandon Sent: Friday, May 31, 2019 4:44 PM To: dev@daffodil.apache.org Subject: Re: Proposal: Add support for lookahead in DFDL expressions Wiki page created: https://cwiki.apache.org/confluence/display/DAFFODIL/Proposal%3A+DFDL+lookAhead In drafting it, I noticed a few

Re: Proposal: Add support for lookahead in DFDL expressions

rt putting together the actual implementation. ____ From: Sloane, Brandon Sent: Friday, May 31, 2019 4:15:52 PM To: dev@daffodil.apache.org Subject: Re: Proposal: Add support for lookahead in DFDL expressions The offset proposal would be sufficient, but seems like overkill f

Re: Proposal: Add support for lookahead in DFDL expressions

382> From: Sloane, Brandon Sent: Thursday, May 30, 2019 2:27:31 PM To: dev@daffodil.apache.org Subject: Re: Proposal: Add support for lookahead in DFDL expressions My initial survey of link16 found 8 instances of this; which I don't think changes the calculus substantially. I s

Re: Proposal: Add support for lookahead in DFDL expressions

formats. The workaround is just a choice, where you have a "late discriminator" on the tag, when you finally get to it. ____ From: Sloane, Brandon Sent: Wednesday, May 29, 2019 1:00:04 PM To: dev@daffodil.apache.org Subject: Proposal: Add support for

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: Differing behaviour between CLI and SAPI

? From: Sloane, Brandon Sent: Wednesday, May 22, 2019 11:08:41 AM To: dev@daffodil.apache.org Subject: Differing behaviour between CLI and SAPI I am having an issue where running with the CLI is producing correct results, whereas the SAPI is producing incorrect results. I suspect

Differing behaviour between CLI and SAPI

I am having an issue where running with the CLI is producing correct results, whereas the SAPI is producing incorrect results. I suspect that this is related to the bitorder unparse error that was recently fixed, as it occurs on unparse and goes away when I switch to "read-only" schema that has

Re: Adding character encoding?

for a generalized facility. I doubt there are many more of them even in that specification. So I suggest we simply add these encodings as we encounter them. From: Sloane, Brandon Sent: Monday, May 20, 2019 3:31:06 PM To: dev@daffodil.apache.org Subject: Re: Adding

Re: Adding character encoding?

From: Sloane, Brandon Sent: Monday, May 20, 2019 11:43:40 AM To: dev@daffodil.apache.org Subject: Adding character encoding? In working on schema for mil-std-6016, I have discovered a 6 bit character encoding that is distinct from the X-DFDL-US-ASCII-6-BIT-PACKED encoding we

Re: Adding character encoding?

X_DFDL_6_BIT_DFI_264_DUI_001.scala From: Sloane, Brandon Sent: Monday, May 20, 2019 11:43:40 AM To: dev@daffodil.apache.org Subject: Adding character encoding? In working on schema for mil-std-6016, I have discovered a 6 bit character encoding that is distinct from the X-DFDL-US-ASCII

Adding character encoding?

In working on schema for mil-std-6016, I have discovered a 6 bit character encoding that is distinct from the X-DFDL-US-ASCII-6-BIT-PACKED encoding we already support. What would the process for supporting this be? Brandon T. Sloane Associate, Services bslo...@tresys.com | tresys.com

New commit to enumeration PR

I know that this PR has already been reviewed, but when I rebased it back onto the latest version of master, I discovered that it exposed a regression in master. There is now a second commit in the PR to fix this. Assuming no one objects, I can squash this into the main enumerations commit.

Re: Schema Definition Error vs Processing Error for empty choiceDispatchKey

oiceDispatchKey We are certainly not waiting for the DFDL Workgroup. This would get consideration in a month or two once I write it up. There's lots of other proposals in flux as well. ________ From: Sloane, Brandon Sent: Monday, May 20, 2019 10:41:19 AM To: dev@daffodi

Re: Schema Definition Error vs Processing Error for empty choiceDispatchKey

Ressurecting this thread, as this seems to be triggering a regression in the enum support PR. Has the DFDL workgroup responded? From: Beckerle, Mike Sent: Tuesday, April 30, 2019 3:16:54 PM To: dev@daffodil.apache.org Subject: Re: Schema Definition Error vs

Re: What is status on PR for typeCalc and enums?

I believe it is done. Steve's last comment is a +1, so I think we are good there. I believe I addressed all of Josh's comments as well, but his review seems to have disappeared (likely due to a force-push on my end) From: Beckerle, Mike Sent: Thursday, May

Re: Schema Definition Error vs Processing Error for empty choiceDispatchKey

In general, it is not possible to know at compile time if a choiceDispatchKey will evaluate to an empty string, so we do not have much choice but to accept processing error as "correct" for an empty string here. Having said that, if we can prove at compile time that the choiceDispatchKey

Understanding bitOrder=leastSignificantFirst

I am trying to work through a bug surrounding changing the bitOrder mid schema and am having trouble figuring out how Daffodil handles bitOrder in general. I see that in InputSourceData, we have code to mask for the correct bits and shift out the gaps, but I do not see where we actually invert

Re: Scala Version

Lawrence Sent: Wednesday, April 17, 2019 10:18:52 AM To: dev@daffodil.apache.org; Sloane, Brandon Subject: Re: Scala Version Our TravisCI build [1] tests on both 2.12.x and 2.11.x, and a few different versions of Java. Our SBT configuration defaults to building on 2.12.6, but can be compiled

Scala Version

While investigating a discrepency between the test results on my machine, and those reported by our automated test system, I noticed that the test system appears to be testing against against. 2.11.12 Scala 2.12.0 was released in November 2016 (and Scala has begum release candidates for

Re: NodeInfo confusion

type system, not the scala type system, but has some extra nodes that are there for convenience also. In dfdl/XML decimal is super type of integer. Get Outlook for Android<https://aka.ms/ghei36> From: Sloane, Brandon Sent: Friday, April 12, 6:17 PM Subject: NodeInfo confusion T

NodeInfo confusion

I am looking at the type hierarchy defined in NodeInfo and am confused about the Integer type. In NodeInfo.scala we have: protected sealed trait IntegerKind extends SignedInteger.Kind case object Integer extends PrimTypeNode(Decimal, List(Long, NonNegativeInteger)) with IntegerKind {

Re: Understanding outputValueCalc elements

ementRuntimeData of the next element From: Steve Lawrence Sent: Wednesday, April 10, 2019 12:57:09 PM To: dev@daffodil.apache.org; Sloane, Brandon Subject: Re: Understanding outputValueCalc elements I'm not sure how the OVC element could appear after where it is

Understanding outputValueCalc elements

I am a bit confused with the behaviour of one of my test cases. I have the schema: With the test case: 0E http://www.w3.org/2001/XMLSchema;

Re: Exposing latent SDEs

about it. From: Steve Lawrence Sent: Tuesday, April 9, 2019 7:42:10 AM To: dev@daffodil.apache.org; Sloane, Brandon Subject: Re: Exposing latent SDEs I personally don't have any problem with detecting errors even those elements aren't used. It is a backwards

Re: Exposing latent SDEs

le to change our behavior to reject such schemas. This will involve refactoring a number of tests which deliberately include broken schema to test for error messages. ________ From: Sloane, Brandon Sent: Friday, April 5, 2019 6:19:46 PM To: dev@daffodil.apache.org Subje

Re: Exposing latent SDEs

Get Outlook for Android<https://aka.ms/ghei36> ____ From: Sloane, Brandon Sent: Friday, April 5, 2019 5:12:26 PM To: dev@daffodil.apache.org Subject: Exposing latent SDEs This is related to the previous thread with the subject "Further design

Exposing latent SDEs

This is related to the previous thread with the subject "Further design difficulties with TypeValueCalculators". I believe I have solved the main issue of that thread by computing attributes that do not depend on the context in the SimpleTypeDefFactory instead of the instance class [0].

Re: Further design difficulties with TypeValueCalculators

as to have enough properties to stand alone. Or am I missing something? Get Outlook for Android<https://aka.ms/ghei36> ________ From: Sloane, Brandon Sent: Thursday, April 4, 2019 5:42:02 PM To: dev@daffodil.apache.org Subject: Further design difficulties with TypeV

Further design difficulties with TypeValueCalculators

I spoke with Mike about this issue the other day, but after more work on the implementation, it appears that the issue is more difficult that we had realized. The enum support proposal allows simpleTypes to define mappings between representation values and logical values. Further, this

Errors in existing test schemas

While working on adding enum support, I seem to have broken a large numbers of existing tests. While investigating, I ran into the following type definition: 4218 4219 4220 4221 4222 in section05/facets/Facets.tdml Which is triggering an error: Schema

Re: Enum proposal flaw

support+enumerations+and+typeValueCalc) has been updated to reflect this. ________ From: Sloane, Brandon Sent: Wednesday, March 27, 2019 4:21:49 PM To: dev@daffodil.apache.org Subject: Enum proposal flaw In implementing the Enum support proposal<https://cwiki.apache

Accessing schema information from runtime system

As part of the enum support proposal (https://cwiki.apache.org/confluence/display/DAFFODIL/Proposal%3A+Feature+to+support+enumerations+and+typeValueCalc), there is a need to lookup types by qname from within the runtime system. For instance, suppose the schema defined the following simpleType:

Enum proposal flaw

In implementing the Enum support proposal, I have noticed a flaw in it with regards to unparsing choices. In order to support complex integrations with IVC/OVC, the proposal

Default attribute values

As part of adding enum support to Daffodil (see proposal here), I am adding attributes to xs:choice (in particular, choiceBranckKeyKind and choiceDispathKeyKind). The issue that

Re: Multiple children of DIDocument

y > temporarily during the lifetime of the repType quasi-element. > > > Get Outlook for Android<https://aka.ms/ghei36> > > ________ > From: Sloane, Brandon > Sent: Tuesday, March 19, 2019 7:24:18 PM > To: dev@daffodil.apache.org > Subject:

Multiple children of DIDocument

As you may have heard, I am working on the proposal to implement a TypeValueCalc feature, where a simple type can be defined by its representation type, describing how it appears in the bitstream, and some conversion functions to translate that to a logical type. To implement this, I am

New Proposal for adding enumeration support to DFDL

All, I have submitted a new proposal to add support for enumeruations types to the apache wikie here Regrads, Brandon T. Sloane Associate, Services bslo...@tresys.com |

Wiki Access

Can I have write access to the Apache Daffodil wiki. I am working on an updated proposal to add enum support to DFDL. My wiki account name is "Brandon Sloane" associated with this email, "bslo...@tresys.com" Thanks, Brandon T. Sloane Associate, Services bslo...@tresys.com | tresys.com