- dfdl-wg - lists.ogf.org

Change of DFDL WG call time
by Alan Powell 11 May '10

11 May '10

Would anyone object if we changed the DFDL WG call to Wednesday at 16:00 UK (11:00 ET) starting this week? A second option is Wednesday 15:00 UK (10:00 ET) Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

Re: [DFDL-WG] dfdl-wg Digest, Vol 45, Issue 3
by Tim Kimber 07 May '10

07 May '10

Not sure whether these items were noted separately, but I don't see them below: - There may be a need to supply a set of rules describing how nils and default values are processed. These rules might be in addition to the tables, or they might replace the tables - it depends on whether the tables look too complex once terminators are added. - It was agreed that the phrase 'default exists for any required children' is not accurate. An element can have a required child without a default value and still be defaultable because there may be another path through its content in which all required elements do have defaults. regards, Tim Kimber, Common Transformation Team, Hursley, UK Internet: kimbert(a)uk.ibm.com Tel. 01962-816742 Internal tel. 246742 From: dfdl-wg-request(a)ogf.org To: dfdl-wg(a)ogf.org Date: 07/05/2010 11:09 Subject: dfdl-wg Digest, Vol 45, Issue 3 Send dfdl-wg mailing list submissions to dfdl-wg(a)ogf.org To subscribe or unsubscribe via the World Wide Web, visit http://www.ogf.org/mailman/listinfo/dfdl-wg or, via email, send a message with subject or body 'help' to dfdl-wg-request(a)ogf.org You can reach the person managing the list at dfdl-wg-owner(a)ogf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dfdl-wg digest..." Today's Topics: 1. Minutes for OGF DFDL Working Group Call, May 05-2010 (Alan Powell) 2. Re: Minutes for OGF DFDL Working Group Call, May 05-2010 - simple infoset item with no value. (Steve Hanson) ----- Message from Alan Powell <alan_powell(a)uk.ibm.com> on Thu, 6 May 2010 18:12:07 +0100 ----- To: dfdl-wg(a)ogf.org Subject: [DFDL-WG] Minutes for OGF DFDL Working Group Call, May 05-2010 Open Grid Forum: Data Format Description Language Working Group OGF DFDL Working Group Call, May 05-2010 Attendees Steve Hanson (IBM) Alan Powell (IBM) Suman Kalia (IBM) Stephanie Fetzer (IBM) Tim Kimber(IBM) Apologies Steve Marting (Progeny) Mike Beckerle (Oco) 1. DFDL Specification status Alan had contacted an automotive standards body (AIAG) to generate interest in getting comments. The request had been forwarded to a number of OMG groups some of whom have at least looked at the specification. He will encourage them to make comments. Steve H had commented on the OMG MDMI site that the DFDL spec was available 2 Nils, defaults and unparsing Alan had distributed tables and examples for defaulting complex elements. Steve H had updated the tables. - emptyValueDelimiterPolicy does apply to complex elements. - on parsing a complex element is empty if its content region is empty. That is there no child delimiters or content. - on unparsing defaulting occurs if a complex item is missing or present present but has no children. Defaulting for complex elements on parsing initiator region content region infoset contains matching Not empty default exists for any missing required children complex element with child elements (real & default values) matching empty default exists for any required children emptyValueDelimiterPolicy must be initiator or both complex element with child elements (real & default values) empty Not empty default exists for any missing required children Initiator must not be specified complex element with child elements (real & default values) empty empty default exists for any required children emptyValueDelimiterPolicy must be none or Initiator must not be specified complex element with child elements (real & default values) Defaulting for complex elements on unparsing infoset contains initiator region contains content region contains not supplied supplied but with no children supplied with some children default exist for all missing required children and final representation of complex element is empty string emptyValueDelimiterPolicy none or Initiator is not specified empty empty emptyValueDelimiterPolicy initiator or both initiator string default values exist for all missing required content and final representation of complex element is not empty string Initiator is not specified initiator string representation of complex element and its children Initiator is not specified empty - The tables need to add terminator which may make them too cluttered - It was agreed that on unparsing a simple infoset item with no value will be treated the same as missing. Steve H to check WMB behaviour. Need to state in 4.1.2 Infoset that value is optional. - Conformed that emptyValueDelimiterPolicy only applies is initiator or terminator is set. - Need to describe defaulting of choices. - Confirmed that a separator is inserted/expected when postfix separator and supressedAtEnd. 3. Current Actions: Updated below 4 AOB The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Tim also questioned the teston/off functions. Alan stated that setting bits in a array was not possible. Will look at ISO8583 to see if needed. Meeting closed, 14:10 Next call Wednesday 12 May 2010 13:00 UK (8:00 ET) Next action: 092 Actions raised at this meeting No Action 091 The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 05/05: Work still progressing 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 21/04: no progress 05/05: no progress 085 ALL: publicize Public comments phase to ensure a good review.. 14/04: see minutes 21/04: Press release, OMG and other standards bodies. 05/05: Alan and Steve H have contacted other standards bodies. Will ask them to add comments on spec 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 14/04: Investigate new property to control empty string behaviour. 21/04: After investigation a new property is not required. New rules developed and tables updated. Need examples of complexTypes to confirm tables apply. Review Nils, defaulting spec section. 05/05: Discussed defaulting complex elements. Tables updated but need to add terminator. SH; to confirm WMD behaviour when infoset item has no value on unparsing Need to describe defaulting choices. 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 14/04Tim had distributed a document starting the definition of calculable length for the longest choice member. Alan had done some investigation of COBOL occurs depending on and when used in the working section of a program then the maximum storage was reserved but when used in the linkage section the dependent number was uses. We need to understand how the WMB COBOL importer deals with ODO. 21/04: Need to define 'calculable length' and WMB importer ODO behaviour. 05/05: TK: Still need definition of calculable length. SKK: WMB COBOL imported behaviour with ODO 091 The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Closed actions No Action 090 Semantics of separatorPolicy 14/04: Discussion on detecting when complex types should be defaulted. Examples needed. 21/04: Complex defaulting examples needed for new rules 05/05: Subsumed into action 086 defaults. CLOSED Work items: No Item target version status 005 Improvements on property descriptions not started 012 Reordering the properties discussion: move representation earlier, improve flow of topics not started 036 Update dfdl schema with change properties ongoing 042 Mapping of the DFDL infoset to XDM none not required for V1 specification 070 Write DFDL primer 071 Write test cases. 083 Implement RFC2116 097 Remove functions that returns duration 098 occursCountKind is parsing only 099 nilValue and OccuresStopValue cannot have an expression. On unparsing only outputValueCalc can have a forward reference. 100 Need to state in 4.1.2 Infoset that value is optional. Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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 ----- Message from Steve Hanson <smh(a)uk.ibm.com> on Fri, 7 May 2010 11:08:35 +0100 ----- To: Alan Powell <alan_powell(a)uk.ibm.com> cc: dfdl-wg(a)ogf.org Subject: Re: [DFDL-WG] Minutes for OGF DFDL Working Group Call, May 05-2010 - simple infoset item with no value. Alan "- It was agreed that on unparsing a simple infoset item with no value will be treated the same as missing. Steve H to check WMB behaviour. Need to state in 4.1.2 Infoset that value is optional. " Something to note. We say that for a simple element infoset item [dataValue] has a value (either type compliant or nil) and for a complex element infoset item [dataValue] has 'no value'. Also we say that for a simple element infoset item [children] has 'no value' and for a complex element infoset item [children] it may have a value (so it could also have 'no value'). The implication therefore is that an element infoset item is deduced to be simple or complex based on the [dataValue] property. If we let a simple item take 'no value' for [dataValue] as proposed, then there is no reliable way to identify an element infoset item as simple or complex. Is that a problem in practice? After parsing, all simple items will have [dataValue] set. For items created by some other means, and presumably destined for unparsing, you could have an item with neither [dataValue] nor [children] set. We could say (1) that an element infoset item is known to be simple or complex only when it is processed by the unparser, at which point the item is matched to the DFDL schema and its type resolved. This is what broker's MRM parser does. Alternatively (2) we introduce a simple/complex flag. Note that I tried creating an MRM 'infoset' item for a string element but just gave a name and no value. The MRM serializer looked at the element, matched it to its model, found it was simple, and treated the value as NULL which invoked null processing. The XML serializer also assumed NULL. Personally I think we should adopt (1) but interpret 'no value' for a simple item as nil and not missing. Regards Steve Hanson Strategy, Common Transformation & DFDL Co-Chair, OGF DFDL WG IBM SWG, Hursley, UK, smh(a)uk.ibm.com, tel +44-(0)1962-815848 From: Alan Powell/UK/IBM@IBMGB To: dfdl-wg(a)ogf.org Date: 06/05/2010 18:12 Subject: [DFDL-WG] Minutes for OGF DFDL Working Group Call, May 05-2010 Sent by: dfdl-wg-bounces(a)ogf.org Open Grid Forum: Data Format Description Language Working Group OGF DFDL Working Group Call, May 05-2010 Attendees Steve Hanson (IBM) Alan Powell (IBM) Suman Kalia (IBM) Stephanie Fetzer (IBM) Tim Kimber(IBM) Apologies Steve Marting (Progeny) Mike Beckerle (Oco) 1. DFDL Specification status Alan had contacted an automotive standards body (AIAG) to generate interest in getting comments. The request had been forwarded to a number of OMG groups some of whom have at least looked at the specification. He will encourage them to make comments. Steve H had commented on the OMG MDMI site that the DFDL spec was available 2 Nils, defaults and unparsing Alan had distributed tables and examples for defaulting complex elements. Steve H had updated the tables. - emptyValueDelimiterPolicy does apply to complex elements. - on parsing a complex element is empty if its content region is empty. That is there no child delimiters or content. - on unparsing defaulting occurs if a complex item is missing or present present but has no children. Defaulting for complex elements on parsing initiator region content region infoset contains matching Not empty default exists for any missing required children complex element with child elements (real & default values) matching empty default exists for any required children emptyValueDelimiterPolicy must be initiator or both complex element with child elements (real & default values) empty Not empty default exists for any missing required children Initiator must not be specified complex element with child elements (real & default values) empty empty default exists for any required children emptyValueDelimiterPolicy must be none or Initiator must not be specified complex element with child elements (real & default values) Defaulting for complex elements on unparsing infoset contains initiator region contains content region contains not supplied supplied but with no children supplied with some children default exist for all missing required children and final representation of complex element is empty string emptyValueDelimiterPolicy none or Initiator is not specified empty empty emptyValueDelimiterPolicy initiator or both initiator string default values exist for all missing required content and final representation of complex element is not empty string Initiator is not specified initiator string representation of complex element and its children Initiator is not specified empty - The tables need to add terminator which may make them too cluttered - It was agreed that on unparsing a simple infoset item with no value will be treated the same as missing. Steve H to check WMB behaviour. Need to state in 4.1.2 Infoset that value is optional. - Conformed that emptyValueDelimiterPolicy only applies is initiator or terminator is set. - Need to describe defaulting of choices. - Confirmed that a separator is inserted/expected when postfix separator and supressedAtEnd. 3. Current Actions: Updated below 4 AOB The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Tim also questioned the teston/off functions. Alan stated that setting bits in a array was not possible. Will look at ISO8583 to see if needed. Meeting closed, 14:10 Next call Wednesday 12 May 2010 13:00 UK (8:00 ET) Next action: 092 Actions raised at this meeting No Action 091 The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 05/05: Work still progressing 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 21/04: no progress 05/05: no progress 085 ALL: publicize Public comments phase to ensure a good review.. 14/04: see minutes 21/04: Press release, OMG and other standards bodies. 05/05: Alan and Steve H have contacted other standards bodies. Will ask them to add comments on spec 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 14/04: Investigate new property to control empty string behaviour. 21/04: After investigation a new property is not required. New rules developed and tables updated. Need examples of complexTypes to confirm tables apply. Review Nils, defaulting spec section. 05/05: Discussed defaulting complex elements. Tables updated but need to add terminator. SH; to confirm WMD behaviour when infoset item has no value on unparsing Need to describe defaulting choices. 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 14/04Tim had distributed a document starting the definition of calculable length for the longest choice member. Alan had done some investigation of COBOL occurs depending on and when used in the working section of a program then the maximum storage was reserved but when used in the linkage section the dependent number was uses. We need to understand how the WMB COBOL importer deals with ODO. 21/04: Need to define 'calculable length' and WMB importer ODO behaviour. 05/05: TK: Still need definition of calculable length. SKK: WMB COBOL imported behaviour with ODO 091 The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Closed actions No Action 090 Semantics of separatorPolicy 14/04: Discussion on detecting when complex types should be defaulted. Examples needed. 21/04: Complex defaulting examples needed for new rules 05/05: Subsumed into action 086 defaults. CLOSED Work items: No Item target version status 005 Improvements on property descriptions not started 012 Reordering the properties discussion: move representation earlier, improve flow of topics not started 036 Update dfdl schema with change properties ongoing 042 Mapping of the DFDL infoset to XDM none not required for V1 specification 070 Write DFDL primer 071 Write test cases. 083 Implement RFC2116 097 Remove functions that returns duration 098 occursCountKind is parsing only 099 nilValue and OccuresStopValue cannot have an expression. On unparsing only outputValueCalc can have a forward reference. 100 Need to state in 4.1.2 Infoset that value is optional. Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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 http://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 http://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

