[daffodil-site] branch main updated: Prepare for 3.4.0-rc2 release

[ji...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jinterrante pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/daffodil-site.git


The following commit(s) were added to refs/heads/main by this push:
     new a4beb34  Prepare for 3.4.0-rc2 release
a4beb34 is described below

commit a4beb348df2bbcb699de78614d1567e29f0fca37
Author: John Interrante <in...@research.ge.com>
AuthorDate: Wed Nov 2 15:24:54 2022 -0400

    Prepare for 3.4.0-rc2 release
    
    Improve active voice and use more precise wording.  Add changes to
    transitive dependencies and one more jira issue fixed in 3.4.0.
    
    DAFFODIL-2740
---
 site/_releases/3.4.0.md | 54 +++++++++++++++++++++++++++++++++----------------
 1 file changed, 37 insertions(+), 17 deletions(-)

diff --git a/site/_releases/3.4.0.md b/site/_releases/3.4.0.md
index 3771e59..5c0eee5 100644
--- a/site/_releases/3.4.0.md
+++ b/site/_releases/3.4.0.md
@@ -31,13 +31,15 @@ The Daffodil CLI adds two new infoset types--`-I exi` and `-I exisa`--to
 support infosets represented as EXI binary XML for non-schema aware and schema
 aware EXI, respectively. EXI infosets are significantly smaller in size than
 normal XML infosets, and are often even smaller than the original data format
-when made schema aware. This support has been enabled with the
-[Exificient](https://exificient.github.io/) library.
+when made schema aware. The Daffodil CLI has added the
+[Exificient](https://exificient.github.io/) library to support these infoset
+types.
 
-API users can create EXI files using the existing `SAXInfosetInputter` and
-`SAXInfosetOutputter` classes and the Exificient SAX API. This has also been
-tested with the Agile Delta EXI SAX API. Schema aware EXI can be enabled using
-the `DaffodilXMLEntityResolver`, newly added to Java and Scala public APIs.
+API users can create EXI files by combining the existing `SAXInfosetInputter`
+and `SAXInfosetOutputter` classes with the Exificient SAX API or they can use
+the Agile Delta EXI SAX API which has been tested with Daffodil as
+well. Daffodil has added the new `DaffodilXMLEntityResolver` class to its
+Java and Scala public APIs to support creating schema aware EXI files too.
 
 * {% jira 1959 %} EXIficient Inputter and outputter for XML EXI representation
 * {% jira 2739 %} Expose DFDLCatalogResolver to the public API
@@ -53,15 +55,16 @@ Daffodil classpath.
 
 #### Embedded XML in the Infoset
 
-When using the `XMLTextInfosetInputter` and `XMLTextInfosetOutputter` in the
-API, or `-I xml` in the CLI, simple string elements with the DFDL extension
-attribute of `dfdl:runtimeProperties="stringAsXml=true"` are treated as XML.
-This means that when parsing, instead of outputting the content as an XML
+When using the `XMLTextInfosetInputter` and `XMLTextInfosetOutputter` classes
+in the API, or `-I xml` in the CLI, simple string elements with the DFDL
+extension attribute `dfdlx:runtimeProperties="stringAsXml=true"` are treated as
+XML. This means that when parsing, instead of outputting the content as an XML
 escaped string, the parsed content is checked to be valid XML and output as if
-it were part of the XML infoset. When unparsing, the XML part of the infoset is
-converted back to a string. Note that because there are multiple ways to read
-and write XML that are syntactically different but semantically the same, it is
-possible that parsed or unparsed data may differ from the original data.
+it were part of the XML infoset. When unparsing, the embedded XML part of the
+infoset is converted back to a string. Note that because there are multiple
+ways to read and write XML that are syntactically different but semantically
+the same, it is possible that parsed or unparsed data may differ from the
+original data.
 
 * {% jira 2708 %} XML String feature in XML Text Infoset Inputter/Outputter
 
@@ -69,17 +72,18 @@ possible that parsed or unparsed data may differ from the original data.
 
 The C code generator backend now supports reading and writing N-bit booleans
 and integers, where N is an explicit length from 1 to 64 bits. Additional
-miscellaneous changes include unit test support, fixes to nested choices, and
-tweaks to how float numbers are output.
+miscellaneous changes include unit test support, fixes to nested choices,
+tweaks to how float numbers are output, and a command line option to choose the
+TDML implementation to run TDML tests.
 
 * {% jira 2696 %} Extend runtime2 to N-bit booleans and integers (1 <= N <= 64)
+* {% jira 2697 %} Choose TDML implementation to run TDML tests
 
 #### Additional New Features/Improvements
 
 * {% jira 2357 %} Update recoverable error to not be an SDW
 * {% jira 2369 %} TDML language needs comment syntax in documentPart byte and bits
 * {% jira 2685 %} Upgrade Scala XML library to 2.1.0 version
-* {% jira 2697 %} Choose TDML implementation to run TDML tests
 * {% jira 2702 %} Eliminate build warning on VSCode scala build of Daffodil
 * {% jira 2719 %} Add tests to illustrate some nillable and fixed-length scenarios
 * {% jira 2723 %} Change DataProcessor.copy() method to public
@@ -100,6 +104,7 @@ tweaks to how float numbers are output.
 * {% jira 2713 %} Release candidate container has poor cacability and reproducability
 * {% jira 2717 %} unparser deadlocks in mil-std-2045 2-message file case
 * {% jira 2726 %} Index out of bounds -1 during unparsing
+* {% jira 2742 %} bin.LICENSE and bin.NOTICE need to be updated
 
 #### Deprecation/Compatibility
 
@@ -120,6 +125,7 @@ The following dependencies have been added or updated:
 * FasterXML Woodstox Core 6.4.0 <small>(update)</small>
 * ICU4J 72.1 <small>(update)</small>
 * Log4j API 2.19.0 <small>(update)</small>
+* Scala Reflect & Standard Library 2.12.17 <small>(update)</small>
 * Scala XML 2.1.0 <small>(update)</small>
 
 **Command Line Interface**
@@ -134,3 +140,17 @@ The following dependencies have been added or updated:
 **Test**
 
 * Scalacheck 1.17.0 <small>(update)</small>
+
+**Changes to Transitive Dependencies**
+
+* Apache Commons Codec 1.15 <small>(update, used by httpclient5 & log4j)</small>
+* Apache HttpClient 5.1.3 <small>(new, used by XML Resolver)</small>
+* Apache HttpComponents Core HTTP/1.1 5.1.3 <small>(upgrade, used by XML Resolver)</small>
+* Apache HttpComponents Core HTTP/2 5.1.3 <small>(new, used by XML Resolver)</small>
+* JAXB API 2.2.11 <small>(new, used by Exificient)</small>
+* JAXB Core Implementation 2.2.11 <small>(new, used by Exificient)</small>
+* JAXB Runtime 2.2.11 <small>(new, used by Exificient)</small>
+* JavaBeans Activation Framework Specification 1.1.1 <small>(new, used by Exificient)</small>
+* SLF4J API 1.7.25 <small>(new, used by httpclient5)</small>
+* XML Resolver & data 4.4.3 <small>(update, used by Saxon-HE)</small>
+* XmlPull 1.1.3.1 <small>(new, used by Exificient)</small>