- dfdl-wg - lists.ogf.org

Action 088 - define semantics of choiceKind 'fixedLength'
by Tim Kimber 14 Apr '10

14 Apr '10

More work to do on this, but no time before the meeting. Let's discuss the rules below, and refine afterwards: If dfdl:choiceKind='fixedLength' then there must be at least one branch of the choice for which all of the content has a calculable length. Definition : A DFDL region is a region of the data stream described by the DFDL grammar. Note : we need to define this term - we use the term 'region' without definition throughout the specification. Sometimes we call it a 'grammar region'. Definition: A DFDL region has a calculable length if the length of its representation in units of bytes can be calculated from the DFDL description alone. The leading alignment region has a calculable length if the alignment of the component is the same as the alignment of the parent. The trailing alignment region has a calculable length if the alignment of the component is the same as the alignment of the parent. Q: Is this rule necessary? The initiator region has a calculable length if all of the possible initiator values have a calculable length. An initiator value is a DFDL string literal. It has a calculable length if the DFDL string literal does not contain any variable-length parts. The terminator region has a calculable length if all of the possible terminator values have a calculable length. A terminator value is a DFDL string literal. It has a calculable length if the DFDL string literal does not contain any variable-length parts. A variable-length part is any of the following - a character string in a variable-width encoding - a DFLD entity in a variable-width encoding - a DFDL generic entity which can match a variable number of characters ( NL, WSP+, WSP* ) The simple content region has a calculable length if both of the following are true: - either the encoding is a fixed-width encoding or the representation does not contain characters. - either lengthKind is 'explicit' and the length is not a DFDL expression or lengthKind is 'implicit' and there is an implicit length for the simple type and its dfdl:representation The complex content region has a calculable length if all of the following are true: - either the encoding is a fixed-width encoding or the representation ( recursively ) does not contain characters. - the element has lengthKind='explicit' and dfdl:length is not a DFDL expression - all group members, recursively, are required ( minOccurs=maxOccurs ) regards, Tim Kimber, Common Transformation Team, Hursley, UK Internet: kimbert(a)uk.ibm.com Tel. 01962-816742 Internal tel. 246742 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

Scenarios for action 086 - nils and defaults
by Tim Kimber 14 Apr '10

14 Apr '10