1 0

Minutes for OGF DFDL Working Group Call, May 05-2010
by Alan Powell 07 May '10

07 May '10

Open Grid Forum: Data Format Description Language Working Group OGF DFDL Working Group Call, May 05-2010 Attendees Steve Hanson (IBM) Alan Powell (IBM) Suman Kalia (IBM) Stephanie Fetzer (IBM) Tim Kimber(IBM) Apologies Steve Marting (Progeny) Mike Beckerle (Oco) 1. DFDL Specification status Alan had contacted an automotive standards body (AIAG) to generate interest in getting comments. The request had been forwarded to a number of OMG groups some of whom have at least looked at the specification. He will encourage them to make comments. Steve H had commented on the OMG MDMI site that the DFDL spec was available 2 Nils, defaults and unparsing Alan had distributed tables and examples for defaulting complex elements. Steve H had updated the tables. - emptyValueDelimiterPolicy does apply to complex elements. - on parsing a complex element is empty if its content region is empty. That is there no child delimiters or content. - on unparsing defaulting occurs if a complex item is missing or present present but has no children. Defaulting for complex elements on parsing initiator region content region infoset contains matching Not empty default exists for any missing required children complex element with child elements (real & default values) matching empty default exists for any required children emptyValueDelimiterPolicy must be initiator or both complex element with child elements (real & default values) empty Not empty default exists for any missing required children Initiator must not be specified complex element with child elements (real & default values) empty empty default exists for any required children emptyValueDelimiterPolicy must be none or Initiator must not be specified complex element with child elements (real & default values) Defaulting for complex elements on unparsing infoset contains initiator region contains content region contains not supplied supplied but with no children supplied with some children default exist for all missing required children and final representation of complex element is empty string emptyValueDelimiterPolicy none or Initiator is not specified empty empty emptyValueDelimiterPolicy initiator or both initiator string default values exist for all missing required content and final representation of complex element is not empty string Initiator is not specified initiator string representation of complex element and its children Initiator is not specified empty - The tables need to add terminator which may make them too cluttered - It was agreed that on unparsing a simple infoset item with no value will be treated the same as missing. Steve H to check WMB behaviour. Need to state in 4.1.2 Infoset that value is optional. - Conformed that emptyValueDelimiterPolicy only applies is initiator or terminator is set. - Need to describe defaulting of choices. - Confirmed that a separator is inserted/expected when postfix separator and supressedAtEnd. 3. Current Actions: Updated below 4 AOB The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Tim also questioned the teston/off functions. Alan stated that setting bits in a array was not possible. Will look at ISO8583 to see if needed. Meeting closed, 14:10 Next call Wednesday 12 May 2010 13:00 UK (8:00 ET) Next action: 092 Actions raised at this meeting No Action 091 The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 05/05: Work still progressing 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 21/04: no progress 05/05: no progress 085 ALL: publicize Public comments phase to ensure a good review.. 14/04: see minutes 21/04: Press release, OMG and other standards bodies. 05/05: Alan and Steve H have contacted other standards bodies. Will ask them to add comments on spec 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 14/04: Investigate new property to control empty string behaviour. 21/04: After investigation a new property is not required. New rules developed and tables updated. Need examples of complexTypes to confirm tables apply. Review Nils, defaulting spec section. 05/05: Discussed defaulting complex elements. Tables updated but need to add terminator. SH; to confirm WMD behaviour when infoset item has no value on unparsing Need to describe defaulting choices. 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 14/04Tim had distributed a document starting the definition of calculable length for the longest choice member. Alan had done some investigation of COBOL occurs depending on and when used in the working section of a program then the maximum storage was reserved but when used in the linkage section the dependent number was uses. We need to understand how the WMB COBOL importer deals with ODO. 21/04: Need to define 'calculable length' and WMB importer ODO behaviour. 05/05: TK: Still need definition of calculable length. SKK: WMB COBOL imported behaviour with ODO 091 The IBM team had questioned whether timezones should be just UTC+/- offset or should GMT and other short time zones be allowed. Alan to investigate Closed actions No Action 090 Semantics of separatorPolicy 14/04: Discussion on detecting when complex types should be defaulted. Examples needed. 21/04: Complex defaulting examples needed for new rules 05/05: Subsumed into action 086 defaults. CLOSED Work items: No Item target version status 005 Improvements on property descriptions not started 012 Reordering the properties discussion: move representation earlier, improve flow of topics not started 036 Update dfdl schema with change properties ongoing 042 Mapping of the DFDL infoset to XDM none not required for V1 specification 070 Write DFDL primer 071 Write test cases. 083 Implement RFC2116 097 Remove functions that returns duration 098 occursCountKind is parsing only 099 nilValue and OccuresStopValue cannot have an expression. On unparsing only outputValueCalc can have a forward reference. 100 Need to state in 4.1.2 Infoset that value is optional. Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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 1

