tuxji commented on code in PR #95: URL: https://github.com/apache/daffodil-site/pull/95#discussion_r1009577898
########## site/_releases/3.4.0.md: ########## @@ -0,0 +1,136 @@ +--- + +released: false +apache: true +title: 3.4.0 +date: 2022-10-31 +summary: > + EXI binary XML support, pluggable character sets, embedded XML, C code + generator updates + +artifact-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; +checksum-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; + +key-file: "https://downloads.apache.org/daffodil/KEYS"; + +source-dist: + - "apache-daffodil-3.4.0-src.zip" + +binary-dist: + - "apache-daffodil-3.4.0-bin.tgz" + - "apache-daffodil-3.4.0-bin.zip" + - "apache-daffodil-3.4.0-bin.msi" + - "apache-daffodil-3.4.0-1.noarch.rpm" + +scala-version: 2.12 +--- + +#### EXI Support + +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. + +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. + +* {% jira 1959 %} EXIficient Inputter and outputter for XML EXI representation +* {% jira 2739 %} Expose DFDLCatalogResolver to the public API + +#### Pluggable Character Sets + +Custom character sets can now be added to Daffodil by implementing a custom +`BitsCharsetDefinition` class and related functions/classes, listing it in a +`META-INF/services` file, packaging it into a jar, and adding it to the +Daffodil classpath. + +* {% jira 2663 %} charset encoders need to be pluggable (doc needed) + +#### Embedded XML in the Infoset + +When using the `XMLTextInfosetInputter` and `XMLTextInfosetOutputter` in the Review Comment: ```When using the `XMLTextInfosetInputter` and `XMLTextInfosetOutputter` classes in the``` ########## site/_releases/3.4.0.md: ########## @@ -0,0 +1,136 @@ +--- + +released: false +apache: true +title: 3.4.0 +date: 2022-10-31 +summary: > + EXI binary XML support, pluggable character sets, embedded XML, C code + generator updates + +artifact-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; +checksum-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; + +key-file: "https://downloads.apache.org/daffodil/KEYS"; + +source-dist: + - "apache-daffodil-3.4.0-src.zip" + +binary-dist: + - "apache-daffodil-3.4.0-bin.tgz" + - "apache-daffodil-3.4.0-bin.zip" + - "apache-daffodil-3.4.0-bin.msi" + - "apache-daffodil-3.4.0-1.noarch.rpm" + +scala-version: 2.12 +--- + +#### EXI Support + +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. + +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. + +* {% jira 1959 %} EXIficient Inputter and outputter for XML EXI representation +* {% jira 2739 %} Expose DFDLCatalogResolver to the public API + +#### Pluggable Character Sets + +Custom character sets can now be added to Daffodil by implementing a custom +`BitsCharsetDefinition` class and related functions/classes, listing it in a +`META-INF/services` file, packaging it into a jar, and adding it to the +Daffodil classpath. + +* {% jira 2663 %} charset encoders need to be pluggable (doc needed) + +#### 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. Review Comment: ```attribute `dfdl:runtimeProperties="stringAsXml=true"` are treated as embedded XML.``` ########## site/_releases/3.4.0.md: ########## @@ -0,0 +1,136 @@ +--- + +released: false +apache: true +title: 3.4.0 +date: 2022-10-31 +summary: > + EXI binary XML support, pluggable character sets, embedded XML, C code + generator updates + +artifact-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; +checksum-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; + +key-file: "https://downloads.apache.org/daffodil/KEYS"; + +source-dist: + - "apache-daffodil-3.4.0-src.zip" + +binary-dist: + - "apache-daffodil-3.4.0-bin.tgz" + - "apache-daffodil-3.4.0-bin.zip" + - "apache-daffodil-3.4.0-bin.msi" + - "apache-daffodil-3.4.0-1.noarch.rpm" + +scala-version: 2.12 +--- + +#### EXI Support + +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. + +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. Review Comment: Let's use active voice here too. ``` 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 also added the new `DaffodilXMLEntityResolver` class to its Java and Scala public APIs to support creating schema aware EXI files. ``` ########## site/_releases/3.4.0.md: ########## @@ -0,0 +1,136 @@ +--- + +released: false +apache: true +title: 3.4.0 +date: 2022-10-31 +summary: > + EXI binary XML support, pluggable character sets, embedded XML, C code + generator updates + +artifact-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; +checksum-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; + +key-file: "https://downloads.apache.org/daffodil/KEYS"; + +source-dist: + - "apache-daffodil-3.4.0-src.zip" + +binary-dist: + - "apache-daffodil-3.4.0-bin.tgz" + - "apache-daffodil-3.4.0-bin.zip" + - "apache-daffodil-3.4.0-bin.msi" + - "apache-daffodil-3.4.0-1.noarch.rpm" + +scala-version: 2.12 +--- + +#### EXI Support + +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. Review Comment: Consider using active voice instead of passive voice: ``` The Daffodil CLI has added the [Exificient](https://exificient.github.io/) library to support the `-I exi` and `-I exisa` infoset types. ``` ########## site/_releases/3.4.0.md: ########## @@ -0,0 +1,136 @@ +--- + +released: false +apache: true +title: 3.4.0 +date: 2022-10-31 +summary: > + EXI binary XML support, pluggable character sets, embedded XML, C code + generator updates + +artifact-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; +checksum-root: "https://dist.apache.org/repos/dist/dev/daffodil/3.4.0-rc1/"; + +key-file: "https://downloads.apache.org/daffodil/KEYS"; + +source-dist: + - "apache-daffodil-3.4.0-src.zip" + +binary-dist: + - "apache-daffodil-3.4.0-bin.tgz" + - "apache-daffodil-3.4.0-bin.zip" + - "apache-daffodil-3.4.0-bin.msi" + - "apache-daffodil-3.4.0-1.noarch.rpm" + +scala-version: 2.12 +--- + +#### EXI Support + +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. + +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. + +* {% jira 1959 %} EXIficient Inputter and outputter for XML EXI representation +* {% jira 2739 %} Expose DFDLCatalogResolver to the public API + +#### Pluggable Character Sets + +Custom character sets can now be added to Daffodil by implementing a custom +`BitsCharsetDefinition` class and related functions/classes, listing it in a +`META-INF/services` file, packaging it into a jar, and adding it to the +Daffodil classpath. + +* {% jira 2663 %} charset encoders need to be pluggable (doc needed) + +#### 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 +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 Review Comment: ```it were part of the XML infoset. When unparsing, the embedded XML part of the infoset is``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