I took an action from the last meeting to document the scenarios relating to nils and defaults, with particular reference to groups that have a separator. The number of combinations is large, but I'll try to do this in an organised way. The variables are: - separatorPolicy ( required / suppressed / suppressedAtEnd ) - element has a zero-length representation / element is missing from the data stream - user wants ( nil / default value / no element ) in the infoset - element is simple / complex Some ground rules: * A group member is missing if the group has initiatedContent="true" and its initiator is not found. * A group member is missing if the group ends before the member has been parsed. * A group member cannot be missing if its parent group has separatorPolicy="required" Scenario 1: Fixed-length elements with initiators, no separators ONE:oneTWO:twoTHREE:three<END> All members are present. ONE:oneTHREE:three<END> 'Two' is missing, and is defaulted if required. ONE:oneTWO:two<END> Group ends early. 'Three' is missing, and is defaulted if required. Scenario 2: Variable-length elements with initiators and infix separators Note how the presence of separators allows a zero-length representation - not possible in scenario 1 ONE:one,TWO:two,THREE:three<END> All members are present. ONE:one,THREE:three<END> If separatorPolicy='suppressed; then 'Two' is missing, and is defaulted if required. If separatorPolicy!='suppressed' then a processing error is reported. ONE:one,,THREE:three<END> If separatorPolicy='required' then 'Two' has a zero-length representation, zero-length is interpreted as 'missing' and 'Two' defaulted if required If separatorPolicy!='required' then 'Two' is present with a zero-length representation. If 'Two' cannot be zero-length, then it is a processing error. The above rules can be discussed, but I believe they have merit. The key point is that 'required' and 'suppressed' really do imply different things about a zero-length member. I'm aware that there may be other lengthKinds where zero-length needs to be interpreted as 'missing'. I think 'pattern' would be one example of that. Not so sure about 'prefixed' and 'explicit-when-length-is-a-DFDL-expression' Note that the next example is the most likely use of defaulting when separatorPolicy='suppress" ONE:one,TWO:,THREE:three<END> 'Two' has a zero-length content region, and is defaulted if missingValueInitiatorPolicy="required". ONE:one,TWO:two,<END> If separatorPolicy='required' then 'Three' has a zero-length representation, zero-length is interpreted as 'missing', and 'Three' is defaulted if required If separatorPolicy='suppressed' then 'Three' has a zero-length representation. If 'Three' cannot be zero-length, then it is a processing error. ONE:one,TWO:two<END> If separatorPolicy='required' then it is a processing error. If separatorPolicy!='required' then the group ends early. 'Three' is missing, and is defaulted if required. Other points: - I think the name 'missingValueInitiatorPolicy' is confusing - the name implies that it is about missing items, and about the presence/absence of the value only The role of this property is actually a) to tell the parser how to recognize a required element that is not missing from the data stream, but does need to be defaulted b) to tell the unparser how to serialize a required element that is missing from the infoset ( or one that is present in the infoset without a value? ) I think the old name 'defaultValueInitiatorPolicy' conveys it a little more accurately (and is consistent with nilValueInitiatorPolicy ), but there were reasons for changing the name. Unfortunately I don't remember what they were. - OccursCountKind: I'm assuming that it is intended to allow variable-length arrays in formats where the array length cannot easily be detected in other ways. Occurences must be contiguous ( so don't try using it for occurrences within an unordered group ). If the data stream ends before all occurences have been parsed, it is a processing error. regards, Tim Kimber, Common Transformation Team, Hursley, UK Internet: kimbert(a)uk.ibm.com Tel. 01962-816742 Internal tel. 246742 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 14 April 2010- 13:00 UK (8:00 ET)
by Alan Powell 13 Apr '10

13 Apr '10

1. DFDL Specification status There has been no announcement of the public comment period so presumably it hasn't started. Chasing email sent. 2 Nils, defaults and unparsing Logical Value initiator region contains content region contains Nil (implies nillable) nilValueInitiatorPolicy 'prohibited' empty representation of nil nilValueInitiatorPolicy 'required' initiator string "" (empty string) (type is xs:string or xs:hexBinary) missingValueInitiatorPolicy 'prohibited' empty empty missingValueInitiatorPolicy 'required' initiator string missing useNilForDefault nilValueInitiatorPolicy 'prohibited' empty representation of nil nilValueInitiatorPolicy 'required' initiator string default is empty string (type is xs:string or xs:hexBinary) missingValueInitiatorPolicy 'prohibited' empty empty missingValueInitiatorPolicy 'required' 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 Other changes: missingValueInitiatorPolicy Enum Valid values ?required', ?prohibited' Specifies whether to expect an initiator when an element is missing. Ignored unless dfdl:initiator is specified and is not "" (empty string). 'required'- Indicates that the dfdl:initiator followed by empty content is the required syntax to indicate that the element is missing. ?prohibited' - Indicates that empty content is the required syntax to indicate that the element is missing. The presence of an initiator implies that real content must follow. Use of ?prohibited' implies an ordered sequence. If used on an initiated element of an unordered group it is a schema definition error. If the element is required, defaulting occurs as defined above. This property also applies on unparsing, when the data to be written (after nil value and default value processing) is empty content. Annotation: dfdl:element Need to decide whether there needs to be a differentiation between 'zero length content' and 'missing from the data stream'. Tim will document the parsing use cases so we can verify the parsing table. 3 dfdl:separatorPoilicy. dfdl:separatorPolicy enumeration definitions are not complete as they do not discuss arrays or defaulting. separatorPolicy="required" All the separators must be there. No group member, except for required members with a default, may be omitted from the data stream. Every group member must have a separator in the correct position. Optional members and variable-occurrence arrays will be allowed, separators will be expected for all maxOccurs ** It is a schema definition error if maxOccurs="unbounded" for any member of the group separatorPolicy="suppressed" Any group member ( optional or required with a default) can be omitted from the data stream, in which case its separator must may also be omitted. For prefix and infix, if a separator is found then another group member is expected. For postfix, if enclosing markup is not found immediately after a postfix separator then another group member is expected. Enclosing markup or end of data can occur where an infix or prefix separator is expected. This terminates the group. Enclosing markup or end of data can occur immediately after a postfix separator (if dfdl:documentfinalSeparatorCanBeMissing is 'yes' then the postfix separator may be missing at the end of the datastream). This terminates the group. If the group terminates before all of its members have been parsed then any required members in the remainder of the group must be defaulted into the infoset. The entire group can have a zero-length representation, which is indicated by enclosing markup at the start of the group's content region. If another group member is expected and the next group member is a point of uncertainty then the identity of the next group member must be determined by resolving the point of uncertainty as described in section XXX. If another group member is expected but no group member is found in the data stream then it is a processing error. If another group member is expected but all group members have been parsed then it is a processing error. separatorPolicy="suppressedAtEnd" suppressAtEnd has the same rules as 'required' up to the last required member that does not have a default, then it has the same rules as 'suppressed' Open questions 1. If a group has separatorPolicy='required' and one of its optional members has a zero-length representation, and that member is allowed to have a zero-length representation, what should the parser do? A similar question arises for required, defaultable elements with a zero-length representation when they are based on a type with xs:minLength="0". Should the default value be used, or the empty string? 2. How should the occursXXX properties be applied when there are other ways to determine the number of occurences ( e.g. by counting separators )? 3. What algorithm should the parser use to decide whether to default a complex element or group ( when the element/group is a child of a separated group)? 4. How does unparsing work for separated groups in all of these scenarios? 4 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. .... 31/03: work is progressing 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 085 ALL: publicize Public comments phase to ensure a good review.. 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to document use cases for parsing 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 089 Need to be able to define unsigned decimal and integer 31/03: MB to agree proposed solution 090 Semantics of separatorPolicy 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

Today's DFDL WG meeting is cancelled
by Steve Hanson 07 Apr '10

07 Apr '10

We have a couple of people missing plus actions from last week are still being progressed. Next call at usual time next week. 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 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 07 Apr '10

07 Apr '10

Cancelled: OGF DFDL Working Group weekly call 07/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, Peter Lambros/UK/IBM@IBMGB, 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

Minutes for OGF DFDL Working Group Call, March 31-2010
by Alan Powell 31 Mar '10

31 Mar '10

