<br><font size=2 face="sans-serif"><b>Open Grid Forum: Data Format Description
Language Working Group<br>
<br>
OGF DFDL Working Group Call, Sept-30-2009<br>
<br>
Attendees</b></font>
<br><font size=2 face="sans-serif">Mike Beckerle (Oco)</font>
<br><font size=2 face="sans-serif">Alan Powell (IBM)</font>
<br><font size=2 face="sans-serif">Suman Kalia (IBM)</font>
<br><font size=2 face="sans-serif">Steve Marting (Progeny)</font>
<br><font size=2 face="sans-serif">Steve Hanson (IBM)</font>
<br><font size=2 face="sans-serif">Tim Kimber (IBM)</font>
<br>
<br>
<br><font size=2 face="sans-serif"><b>Apologies</b></font>
<br><font size=2 face="sans-serif">Peter Lambros (IBM)</font>
<br>
<br>
<br><font size=2 face="sans-serif">1. %#rxx in TextPadCharacter </font>
<br><font size=2 face="sans-serif"><br>
It has been proposed that use of the raw entity should be restricted in
textPadCharacter</font><font size=3> </font>
<br>
<br><font size=2 face="sans-serif">It was agreed that </font>
<br><font size=2 face="sans-serif">- dfdl:textPadCharacter only one byte
raw entity (%#rxx) can be specified </font>
<br><font size=2 face="sans-serif">- dfdl:textPadCharacter must not be
specified as a raw byte value if the code page is a variable-width code
page.</font>
<br>
<br><font size=2 face="sans-serif">Also SH proposed that dfdl:textPadCharacter
be split to allow a default be specified for each logical type in a similar
way to dfdl:textxxxJustification. Approved </font>
<br>
<br><font size=2 face="sans-serif">dfdl:textPadCharacter will be split
into dfdl:textStringPadCharacter, dfdl:textNumberPadCharacter, dfdl:textBooloeanPadCharacter,
dfdl:textCalendarPadCharacter</font>
<br>
<br><font size=2 face="sans-serif">2. finalTerminatorCanBeMissing</font><font size=3>
</font><font size=2 face="sans-serif"><br>
It has been proposed to restrict the use of this property to the last field
in a definition as the only known used case is missing terminator (typically
<LF>) at end of file</font>
<br>
<br><font size=2 face="sans-serif">MB expressed concern that if the property
was only allowed to be specified on the last element in the schema it would
make it difficult for that definition to be reused. </font>
<br><font size=2 face="sans-serif">Agreed that dfdl:finalTerminatorCanBeMissing
can be specified on any element but is ignore expect on the last element
in the schema.</font>
<br>
<br><font size=2 face="sans-serif">051 - New scoping rules </font>
<br>
<br><font size=2 face="sans-serif">There had been a number of emails from
most of the members of the work group during the week, mostly expressing
dissatisfaction with the new rules based on usability and lack of referential
transparency. SKK expressed support for the new rules as he felt is was
easier to implement tooling.</font>
<br>
<br><font size=2 face="sans-serif">After considerable debate which mainly
re-evaluated previously suggested solutions. </font>
<br><font size=2 face="sans-serif">Need to be able to </font>
<br><font size=2 face="sans-serif">a. Set defaults for dfdl properties</font>
<br><font size=2 face="sans-serif">b. Allow the normal use of xs:include
and xs:import to build schemas.</font>
<br><font size=2 face="sans-serif">c. Allow the applicable dfdl:properties
on any given component to be easily discoverable.</font>
<br><font size=2 face="sans-serif">d. Be 'easy' for users to understand.</font>
<br>
<br><font size=2 face="sans-serif">The following proposal evolved.</font>
<br>
<br><font size=2 face="sans-serif">- A way to define dfdl property
defaults at a schema level. Probably by a global dfdl:format annotation.
The defaults apply to every component in the schema document.</font>
<br><font size=2 face="sans-serif">- The global defaults belong to the
target namespace of the schem so follow normal schema composition rules.</font>
<br><font size=2 face="sans-serif">- dfdl properties on xs:complexType
and xs:group do not put the properties in scope.</font>
<br><font size=2 face="sans-serif">- dfdl:properties on an element and
its referenced simpleType are merged. It is an error if the same property
is defined on the element and the referenced simpleType</font>
<br><font size=2 face="sans-serif">- dfdl:properties on an element do not
override properties on its referenced complexType. dfdl:properties on a
complex element effectively only apply to the syntax part of the element
(initiator terminator, etc),</font>
<br><font size=2 face="sans-serif">- dfdl:properties on an element reference
and its global element declaration are merged. It is an error if
the same property is defined on the element reference and the element declaration.</font>
<br><font size=2 face="sans-serif">- dfdl:properties on an group reference
and its global group declaration are merged. It is an error if the
same property is defined on the group reference and the group declaration</font>
<br><font size=2 face="sans-serif">- variables can still be used for 'parameterization'
but expected to be the exception.</font>
<br>
<br><font size=2 face="sans-serif">AP to write up proposal</font>
<br>
<br><font size=2 face="sans-serif">045: Resolving points of uncertainty</font>
<br>
<br><font size=2 face="sans-serif">A brief discussion of AP proposal and
subsequent comments. These were mostly clarification and expansions rather
than disagreement. AP to incorporate comment and reissue.</font>
<br>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">Next call 7 October 13:00 UK for 2 hours</font>
<br>
<br><font size=2 face="sans-serif"><b>Meeting closed, 15:15</b></font>
<br>
<br><font size=3 face="sans-serif"><b>Actions raised at this meeting</b></font>
<br>
<table border width=100%>
<tr valign=top>
<td width=5%>
<div align=center><font size=2 face="sans-serif"><b>No</b></font></div>
<td width=94%><font size=2 face="sans-serif"><b>Action </b></font>
<tr valign=top>
<td>
<div align=center></div>
<td></table>
<p>
<p>
<p><font size=3 face="sans-serif"><b>Current Actions:</b></font>
<table border width=100%>
<tr valign=top>
<td width=7%>
<div align=center><font size=2 face="sans-serif"><b>No</b></font></div>
<td width=92%><font size=2 face="sans-serif"><b>Action </b></font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>012</b></font></div>
<td><font size=2 face="sans-serif">AP/SH: Update decimalCalendarScheme</font>
<br><font size=2 face="sans-serif">10/9: Not allocated yet</font>
<br><font size=2 face="sans-serif">17/9: No update</font>
<br><font size=2 face="sans-serif">24/9: Add calendar binary formats to
actions</font>
<br><font size=2 face="sans-serif">22/10: No progress</font>
<br><font size=2 face="sans-serif">16/1: proposal distributed and discussed.
Will be redistributed</font>
<br><font size=2 face="sans-serif">21/1: add locale, </font>
<br><font size=2 face="sans-serif">04/02: changed from locale to specific
properties</font>
<br><font size=2 face="sans-serif">18/2: Need more investigation of ICU
strict/lax behaviour.</font>
<br><font size=2 face="sans-serif">08/04: Not discussed</font>
<br><font size=2 face="sans-serif">22/04: AP to complete asap once the
ICU strict/lax behaviour is understood. </font>
<br><font size=2 face="sans-serif">29/04: No progress</font>
<br><font size=2 face="sans-serif">06/05: No progress</font>
<br><font size=2 face="sans-serif">13/05: Calendar has been added to latest
spec version v034 but still a few details to clarify.</font>
<br><font size=2 face="sans-serif">20/05: No Progress</font>
<br><font size=2 face="sans-serif">27/05: No Progress</font>
<br><font size=2 face="sans-serif">03/06: No Progress (low priority)</font>
<br><font size=2 face="sans-serif">09/06: No Progress (low priority)</font>
<br><font size=2 face="sans-serif">17/06: SH to check ICU code for lax
calendar behaviour</font>
<br><font size=2 face="sans-serif">24/06: no progress</font>
<br><font size=2 face="sans-serif">01/07: no progress</font>
<br><font size=2 face="sans-serif">15/07: no progress</font>
<br><font size=2 face="sans-serif">29/07: no progress</font>
<br><font size=2 face="sans-serif">05/08: no progress</font>
<br><font size=2 face="sans-serif">12/08: no progress</font>
<br><font size=2 face="sans-serif">19/08: Inconsistencies are being found
in ICU behaviour so Calendars need reviewing again.</font>
<br><font size=2 face="sans-serif">26/08: Specific three character short
time zones may not be maintained during round tripping when there
is more than one short form for a time zone offset. Because dates and datetimes
in the infoset only maintain a time zone offset so on unparsing it isn't
possible to say which short form will be selected for a particular offset
when there is more than one possible. Need to document.</font>
<br><font size=2 face="sans-serif">09/09: no progress</font>
<br><font size=2 face="sans-serif">16/09: no progress</font>
<br><font size=2 face="sans-serif">30/09: no progress</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>033</b></font></div>
<td><font size=2 face="Arial">AP/TK: Assert/Discriminator semantics. AP
to document. TK to check uses of discriminator besides choice.</font>
<br><font size=2 face="sans-serif">08/04: In progress within IBM</font>
<br><font size=2 face="sans-serif">22/04: Waiting for TK to return from
leave to complete. </font>
<br><font size=2 face="sans-serif">29/04: TK has sent examples shown need
for discriminators beyond choice. Agreed. MB to respond to TK </font>
<br><font size=2 face="sans-serif">06/05: Discussed suggestion of adding
type indicator to discriminator. MB to provide examples.</font>
<br><font size=2 face="sans-serif">15/03: Semantic documented in v034.
MB to provide examples of need for scope indicator on discriminator</font>
<br><font size=2 face="sans-serif">20/05: MB to provide examples of need
for scope indicator on discriminator (but lower priority than action 029)</font>
<br><font size=2 face="sans-serif">27/05: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">....</font>
<br><font size=2 face="sans-serif">19/08: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">26/08: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">09/09: no progress</font>
<br><font size=2 face="sans-serif">16/09: no progress</font>
<br><font size=2 face="sans-serif">30/09: no progress</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>037</b></font></div>
<td><font size=2 face="sans-serif">All: Approach for XML Schema 1.0 UPA
checks.</font>
<br><font size=2 face="sans-serif">22/04: Several non-XML models, when
expressed in their most obvious DFDL Schema form, would fail XML Schema
1.0 Unique Particle Attribution checks that police model ambiguity. And
even re-jigging the model sometimes fails to fix this. Note this is equally
applicable to XMl Schema 1.1 and 1.0. While the DFDL parser/unparser can
happily resolve the ambiguities, the issue is one of definition. If an
XSD editor that implements UPA checks is used to create DFDL Schema, then
errors will be flagged. DFDL may have to adopt the position that: </font>
<br><font size=2 face="sans-serif">a)DFDL parser/unparser will not implement
some/all UPA checks (exact checks tbd)</font>
<br><font size=2 face="sans-serif">b) XML Schema editors that implement
UPA checks will not be suitable for all DFDL models</font>
<br><font size=2 face="sans-serif">c) If DFDL annotations are removed,
the resulting pure XSD will not always be valid (ie, the equivalent XML
is ambiguous and can't be modelled by XML Schema 1.0)</font>
<br><font size=2 face="sans-serif">Ongoing in case another solution can
be found.</font>
<br><font size=2 face="sans-serif">29/04: Will ask DG and S Gao for opinion
before closing</font>
<br><font size=2 face="sans-serif">06/05: Discussed S Gao email and suggestions.
Decided need to review all XML UPA rules and decide which apply to dfdl.</font>
<br><font size=2 face="sans-serif">20/05: SH or SKK to investigate</font>
<br><font size=2 face="sans-serif">27/05: No Progress</font>
<br><font size=2 face="sans-serif">03/06: The concern is that some dfdl
schemas will fail UPA check when validation is turned on or when editted
using tooling that enforces UPA checks. Renaming fields will resolve some/most
issues. Need documentation that describes issue and best practice.</font>
<br><font size=2 face="sans-serif">17/06: no change</font>
<br><font size=2 face="sans-serif">24/06: no change</font>
<br><font size=2 face="sans-serif">01/07: no prgress</font>
<br><font size=2 face="sans-serif">15/07: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">29/07: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">05/08: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">12/08: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">19/08: Clarify that this action is to
go through the XML UPA checks to assess impact on dfdl schemas and advice
best practice. Name clashes is just one example. SH or SKK</font>
<br><font size=2 face="sans-serif">26/08: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">09/09: no progress</font>
<br><font size=2 face="sans-serif">16/09: no progress</font>
<br><font size=2 face="sans-serif">30/09: no progress</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>045</b></font></div>
<td><font size=2 face="sans-serif">20/05 AP: Speculative Parsing</font>
<br><font size=2 face="sans-serif">27/05: Psuedo code has been circulated.
Review for next call</font>
<br><font size=2 face="sans-serif">03/06: Comments received and will be
incorporated</font>
<br><font size=2 face="sans-serif">09/06: Progress but not discussed</font>
<br><font size=2 face="sans-serif">17/06: Discussed briefly</font>
<br><font size=2 face="sans-serif">24/06: No Progress</font>
<br><font size=2 face="sans-serif">01/07: No Progress</font>
<br><font size=2 face="sans-serif">15/07: No progress. MB not happy with
the way the algorithm is documented, need to find a better way.</font>
<br><font size=2 face="sans-serif">29/07: No Progress </font>
<br><font size=2 face="sans-serif">05/08: No Progress. Will document behaviour
as a set of rules.</font>
<br><font size=2 face="sans-serif">12/08: No Progress </font>
<br><font size=2 face="sans-serif">19/08: No Progress </font>
<br><font size=2 face="sans-serif">26/08: No Progress </font>
<br><font size=2 face="sans-serif">09/09: no progress</font>
<br><font size=2 face="sans-serif">16/09: no progress</font>
<br><font size=2 face="sans-serif">30/09: AP distributed proposal and others
commented. Brief discussion AP to incorporate update and reissue</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>049</b></font></div>
<td><font size=2 face="sans-serif">20/05 AP Built-in specification description
and schemas</font>
<br><font size=2 face="sans-serif">03/06: not discussed</font>
<br><font size=2 face="sans-serif">24/06: No Progress</font>
<br><font size=2 face="sans-serif">24/06: No Progress (hope to get these
from test cases)</font>
<br><font size=2 face="sans-serif">15/07: No progress. Once available,
the examples in the spec should use the dfdl:defineFormat annotations they
provide.</font>
<br><font size=2 face="sans-serif">.....</font>
<br><font size=2 face="sans-serif">19/08: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">26/08: No Progress (lower priority)</font>
<br><font size=2 face="sans-serif">09/09: no progress</font>
<br><font size=2 face="sans-serif">30/09: no progress</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>051</b></font></div>
<td><font size=2 face="sans-serif">Scoping rules.</font>
<br><font size=2 face="sans-serif">MB: to document change to scoping rules
to satisfy implementation concerns</font>
<br><font size=2 face="sans-serif">17/06: MB and SH proposals discussed.
Needs further discussion</font>
<br><font size=2 face="sans-serif">24/06: AP to update presentation with
latest proosal</font>
<br><font size=2 face="sans-serif">24/06: AP had updated presentation.
MB to review</font>
<br><font size=2 face="sans-serif">08/07: Discussed at length. Simple types
will now take annotations. Variables will be used for parameters.</font>
<br><font size=2 face="sans-serif">15/07: No further progress. Needs final
write up.</font>
<br><font size=2 face="sans-serif">29/07: No Progress</font>
<br><font size=2 face="sans-serif">05/08: No Progress </font>
<br><font size=2 face="sans-serif">12/08: No Progress </font>
<br><font size=2 face="sans-serif">19/08: AP will document new syntax rules.</font>
<br><font size=2 face="sans-serif">26/08: No Progress </font>
<br><font size=2 face="sans-serif">09/09: AP has documented new scoping
rules. Not discussed</font>
<br><font size=2 face="sans-serif">16/09: Not disussed. AP to update element
reference examples</font>
<br><font size=2 face="sans-serif">30/09: Significant dissatisfaction with
proposed new rules. New proposal developed during call. AP to document.</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>054</b></font></div>
<td><font size=2 face="sans-serif">ICU DecimalNumber/ Calendar behaviour</font>
<br><font size=2 face="sans-serif">15/07: No progress</font>
<br><font size=2 face="sans-serif">29/07: No Progress.</font>
<br><font size=2 face="sans-serif">05/08: No Progress. This action is to
discover and document ICU behaviour. DFDL will do whatever ICU does.</font>
<br><font size=2 face="sans-serif">12/08: No Progress </font>
<br><font size=2 face="sans-serif">19/09: More examples of inconsistent
behaviour discovered</font>
<br><font size=2 face="sans-serif">09/09: no progress</font>
<br><font size=2 face="sans-serif">16/09: no progress</font>
<br><font size=2 face="sans-serif">30/09: no progress</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>056</b></font></div>
<td><font size=2 face="sans-serif">resolve lenghtUnit=bits including fillbytes</font>
<br><font size=2 face="sans-serif">12/08: No Progress</font>
<br><font size=2 face="sans-serif">19/08: No Progress</font>
<br><font size=2 face="sans-serif">26/08: No Progress </font>
<br><font size=2 face="sans-serif">09/09: no progress</font>
<br><font size=2 face="sans-serif">30/09: no progress</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>059</b></font></div>
<td><font size=2 face="sans-serif">9/9: define how encoding, byteorder
and floating point format externally</font>
<br><font size=2 face="sans-serif">16/09: no progress</font></table>
<p>
<p><font size=3 face="sans-serif"><b>Closed actions:</b></font>
<br>
<table border width=100%>
<tr valign=top>
<td width=7%>
<div align=center><font size=2 face="sans-serif"><b>057</b></font></div>
<td width=92%><font size=2 face="sans-serif">Decide semantics and enumeration
for 'parsed' occursCountKind </font>
<br><font size=2 face="sans-serif">26/08: Subsequent discussion agreed
on 'parsed' Need to agree semantics</font>
<br><font size=2 face="sans-serif">09/09: no progress</font>
<br><font size=2 face="sans-serif">16/09: occursxxx applies to array and
optional elements. occursCountKind enumeration agreed. Semantics of 'parsed'
are 'parse as many as possible.</font>
<br><font size=2 face="sans-serif">30/09: Closed</font>
<tr valign=top>
<td>
<div align=center></div>
<td>
<tr valign=top>
<td>
<div align=center></div>
<td>
<tr valign=top>
<td>
<td></table>
<p>
<p><font size=3 face="sans-serif"><b>Work items:</b></font>
<table border width=100%>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>No</b></font></div>
<td><font size=2 face="sans-serif"><b>Item</b></font>
<td><font size=2 face="Arial"><b>target version</b></font>
<td><font size=2 face="sans-serif"><b>status</b></font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>003</b></font></div>
<td><font size=2 face="Arial">Variables </font><font size=2 color=blue face="Arial">(from
action 042) </font>
<td><font size=2 face="Arial">036</font>
<td><font size=2 face="sans-serif">done</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>005</b></font></div>
<td><font size=2 face="Arial">Improvements on property descriptions </font>
<td>
<td><font size=2 face="sans-serif">not started</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>006</b></font></div>
<td><font size=2 face="Arial">Envelopes and Payloads </font><font size=2 color=blue face="Arial">(from
action 026)</font>
<td><font size=2 face="Arial">036</font>
<td><font size=2 face="sans-serif">done</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>007</b></font></div>
<td><font size=2 face="Arial">valueCalc </font><font size=2 color=blue face="Arial">(from
action 029) </font>
<td><font size=2 face="Arial">036</font>
<td><font size=2 face="sans-serif">done</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>011</b></font></div>
<td><font size=2 face="Arial">How speculative parsing works (combining
choice and variable-occurence - currently these are separate) </font><font size=3 color=blue>(from
action 045)</font>
<td>
<td><font size=2 face="sans-serif">awaiting completion of actions 045</font><font size=3><b>
</b> </font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>012</b></font></div>
<td><font size=2 face="Arial">Reordering the properties discussion: move
representation earlier, improve flow of topics </font>
<td>
<td><font size=3>not started </font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>033</b></font></div>
<td><font size=2 face="sans-serif">Numeric data - what physical reps are
allowed for what logical types </font><font size=2 color=blue face="sans-serif">(from
action 020)</font>
<td><font size=2 face="sans-serif">036</font>
<td><font size=2 face="sans-serif">ensure all behaviour documented</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>036</b></font></div>
<td><font size=2 face="sans-serif">Update dfdl schema with change properties
</font>
<td>
<td>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>038</b></font></div>
<td><font size=2 face="sans-serif">Improve length section including bit
handling</font>
<td>
<td><font size=2 face="sans-serif">some improvement in 036</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>042</b></font></div>
<td><font size=2 face="sans-serif">Mapping of the DFDL infoset to XDM </font>
<td>
<td><font size=2 face="sans-serif">not required for V1 specification</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>051</b></font></div>
<td><font size=2 face="sans-serif">Revised scoping rules </font><font size=2 color=blue face="sans-serif">(from
action 051)</font>
<td><font size=2 face="sans-serif">036</font>
<td><font size=2 face="sans-serif">awaiting completion of action 051</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>052</b></font></div>
<td><font size=2 face="sans-serif">add entity for 'one or more white
space characters'</font>
<td><font size=2 face="sans-serif">036</font>
<td><font size=2 color=blue face="sans-serif">done</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>053</b></font></div>
<td><font size=2 face="Default San Serif">name, baseFormat, selector, escapeSchemeRef,
textNumberFormatRef, textCalendarFormatRef, binaryCalendarFormatRef attributes
only</font>
<td><font size=2 face="sans-serif">036</font>
<td>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>054</b></font></div>
<td><font size=2 face="sans-serif">Add occureCountKind='parsed'</font>
<td><font size=2 color=blue face="sans-serif">036</font>
<td><font size=2 color=blue face="sans-serif">done</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>055</b></font></div>
<td><font size=2 face="Default San Serif">Make dfdl:initiatedConet discriminating
(from action 58)</font>
<td><font size=2 face="Default San Serif">036</font>
<td><font size=2 face="Default San Serif">done</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>056</b></font></div>
<td><font size=2 face="Default San Serif">bidi support (action 044)</font>
<td><font size=2 face="Default San Serif">036</font>
<td><font size=2 face="Default San Serif">done</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>057</b></font></div>
<td><font size=2 face="Default San Serif">Properties that take an expression
(action 55)</font>
<td><font size=2 face="Default San Serif">036</font>
<td><font size=2 face="Default San Serif">done</font>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>058</b></font></div>
<td><font size=2 face="Default San Serif">textPadCharacter %#rxx limitation
and split to textxxxxPadCharacter</font>
<td>
<td>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>057</b></font></div>
<td><font size=2 face="Default San Serif">limit terminatorCanBeMissing
to last element in schema. Ignore elsewhere.</font>
<td>
<td>
<tr valign=top>
<td>
<div align=center><font size=2 face="sans-serif"><b>057</b></font></div>
<td>
<td>
<td></table>
<p>
<p>
<br>
<br>
<div align=right>
<br><font size=2 face="sans-serif"><br>
Alan Powell<br>
<br>
MP 211, IBM UK Labs, Hursley, Winchester, SO21 2JN, England<br>
Notes Id: Alan Powell/UK/IBM email: alan_powell@uk.ibm.com
<br>
Tel: +44 (0)1962 815073
Fax: +44 (0)1962 816898<br>
<br>
</font></div>
<br><font size=2 face="sans-serif"><br>
</font>
<hr><font size=2 face="sans-serif"><br>
<i><br>
</i></font>
<p><font size=2 face="sans-serif"><i>Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU</i></font>
<p><font size=2 face="sans-serif"><br>
<br>
</font>
<br>
<br><font size=2 face="sans-serif"><br>
</font>