Action 086: Nils and Defaults for complex elements
by Alan Powell 05 May '10

05 May '10

Part of Action 086 is to apply the clarified Nils and Defaulting rules to complex elements and develop some examples. The tables for parsing and unparsing are simpler because there is no need to consider nillable. I have assumed - emptyValueDelimiterPolicy does apply to complex elements. - on parsing a complex element is empty if its children's content is empty. That is the child delimiters may be present. - on unparsing defaulting occurs if a complex item is missing or present present but has no children. Defaulting for complex elements on parsing initiator region content region Logical Value matching Not empty parsed children matching empty A default is specified emptyValueDelimiterPolicy must be initiator or both default value of children empty Not empty Initiator must not be specified parsed children empty empty A default is specified emptyValueDelimiterPolicy must be none or Initiator must not be specified default value of children Defaulting for complex elements on unparsing Logical Value initiator region contains content region contains Missing or present with no children default of all children is empty string emptyValueDelimiterPolicy none empty empty emptyValueDelimiterPolicy initiator or both initiator string default of any child is not empty string initiator string representation of the child default value. a least on child exists initiator string representation of children Examples Defaulting Complex types ONE:one, TWO: TWOONE:twoone; TWOTWO:twotwo; TWOTHREE:twothree, THREE:three <end> In the following TWO is 'empty' (when relevant dfdl properties are set) ONE:one,THREE:three<end> |separatorPolicy='suppressed', emptyValueDelimiterPolicy='none' ONE:one,,THREE:three<end> separatorPolicy='required', emptyValueDelimiterPolicy='none' ONE:one<end> separatorPolicy='suppressed' or 'suppressedAtEnd', emptyValueDelimiterPolicy='none' <end> separatorPolicy='suppressed' or 'suppressedAtEnd', emptyValueDelimiterPolicy='none' ONE:one,TWO:,THREE:three<end> separatorPolicy= don't care , emptyValueDelimiterPolicy='initiator' ONE:one,TWO:<end> separatorPolicy= 'suppressed' or 'suppressedAtEnd', emptyValueDelimiterPolicy='initiator' ONE:one,TWO:,<end> separatorPosition='postfix' separatorPolicy= 'suppressed' or 'suppressedAtEnd', emptyValueDelimiterPolicy='initiator' *** Should 'postfix' separator be there when 'supressedAtEnd' *** ONE:one,TWO:TWOONE:,THREE:three<end> separatorPolicy= 'suppressed' or 'suppressedAtEnd', (TWO)emptyValueDelimiterPolicy='initiator' (TWOONE)emptyValueDelimiterPolicy='initiator' ONE:one,TWOONE:,THREE:three<end> separatorPolicy= 'suppressed' or 'suppressedAtEnd', (TWO)emptyValueDelimiterPolicy='none' (TWOONE)emptyValueDelimiterPolicy='initiator' *** We should discuss this example. *** Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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 2

