February 2015 - dfdl-wg - lists.ogf.org

still no need for fn:error
by Mike Beckerle 03 Aug '16

03 Aug '16

Here's the example as suggested by Jonathan of how to issue an error that I previously was suggesting needed fn:error. I'm convinced this is sufficient and we can avoid the need for fn:error now. <xs:element name="magic_number" type="ex:uint32" dfdl:byteOrder="bigEndian"> <xs:annotation> <xs:appinfo source="*http://www.ogf.org/dfdl/*<http://www.ogf.org/dfdl/dfdl-1.0/> "> <dfdl:assert test="{ (xs:unsignedInt(.) eq *dfdl:hUInt('0xa1b2c3d4')*) | (xs:unsignedInt(.) eq *dfdl:hUInt('0xd4c3b2a1')*) }" message="{ fn:concat( 'Magic number ', dfdl:hexBinary(dfdl:unsignedInt(.)), ' was not 0xA1B2C3D4 (for bigEndian) or 0xD4C3B2A1 (for littleEndian).' }" /> <dfdl:setVariable ref="ex:bOrd">{ xs:unsignedInt(.) }<dfdl:setVariable> </xs:appinfo> </xs:annotation> </xs:element> -- Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | www.tresys.com

2 11

Action 278: Unparser maxOccurs issue
by Steve Hanson 24 Mar '15

24 Mar '15

Please have a position on the below proposal from IBM for this week's WG 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 From: Steve Hanson/UK/IBM To: DFDL-WG <dfdl-wg(a)ogf.org> Date: 12/01/2015 16:56 Subject: Unparser maxOccurs issue Possible change to spec needed., where it describes what happens when maxOccurs is exceeded during unparsing for occursCountKind 'fixed' and 'implicit' (and by implication scalar elements). It currently says it is a processing error. I think it is better to say that the unparser moves on when maxOccurs is reached. This makes the behaviour analogous to parsing, when it does not try to parse beyond maxOccurs and moves on. The current unparser wording is based on the assumption that any next occurrence of the element in the infoset must be an error, but this is not true - the next occurrence could be an occurrence of a same named element later in the schema. An obvious example is: <xs:element name="data" minOccurs="2"maxOccurs="2" dfdl:occursCountKind="fixed" ... /> <xs:element name="stuff" minOccurs="0" dfdl:occursCountKind="implicit" ... /> <xs:element name="data" maxOccurs="2" maxOccurs="2" dfdl:occursCountKind="fixed" ... /> with an infoset where 'stuff' is missing: message_data data - xx1 data - xx2 data - yy1 data - yy2 A more interesting example is this, taken from MIL-STD-2045 schema (my bold comments added): <xsd:sequence dfdl:separator="">  <xsd:choice> <xsd:sequence dfdl:separator=""> <xsd:group ref="FPI_true"/> <xsd:element dfdl:length="4" dfdl:lengthKind="explicit" name="Value1" type="xsd:string"/> </xsd:sequence> <xsd:sequence dfdl:separator=""> <xsd:group ref="FPI_false"/> </xsd:sequence> </xsd:choice>  <xsd:choice> <xsd:sequence dfdl:separator=""> <xsd:group ref="FPI_true"/> <xsd:element dfdl:length="4" dfdl:lengthKind="explicit" name="Value2" type="xsd:string"/> </xsd:sequence> <xsd:sequence dfdl:separator=""> <xsd:group ref="FPI_false"/> </xsd:sequence> </xsd:choice>  <xsd:choice> <xsd:sequence dfdl:separator=""> <xsd:group ref="FPI_true"/> <xsd:element dfdl:length="4" dfdl:lengthKind="explicit" name="Value3" type="xsd:string"/> </xsd:sequence> <xsd:sequence dfdl:separator=""> <xsd:group ref="FPI_false"/> </xsd:sequence> </xsd:choice> </xsd:sequence> ...where the FPI_true and FPI_false elements are defined in their own global groups. <xsd:group name="FPI_true"> <xsd:sequence dfdl:separator=""> <xsd:element default="true" dfdl:length="1" dfdl:lengthKind="explicit" dfdl:textBooleanFalseRep="0" dfdl:textBooleanTrueRep="1" name="FPI_true" type="xsd:boolean"> <xsd:annotation> <xsd:appinfo source="http://www.ogf.org/dfdl/"> <dfdl:discriminator>{. eq fn:true()}</dfdl:discriminator> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:group> <xsd:group name="FPI_false"> <xsd:sequence dfdl:separator=""> <xsd:element default="false" dfdl:length="1" dfdl:lengthKind="explicit" dfdl:textBooleanFalseRep="0" dfdl:textBooleanTrueRep="1" name="FPI_false" type="xsd:boolean"> </xsd:element> </xsd:sequence> </xsd:group> If the infoset looked like the following an error would be given, whereas it is valid because the second FPI_false is for Value2: message_prefixedOccurs FPI_false - false FPI_false - false FPI_true - true Value3 - 9999 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

