- dfdl-wg - lists.ogf.org

Tracker 233 - Minor typographical
by Mike Beckerle 16 Oct '14

16 Oct '14

I accidently deleted tracker 232 - but I've recreated its content in tracker 233 - https://redmine.ogf.org/issues/233 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>

1 0

OGF DFDL WG Call Minutes 2014-10-14
by Steve Hanson 15 Oct '14

15 Oct '14

Please find minutes from the above call at http://redmine.ogf.org/dmsf_files/13364?download= No call next week, so next one is Oct 28th. Regards Steve Hanson Architect, IBM DFDL, Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848

1 0

spec bug in dfdl:hexBinary function example
by Mike Beckerle 15 Oct '14

15 Oct '14

In discussion of the dfdl:hexBinary function, it says literals are given the smallest signed type that will hold them. This example is therefore incorrect: • dfdl:hexBinary(208) is the hexBinary value "D0". EXB Should be value 00D0 since 208 is beyond the range of a signed byte, so must be a signed short. 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>

2 1

Re: [DFDL-WG] typographical error
by Steve Hanson 15 Oct '14

15 Oct '14

All tracked by issue http://redmine.ogf.org/issues/232. Regards Steve Hanson Architect, IBM DFDL Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848 From: Steve Hanson/UK/IBM To: Andrew Edwards/UK/IBM@IBMGB Cc: Mike Beckerle <mbeckerle.dfdl(a)gmail.com>, "dfdl-wg(a)ogf.org" <dfdl-wg(a)ogf.org>, dfdl-wg-bounces(a)ogf.org Date: 14/10/2014 15:56 Subject: Re: [DFDL-WG] typographical error Two more typos spotted: textNumberCheckPolicy: On unparsing the pattern is always followed and follow the rules in 13.6.2 Converting logical numbers to/from text representation. textStandardDecimalSeparator: Defines the a whitespace separated ... Regards Steve Hanson Architect, IBM DFDL Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848 From: Andrew Edwards/UK/IBM@IBMGB To: Mike Beckerle <mbeckerle.dfdl(a)gmail.com> Cc: "dfdl-wg(a)ogf.org" <dfdl-wg(a)ogf.org>, dfdl-wg-bounces(a)ogf.org Date: 08/10/2014 16:10 Subject: Re: [DFDL-WG] typographical error Sent by: dfdl-wg-bounces(a)ogf.org Yep - confirmed. Andy Andy Edwards - IBM Integration Bus - DFDL Email: andy.edwards(a)uk.ibm.com Snail Mail: MP211, Hursley park, Hursley, WINCHESTER, Hants, SO21 2JN Tel int: 247222 Tel ext: +44 (0)1962 817222 Desk: DE3 V17 The Feynman problem solving Algorithm 1) Write down the problem 2) Think real hard 3) Write down the answer -- Murray Gell-mann in the NY Times Mike Beckerle <mbeckerle.dfdl(a)gmail.com> Sent by: dfdl-wg-bounces(a)ogf.org 07/10/2014 19:40 To "dfdl-wg(a)ogf.org" <dfdl-wg(a)ogf.org> cc Subject [DFDL-WG] typographical error Page 222: dfdl:hexBinary(-2084) is the hexBinary value "F7FF". The hex is incorrect. Should be "F7DC" 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 -- dfdl-wg mailing list dfdl-wg(a)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 -- dfdl-wg mailing list dfdl-wg(a)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 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

1 0

typographical error
by Mike Beckerle 14 Oct '14

14 Oct '14

Page 222: dfdl:hexBinary(-2084) is the hexBinary value "F7FF". The hex is incorrect. Should be "F7DC" 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>

3 2

OGF DFDL WG Call Agenda 2014-10-14
by Steve Hanson 13 Oct '14

13 Oct '14

Please find agenda for call on Redmine at http://redmine.ogf.org/dmsf_files/13364?download= Regards Steve Hanson Architect, IBM Data Format Description Language (DFDL) Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848

