- dfdl-wg - lists.ogf.org

Cancelled: DFDL Working Group Call
by Steve Hanson 03 Mar '14

03 Mar '14

Mike not available

1 0

FW: DFDL - default and fixed
by Cranford, Jonathan W. 25 Feb '14

25 Feb '14

DFDL WG, Question from James Garriss: Can an element have a default property and a fixed property? If so, what happens if their values are different? I think the answer is that the default property and fixed property are mutually exclusive, as they are mutually exclusive in XSD 1.0. Is that correct? If so, the DFDL specification could be a little clearer on this point. Adding a sentence to section 5.2.6 or 5.2.7 (or both) should suffice, something along the lines of "Note that the default and fixed properties are mutually exclusive in DFDL, just as they are in XSD 1.0; both properties may not be applied to the same element." Thanks in advance, -- Jonathan W. Cranford Senior Information Systems Engineer The MITRE Corporation (http://www.mitre.org)

1 0

Cancelled: DFDL Working Group Call
by Steve Hanson 25 Feb '14

25 Feb '14

Tim and Mike away

1 0

OGF DFDL WG Call 2014-02-25 - cancelled
by Steve Hanson 25 Feb '14

25 Feb '14

Sorry have to cancel the call as Mike and Tim are both unable to make it. Regards Steve Hanson Architect, IBM DFDL Co-Chair, OGF DFDL Working Group Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848

1 0

first half of implementation-specific behavior review
by Cranford, Jonathan W. 25 Feb '14

25 Feb '14

All, Attached is the first half of my review of implementation-specific behavior in the 1.0.4 version of the DFDL specification. I categorized each feature/behavior as either implementation-defined or implementation-dependent. I put these all in a Word document to simplify review. I don't have a preference for whether it remains as a separate document (as with action 140) or whether it gets folded into an errata document. Fyi, -- Jonathan W. Cranford <jcranford(a)mitre.org> Senior Information Systems Engineer The MITRE Corporation (http://www.mitre.org) 801-572-7446 [office] 801-903-3431 [cell] AIM, XMPP: jcranford(a)mitre.org

2 1

DFDL: Evaluation of operands in XPath logical expressions
by Steve Hanson 20 Feb '14

20 Feb '14

I thought I'd let you know about an interesting processing error that occurred today when testing IBM DFDL. An expression of the form: {if (fn:exists(x) and fn:contains('abc', x/y)) then 1 else 0} gave a parser error saying that x/y didn't exist, when x was not in the message. This surprised me, as I was assuming that the IBM DFDL parser would lazily evaluate the operands of the logical expression. I was going to raise a bug, but thought I had best read the XPath 2.0 spec first. The relevant section is here: http://www.w3.org/TR/xpath20/#id-logical-expressions The section says that unless you are in XPath 1.0 compatibility mode (which a DFDL processor would not be), the order of evaluation of operands of a logical expression is actually implementation dependent. So it is therefore unsafe to rely on lazy evaluation to implement a guard in the manner that I had. I have rewritten the expression as: {if (fn:exists(x)) then if (fn:contains('abc', x/y)) then 1 else 0 else 0} I think this might catch people out and is certainly worthy of mention in (at least) a tutorial on DFDL expressions. 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 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

Fw: Action 252: Clarify binary packed calendar relationship with calendar pattern - update
by Steve Hanson 18 Feb '14

18 Feb '14

Minor update as per call. 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 18/02/2014 16:54 ----- From: Steve Hanson/UK/IBM To: dfdl-wg(a)ogf.org, Date: 17/02/2014 17:51 Subject: Action 252: Clarify binary packed calendar relationship with calendar pattern The following updates are proposed to satisfy action 252: Section 13.13 Property Name Description binaryCalendarRep Enum Valid values are 'packed', 'bcd', 'ibm4690Packed', 'binarySeconds', 'binaryMilliseconds' For all values, the dfdl:byteOrder property is used to determine the numeric significance of the bytes making up the representation. 'packed' means represented as an IBM 390 packed decimal. Each byte contains two decimal digits, except for the rightmost byte, which contains a sign to the right of a decimal digit. The digits are interpreted according to the dfdl:calendarPattern property. Property dfdl:binaryPackedSignCodes is applicable. 'bcd' means represented as a binary coded decimal with two digits per byte. The digits are interpreted according to the dfdl:calendarPattern property. 'ibm4690Packed' means represented as a variant of packed format as described in property dfdl:binaryNumberRep.The digits are interpreted according to the dfdl:calendarPattern property. For all packed decimals, property dfdl:binaryNumberCheckPolicy is applicable. See Properties specific to numbers with binary representation section : 13.7 Properties Specific to Numbers with Binary Representation. For all these packed decimals, dfdl:calendarPattern can contain only characters and symbols that always result in the presentation of digits. It is a schema definition error otherwise. This implies that property dfdl:calendarPatternKind must be 'explicit' because the default patterns for 'implicit' contain non-numeric characters. It is a schema definition error otherwise. For all packed decimals, a virtual decimal point for the boundary between seconds and fractional seconds is implied from the pattern at the boundary of 's' and 'S', i.e., where the substring 'sS' appears in the pattern. 'binarySeconds' means represented as binary xs:int, that is, as a 4 byte signed integer that is the number of seconds from the epoch (positive or negative). It is a schema definition error if there is a specified length not equivalent to 4 bytes. 'binaryMilliseconds' means represented as binary xs:long, that is, as an 8 byte signed integer that is the number of milliseconds from the epoch (positive or negative). It is a schema definition error if there is a specified length not equivalent to 8 bytes. binarySeconds and binaryMilliseconds may only be used when the type is xs:dateTime. It is a schema definition error otherwise. Annotation: dfdl:element, dfdl:simpleType Section 13.11.1 Change sentence "If dfdl:representation is binary, any characters in the pattern that are not digits must be quoted." to "If dfdl:representation is binary, then the pattern can contain only characters and symbols that always result in the presentation of digits." (Same phrase as used in the calendarPattern and binaryCalendarRep properties). Section 12.3.7.2.5 This section talks about packed decimal numbers. It should occur between existing sections 12.3.7.2 and 12.3.7.3, to keep the Number reps together, and to occur before 12.3.7.2.4 on binary calendars. Content is fine. (Current) Section 12.3.7.2.4 Change bullet 3 to read: 3. Any of the packed decimal values - the representation maximum specified length is implementation defined but must be at least 17 (corresponding to calendar pattern 'yyyyMMddhhmmssSSS'). (This is the smallest pattern that contains all the digit-only symbols. SSS is the minimum precision for fractional seconds, but in can be more, hence why 'at least 17'. See 13.11.1, it's another implementation defined thing.) 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 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 DFDL WG Call Minutes 2014-02-18
by Steve Hanson 18 Feb '14

18 Feb '14

Please find minutes from the above call at http://redmine.ogf.org/dmsf_files/13211?download= 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

OGF DFDL WG Call Agenda 2014-02-18
by Steve Hanson 17 Feb '14

17 Feb '14

Please find agenda for call on Redmine at http://redmine.ogf.org/dmsf_files/13211?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

Action 252: Clarify binary packed calendar relationship with calendar pattern
by Steve Hanson 17 Feb '14

17 Feb '14

The following updates are proposed to satisfy action 252: Section 13.13 Property Name Description binaryCalendarRep Enum Valid values are 'packed', 'bcd', 'ibm4690Packed', 'binarySeconds', 'binaryMilliseconds' For all values, the dfdl:byteOrder property is used to determine the numeric significance of the bytes making up the representation. 'packed' means represented as an IBM 390 packed decimal. Each byte contains two decimal digits, except for the rightmost byte, which contains a sign to the right of a decimal digit. The digits are interpreted according to the dfdl:calendarPattern property. 'bcd' means represented as a binary coded decimal with two digits per byte. The digits are interpreted according to the dfdl:calendarPattern property. 'ibm4690Packed' means represented as a variant of packed format as described in property dfdl:binaryNumberRep.The digits are interpreted according to the dfdl:calendarPattern property. For all these packed decimals the following properties are also applicable · dfdl:binaryPackedSignCodes ('packed' only) · dfdl:binaryNumberCheckPolicy See Properties specific to numbers with binary representation section : 13.7 Properties Specific to Numbers with Binary Representation. For all these packed decimals, dfdl:calendarPattern can contain only characters and symbols that always result in the presentation of digits. It is a schema definition error otherwise. This implies that property dfdl:calendarPatternKind must be 'explicit' because the default patterns for 'implicit' contain non-numeric characters. It is a schema definition error otherwise. For all these packed decimals, a virtual decimal point for the boundary between seconds and fractional seconds is implied from the pattern at the boundary of 's' and 'S', i.e., where the substring 'sS' appears in the pattern. 'binarySeconds' means represented as binary xs:int, that is, as a 4 byte signed integer that is the number of seconds from the epoch (positive or negative). It is a schema definition error if there is a specified length not equivalent to 4 bytes. 'binaryMilliseconds' means represented as binary xs:long, that is, as an 8 byte signed integer that is the number of milliseconds from the epoch (positive or negative). It is a schema definition error if there is a specified length not equivalent to 8 bytes. binarySeconds and binaryMilliseconds may only be used when the type is xs:dateTime. (It is a schema definition error otherwise.) Annotation: dfdl:element, dfdl:simpleType Section 13.11.1 Change sentence "If dfdl:representation is binary, any characters in the pattern that are not digits must be quoted." to "If dfdl:representation is binary, then the pattern can contain only characters and symbols that always result in the presentation of digits." (Same phrase as used in the calendarPattern and binaryCalendarRep properties). Section 12.3.7.2.5 This section talks about packed decimal numbers. It should occur between existing sections 12.3.7.2 and 12.3.7.3, to keep the Number reps together, and to occur before 12.3.7.2.4 on binary calendars. Content is fine. (Current) Section 12.3.7.2.4 Change bullet 3 to read: 3. Any of the packed decimal values - the representation maximum specified length is implementation defined but must be at least 17 (corresponding to calendar pattern 'yyyyMMddhhmmssSSS'). (This is the smallest pattern that contains all the digit-only symbols. SSS is the minimum precision for fractional seconds, but in can be more, hence why 'at least 17'. See 13.11.1, it's another implementation defined thing.) 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 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