2 3

typographical error
by Mike Beckerle 27 Feb '15

27 Feb '15

Reported by michael.behrens(a)r2ad.com Note: When looking at one of the experience docs, it had a typo in the reference to the spec: https://www.ogf.org/documents/GFD.207.pdf/ <https://exchange10.columbia.tresys.com/owa/redir.aspx?C=17c93eb96d1b4222a0f…> should have been: https://www.ogf.org/documents/GFD.207.pdf <https://exchange10.columbia.tresys.com/owa/redir.aspx?C=17c93eb96d1b4222a0f…> 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

typos found in spec: choiceChoiceBranchKey, and inconsistencies about case sensitivity
by Mike Beckerle 26 Feb '15

26 Feb '15

Steve Lawrence of Tresys found: On 02/25/2015 01:40 PM, Steve Lawrence wrote: > FYI, I noticed a handful of places in the specification that have > dfdl:choiceChoiceBranchKey (with choice repeated twice). > > - Steve > Also, I noticed there seems to be an inconsistencty in whether or not choiceDispatchKey and choiceBranchKey are case insensitive or not. choiceDispatchKey says: The resultant string must match the dfdl:choiceBranchKey property value of one of the branches of the choice. This match is case sensitive. choiceBranchKey says: When the dfdl:choiceDispatchKey expression evaluates to a string matching this property's value, the choice is discriminated to this branch. The match is case insensitive. So choiceDispatch says the match is case sensitive, choiceBranch says the match is case insensitive. 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

OGF DFDL WG Call Minutes 2015-02-24
by Steve Hanson 24 Feb '15

24 Feb '15

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

Confirmed: DFDL Working Group Call (24 Feb 16:00 GMT in IBM Hursley DE3S09)
by Steve Hanson 24 Feb '15

24 Feb '15

Confirmed: DFDL Working Group Call 24/02/2015 - (Repeats) Location: IBM Hursley DE3S09 Steve Hanson has confirmed this meeting Repeats This entry repeats Required: mbeckerle(a)tresys.com, mbeckerle.dfdl(a)gmail.com Optional: Alex Wood1/UK/IBM@IBMGB, Andrew Edwards/UK/IBM@IBMGB, dfdl-wg(a)ogf.org, jorge.marizan(a)gmail.com, Mark Frost/UK/IBM FYI: OGF DFDL WG weekly call dial-in details. Passcode for Participants: 5381214 Canada Toll-Free 888-426-6840 China Toll-Free 10-800-711-1071 CHINA NETCOM GROUP USERS China Toll-Free 10-800-110-0996 CHINA TELECOM SOUTH USERS France Toll-Free 0800-94-0558 Germany Toll-Free 0800-000-1018 India Toll-Free 000-800-100-1176 Ireland Toll-Free 1-800-943-427 Israel Toll-Free 1-809-417-783 United Kingdom Caller Paid 0-20-30596451 United Kingdom Toll-Free 0800-368-0638 USA Caller Paid 215-861-6239 USA Toll-Free 888-426-6840 Other international numbers available - e-mail smh(a)uk.ibm.com. OGF DFDL Home: http://www.ogf.org/dfdl Redmine DFDL: http://redmine.ogf.org/projects/dfdl-wg DFDL Getting Started: http://www.ibm.com/developerworks/library/se-dfdl/ DFDL 1.0 Spec: http://www.ogf.org/documents/GFD.207.pdf

1 0

OGF DFDL WG Call Agenda 2015-02-24
by Steve Hanson 24 Feb '15

24 Feb '15

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

bug: calendarLanguage property can be expression, but does not say no forward references allowed.
by Mike Beckerle 17 Feb '15

17 Feb '15

Every property that can be an expression needs to stipulate "The expression must not contain forward references to elements which have not yet been processed." There are only two exceptions which are for the message of asserts/discriminators. This phrase is missing for calendarLanguage. 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 4

OGF DFDL WG Call 2015-02-17 - cancelled
by Steve Hanson 13 Feb '15

13 Feb '15

Steve not available due to school half-term. Next meeting is 24th. 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

Cancelled: DFDL Working Group Call
by Steve Hanson 13 Feb '15

13 Feb '15

Steve not available

1 0