1 0

Cancelled: DFDL Working Group Call
by Steve Hanson 07 Oct '14

07 Oct '14

Busy this week, and unable to make progress on any open issues

1 0

OGF DFDL WG Call Minutes 2014-09-23
by Steve Hanson 23 Sep '14

23 Sep '14

Please find minutes from the above call at http://redmine.ogf.org/dmsf_files/13356?download= No call next week, so next one is Oct 7th. Regards Steve Hanson Architect, IBM DFDL, Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848

1 0

Fw: stop bit encoding
by Steve Hanson 23 Sep '14

23 Sep '14

Agreed to defer to future DFDL 1.1. Regards Steve Hanson Architect, IBM DFDL Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848 ----- Forwarded by Steve Hanson/UK/IBM on 23/09/2014 17:37 ----- From: Steve Hanson/UK/IBM To: Mike Beckerle <mbeckerle.dfdl(a)gmail.com>, Cc: "dfdl-wg(a)ogf.org" <dfdl-wg(a)ogf.org>, dfdl-wg-bounces(a)ogf.org Date: 16/07/2014 08:51 Subject: Re: [DFDL-WG] stop bit encoding That's correct. This is the example of stop-bit encoding that I have referred to in the past. It's actually the FAST (FIX Adapted for STreaming) protocol, and not the standard FIX format. Regards Steve Hanson Architect, IBM DFDL Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848 From: Mike Beckerle <mbeckerle.dfdl(a)gmail.com> To: "dfdl-wg(a)ogf.org" <dfdl-wg(a)ogf.org>, Date: 15/07/2014 18:34 Subject: [DFDL-WG] stop bit encoding Sent by: dfdl-wg-bounces(a)ogf.org The FIX protocols (financial interchange) make use of stop bit encoding. I have heard of other places using this also. This is modern, current, non-legacy usage. This is the length encoding where the most-significant bit of a byte is used to determine whether there are more ASCII characters or not. The last byte will have the most-significant bit of 1, prior bytes most-significant bit of 0. Minimum length in this length kind is 1. It seems we are missing this lengthKind, which applies only to text in the ASCII/US-ASCII encoding. 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 -- dfdl-wg mailing list dfdl-wg(a)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 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

1 0

OGF spec updates - planning for errata vs. editorial vs. respins
by Mike Beckerle 23 Sep '14

23 Sep '14

Below are the relevant 3 paragraphs from: http://www.ogf.org/Public_Comment_Docs/Documents/2007-10/draft-gwdc-gfsg-c1… Our existing errata process divides into editorial things (which we just fix), minor tech issues, major tech issues which is consistent with the below. Note that the discussion suggests not a separate errata document, but that the errata must be added to the spec itself - and the notion that they are listed on the cover sheet means they are anticipating only a relatively small set of such errata compared what has happened since 2013 Sept. To me this suggests such errata are not suitable for anything one can anticipate as a "parked issue" for the future. Such things must be in a new revision of the standard. Editorial fixes applied within the first month after publication will generally not be publicly announced to the OGF community. Any other changes to a document, whether major or minor, will be announced using the same mechanism as for a newly published document (i.e., email to the OGF community, posting to the OGF Web site, etc.). Whenever a document is updated, even for minor editorial updates, the document header will be adjusted to reflect the date the document was updated. The date of the update should appear in the upper right side of the document's first page, beneath any prior date. For very minor updates, especially those within the first month after publication, no additional information needs to be added to the document. A publicly accessible archive of all old versions of the document is maintained, and accessible through the same means as current documents. For all other updates, minor and major technical fixes, an errata report must be added to the document itself. Recommended practice is to put an errata report labeled as “Document Change History” on the first page of the document, directly under the copyright statement and before the abstract. A brief report on what was changed is sufficient, along with the date. If a more discussion is desired, the Document Change History can refer to a later section where the update is discussed in detail. 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>

2 1