Re: [VOTE] Daffodil into the Apache Incubator
Sorry, I've been distracted. +1. Regards, Dave Sent from my iPhone > On Aug 14, 2017, at 12:11 AM, Bertrand Delacretaz > wrote: > > On Thu, Aug 10, 2017 at 9:03 PM, Steve Lawrence > wrote: >> ...I would like >> to start a VOTE to bring the Daffodil project in as an Apache incubator >> podling... > > +1 > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Daffodil into the Apache Incubator
On Thu, Aug 10, 2017 at 9:03 PM, Steve Lawrence wrote: > ...I would like > to start a VOTE to bring the Daffodil project in as an Apache incubator > podling... +1 -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Daffodil into the Apache Incubator
+1 Best regards Pierre On Thu, 10 Aug 2017 at 21:09 John D. Ament wrote: > +1 to accept > > On Thu, Aug 10, 2017 at 3:03 PM Steve Lawrence < > stephen.d.lawre...@gmail.com> > wrote: > > > Hi All, > > > > Based on the discussion on the incubator mailing list [1], I would like > > to start a VOTE to bring the Daffodil project in as an Apache incubator > > podling. > > > > The ASF voting rules are described: > > > > https://www.apache.org/foundation/voting.html > > > > A vote for accepting a new Apache Incubator podling is a majority vote > > for which only Incubator PMC member votes are binding. > > > > This vote will run for at least 72 hours. Please VOTE as follows > > [] +1 Accept Daffodil into the Apache Incubator > > [] +0 Abstain. > > [] -1 Do not accept Daffodil into the Apache Incubator because ... > > > > The proposal is listed below, but you can also access it on the wiki: > > > > https://wiki.apache.org/incubator/DaffodilProposal > > > > Thank you, > > - Steve > > > > [1] > > > > > https://lists.apache.org/thread.html/190d73e84508d2deaa6cfde1be197cb70ca4caddfb215bc269b3e44f@%3Cgeneral.incubator.apache.org%3E > > > > > > > > = Daffodil Proposal = > > > > == Abstract == > > > > Daffodil is an implementation of the Data Format Description Language > > (DFDL) used to convert between fixed format data and XML/JSON. > > > > == Proposal == > > > > The Data Format Description Language (DFDL) is a specification, > > developed by the Open Grid Forum, capable of describing many data > > formats, including both textual and binary, scientific and numeric, > > legacy and modern, commercial record-oriented, and many industry and > > military standards. It defines a language that is a subset of W3C XML > > schema to describe the logical format of the data, and annotations > > within the schema to describe the physical representation. > > > > Daffodil is an open source implementation of the DFDL specification that > > uses these DFDL schemas to parse fixed format data into an infoset, > > which is most commonly represented as either XML or JSON. This allows > > the use of well-established XML or JSON technologies and libraries to > > consume, inspect, and manipulate fixed format data in existing > > solutions. Daffodil is also capable of the reverse by serializing or > > "unparsing" an XML or JSON infoset back to the original data format. > > > > == Background == > > > > Many different software solutions need to consume and manage data, > > including data directed routing, databases, data analysis, data > > cleansing, data visualizing, and more. A key aspect of such solutions is > > the need to transform the data into an easily consumable format. > > Usually, this means that for each unique data format, one develops a > > tool that can read and extract the necessary information, often leading > > to ad-hoc and data-format-specific description systems. Such systems are > > often proprietary, not well tested, and incompatible, leading to vendor > > lock-in, flawed software, and increased training costs. DFDL is a new > > standard, with version 1.0 completed in October of 2016, that solves > > these problems by defining an open standard to describe many different > > data formats and how to parse and unparse between the data and XML/JSON. > > > > Two closed source implementations of DFDL currently exist. The first was > > created by IBM and is now part of their IBM® Integration Bus product. > > The second was created by the European Space Agency, called DFDL4S or > > "DFDL for Space" targeted at the challenges of their satellite data > > processing. > > > > Around 2005, Pacific Northwest National Lab created Defuddle, built as > > an open source implementation and proof of concept of the draft DFDL > > specification and a test bed to feed new concepts into specification > > development. Primary development of Defuddle was eventually taken over > > by the National Center for Supercomputing Applications (NCSA). However, > > due to evolution of the DFDL specification and architectural and > > performance issues with Defuddle, around 2009, NCSA restarted the > > project with the new name of Daffodil, with a goal of implementing the > > complete DFDL specification. Daffodil development continued at NCSA > > until around 2012, at which point development slowed due to budget > > limitations. Shortly thereafter, primary development was picked up by > > Tresys Technology where it continues today, with contributions from > > other entities such as the Navy Research Lab, the Air Force Research > > Lab, MITRE, and Booz Allen Hamilton. In February of 2015, Daffodil > > version 1.0.0 was released, including support for the DFDL features > > needed to parse many common file formats. Daffodil version 2.0.0 is > > expected to be released in August of 2017, which will include unparse > > support with one-to-one parsing feature parity. > > > > Entities including IBM, MITRE, NATO NCI Agency, Northrop-Grumman, Quark > > Security, Ra
Re: [VOTE] Daffodil into the Apache Incubator
+1 to accept On Thu, Aug 10, 2017 at 3:03 PM Steve Lawrence wrote: > Hi All, > > Based on the discussion on the incubator mailing list [1], I would like > to start a VOTE to bring the Daffodil project in as an Apache incubator > podling. > > The ASF voting rules are described: > > https://www.apache.org/foundation/voting.html > > A vote for accepting a new Apache Incubator podling is a majority vote > for which only Incubator PMC member votes are binding. > > This vote will run for at least 72 hours. Please VOTE as follows > [] +1 Accept Daffodil into the Apache Incubator > [] +0 Abstain. > [] -1 Do not accept Daffodil into the Apache Incubator because ... > > The proposal is listed below, but you can also access it on the wiki: > > https://wiki.apache.org/incubator/DaffodilProposal > > Thank you, > - Steve > > [1] > > https://lists.apache.org/thread.html/190d73e84508d2deaa6cfde1be197cb70ca4caddfb215bc269b3e44f@%3Cgeneral.incubator.apache.org%3E > > > > = Daffodil Proposal = > > == Abstract == > > Daffodil is an implementation of the Data Format Description Language > (DFDL) used to convert between fixed format data and XML/JSON. > > == Proposal == > > The Data Format Description Language (DFDL) is a specification, > developed by the Open Grid Forum, capable of describing many data > formats, including both textual and binary, scientific and numeric, > legacy and modern, commercial record-oriented, and many industry and > military standards. It defines a language that is a subset of W3C XML > schema to describe the logical format of the data, and annotations > within the schema to describe the physical representation. > > Daffodil is an open source implementation of the DFDL specification that > uses these DFDL schemas to parse fixed format data into an infoset, > which is most commonly represented as either XML or JSON. This allows > the use of well-established XML or JSON technologies and libraries to > consume, inspect, and manipulate fixed format data in existing > solutions. Daffodil is also capable of the reverse by serializing or > "unparsing" an XML or JSON infoset back to the original data format. > > == Background == > > Many different software solutions need to consume and manage data, > including data directed routing, databases, data analysis, data > cleansing, data visualizing, and more. A key aspect of such solutions is > the need to transform the data into an easily consumable format. > Usually, this means that for each unique data format, one develops a > tool that can read and extract the necessary information, often leading > to ad-hoc and data-format-specific description systems. Such systems are > often proprietary, not well tested, and incompatible, leading to vendor > lock-in, flawed software, and increased training costs. DFDL is a new > standard, with version 1.0 completed in October of 2016, that solves > these problems by defining an open standard to describe many different > data formats and how to parse and unparse between the data and XML/JSON. > > Two closed source implementations of DFDL currently exist. The first was > created by IBM and is now part of their IBM® Integration Bus product. > The second was created by the European Space Agency, called DFDL4S or > "DFDL for Space" targeted at the challenges of their satellite data > processing. > > Around 2005, Pacific Northwest National Lab created Defuddle, built as > an open source implementation and proof of concept of the draft DFDL > specification and a test bed to feed new concepts into specification > development. Primary development of Defuddle was eventually taken over > by the National Center for Supercomputing Applications (NCSA). However, > due to evolution of the DFDL specification and architectural and > performance issues with Defuddle, around 2009, NCSA restarted the > project with the new name of Daffodil, with a goal of implementing the > complete DFDL specification. Daffodil development continued at NCSA > until around 2012, at which point development slowed due to budget > limitations. Shortly thereafter, primary development was picked up by > Tresys Technology where it continues today, with contributions from > other entities such as the Navy Research Lab, the Air Force Research > Lab, MITRE, and Booz Allen Hamilton. In February of 2015, Daffodil > version 1.0.0 was released, including support for the DFDL features > needed to parse many common file formats. Daffodil version 2.0.0 is > expected to be released in August of 2017, which will include unparse > support with one-to-one parsing feature parity. > > Entities including IBM, MITRE, NATO NCI Agency, Northrop-Grumman, Quark > Security, Raytheon, and Tresys Technology have developed DFDL schemas > for many data formats from varying technology domains, including PNG, > GIF, BMP, PCAP, HL7, EDIFACT, NACHA, vCard, iCalendar, and MIL-STD-2045 > , many of which are publicly available on the DFDL Schemas github. There > are also a number of military-applic