[jira] [Updated] (DAFFODIL-1959) EXIficient Inputter and outputter for XML EXI representation

[ https://issues.apache.org/jira/browse/DAFFODIL-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Beckerle updated DAFFODIL-1959: Priority: Major (was: Minor) > EXIficient Inputter and outputter for XML

[jira] [Updated] (DAFFODIL-853) textNumberPattern: 'V' and 'P' Symbols

[ https://issues.apache.org/jira/browse/DAFFODIL-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Beckerle updated DAFFODIL-853: --- Labels: COBOL (was: ) > textNumberPattern: 'V' and 'P' Symb

[jira] [Updated] (DAFFODIL-1781) layer transformer for ASN.1 Object Identifier

[ https://issues.apache.org/jira/browse/DAFFODIL-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Beckerle updated DAFFODIL-1781: Priority: Trivial (was: Minor) > layer transformer for ASN.1 Object Identif

[jira] [Commented] (DAFFODIL-645) Bidirectional Text

[ https://issues.apache.org/jira/browse/DAFFODIL-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942322#comment-16942322 ] Mike Beckerle commented on DAFFODIL-645: Looks as though this DFDL feature is being withdrawn

[jira] [Updated] (DAFFODIL-645) Bidirectional Text

[ https://issues.apache.org/jira/browse/DAFFODIL-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Beckerle updated DAFFODIL-645: --- Priority: Trivial (was: Minor) > Bidirectional T

[jira] [Commented] (DAFFODIL-2208) Empty strings never allowed as optional repeats - not compliant with DFDL spec.

[ https://issues.apache.org/jira/browse/DAFFODIL-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939692#comment-16939692 ] Mike Beckerle commented on DAFFODIL-2208: - This change is not yet agreed by the DFDL Workgroup

[jira] [Resolved] (DAFFODIL-2207) Tests needed to reassure that choices nested in fact work.

[ https://issues.apache.org/jira/browse/DAFFODIL-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Beckerle resolved DAFFODIL-2207. - Resolution: Fixed Fixed in 9c5a6b1d352939aeb6cd0e4ff09b7f2d1f53dea3 > Tests nee

[jira] [Resolved] (DAFFODIL-2204) unparserTestCase should dump hex data not just iso-8859-1 when mixed text/binary TDML doesn't compare

[ https://issues.apache.org/jira/browse/DAFFODIL-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Beckerle resolved DAFFODIL-2204. - Resolution: Fixed Fixed in 5f167e3685d35959055e92acdecab9c9959c3e7b

[jira] [Resolved] (DAFFODIL-2200) xs:import problems with xsd files provided in daffodil-lib

[ https://issues.apache.org/jira/browse/DAFFODIL-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Beckerle resolved DAFFODIL-2200. - Resolution: Fixed Fixed in 856938733a27c997c6e9e3e79de85d4c4bc0dc09 Thanks Dinesh

[jira] [Commented] (DAFFODIL-2208) Empty strings never allowed as optional repeats - not compliant with DFDL spec.

[ https://issues.apache.org/jira/browse/DAFFODIL-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938957#comment-16938957 ] Mike Beckerle commented on DAFFODIL-2208: - In addition, this fix is a change in behavior

[jira] [Created] (DAFFODIL-2208) Empty strings never allowed as optional repeats - not compliant with DFDL spec.

Mike Beckerle created DAFFODIL-2208: --- Summary: Empty strings never allowed as optional repeats - not compliant with DFDL spec. Key: DAFFODIL-2208 URL: https://issues.apache.org/jira/browse/DAFFODIL-2208

[jira] [Created] (DAFFODIL-2207) Tests needed to reassure that choices nested in fact work.

Mike Beckerle created DAFFODIL-2207: --- Summary: Tests needed to reassure that choices nested in fact work. Key: DAFFODIL-2207 URL: https://issues.apache.org/jira/browse/DAFFODIL-2207 Project

Re: DFDL & Input Formats

Patrick and I have recently attended a Spark meetup in Boston where Mike Beckerle has presented Apache Daffodil (incubating). I work for a company that has to deal with many data formats, both new (JSON, XML, YAML, Protobuf, etc) and old (EDIFACT, IATA formats, etc). More recently, we have start

Progress, but.... Expecting some nightly batch test failures

I pushed the TDML runner changes for IBM cross testing today to the master. I am fully expecting that some of the tests outside of the daffodil tree will fail. E.g., the nightly runs that Tresys has on a batch system that test the various DFDL schemas on DFDLSchemas on github or on DI2E.net.

Re: Daffodil & Social Media/Twitter

What set of hash tags should go on these tweets? I noticed #DFDL is taken by a law firm in southeast asia. But #dataFormat is relevant as is #BigData. From: Steve Lawrence Sent: Monday, October 15, 2018 8:18:50 AM To: dev@daffodil.apache.org Subject: Re:

fixing https://issues.apache.org/jira/browse/DAFFODIL-1440

This qualifies as an easy one to fix I think, but would be very helpful for Apache Spark users if release 2.3.0 had this one fixed.

Re: ICU version incompatible between IBM DFDL and Daffodil

nn diagram where one circle is DFDL schemas that work on Daffodil, the other is DFDL schemas that work on IBM DFDL, the intersection of the two circles is much too small. Just a few schemas are demonstrably portable. That's what we've got to fix as soon as possible. - Mik

Re: ICU version incompatible between IBM DFDL and Daffodil

online with more searching about Child First Class Loader (aka Parent Last Class Loader). This may be sufficient, though I'm not yet convinced. From: Steve Lawrence Sent: Friday, November 2, 2018 7:45:51 AM To: dev@daffodil.apache.org; Mike Beckerle Subject

ICU version incompatible between IBM DFDL and Daffodil

Daffodil 2.2.0 uses ICU4J 62.1 IBM DFDL uses ICU4J 51.1 These are not compatible. Hence, annotating some of the tests in Daffodil, so that they will try to also run the test under IBM DFDL if it is found on the classpath doesn't work. I tried backing out daffodil's dependency to 51.1,

cross testing rig design questions

I am working on enhancing the TDML Runner to enable cross testing against both Daffodil and IBM DFDL, or really any DFDL implementation. So I need to build a dynamically-loading module that provides a TDMLRunner friendly API, but calls the IBM DFDL implementation underneath. The module will

IBM4690TLog format - created forDaffodilDev branch

I created a forDaffodilDev branch for this schema and reorganized it with the standard layout, and recast the existing 5 tests that were there as TDML tests with a scala driver so 'sbt test' will execute them. This is one of the important DFDL schemas for interoperability demonstration. We

Re: how hard is encodingErrorPolicy='error' to implement?

fragments of characters are errors subject to encodingErrorPolicy. From: Steve Lawrence Sent: Monday, October 8, 2018 7:26:28 AM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: how hard is encodingErrorPolicy='error' to implement? BitsCharsetDecoder.scala has

how hard is encodingErrorPolicy='error' to implement?

Turns out IBM DFDL implements only encodingErrorPolicy='error', and Daffodil only encodingErrorPolicy='replace'. That means for any data where there are encoding errors the two implementations will not behave the same. For compatibility testing, this will be problematic. The I/O layer was

Re: [PPMCS] Podling project logos wanted

enough community right now to generate many >>> entries (I've dabbled with inkscape and could maybe try to contribute, >>> but I too know my limits) but it might be a way to help to build a >>> community? >>> >>>

schemas and branches of schema repos

So there are all these github DFDL schemas. Testing against them is becoming too painful. Right now they have a master branch pointing at daffodil 2.1.0, and a for-daffodil-2.2.0 branch which is obsolete and pointing at 2.2.0-SNAPSHOT daffodil, which presumably doesn't exist anymore, and

Re: JIRA ticket releases - never and deferred

ll the fix versions for all open tickets except a few that we are already working, or that are clearly in scope of 2.3.0 From: Steve Lawrence Sent: Thursday, September 13, 2018 8:29:41 AM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: JIRA ticket releas

Getting Daffodil on Scaladex - Fw: [scalacenter/scaladex] Apache Daffodil (Incubating) not being found/incorporated into scaladex (#554)

, September 7, 2018 4:37 AM To: scalacenter/scaladex Cc: Mike Beckerle; Author Subject: Re: [scalacenter/scaladex] Apache Daffodil (Incubating) not being found/incorporated into scaladex (#554) This is because the tag of your POM does not point to a GitHub repository: https://search.maven.org

Re: tabs vs. spaces

. From: Steve Lawrence Sent: Thursday, September 6, 2018 9:38:00 AM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: tabs vs. spaces Generally, I'm not a fan of fixing tabs vs spaces errors since it can make it a little more difficult to view the real history of changes. Though, it's

tabs vs. spaces

I may be as guilty as others here or more, but somehow our spaces vs. tabs convention which uses 2 spaces for indenting in our code base, has gotten modified and lots of files are showing tabs now. Especially for XML and XSD files, less so, but true for some scala and java files. Do we have

Fwd: [ANNOUNCE] Apache Daffodil (incubating) 2.2.0

The Apache Daffodil (incubating) community is pleased to announce the release of version 2.2.0. Release notes and downloads are available at: https://daffodil.apache.org/releases/2.2.0/ Daffodil is an open source implementation of the DFDL (Data Format Description Language) specification that

Re: BLOB thoughts

turned out to be quite a bit longer than I expected ^_^;; Cheers, — Russ PS - this email client *really* hates the word “infoset” and keeps wanting to turn it into “infest”... > On 30 Aug 2018, at 19:34, Mike Beckerle wrote: > > I put some thought into the design of the BLOB fea

Spark not yet on scala 2.12

According to https://issues.apache.org/jira/browse/SPARK-14220, Spark is not yet on 2.12. I guess that's plenty of reason why we have to maintain a 2.11 version of Daffodil for now.

BLOB thoughts

I put some thought into the design of the BLOB feature we need to add to Daffodil for image file parsing. I think it's actually rather easily done using layering. I.e., a BLOB is parsed/unparsed via a layer with dfdl:layerTransform="BLOB". This layer actually is a fake out that produces the

Re: [PPMCS] Podling project logos wanted

These from Daniel Gruno are improvements. http://www.apache.org/logos/res/daffodil/daffodil-proposal.svg From: Mike Beckerle Sent: Tuesday, August 28, 2018 10:58:22 AM To: dev@daffodil.apache.org Subject: Fw: [PPMCS] Podling project logos wanted A call came

Fw: [PPMCS] Podling project logos wanted

A call came out for podling project logos. With a project name like "Daffodil" we should be able to have an awesome logo. What we have right now, is this one I did a little while ago, that I think leaves something to be desired. Attached for your amusement. I am under no illusions about

[RESULT] VOTE - Release Apache Daffodil (incubating) 2.2.0-rc2

(resent: this time with the vote emails in the message) Myself plus 3 more +1 from committers who did significant testing. No -1 or 0 votes. Let's take the next step to get this released. -Mike Beckerle p.s., Voting thread is below -- *From:* Beth Finnegan Fahl

[RESULT] VOTE - Release Apache Daffodil (incubating) 2.2.0-rc2

Myself plus 3 more +1 from committers who did significant testing. No -1 or 0 votes. Let's take the next step to get this released. -Mike Beckerle

[VOTE] Release Apache Daffodil (incubating) 2.2.0-rc2

Hi all, We made some critical fixes and cleanups since 2.2.0-rc1. I'd like to call a vote to release Apache Daffodil (Incubating) 2.2.0-rc2. All distribution packages, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.2.0-rc2/

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

I will fix these things and start trying to create RC2 today. From: Steve Lawrence Sent: Tuesday, August 21, 2018 2:28:41 PM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: [VOTE] Release Apache Daffodil (incubating) 2.2.0-rc1 Scanned the release page

Vote Cancelled - Re: [VOTE] Release Apache Daffodil (incubating) 2.2.0-rc1

(Resending from my apache email address) Cancelling the vote. There will be an RC2, as we've found a few significant glitches. On Mon, Aug 20, 2018 at 9:44 AM, Mike Beckerle wrote: > Hi all, > > I'd like to call a vote to release Apache Daffodil (Incubating) 2.2.0-rc1. > > A

[VOTE] Release Apache Daffodil (incubating) 2.2.0-rc1

Hi all, I'd like to call a vote to release Apache Daffodil (Incubating) 2.2.0-rc1. All distribution packages, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.2.0-rc1/ Staging artifacts can be found at:

serving tdml stylesheets from our apache-site ?

I know the javadoc and scaladoc go into the daffodil-site tree somehow. How is this accomplished? We will want to do this for 2.2.0-rc1, and update the content and the 'latest' link once it is fully released. I was also thinking of putting the tdml xslt and css stylesheets into a subdir on

Burn down of bug backlog

After 2.2.0 is released, we should try to burn down the backlog of bugs. In going through the deferred bugs I've discovered that many of them are fixed, and tests just have to move from scala-debug to scala, or in some cases a test needs to be written, but the behavior is clearly fixed.

Re: how to test modified daffodil-site

Nevermind. I shoudl RTFM the readme.md file. From: Mike Beckerle Sent: Wednesday, August 15, 2018 1:42:53 PM To: dev@daffodil.apache.org Subject: how to test modified daffodil-site I have fixed a problem on the daffodil-site. (See DAFFODIL-1939 about missing

how to test modified daffodil-site

I have fixed a problem on the daffodil-site. (See DAFFODIL-1939 about missing errata) How do I test view my change, which is to site/unsupported.md file? Thanks

travis CI builds inconsistent - multi_base_09 file (which is UTF-16BE charset)

So the travis CI build failed for a recent PR of mine. It's complaining about file daffodil-test/src/test/resources/org/apache/daffodil/section07/namespaces/multi_base_09.dfdl.xsd I haven't touched this file. It has not been modified in a long time I believe. Perhaps unique in our system,

for-daffodil-2.2.0 branches for FOUO schemas

Created and pushed these branches for all the fouo schemas on di2e.net as well. There are a few changes there besides the build.sbt 2.2.0-SNAPSHOT version change. Recent changes have made use of xsi:schemaLocation on the root element of TDML files or DFDL schemas cause warnings from Xerces.

for-daffodil-2.2.0

I've created branches named for-daffodil-2.2.0 which request 2.2.0-SNAPSHOT of daffodil, for these DFDLSchemas on github bmp CSV gif jpeg mil-std-2045 NACHA NITF PCAP png quasiXML This facilitates testing these against the daffodil 2.2.0 development branch

Re: [DISCUSS] split separator work into two phases - to isolate non-backward-compatible behavior change

ror is an SDE, default value is Long.MaxValue (unlimited) - so the error will never occur, and applications can tune it lower to get the SDE if they want to. From: Steve Lawrence Sent: Thursday, August 9, 2018 1:42:25 PM To: Mike Beckerle; dev@daffodil.apache.

Re: [DISCUSS] split separator work into two phases - to isolate non-backward-compatible behavior change

body arrays are BIG, that this default of 1024 just seems silly to me. Comments? From: Steve Lawrence Sent: Wednesday, August 8, 2018 11:49:46 AM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: [DISCUSS] split separator work into two phases - to isolate

[DISCUSS] split separator work into two phases - to isolate non-backward-compatible behavior change

Due to this issue: https://issues.apache.org/jira/browse/DAFFODIL-1975 This is a non-backward-compatible change. The impact of it could be significant on existing schemas. Depending on scale of the impact we may have to put in flags to turn on/off the changed behavior. Love to avoid that, but

[DISCUSS] move blob feature to 2.3.0 so we can release 2.2.0 sooner

major new feature to it is unwise. Discussion? -mike beckerle

Re: Daffodil development on Scala 2.12 using Eclipse

eclipse workspaces. From: Steve Lawrence Sent: Monday, August 6, 2018 8:07:45 AM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: Daffodil development on Scala 2.12 using Eclipse Perhaps we should revert the changes to .classpath/.project to use the 2.11

Re: [DFDL-WG] Clarification needed: separator for empty sequence

ators in separated sequences even if they have zero length. Separator suppression based on dfdl:separatorSuppressionPolicy does not apply." Does this go for empty choices as well? I think it should. Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | www.tresys.com Please note: Con

separtors work arRUA

(Resending - email thread appears to have gotten messed up. Last email about this showed up in my inbox with a stale old message at the top of the thread.) All the tests have been fixed. All existing schemas tested also. One odd one (army-drrs) doesn't work. All others tested work. I didn't

Re: Status on work on sequences and separators

All the tests have been fixed. All existing schemas tested also. So this is now open for your review. See PR https://github.com/apache/incubator-daffodil/pull/88 From: Mike Beckerle Sent: Friday, July 27, 2018 12:59:26 PM To: dev@daffodil.apache.org Subject

logging statements - should be removing/scrutinizing them

As a part of code review for PRs, I think it's time we should start giving the logging calls some scrutiny. Most of the logging calls are just leftover debug print statements disguised as logging, from back when we had no debug/trace capability. We should be removing the logging calls that

Status on work on sequences and separators

I am making much progress on this, but didn't finish it this week as I'd hoped. Here's the status: Rebased on top of current asf/master. Branch is visible on https://github.com/mbeckerle/incubator-daffodil/tree/daffodil-1919-separators All basic tests run. See note below

Daffodil development on Scala 2.12 using Eclipse

In rebasing onto the latest, I had to upgrade to Scala 2.12, which means getting an Eclipse and Scala IDE that support 2.12. I tried the current stable Scala IDE with these releases: * Eclipse Mars - can't set a breakpoint to debug in Scala code, running unit tests from src/test/scala

Re: Status of work on separators and separator suppression

to confirm these behaviors. The spec is not clear in this area at all, and needs corrections/errata. ____ From: Mike Beckerle Sent: Friday, July 20, 2018 7:50:32 AM To: dev@daffodil.apache.org Subject: FYI: Status of work on separators and separator suppression I

Re: XPath sum function

A sum function would be nice. You can accomplish what you want without it however. The trick for adding up an array is to make the elements of the array a complex type containing a regular element named "value" to hold the parsed number value, and then along side it a computed element to

Re: daffodil-trailing-sep branch - status of work on trailing separator sequences

, but in shape for preliminary design-of-code review before I leave on vacation. My last day before is Tuesday June 12, then I am out until July 2nd. ...mike beckerle From: Mike Beckerle Sent: Tuesday, June 5, 2018 10:51:49 AM To: dev@daffodil.apache.org Subject

Re: Avoiding use of Java CharsetDecoders

would be in the Decoder logic, so if an odd charset needs to do something more complex that seems possible with this proposal. Just curious what that might be. - Steve On 06/06/2018 01:05 PM, Mike Beckerle wrote: > I am easily convinced that the complexity of maintaining maybe 10 or 20 of > our own cha

Re: Avoiding use of Java CharsetDecoders

r. I think quite literally there would be no code for surrogate pairs outside of the definition of the UTF-8 encoder/decoder. I really like having this issue not impacting the code so much given what an utterly obscure corner case it is. -mike beckerle F

Re: daffodil-trailing-sep branch - status of work on trailing separator sequences

(GMT-05:00) To: dev@daffodil.apache.org, Mike Beckerle Subject: Re: daffodil-trailing-sep branch - status of work on trailing separator sequences Hi Mike! I’m not familiar with the code or the design for the parsing, aside from seeing a mention of Parser Combinators, so this may sound really

daffodil-trailing-sep branch - status of work on trailing separator sequences

I branched off Josh Adams' daffodil-trailing-sep branch a while back. Starting at hash 9f8173d4a962d9373d29f85d5a92435afe622bba I have since made substantial changes, and just successfully rebased onto the 2.2.0 development branch. That is, for some definition of "success". I had 44

Re: [DRAFT] June 2018 Daffodil Podling Report

cense were clarified (LEGAL-369) How has the community developed since the last report? - Starting community building, including conversations on the user@ and dev@ lists from a handful of users requesting some support and information on Daffodil for DFDL schema creation. - Mike Beckerle wa

Re: Can I help?

ckets open, so there is lots to work on. I'll leave it at that for this message. ...mike beckerle From: Russ Williams <r...@reciprocity.com> Sent: Wednesday, May 23, 2018 5:54:14 AM To: dev@daffodil.apache.org Subject: Can I help? Hi! I stumbled acro

thoughts on fixing trailing separator suppression

I haven't completed this note yet, but as I am having to shift gears for a few days, I am providing my current state of thinking around what's actually required here for posterity/amusement, and to share what I anticipate will actually be a great improvement to Daffodil, but non-trivial to

Re: Old Daffodil Wiki Migration

I fixed the remaining old NCSA wiki pages per Steve L's list below. I believe the old NCSA Daffodil Wiki is now fully "obsoleted" in that all irrelevant pages are gone. All other pages now forward to somewhere on the new web-site or wiki. What I did: I replaced all the pages on the old

TravisCI builds of DFDLSchemas

By way of regression testing for Daffodil, I created travisCI jobs for all the DFDLSchemas that are published on github that work on Daffodil today. I don't yet have them setup to trigger a rebuild when daffodil itself changes. This would require a development branch be monitored rather than

Re: [DRAFT][ANNOUNCE] Apache Daffodil (incubating) 2.1.0 released

Minor edits below. From: Steve Lawrence Sent: Tuesday, May 15, 2018 9:34 AM To: dev@daffodil.apache.org Subject: [DRAFT][ANNOUNCE] Apache Daffodil (incubating) 2.1.0 released All steps have been taken to release 2.1.0. We now just need to

Re: Daffodil tuning

idea of the complexity involved in unparsing. Are your tests both parsing and unparsing the data? I suspect unparsing is the bottleneck, but it would be good to tease those apart if possible. --Mike Beckerle Tresys From: Perpignand, Weber <wperp

PR 61 - base64/layering - ready for real review

So I pushed a more complete layering/base64 implementation. There's 10 commits now, so eventually they'll get squashed. But It's ready for a real PR review now, not just a preliminary look see. It implements base64_MIME, gzip, lineFolded_IMF, and lineFolded_iCalendar layer transforms.

dfdl:calendarTimeZone issue

So in DFDLGeneralFormat.dfdl.xsd, which is built-in to Daffodil, there is a binding for dfdl:calendarTimeZone="UTC". That seems ok, but if you import a date like "07/04/1999" you get an XML date like: 1999-07-04+00:00 That is, you get a UTC time zone specifier on any date. This is really

base64 feature - re-review of PR worthwhile now

I added commits to the PR on the base64/layering feature. https://github.com/apache/incubator-daffodil/pull/61 Unparsing that is symmetric with parsing now works. There's only a few tests, but they do include one that gzips text, measuring how big it turns out to be, stores that length

Re: incubator-daffodil

luence/display/DAFFODIL/Roadmap+for+Upcoming+Releases Your input/suggestions on this and the priority of various needs are of course welcome. ...mike beckerle From: Perpignand, Weber <wperpign...@owlcyberdefense.com> Sent: Tuesday, April 17, 2018 3:03:5

Re: Java 7 and Base64

with Java 8. Or perhaps can't use pre-compiled schemas at all? From: Steve Lawrence <slawre...@apache.org> Sent: Tuesday, April 10, 2018 8:37:53 AM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: Java 7 and Base64 Considering that Java 7 w

Re: Simplified DFDL layering/base64 proposal

Never mind that one. I've simplified it even further: https://cwiki.apache.org/confluence/display/DAFFODIL/Proposal%3A+Data+Layering+for+base64+-+Super+Simplified From: Mike Beckerle Sent: Friday, April 6, 2018 3:12:31 PM To: dev@daffodil.apache.org Subject

Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3

+1 from me. From: Steve Lawrence Sent: Friday, April 6, 2018 8:00:30 AM To: dev@daffodil.apache.org Subject: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3 Hi all, I'd like to call a vote to release Apache Daffodil (incubating)

Re: Feedback wanted on Proposal: DFDL Features to Support Table-Lookup

structure. From: Steve Lawrence <slawre...@apache.org> Sent: Tuesday, April 3, 2018 1:16:32 PM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: Feedback wanted on Proposal: DFDL Features to Support Table-Lookup I like this. One thing I might change, though I don't feel strongly, is w

Re: large PCAP files and changes to message-streaming API for onPath() support vs. SAX behavior

o: dev@daffodil.apache.org; Mike Beckerle Subject: Re: large PCAP files and changes to message-streaming API for onPath() support vs. SAX behavior It sounds to me like you're suggesting something like the following: val headerDP = pf.onPath(/PCAPHeader) val packetDP = pf.onPath(/Packet) val he

Feedback wanted on Proposal: DFDL Features to Support Table-Lookup

Feedback on this idea/proposal is welcome. We need to be able to deal with enumerated constants, converting them from integers to/from strings in DFDL. The idea here would be to refine this proposal, then prototype in Daffodil and try it out on some of the schemas that really need it.

large PCAP files and changes to message-streaming API for onPath() support vs. SAX behavior

I was recently asked about Daffodil and processing gigantic (multi-gigabyte) PCAP files. We have two features planned for 2.2.0 which help with memory footprint issues. BLOBs, and the message-streaming feature. At first glance, neither will help with giant PCAP files. It's a large file that

Re: [incubator-daffodil-site] branch asf-site updated: Publishing from d4f1919ed5ae2011eec37087fe9a974dfbf35bc6

I installed jekyll using the default sudo apt-get install jekyll. jekyll --help says version 3.0.1 So looks like jekyll may be the issue. I'll see if I can update it and retry. Otherwise I'll revert this. The changes in content I pushed also to master branch, so those tiny changes are

Re: New DFDL Character Classes

This is a good idea. So good in fact that it already exists in the dfdl2.0 wishlist. Suggested name there is LSP for Line spaces. With usual + and * variants. The NL+ and NL* are Also a good idea. For security reasons we need a tunable limit for the max number of repeats of any of these. Not

Re: [DRAFT] March 2018 Daffodil Podling Report

+1 with the edits John D. Ament suggested. From: John D. Ament Sent: Wednesday, March 7, 2018 9:23:56 AM To: dev@daffodil.apache.org Subject: Re: [DRAFT] March 2018 Daffodil Podling Report Steve, Please remove the releases listed. You

Re: [VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc2

My vote +1 From: Steve Lawrence Sent: Friday, February 16, 2018 2:46:25 PM To: dev@daffodil.apache.org Subject: [VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc2 Hi all, I'd like to call a vote to release Apache Daffodil (Incubating)

Need to revert change to DAFFODIL-1897 (built-in-formats.xsd move to test)

This change is causing no end of headaches. I have wasted a day already fixing things that are now broken on account of this. Turns out built-in-formats.xsd is *not* only used by our internal tests. It is part of the TDML runner's tdml:defineSchema infrastructure - included into every such

Re: tag for last NCSA-based commit?

<slawre...@apache.org> Sent: Thursday, February 8, 2018 9:45:31 AM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: tag for last NCSA-based commit? I'm not sure a tag would add a whole lot of value, and would add a little bit of clutter. I don't think splitting a rebase into two wil

tag for last NCSA-based commit?

I believe this: 945a1c1ab363485003ebf14fef3463055d4fab37 Is the last commit using the old file structure, old packages, etc. I suspect it would be prudent to make a tag for this. This would be in case some developer has lots of outstanding changes based on earlier commits. They could first

Re: bitOrder Regression - DAFFODIL-1884

l nothing was running it anymore, so it falsely looked to be fixed. So I simply never finished the priorBitOrder change in the unparser code. ____ From: Mike Beckerle Sent: Monday, February 5, 2018 11:48:10 AM To: Steve Lawrence; dev@daffodil.apache.org Subject: Re:

Re: bitOrder Regression - DAFFODIL-1884

on the DirectOrBufferedDataOutputStream class. But, it is never called. Oops. Looks like I put the mechanism in place to do this, but didn't finish the implementation. ...mikeb From: Stephen Lawrence Sent: Monday, February 5, 2018 10:29 AM To: Mike Beckerle Subject

Re: [GitHub] jadams-tresys commented on issue #29: Fixed bug in calculating bit length for delimited unparsing

There is a DFDL property named textoutputminlength I think which is the minlength equivalent for non string type with text representation. That prop is almost certainly 0 in most schemas. Original message From: GitBox Date: 1/29/18 11:29 AM (GMT-05:00) To:

Re: old support branches - that are unsupported

Lawrence <slawre...@apache.org> Date: 1/26/18 3:41 PM (GMT-05:00) To: dev@daffodil.apache.org, Mike Beckerle <mbecke...@tresys.com> Subject: Re: old support branches - that are unsupported I guess it comes down to what our actual support policy is. Do we support a release for N m

old support branches - that are unsupported

Can we get rid of all the support/v0.10 and similar branches prior to support/v1.0.0 There is nothing on any of these branches, and we won't do any support on them. (Based on that we should eliminate support/v1.0.0 and support/v1.1.0 as well.) but when I pull down the menu for choosing a

Re: Code review request

Done. See PR 26 https://github.com/apache/incubator-daffodil/pull/26 From: Steve Lawrence <slawre...@apache.org> Sent: Tuesday, January 16, 2018 7:13:57 AM To: dev@daffodil.apache.org; Mike Beckerle Subject: Re: Code review request I think a better way

Re: poor-man's daffodil-server idea

y? The > CLI would then just be an interface to load schema's or more so to just > send data to it and receive results. > > On Jan 15, 2018 12:21 PM, "Mike Beckerle" <mbecke...@tresys.com> wrote: > >> What if we changed the Daffodil CLI to have a --server mode.

poor-man's daffodil-server idea

What if we changed the Daffodil CLI to have a --server mode. In this mode the CLI would reads command-lines from std input, then does what it does now for a command line, but at the end it would go back to reading another command from std input, and stay in that loop until EOF on std input.

Re: Help implementing schema for SISO-J

of the J message. The pre/post processing feature does seem like a better hammer for the problem. I believe we could contribute a pre/post processor that can handle swapping. Do you have an idea on when this new feature will start to be implemented? On Thu, Jan 11, 2018 at 8:11 PM, Mike Beckerle <m

<    1   2   3   4   5   6   >