Agenda for OGF DFDL WG call 05 May 2010- 13:00 UK (8:00 ET)
by Alan Powell 04 May '10

04 May '10

1. DFDL Specification status 2 Nils, defaults and unparsing Confirm tables for parsing/unparsing simple types in last call minutes. 2.1 Nils and Defaults for complex elements I have assumed - emptyValueDelimiterPolicy does apply to complex elements. - on parsing a complex element is empty if its children's content is empty. That is the child delimiters may be present. - on unparsing defaulting occurs if a complex item is missing or present present but has no children. Defaulting for complex elements on parsing initiator region content region Logical Value matching Not empty parsed children matching empty A default is specified emptyValueDelimiterPolicy must be initiator or both default value of children empty Not empty Initiator must not be specified parsed children empty empty A default is specified emptyValueDelimiterPolicy must be none or Initiator must not be specified default value of children Defaulting for complex elements on unparsing Logical Value initiator region contains content region contains Missing or present with no children default of all children is empty string emptyValueDelimiterPolicy none empty empty emptyValueDelimiterPolicy initiator or both initiator string default of any child is not empty string initiator string representation of the child default value. a least on child exists initiator string representation of children Examples Defaulting Complex types ONE:one, TWO: TWOONE:twoone; TWOTWO:twotwo; TWOTHREE:twothree, THREE:three <end> In the following TWO is 'empty' (when relevant dfdl properties are set) ONE:one,THREE:three<end> |separatorPolicy='suppressed', emptyValueDelimiterPolicy='none' ONE:one,,THREE:three<end> separatorPolicy='required', emptyValueDelimiterPolicy='none' ONE:one<end> separatorPolicy='suppressed' or 'suppressedAtEnd', emptyValueDelimiterPolicy='none' <end> separatorPolicy='suppressed' or 'suppressedAtEnd', emptyValueDelimiterPolicy='none' ONE:one,TWO:,THREE:three<end> separatorPolicy= don't care , emptyValueDelimiterPolicy='initiator' ONE:one,TWO:<end> separatorPolicy= 'suppressed' or 'suppressedAtEnd', emptyValueDelimiterPolicy='initiator' ONE:one,TWO:,<end> separatorPosition='postfix' separatorPolicy= 'suppressed' or 'suppressedAtEnd', emptyValueDelimiterPolicy='initiator' *** Should 'postfix' separator be there when 'supressedAtEnd' *** ONE:one,TWO:TWOONE:,THREE:three<end> separatorPolicy= 'suppressed' or 'suppressedAtEnd', (TWO)emptyValueDelimiterPolicy='initiator' (TWOONE)emptyValueDelimiterPolicy='initiator' ONE:one,TWOONE:,THREE:three<end> separatorPolicy= 'suppressed' or 'suppressedAtEnd', (TWO)emptyValueDelimiterPolicy='none' (TWOONE)emptyValueDelimiterPolicy='initiator' *** We should discuss this example. *** 3. Current Actions: Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 21/04: no progress 085 ALL: publicize Public comments phase to ensure a good review.. 14/04: see minutes 21/04: Press release, OMG and other standards bodies. 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 14/04: Investigate new property to control empty string behaviour. 21/04: After investigation a new property is not required. New rules developed and tables updated. Need examples of complexTypes to confirm tables apply. Review Nils, defaulting spec section. 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 14/04Tim had distributed a document starting the definition of calculable length for the longest choice member. Alan had done some investigation of COBOL occurs depending on and when used in the working section of a program then the maximum storage was reserved but when used in the linkage section the dependent number was uses. We need to understand how the WMB COBOL importer deals with ODO. 21/04: Need to define 'calculable length' and WMB importer ODO behaviour. 090 Semantics of separatorPolicy 14/04: Discussion on detecting when complex types should be defaulted. Examples needed. 21/04: Complex defaulting examples needed for new rules Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

