Agenda for OGF DFDL WG call 3 March 2010- 13:00 UK (9:00 ET)

NOTE: The east coast is 4 hours behind the UK for the next two weeks so start time is 9:00 am ET 1 Process for dealing with internal issues during Public comment phase. 2. Nils and Defaults during unparsing The table 17 in section 13.16.2 was corrected in draft 40 but here are still some ambiguities, for example when nil is the default. Logical Value nilValueInitiatorPolicy Has default value specified missingValueInitiatorPolicy initiator region contains content region contains Nil (implies nillable) prohibited don't care don't care empty representation of nil based on nilKind, nilValue, etc. required initiator string "" (empty string) Note that this implies that the element type is xs:string don't care prohibited empty empty string required initiator string a non-nil non-empty-string value don't care don't care initiator string The representation of the logical value Not supplied don?t care Yes (non-empty sting) don't care Initiator string The representation of the default value. Yes (empty string) prohibited empty empty required initiator string empty 3 dfdl:choiceKind 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 4 DFDL time functions fn:timezone-from-dateTime Returns the timezone from an xs:dateTime value. fn:timezone-from-date Returns the timezone from an xs:date value. fn:timezone-from-time Returns the timezone from an xs:time value. Function Meaning fn:adjust-dateTime-to-timezone Adjusts an xs:dateTime value to a specific timezone, or to no timezone at all. fn:adjust-date-to-timezone Adjusts an xs:date value to a specific timezone, or to no timezone at all. fn:adjust-time-to-timezone Adjusts an xs:time value to a specific timezone, or to no timezone at all. All return an xs:duration. Do we need these functions? 5 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 084 Check behaviour of dfdl:inputValueCalc and outputValueCalc. 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
participants (1)
-
Alan Powell