Open Grid Forum: Data Format Description Language Working Group OGF DFDL Working Group Call, March 31-2010 Attendees Steve Hanson (IBM) Alan Powell (IBM) Steve Marting (Progeny) Stephanie Fetzer (IBM) Mike Beckerle (Oco) Tim Kimber(IBM) Apologies Suman Kalia (IBM) 0 DFDL specification status The draft specification was passed by the OGF technical committee on March 30th so will now be made available for public comment. 1 Nils, defaults and unparsing The semantics need clarifying I have reorganized the table Logical Value initiator region contains content region contains Nil (implies nillable) nilValueInitiatorPolicy 'prohibited' empty representation of nil nilValueInitiatorPolicy 'required' initiator string "" (empty string) (type is xs:string or xs:hexBinary) missingValueInitiatorPolicy 'prohibited' empty empty missingValueInitiatorPolicy 'required' initiator string missing useNilForDefault nilValueInitiatorPolicy 'prohibited' empty representation of nil nilValueInitiatorPolicy 'required' initiator string default is empty string (type is xs:string or xs:hexBinary) missingValueInitiatorPolicy 'prohibited' empty empty missingValueInitiatorPolicy 'required' 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 Note: If nilValue is the empty string then missingValueInitiatorPolicy is not used. Other changes: missingValueInitiatorPolicy Enum Valid values ?required', ?prohibited' Specifies whether to expect an initiator when an element is missing. Ignored unless dfdl:initiator is specified and is not "" (empty string). 'required'- Indicates that the dfdl:initiator followed by empty content is the required syntax to indicate that the element is missing. ?prohibited' - Indicates that empty content is the required syntax to indicate that the element is missing. The presence of an initiator implies that real content must follow. Use of ?prohibited' implies an ordered sequence. If used on an initiated element of an unordered group it is a schema definition error. If the element is required, defaulting occurs as defined above. This property also applies on unparsing, when the data to be written (after nil value and default value processing) is empty content. Annotation: dfdl:element (string or hexbinary) The WG agreed that the unparsing table was correct though there was some discussion and misunderstanding about the comment that a nilValue of the empty string did not use missingValueInitiatorPolicy. The comment was asking fro agreement from reviewers and does not add any new rule to the tavle. The meaning of the columns needs a better explanation. SH pointed out that missingValueInitiatorPolicy applies to all simple types not just string and hexbinary and to complex types. The description implies parsing and needs to include unparsing. There was a lot of discussion about paring behaviour. In particular whether there needs to be a differentiation between 'zero length content' and 'missing from the data stream'. Action: Tim will document the parsing use cases so we can verify the parsing table. 2 dfdl:choiceKind 'fixedLength' The main issues are: a) The calculation of the length of the longest branch is not obvious. b) The length units to use - the dfdl:lengthUnits property does not exist on a choice c) The name could be better Proposal is therefore to retain the property but to: i) State the conditions that must apply to use this property, and enforce them in the validator => schema definition error otherwise ii) Decouple the choice from its parent by calculating the length of each branch based solely on the properties of the branches components, irrespective of any parent dfdl:lengthKind The use cases are COBOL redefines. C unions and PL/1 ? Restrictions: - At least one of the choice branches must be of calculable length. (Tim to provide definition of calculable) To be calculable - minOccurs must equal maxOccurs for all children - All lengths will be calculated in bytes. All encodings must be fixed width. Actions: - investigate how PL/1 allocates storage for varchars - investigate how COBOL allocates storage for 'occurs dependingon' and how these are modelled in DFDL. 3 dfdl:occursCountKind 'expression' When dfdl:occursCountKind is 'expression' the occursCount should only be used when parsing. On unpasring the number of occurrences is specified by minOccurs etc Note this behaviour is different from dfdl:lengthKind. Agreed that the dfdl:occursCountKind 'expression' is only used on parsing. 4 Unsigned decimal Whether a logical type is signed or not is used to determine whether a sign is output in some representations. However there isn't an unsigned decimal or integer so these will always be output with a sign so COBOL declarations such as 05 CFCFDN-FLD12 PIC 9(05)V99 COMP-3. cannot be supported. Proposed solution: - Allow xs:nonNegativeInteger which enables unsigned unbounded integers to be modelled. The problem to solve is then just for xs:decimal. - Call the new property dfdl:decimalSigned. It only applies to xs:decimal or user defined restrictions thereof. It applies to all physical decimals, as its name implies (not just zoned or packed). We considered added a dfdl:unsignedDecimal type but rejected it as causing confusion between dfdl type restrictions and user restrictions. The preferred solution is as proposed. Action Mike to agree. 5 dfdl:separatorPoilicy. dfdl:separatorPolicy enumeration definitions are not complete as they do not discuss arrays or defaulting. separatorPolicy="required" All the separators must be there. No group member, except for required members with a default, may be omitted from the data stream. Every group member must have a separator in the correct position. Optional members and variable-occurrence arrays will be allowed, separators will be expected for all maxOccurs ** It is a schema definition error if maxOccurs="unbounded" for any member of the group separatorPolicy="suppressed" Any group member ( optional or required with a default) can be omitted from the data stream, in which case its separator must may also be omitted. For prefix and infix, if a separator is found then another group member is expected. For postfix, if enclosing markup is not found immediately after a postfix separator then another group member is expected. Enclosing markup or end of data can occur where an infix or prefix separator is expected. This terminates the group. Enclosing markup or end of data can occur immediately after a postfix separator (if dfdl:documentfinalSeparatorCanBeMissing is 'yes' then the postfix separator may be missing at the end of the datastream). This terminates the group. If the group terminates before all of its members have been parsed then any required members in the remainder of the group must be defaulted into the infoset. The entire group can have a zero-length representation, which is indicated by enclosing markup at the start of the group's content region. If another group member is expected and the next group member is a point of uncertainty then the identity of the next group member must be determined by resolving the point of uncertainty as described in section XXX. If another group member is expected but no group member is found in the data stream then it is a processing error. If another group member is expected but all group members have been parsed then it is a processing error. separatorPolicy="suppressedAtEnd" suppressAtEnd has the same rules as 'required' up to the last required member that does not have a default, then it has the same rules as 'suppressed' Open questions 1. If a group has separatorPolicy='required' and one of its optional members has a zero-length representation, and that member is allowed to have a zero-length representation, what should the parser do? A similar question arises for required, defaultable elements with a zero-length representation when they are based on a type with xs:minLength="0". Should the default value be used, or the empty string? 2. How should the occursXXX properties be applied when there are other ways to determine the number of occurences ( e.g. by counting separators )? 3. What algorithm should the parser use to decide whether to default a complex element or group ( when the element/group is a child of a separated group)? 4. How does unparsing work for separated groups in all of these scenarios? The changes above were suggested. The unparsing behaviour needs adding. There was discussion about defaulting of complex elements and when this should occur. More discussion is needed. 6 Current Actions Updated below Meeting closed, 15:00 Next call Wednesday 7 April January 2010 13:00 UK (8:00 ET) Next action: 091 Actions raised at this meeting No Action 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 089 Need to be able to define unsigned decimal and integer 31/03: MB to agree proposed solution 090 Semantics of separatorPolicy 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 09/12: no update 16/12: reminded dent to project manager 23/12: SH will send another reminder. 06/01: Another reminder will be sent 13/01: no update 20/01: no update 27/01: no progress 29/01: no progress 03/02: IBM is still investigating 10/02: IBM is still investigating 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 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 085 ALL: publicize Public comments phase to ensure a good review.. 086 AP: Nils and Defaults during unparsing - update table 31/03: TK to documetn use cases for parsing 088 define semantics of choiceKind 'fixedLength' 31/03: TK to provide definition of calculable length. Investigate PL/I varchars and Cobol occurs dependingon. 089 Need to be able to define unsigned decimal and integer 31/03: MB to agree proposed solution 090 Semantics of separatorPolicy 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

Fw: Agenda for OGF DFDL WG call 31 March 2010- 13:00 UK (8:00 ET)
by Alan Powell 31 Mar '10

31 Mar '10

Corrected date in subject 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 ----- Forwarded by Alan Powell/UK/IBM on 31/03/2010 08:37 ----- From: Alan Powell/UK/IBM@IBMGB To: dfdl-wg(a)ogf.org Date: 30/03/2010 18:13 Subject: [DFDL-WG] Agenda for OGF DFDL WG call 3 March 2010- 13:00 UK (8:00 ET) NOTE: The UK has switched to daylight saving time so call starts at 8:00am ET 1 Nils, defaults and unparsing The semantics need clarifying I have reorganized the table Logical Value initiator region contains content region contains Nil (implies nillable) nilValueInitiatorPolicy 'prohibited' empty representation of nil nilValueInitiatorPolicy 'required' initiator string "" (empty string) (type is xs:string or xs:hexbinary) missingValueInitiatorPolicy 'prohibited' empty empty missingValueInitiatorPolicy 'required' initiator string missing useNilForDefault nilValueInitiatorPolicy 'prohibited' empty representation of nil nilValueInitiatorPolicy 'required' initiator string default is empty string (type is xs:string or xs:hexBinary) missingValueInitiatorPolicy 'prohibited' empty empty missingValueInitiatorPolicy 'required' 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 Note: If nilValue is the empty string then missingValueInitiatorPolicy is not used. Other changes: missingValueInitiatorPolicy Enum Valid values ?required', ?prohibited' Specifies whether to expect an initiator when an element is missing. Ignored unless dfdl:initiator is specified and is not "" (empty string). 'required'- Indicates that the dfdl:initiator followed by empty content is the required syntax to indicate that the element is missing. ?prohibited' - Indicates that empty content is the required syntax to indicate that the element is missing. The presence of an initiator implies that real content must follow. Use of ?prohibited' implies an ordered sequence. If used on an initiated element of an unordered group it is a schema definition error. If the element is required, defaulting occurs as defined above. This property also applies on unparsing, when the data to be written (after nil value and default value processing) is empty content. Annotation: dfdl:element (string or hexbinary) 2 dfdl:choiceKind 'fixedLength' The main issues are: a) The calculation of the length of the longest branch is not obvious. b) The length units to use - the dfdl:lengthUnits property does not exist on a choice c) The name could be better Proposal is therefore to retain the property but to: i) State the conditions that must apply to use this property, and enforce them in the validator => schema definition error otherwise ii) Decouple the choice from its parent by calculating the length of each branch based solely on the properties of the branches components, irrespective of any parent dfdl:lengthKind 3 dfdl:occursCountKind 'expression' When dfdl:occursCountKind is 'expression' the occursCount should only be used when parsing. On unpasring the number of occurrences is specified by minOccurs etc Note this behaviour is different from dfdl:lengthKind. 4 Unsigned decimal Whether a logical type is signed or not is used to determine whether a sign is output in some representations. However there isn't an unsigned decimal or integer so these will always be output with a sign so COBOL declarations such as 05 CFCFDN-FLD12 PIC 9(05)V99 COMP-3. cannot be supported. Proposed solution: - Allow xs:nonNegativeInteger which enables unsigned unbounded integers to be modelled. The problem to solve is then just for xs:decimal. - Call the new property dfdl:decimalSigned. It only applies to xs:decimal or user defined restrictions thereof. It applies to all physical decimals, as its name implies (not just zoned or packed). We considered added a dfdl:unsignedDecimal type but rejected it as causing confusion between dfdl type restrictions and user restrictions. 5 dfdl:separatorPoilicy. dfdl:separatorPolicy enumeration definitions are not complete as they do not discuss arrays or defaulting. separatorPolicy="required" No group member, except for required members with a default, may be omitted from the data stream. Every group member must have a separator in the correct position. Optional members and variable-occurrence arrays will be allowed, separators will be expected for all maxOccurs ** It is a schema definition error if maxOccurs="unbounded" for any member of the group separatorPolicy="suppressed" Any group member ( optional or required with a default) can be omitted from the data stream, in which case its separator must also be omitted. For prefix and infix, if a separator is found then another group member is expected. For postfix, if enclosing markup is not found immediately after a postfix separator then another group member is expected. Enclosing markup or end of data can occur where an infix or prefix separator is expected. This terminates the group. Enclosing markup or end of data can occur immediately after a postfix separator (if dfdl:documentfinalSeparatorCanBeMissing is 'yes' then the postfix separator may be missing at the end of the datastream). This terminates the group. If the group terminates before all of its members have been parsed then any required members in the remainder of the group must be defaulted into the infoset. The entire group can have a zero-length representation, which is indicated by enclosing markup at the start of the group's content region. If another group member is expected and the next group member is a point of uncertainty then the identity of the next group member must be determined by resolving the point of uncertainty as described in section XXX. If another group member is expected but no group member is found in the data stream then it is a processing error. If another group member is expected but all group members have been parsed then it is a processing error. separatorPolicy="suppressedAtEnd" suppressAtEnd has the same rules as 'required' up to the last required member that does not have a default, then it has the same rules as 'suppressed' Open questions 1. If a group has separatorPolicy='required' and one of its optional members has a zero-length representation, and that member is allowed to have a zero-length representation, what should the parser do? A similar question arises for required, defaultable elements with a zero-length representation when they are based on a type with xs:minLength="0". Should the default value be used, or the empty string? 2. How should the occursXXX properties be applied when there are other ways to determine the number of occurences ( e.g. by counting separators )? 3. What algorithm should the parser use to decide whether to default a complex element or group ( when the element/group is a child of a separated group)? 4. How does unparsing work for separated groups in all of these scenarios? 6 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 09/12: no update 16/12: reminded dent to project manager 23/12: SH will send another reminder. 06/01: Another reminder will be sent 13/01: no update 20/01: no update 27/01: no progress 29/01: no progress 03/02: IBM is still investigating 10/02: IBM is still investigating 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 progressin 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 085 ALL: publicize Public comments phase to ensure a good review.. 086 AP: Nils and Defaults during unparsing - update table 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