Cancelled: OGF DFDL Working Group weekly call
by Steve Hanson 28 Apr '10

28 Apr '10

Cancelled: OGF DFDL Working Group weekly call 28/04/2010 - (Repeats) Chair: Steve Hanson/UK/IBM Sent By: Steve_Hanson/UK/IBM%IBMGB Location: Participant Passcode: 8190865 Country Toll Numbers Freephone/Toll Free Number AUSTRIA 43-1-928-9652 BELGIUM 32-2-400-6791 0800-4-9612 DENMARK 45-7014-0237 FRANCE LYON: 33-4-26-69-12-74 080-511-3725 FRANCE MARSEILLE: 33-4-86-06-00-74 080-511-3725 FRANCE PARIS: 33-1-70-70-81-58 080-511-3725 GERMANY 49-69-2222-20363 0800-100-6504 IRELAND 353-1-247-7768 ITALY 39-02-3600-3648 800-985-679 LUXEMBOURG 352-27-000-1312 NETHERLANDS 31-20-713-2741 0800-020-3237 SPAIN 34-91-414-1542 800-099-667 SWEDEN 46-8-566-10-780 SWITZERLAND 41-44-580-3334 0800-000-516 UNITED KINGDOM BIRMINGHAM: 44-121-210-9014 0800-279-9193 UNITED KINGDOM GLASGOW: 44-141-202-3214 0800-279-9193 UNITED KINGDOM LEEDS: 44-113-301-2114 0800-279-9193 UNITED KINGDOM LONDON: 44-20-7019-0808 0800-279-9193 UNITED KINGDOM MANCHESTER: 44-161-601-1414 0800-279-9193 USA 866-505-4412 Steve_Hanson Steve Hanson has cancelled this meeting. Your calendar will be updated to reflect this change. Repeats This entry repeats Required: Akmal Chaudhri, Alan Powell/UK/IBM@IBMGB, mbeckerle.dfdl(a)gmail.com, Stephanie Fetzer/Charlotte/IBM@IBMUS, steve.marting(a)progeny.net, Suman Kalia/Toronto/IBM@IBMCA, Tim Kimber/UK/IBM@IBMGB Optional: alejandr(a)ncsa.illinois.edu, dfdl-wg(a)ogf.org, gary.sikora(a)progeny.net

