Corrected call date.

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@uk.ibm.com

----- Forwarded by Alan Powell/UK/IBM on 01/06/2010 17:42 -----

From:	Alan Powell/UK/IBM@IBMGB
To:	dfdl-wg@ogf.org
Date:	01/06/2010 17:42
Subject:	[DFDL-WG] Agenda for OGF DFDL WG call 02 June 2010- 15:00 UK (10:00 ET)

1 Nils, defaults and unparsing
Continue review proposal emailed by Alan

2 OGF 29
Chicago, June 20-22

3 Current Actions

4 Trailing alignment with lengthKind delimited or endOfParent
Is it sensible to allow Trailing skip bytes with LK delimited

The grammar says that trailing alignment is applied before the separator

So the parser must search for the separator then remove the trailing bytes from the value and length.

@Data1 *Data2*# - Test1 value=Data1 length=5

@Data1*Data2*# - Test1 value=Da length=2 (do we require that the trailing data must be the fillByte?)

But bear in mind that the grammar effectively says:

RightFraming = Terminator TrailingSkipBytes

So the combination of dfdl:lengthKind="delimited" & dfdl:trailingSkipBytes would work when the delimiter is a terminator

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
12/05: Work still progressing

084
Check behaviour of dfdl:inputValueCalc and outputValueCalc.
14/04: no prorgess
21/04: no progress
05/05: no progress
26/05: Alan has looked at the precedence tables and the look OK. Suggest closing.

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
15/05: still no public comments

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.
15/05: More discussion. Alan updating sections
26/05: Discussed draft updates. Stephanie to confirm asserts do not make an element required.
Alan will update draft.. All: review rest of draft.

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
15/05: Suman sent an expmle of an imported Cobol ODo which suggested that the maximum space was reserved. He will extend the example.

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
15/05: Alan to talk to Ruth.
26/05: Ruth confirmed that it was only the offset from UTC or GMT. For DFDL purposes thates are the same. Suggest closing.

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@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@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

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 12/05: Work still progressing
084	Check behaviour of dfdl:inputValueCalc and outputValueCalc. 14/04: no prorgess 21/04: no progress 05/05: no progress 26/05: Alan has looked at the precedence tables and the look OK. Suggest closing.
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 15/05: still no public comments
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. 15/05: More discussion. Alan updating sections 26/05: Discussed draft updates. Stephanie to confirm asserts do not make an element required. Alan will update draft.. All: review rest of draft.
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 15/05: Suman sent an expmle of an imported Cobol ODo which suggested that the maximum space was reserved. He will extend the example.
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 15/05: Alan to talk to Ruth. 26/05: Ruth confirmed that it was only the offset from UTC or GMT. For DFDL purposes thates are the same. Suggest closing.