1 0

Agenda for OGF DFDL WG call 3 March 2010- 13:00 UK (8:00 ET)
by Alan Powell 30 Mar '10

30 Mar '10

NOTE: The UK has switched to daylight saving time so call starts at 8:00am ET 1 Nils, defaults and unparsing The semantics need clarifying I have reorganized the table Logical Value initiator region contains content region contains Nil (implies nillable) nilValueInitiatorPolicy 'prohibited' empty representation of nil nilValueInitiatorPolicy 'required' initiator string "" (empty string) (type is xs:string or xs:hexbinary) missingValueInitiatorPolicy 'prohibited' empty empty missingValueInitiatorPolicy 'required' initiator string missing useNilForDefault nilValueInitiatorPolicy 'prohibited' empty representation of nil nilValueInitiatorPolicy 'required' initiator string default is empty string (type is xs:string or xs:hexBinary) missingValueInitiatorPolicy 'prohibited' empty empty missingValueInitiatorPolicy 'required' 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 Note: If nilValue is the empty string then missingValueInitiatorPolicy is not used. Other changes: missingValueInitiatorPolicy Enum Valid values ?required', ?prohibited' Specifies whether to expect an initiator when an element is missing. Ignored unless dfdl:initiator is specified and is not "" (empty string). 'required'- Indicates that the dfdl:initiator followed by empty content is the required syntax to indicate that the element is missing. ?prohibited' - Indicates that empty content is the required syntax to indicate that the element is missing. The presence of an initiator implies that real content must follow. Use of ?prohibited' implies an ordered sequence. If used on an initiated element of an unordered group it is a schema definition error. If the element is required, defaulting occurs as defined above. This property also applies on unparsing, when the data to be written (after nil value and default value processing) is empty content. Annotation: dfdl:element (string or hexbinary) 2 dfdl:choiceKind 'fixedLength' The main issues are: a) The calculation of the length of the longest branch is not obvious. b) The length units to use - the dfdl:lengthUnits property does not exist on a choice c) The name could be better Proposal is therefore to retain the property but to: i) State the conditions that must apply to use this property, and enforce them in the validator => schema definition error otherwise ii) Decouple the choice from its parent by calculating the length of each branch based solely on the properties of the branches components, irrespective of any parent dfdl:lengthKind 3 dfdl:occursCountKind 'expression' When dfdl:occursCountKind is 'expression' the occursCount should only be used when parsing. On unpasring the number of occurrences is specified by minOccurs etc Note this behaviour is different from dfdl:lengthKind. 4 Unsigned decimal Whether a logical type is signed or not is used to determine whether a sign is output in some representations. However there isn't an unsigned decimal or integer so these will always be output with a sign so COBOL declarations such as 05 CFCFDN-FLD12 PIC 9(05)V99 COMP-3. cannot be supported. Proposed solution: - Allow xs:nonNegativeInteger which enables unsigned unbounded integers to be modelled. The problem to solve is then just for xs:decimal. - Call the new property dfdl:decimalSigned. It only applies to xs:decimal or user defined restrictions thereof. It applies to all physical decimals, as its name implies (not just zoned or packed). We considered added a dfdl:unsignedDecimal type but rejected it as causing confusion between dfdl type restrictions and user restrictions. 5 dfdl:separatorPoilicy. dfdl:separatorPolicy enumeration definitions are not complete as they do not discuss arrays or defaulting. separatorPolicy="required" No group member, except for required members with a default, may be omitted from the data stream. Every group member must have a separator in the correct position. Optional members and variable-occurrence arrays will be allowed, separators will be expected for all maxOccurs ** It is a schema definition error if maxOccurs="unbounded" for any member of the group separatorPolicy="suppressed" Any group member ( optional or required with a default) can be omitted from the data stream, in which case its separator must also be omitted. For prefix and infix, if a separator is found then another group member is expected. For postfix, if enclosing markup is not found immediately after a postfix separator then another group member is expected. Enclosing markup or end of data can occur where an infix or prefix separator is expected. This terminates the group. Enclosing markup or end of data can occur immediately after a postfix separator (if dfdl:documentfinalSeparatorCanBeMissing is 'yes' then the postfix separator may be missing at the end of the datastream). This terminates the group. If the group terminates before all of its members have been parsed then any required members in the remainder of the group must be defaulted into the infoset. The entire group can have a zero-length representation, which is indicated by enclosing markup at the start of the group's content region. If another group member is expected and the next group member is a point of uncertainty then the identity of the next group member must be determined by resolving the point of uncertainty as described in section XXX. If another group member is expected but no group member is found in the data stream then it is a processing error. If another group member is expected but all group members have been parsed then it is a processing error. separatorPolicy="suppressedAtEnd" suppressAtEnd has the same rules as 'required' up to the last required member that does not have a default, then it has the same rules as 'suppressed' Open questions 1. If a group has separatorPolicy='required' and one of its optional members has a zero-length representation, and that member is allowed to have a zero-length representation, what should the parser do? A similar question arises for required, defaultable elements with a zero-length representation when they are based on a type with xs:minLength="0". Should the default value be used, or the empty string? 2. How should the occursXXX properties be applied when there are other ways to determine the number of occurences ( e.g. by counting separators )? 3. What algorithm should the parser use to decide whether to default a complex element or group ( when the element/group is a child of a separated group)? 4. How does unparsing work for separated groups in all of these scenarios? 6 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 09/12: no update 16/12: reminded dent to project manager 23/12: SH will send another reminder. 06/01: Another reminder will be sent 13/01: no update 20/01: no update 27/01: no progress 29/01: no progress 03/02: IBM is still investigating 10/02: IBM is still investigating 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 progressin 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 085 ALL: publicize Public comments phase to ensure a good review.. 086 AP: Nils and Defaults during unparsing - update table 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 22 Mar '10

22 Mar '10

Cancelling as Alan is away and the 4 hour time difference is a problem for Suman.

1 0

Rescheduled: OGF DFDL Working Group weekly call (24 Mar 13:00 GMT in Participant Passcode: 8190865 )
by Steve Hanson 22 Mar '10

22 Mar '10

IBM Hursley attendees - DE3S09 Reducing the time to 1 hour now that spec has been sent to OGF

1 0