1 0

OGF DFDL WG call 28 April 20 - Cancelled
by Alan Powell 27 Apr '10

27 Apr '10

All Steve H, Tim and I will not be available for the call so we have cancelled for this week. Please send me any updates to current actions Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 21/04: no progress 085 ALL: publicize Public comments phase to ensure a good review.. 14/04: see minutes 21/04: Press release, OMG and other standards bodies. 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 14/04: Investigate new property to control empty string behaviour. 21/04: After investigation a new property is not required. New rules developed and tables updated. Need examples of complexTypes to confirm tables apply. Review Nils, defaulting spec section. 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 14/04Tim had distributed a document starting the definition of calculable length for the longest choice member. Alan had done some investigation of COBOL occurs depending on and when used in the working section of a program then the maximum storage was reserved but when used in the linkage section the dependent number was uses. We need to understand how the WMB COBOL importer deals with ODO. 21/04: Need to define 'calculable length' and WMB importer ODO behaviour. 090 Semantics of separatorPolicy 14/04: Discussion on detecting when complex types should be defaulted. Examples needed. 21/04: Complex defaulting examples needed for new rules Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

Minutes for OGF DFDL Working Group Call, April 21-2010
by Alan Powell 22 Apr '10

22 Apr '10

Open Grid Forum: Data Format Description Language Working Group OGF DFDL Working Group Call, April 21-2010 Attendees Steve Hanson (IBM) Alan Powell (IBM) Mike Beckerle (Oco) Stephanie Fetzer (IBM) Tim Kimber(IBM) Apologies Steve Marting (Progeny) Suman Kalia (IBM) 1. DFDL Specification status There have been no public comments so far but this is not unexpected. Steve H is pursuing a press release from IBM and OCO. Mike will send updated information to the OMG. Alan will pursue contacts from the Athena EU project. 2 Nils, defaults and unparsing Steve H, Tim and Alan have had further discussions and concluded and new property was not required so propose - Elements that are zero length and elements that are 'missing' from the data stream should be treated the same. - missingValueInitiatorPolicy should be renamed to emptyValueInitiatorPolicy to distinguish from a missing infoset value on unparsing - Any 'initiator' policy needs to also include terminators so the enumerations should be extended to "none", "initiator", "terminator", "both". and the properties renamed emptyValueDelimiterPolicy and nilValueDelimiterPolicy . The tables have been reworked Nils and Defaults on Parsing initiator region content region Logical Value matching content content matches nilValue nilValueDelimiterPolicy must be initiator or both nil Content does not match nilValue parse content to get value matching empty empty string is a nil value nilValueDelimiterPolicy must be initiator or both nil A default is specified emptyValueDelimiterPolicy must be initiator or both default value (may be nil, empty space or value) empty content content matches nilValue nilValueDelimiterPolicy must be none nil Content does not match nilValue Initiator must not be specified parse content to get value Initiator is specified ERROR empty empty empty string is a nil value nilValueDelimiterPolicy must be none nil A default is specified emptyValueDelimiterPolicy must be none default value (may be nil, empty space or value) Note. The default value can be the empty space. Nils and Defaults on Unparsing Logical Value initiator region contains content region contains Nil (implies nillable) nilValueDelimiterPolicy none empty representation of nil nilValueDelimiterPolicy initiator or both initiator string "" (empty string) (type is xs:string or xs:hexBinary) emptyValueDelimiterPolicy none empty empty emptyValueDelimiterPolicy initiator or both initiator string missing useNilForDefault nilValueDelimiterPolicy none empty representation of nil nilValueDelimiterPolicy initiator or both initiator string default is empty string (type is xs:string or xs:hexBinary) emptyValueDelimiterPolicy none empty empty emptyValueDelimiterPolicy initiator or both initiator string Other default initiator string representation of the default value. a non-nil non-empty-string value initiator string representation of the logical value The above tables (with minor changes) were agreed. The tables currently apply to simpleTypes, examples are needed to confirm that they are correct for complexTypes as well. Steve questioned whether complexTypes can be nillable as WTX allow this. Stephanie will investigate. Subsequently Stephanie confirmed that this was only needed for XML support in WTX so is not needed in DFDL. The Nils, defaulting section in the spec will be reviewed/rewritten to incorporate the new understanding. 3. Current Actions: Updated below. 4 Expressions during Unparsing. In order to reduce complexity and potential performance problems it is proposed to - nilValue and occursStopValue should NOT be able to take an expression. Agreed - Very few properties should be allowed to have forward references. Table below agreed Here's the list of properties that can take an expression, along with some suggested restrictions on forward referencing: byteOrder backward reference only encoding backward reference only initiator backward reference only terminator backward reference only separator backward reference only outputNewline backward reference only length simple elements : backward reference only. complex elements : forward reference allowed Quote "When unparsing with dfdl:lengthKind="explicit", the calculation of dfdl:representationLength() returns the value of the dfdl:length property." A simple element's length needs to be known in advance, else it cannot be parsed. A complex element's length might get resolved while parsing its content, so a forward reference within the scope of the complex element is possible. Having said that, we might want to impose a restriction in IBM's DFDL processor v1.0 that only backward references are allowed. escapeCharacter backward reference only escapeEscapeCharacter backward reference only textNumberDecimalSeparator backward reference only textNumberGroupSeparator backward reference only textNumberExponentCharacter backward reference only binaryFloatRep backward reference only textBooleanTrueRep backward reference only textBooleanFalseRep backward reference only nilValue backward reference only Not clear why this needs to be specified as an expression. ( may already be on a list of open issues somewhere ) nilIndicatorPath backward reference only occursCount backward reference only occursStopValue Not clear why this needs to be specified as an expression. [inputValueCalc] [Parser only] Backward reference only outputValueCalc Forward or backward reference Meeting closed, 14:10 Next call Wednesday 28 April January 2010 13:00 UK (8:00 ET) Next action: 091 Actions raised at this meeting No Action Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 21/04: no progress 085 ALL: publicize Public comments phase to ensure a good review.. 14/04: see minutes 21/04: Press release, OMG and other standards bodies. 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 14/04: Investigate new property to control empty string behaviour. 21/04: After investigation a new property is not required. New rules developed and tables updated. Need examples of complexTypes to confirm tables apply. Review Nils, defaulting spec section. 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 14/04Tim had distributed a document starting the definition of calculable length for the longest choice member. Alan had done some investigation of COBOL occurs depending on and when used in the working section of a program then the maximum storage was reserved but when used in the linkage section the dependent number was uses. We need to understand how the WMB COBOL importer deals with ODO. 21/04: Need to define 'calculable length' and WMB importer ODO behaviour. 089 Need to be able to define unsigned decimal and integer 31/03: MB to agree proposed solution 14/04: MB to agree proposed solution 21/04: Agreed. Closed 090 Semantics of separatorPolicy 14/04: Discussion on detecting when complex types should be defaulted. Examples needed. 21/04: Complex defaulting examples needed for new rules Closed actions No Action Work items: No Item target version status 005 Improvements on property descriptions not started 012 Reordering the properties discussion: move representation earlier, improve flow of topics not started 036 Update dfdl schema with change properties ongoing 042 Mapping of the DFDL infoset to XDM none not required for V1 specification 070 Write DFDL primer 071 Write test cases. 083 Implement RFC2116 097 Remove functions that returns duration 098 occursCountKind is parsing only 099 nilValue and OccuresStopValue cannot have an expression. On unparsing only outputValueCalc can have a forward reference. Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

Agenda for OGF DFDL WG call 21 April 2010- 13:00 UK (8:00 ET)
by Alan Powell 20 Apr '10

20 Apr '10

1. DFDL Specification status 2 Nils, defaults and unparsing 3. Current Actions: 4 Expressions during Unparsing. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1. DFDL Specification status 2 Nils, defaults and unparsing Steve H, Tim and Alan have had further discussions and concluded and new property was not required so propose - Elements that are zero length and elements that are 'missing' from the data stream should be treated the same. - missingValueInitiatorPolicy should be renamed to emptyValueInitiatorPolicy to distinguish from a missing infoset value on unparsing - Any 'initiator' policy needs to also include terminators so the enumerations should be extended to "none", "initiator", "terminator", "both". and the properties renamed emptyValueDelimiterPolicy and nilValueDelimiterPolicy . The tables have been reworked Nils and Defaults on Parsing initiator region content region Logical Value matching content content matches nilValue nilValueDelimiterPolicy must be initiator or both nil Content does not match nilValue parse content to get value matching empty empty string is a nil value nilValueDelimiterPolicy must be initiator or both nil A default is specified emptyValueDelimiterPolicy must be initiator or both default value (may be nil, empty space or value) empty content content matches nilValue nilValueDelimiterPolicy must be none nil content does not match nilValue Initiator is not specified parse content to get value Initiator is specified ERROR empty empty empty string is a nil value nilValueDelimiterPolicy must be none nil A default is specified emptyValueDelimiterPolicy must be none default value (may be nil, empty space or value) Nils and Defaults on Unparsing Logical Value initiator region contains content region contains Nil (implies nillable) nilValueDelimiterPolicy none empty representation of nil nilValueDelimiterPolicy initiator or both initiator string "" (empty string) (type is xs:string or xs:hexBinary) emptyValueDelimiterPolicy none empty empty emptyValueDelimiterPolicy initiator or both initiator string missing useNilForDefault nilValueDelimiterPolicy none empty representation of nil nilValueDelimiterPolicy initiator or both initiator string default is empty string (type is xs:string or xs:hexBinary) emptyValueDelimiterPolicy none empty empty emptyValueDelimiterPolicy initiator or both initiator string Other default initiator string representation of the default value. a non-nil non-empty-string value initiator string representation of the logical value 3. Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 085 ALL: publicize Public comments phase to ensure a good review.. 14/04: see minutes 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 14/04: Investigate new property to control empty string behaviour. 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 14/04Tim had distributed a document starting the definition of calculable length for the longest choice member. Alan had done some investigation of COBOL occurs depending on and when used in the working section of a program then the maximum storage was reserved but when used in the linkage section the dependent number was uses. We need to understand how the WMB COBOL importer deals with ODO. 089 Need to be able to define unsigned decimal and integer 31/03: MB to agree proposed solution 14/04: MB to agree proposed solution 090 Semantics of separatorPolicy 14/04: Discussion on detecting when complex types should be defaulted. Examples needed. 4 Expressions during Unparsing. In order to reduce complexity and potential performance problems it is proposed to - nilValue and occursStopValue should NOT be able to take an expression. - Very few properties should be allowed to have forward references. Here's the list of properties that can take an expression, along with some suggested restrictions on forward referencing: byteOrder backward reference only encoding backward reference only initiator backward reference only terminator backward reference only separator backward reference only outputNewline backward reference only length simple elements : backward reference only. complex elements : forward reference allowed Quote "When unparsing with dfdl:lengthKind="explicit", the calculation of dfdl:representationLength() returns the value of the dfdl:length property." A simple element's length needs to be known in advance, else it cannot be parsed. A complex element's length might get resolved while parsing its content, so a forward reference within the scope of the complex element is possible. Having said that, we might want to impose a restriction in IBM's DFDL processor v1.0 that only backward references are allowed. escapeCharacter backward reference only escapeEscapeCharacter backward reference only textNumberDecimalSeparator backward reference only textNumberGroupSeparator backward reference only textNumberExponentCharacter backward reference only binaryFloatRep backward reference only textBooleanTrueRep backward reference only textBooleanFalseRep backward reference only nilValue backward reference only Not clear why this needs to be specified as an expression. ( may already be on a list of open issues somewhere ) nilIndicatorPath backward reference only occursCount backward reference only occursStopValue Not clear why this needs to be specified as an expression. [inputValueCalc] [Parser only] Backward reference only outputValueCalc Forward or backward reference Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

Minutes for OGF DFDL Working Group Call, April 14-2010
by Alan Powell 15 Apr '10

15 Apr '10

Open Grid Forum: Data Format Description Language Working Group OGF DFDL Working Group Call, April 14-2010 Attendees Steve Hanson (IBM) Alan Powell (IBM) Steve Marting (Progeny) Stephanie Fetzer (IBM) Suman Kalia (IBM) Tim Kimber(IBM) Apologies Mike Beckerle (Oco) 1. DFDL Specification status After a slight delay the DFDL v1 Specification was opened to public comment on April 15th until June 15th. There was some discussion about publicizing the review. Steve H mentioned he started the process for getting approval for IBM to be included in a press release. Steve M indicated that Progeny may also be willing. Steve M mentioned that Progeny were working on an OMG mediation framework that requires DFDL and theat Progeny will have at least a partial implementation of DFDL that may satisfy the OGF requirement. 2 Nils, defaults and unparsing Tim had distributed some uses cases of fixed and delimited formats with initiated and non-initaited element. The was considerable discussion of the initiated, delimited cases ONE:one,THREE:three<END> ONE:one,,THREE:three<END> The discussion was mainly about whether was any difference in intent between missing and zero length in these examples and whether zero length string or default should be inserted into the infoset, Tim suggested using separatorPolicy required as a trigger. Alan pointed out that the table in the spec used the presence or absence of a default value to decide is the default or empty string should be the result. Eventually concluded that an additional property may be needed and a proposal will be developed. In addition it was noted that the interaction between dfdl:initiatedContent and dfdl:missingValueInitiatorPoilcy may need clarifying. It was also question whether XSDL allows the empty space to be specified as a default value. 3 dfdl:separatorPoilicy. The main discussion was about how to detect when complex types should be defaulted which was similar to the defaulting discussion for simpleTypes. The added complication for complex types is that the content region is the children so should you detect missing by parsing the first child? It was agreed that examples simpler to the ones above would be helpful. Meeting closed, 14:45 Next call Wednesday 21 April January 2010 13:00 UK (8:00 ET) Next action: 091 Actions raised at this meeting No Action Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 085 ALL: publicize Public comments phase to ensure a good review.. 14/04: see minutes 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 14/04: Investigate new property to control empty string behaviour. 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 14/04Tim had distributed a document starting the definition of calculable length for the longest choice member. Alan had done some investigation of COBOL occurs depending on and when used in the working section of a program then the maximum storage was reserved but when used in the linkage section the dependent number was uses. We need to understand how the WMB COBOL importer deals with ODO. 089 Need to be able to define unsigned decimal and integer 31/03: MB to agree proposed solution 14/04: MB to agree proposed solution 090 Semantics of separatorPolicy 14/04: Discussion on detecting when complex types should be defaulted. Examples needed. Closed actions No Action Work items: No Item target version status 005 Improvements on property descriptions not started 012 Reordering the properties discussion: move representation earlier, improve flow of topics not started 036 Update dfdl schema with change properties ongoing 042 Mapping of the DFDL infoset to XDM none not required for V1 specification 070 Write DFDL primer 071 Write test cases. 083 Implement RFC2116 097 Remove functions that returns duration 098 occursCountKind is parsing only Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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