[DFDL-WG] Agenda for OGF DFDL WG call 24 February 2010- 13:00 UK (8:00 ET)

Wed Feb 24 04:38:26 CST 2010

1. Remaining 037 review issues 

A:
16.2 scannablility with lengthKind pattern:   
Confirm that this is what we agreed 
In summary, you can use a data pattern on any element (complex, simple 
text, simple binary) as long as the bytes are legal in the stated 
encoding, which where binary data is involved in practice means an 8-bit 
ASCII encoding. 

By 8-bit ASCII we really mean an encoding where all the codepoints from 
0-255 map to the equivalent value. Subsequent investigation indicates that 
'all' 8-bit ASCII encodings have gaps so there isn't a valid character. 
Mike has suggested 
1) for all ascii-based character sets, we say that bytes 0x00 to 0xFF all 
map to exactly those codepoints in ISO 10646 for the infoset, and vice 
versa. 

2) define dfdl:encoding="bytes" as a special character set name which has 
the above property. 

Briefly discussed but no conclusion. 

B:
Glossary

Variable-Occurrence Item - Optional elements have a variable number of 
occurrences (0 or 1) and arrays also can have a variable number of 
occurrences (when minOccurs < maxOccurs). So when we say an item with a 
variable number of occurrences, this can mean either an optional element, 
or an array where minOccurs < maxOccurs. In either array or optional 
elements, we have the additional constraint that the DFDL representation 
properties do not preclude a variable number of occurrences. When 
dfdl:occursCountKind='explicit' and dfdl:occursCount has a literal 
constant as its value, or an expression that statically evaluates to a 
constant, then the DFDL properties are specifying exactly the number of 
occurrences for all instances and so are said to preclude a variable 
number of occurrences. If dfdl:occursCount has a formula as its expressed 
value, then the DFDL properties do not preclude a variable number of 
occurrences. 
MikeB Comment:
This idea that you can have minOccurs < maxOccurs, but dfdl:occurs is 
equal to a constant and dfdl:occursKind="explicit" is causing us a bunch 
of grief in these definitions.
Can we be conservative and just say it is a schema definition error if 
minOccurs < maxOccurs but the length is static, i.e., an explicit 
constant-valued expression?

C:
DFDL Schema Component Model
What needs to be changed in the UML diagram?

D:
Sequence Groups
Mike B:
TBD: rewrite these property descriptions in terms of the grammar for 
sequences 
Specifically, this is where the FinalUnused Region must be described.

E: Check other comments in document.

2. Go through Actions

Current Actions: 
No
Action 
049
20/05 AP Built-in specification description and schemas 
03/06: not discussed 
24/06: No Progress 
24/06: No Progress (hope to get these from test cases) 
15/07: No progress. Once available, the examples in the spec should use 
the dfdl:defineFormat annotations they provide. 
... 
14/10: no progress 
21/10: Discussed the real need for this being in the specification. It 
seemed that the main value is it define a schema location for downloading 
'known' defaults from the web. 
28/10: no progress 
04/11: no progress 
11/11: no update 
18/11: no update 
25/11: Agreed to try to produce for CSV and fixed formats 
04/12: no update 
09/12: no update 
16/12: no update 
23/12: no update 
06/01: no progress. If there is no resource to complete this action it can 
be deferred 
13/01:no progress 
20/01: no progress 
27/01: no progress 
29/01: No progress.  The predefined formats do not need to be available 
when the spec is published. 
Suman said that he had been mapping COBOL structures to DFDL and it didn't 
look as though the way text numbers are define is very usable. He will 
document for next call 
03/02: No progress 
10/02: No progress 
17/03: No progress 
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' 
079
MB:Encoding for binary fields when lenghtkind is pattern 
17/02: Discussed but no conclusion 
080
AP:Clarify semantics of fn:poisition and fn:count 
17/02: no progress 
081
AP: Inf and Nan 
The description is the way ICU behaves but need clarification. It isn't 
clear how inf and Nan are represented in the infoset. Need to investigate 
if XML allows these values 
17/02: XML allows Nan and inf for float and double Dfdl will do the same. 
Requires more investigation of ICU. 

3 DFDL v1 Specification completion. 
Draft 039 will be publish today. 
WG review and Comments by 3 March 
Draft 40 with updates for OGF submission - available 5 March 

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/dfdl-wg/attachments/20100224/76c0b7f7/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 25343 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/dfdl-wg/attachments/20100224/76c0b7f7/attachment-0001.gif 