This is excellent. Thanks Steve. I will accept all tracked changes in the errata document, and then edit them according to your suggestions with change tracking on again so you can see easily what I've done to fix them. I'll push this as an updated revision to the redmine repo for a second pass of review, and let you know. A couple of these errata may require discussion on our call, but most of it is straightforward corrections/improvements. ...mikeb Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | www.tresys.com Please note: Contributions to the DFDL Workgroup's email discussions are subject to the OGF Intellectual Property Policy <http://www.ogf.org/About/abt_policies.php> On Wed, Oct 16, 2019 at 11:22 AM Steve Hanson <smh@uk.ibm.com> wrote:
Mike
Comments added. I used LibreOffice I'm ok using this for adding comments to small docs but not to the spec itself.
I've* indicated below* and via email to you where significant comments apply.
Regards
Steve Hanson
IBM Hybrid Integration, Hursley, UK Architect, *IBM DFDL* <http://www.ibm.com/developerworks/library/se-dfdl/index.html> Co-Chair, *OGF DFDL Working Group* <http://www.ogf.org/dfdl/> *smh@uk.ibm.com* <smh@uk.ibm.com> tel:+44-1962-815848 mob:+44-7717-378890 Note: I work Tuesday to Friday
From: Mike Beckerle <mbeckerle.dfdl@gmail.com> To: DFDL-WG <dfdl-wg@ogf.org> Date: 14/10/2019 19:58 Subject: [EXTERNAL] [DFDL-WG] Errata doc updated with draft errata 5.39 to 5.59 - from all Trackers Sent by: "dfdl-wg" <dfdl-wg-bounces@ogf.org> ------------------------------
I have updated our document gwde-dfdl-experience-4-v0.9.docx (The Errata doc) with draft errata for all known issues that had trackers. This adds Errata 5.39 to 5.59.
This is mostly just copying language that was in the trackers into the Errata document, but in some cases language had to be consolidated across the original tracker description and subsequent update comments. In some cases I had to compose descriptive language.
5.41 is not complete, as it involves review of all occurrences of MUST, MUST NOT, SHOULD, SHOULD NOT, etc. throughout the document. I plan to handle this after all other errata are incorporated into the spec, with a single sweep, then people can review by looking for those keywords.
In reviewing these errata, I suggest they are bucketed into those that are not controversial, and are best reviewed by editing them into the specification, and reviewing there, versus those where there is more concern as to whether the described change is correct and complete.
The list of these new errata is below. They are not controversial (to me) except where noted.
*5.39* 5.40 5.41 - one identified change not controvercial. The sweeping pass to examine all MUST/SHOULD, etc. is separate. 5.42 *5.43* 5.44 - needs careful review *5.45 - needs careful review* *5.46 - new language - needs review. It is a lengthy discussion. Perhaps can be made shorter ? * 5.47 - needs careful review 5.48 - do we need all 3 overloads of fn:error()? - also, all behavior here is very implementation-dependent. 5.49 5.50 5.51 5.52 5.53 5.54 5.55 *5.56* 5.57 5.58 5.59 - needs careful review - description may not match desired/actual behavior of implemetations
Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | *www.tresys.com* <http://www.tresys.com> Please note: Contributions to the DFDL Workgroup's email discussions are subject to the *OGF Intellectual Property Policy* <http://www.ogf.org/About/abt_policies.php> -- dfdl-wg mailing list dfdl-wg@ogf.org https://www.ogf.org/mailman/listinfo/dfdl-wg
Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU