<br><font size=2 face="sans-serif">Hi Mike</font>
<br>
<br><font size=2 face="sans-serif">My specific item is:</font>
<br>
<br><font size=3 color=#800080 face="sans-serif"><b>Ways of handling variable
markup</b></font>
<p>
<br><font size=2 face="sans-serif">These thoughts came out of observations
of WTX and how it handles variable terminators: </font>
<br>
<br><font size=2 face="Arial">1) One way to handle the situation where
the terminator can vary is to allow the DFDL markup properties (dfdl:terminator,
dfdl:separator, etc) to be lists, just like we already do for dfdl:nullValues.
<br>
<br>
2) We've allowed the prefix of a prefixed length to be explicitly described
as a non-event field using dfdl:lengthPrefixType. Should we permit this
for markup properties? Instead of supplying a list of possible values,
you supply a simple type with enums for the values. This could be viewed
as an alternative/complementary to 1). (WTX has this). </font>
<br>
<br><font size=2 face="Arial">3) Extending 2) you could say that elements
as well as simple types are available to model markup, so you have the
full power of DFDL available.</font>
<br>
<br><font size=2 face="Arial">Now 2) and 3) are very powerful, but there
are issues. </font>
<br><font size=2 face="Arial">- If using XSDL enumeration facet, we are
constrained by its syntax so I don't see how we could use our own entity
scheme or expressions.</font>
<br><font size=2 face="Arial">- What to do on output - use an element of
simple type as then you can use the XSDL default attribute. </font>
<br><font size=2 face="Arial">- If the markup variations are of different
lengths, how do we handle that? </font>
<br><font size=2 face="Arial"> - Take
enums into account when parsing </font>
<br><font size=2 face="Arial"> - But
that breaks a rule we had that enum facets were not used when parsing</font>
<br><font size=2 face="Arial"> - Maybe
we need that anyway to help with speculative parsing?</font>
<br><font size=2 face="Arial">- Is such an element hidden by implication?</font>
<br>
<br><font size=2 face="Arial">Clearly, we should not force a user to model
markup as an element/type - most users just see it as a piece of text so
just entering the value must still be allowed. </font>
<br>
<br><font size=2 face="Arial">Example: </font>
<br>
<br><font size=2 face="Courier New"><xsd:element name="terminatedfield"
type="xsd:string" dfdl:lengthKind="delimited" dfdl:terminator="urn:terminator"
/></font>
<br>
<br><font size=2 face="Courier New"><xsd:element name="terminator"
dfdl:lengthKind="implicit" default=";" /></font>
<br><font size=2 face="Courier New"> <xsd:simpleType></font>
<br><font size=2 face="Courier New"> <xsd:restriction
base="xsd:string"></font>
<br><font size=2 face="Courier New"> <xsd:enumeration
value=":"/></font>
<br><font size=2 face="Courier New"> <xsd:enumeration
value=";"/></font>
<br><font size=2 face="Courier New"> </xsd:restriction></font>
<br><font size=2 face="Courier New"> </xsd:simpleType></font>
<br><font size=2 face="Courier New"> </xsd:element></font>
<br>
<br><font size=2 face="Arial">(Note: proper syntax needs defining)</font>
<br>
<br><font size=2 face="Arial">Last question: Let's say my delimiter is
dynamically defined at the start of the data, like EDI allows. We would
handle that in DFDL using an expression or variable. However, EDI also
allows random white space to appear after the delimiter. Can our expression/entity
syntaxes handle this? Does this preclude use of 1) or 2) or 3) above?
</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
</font><font size=2 face="sans-serif"><br>
</font>
<br><font size=2 face="sans-serif">Regards, Steve<br>
<br>
Steve Hanson<br>
WebSphere Message Brokers<br>
Hursley, UK<br>
Internet: smh@uk.ibm.com<br>
Phone (+44)/(0) 1962-815848</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Mike Beckerle"
<mbeckerle.dfdl@gmail.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: dfdl-wg-bounces@ogf.org</font>
<p><font size=1 face="sans-serif">30/01/2008 02:05</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif"><dfdl-wg@ogf.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[DFDL-WG] Agenda for DFDL WG call -
2008-01-30</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 color=#004080 face="sans-serif">Thanks Alan and Steve
for some agenda topics:</font>
<br><font size=2 color=#004080 face="sans-serif"> </font>
<br><font size=2 face="Arial">Follow up the items from last week</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
- Specification drafts - I need updates from everyone
to produce next spec draft</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
- Expression language - Comments from only Steve H. so
far</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
- Property precedence - Any more comments/discussion</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
- UML for DFDL schema - status update</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
- Entity proposal updates?</font><font size=3 face="Times New Roman"><br>
</font><font size=2 face="Arial"><br>
Discussion for this call</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
- White space</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
- Steve’s items (??) </font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">- OGF presentation</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">Other Topics?</font><font size=3 face="Times New Roman"><br>
</font>
<br><font size=2 color=#004080 face="sans-serif"> </font>
<br><font size=2 face="Tahoma"><b>From:</b> Steve Hanson [mailto:smh@uk.ibm.com]
<b><br>
Sent:</b> Tuesday, January 29, 2008 1:10 PM<b><br>
To:</b> Mike Beckerle<b><br>
Cc:</b> Alan Powell<b><br>
Subject:</b> Agenda for DFDL WG call</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial"><br>
Hi Mike - possible agenda items for tomorrow.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
Regards, Steve<br>
<br>
Steve Hanson<br>
WebSphere Message Brokers<br>
Hursley, UK<br>
Internet: smh@uk.ibm.com<br>
Phone (+44)/(0) 1962-815848</font><font size=3 face="Times New Roman">
</font><font size=1 color=#800080 face="Arial"><br>
----- Forwarded by Steve Hanson/UK/IBM on 29/01/2008 17:55 -----</font><font size=3 face="Times New Roman">
</font>
<p>
<table width=100%>
<tr valign=top>
<td width=19%><font size=1 face="Arial"><b>Alan Powell/UK/IBM</b> </font>
<p><font size=1 face="Arial">29/01/2008 17:25</font><font size=3 face="Times New Roman">
</font>
<td width=80%>
<br>
<table width=100%>
<tr valign=top>
<td width=8%>
<div align=right><font size=1 face="Arial">To</font></div>
<td width=91%><font size=1 face="Arial">Steve Hanson/UK/IBM@IBMGB</font><font size=3 face="Times New Roman">
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="Arial">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="Arial">Subject</font></div>
<td><font size=1 face="Arial">Fw: [DFDL-WG] DFDL: Minutes from OGF WG call,
23 Jan 2007 *CORRECTED*</font></table>
<br><font size=3 face="Times New Roman"> </font>
<p>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br></table>
<br><font size=3 face="Times New Roman"><br>
</font><font size=2 face="Arial"><br>
Steve</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
I will try to make the WG call tomorrow but may be still on a course.</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
We need to follow up the items from last week</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
- Specification drafts - I need updates from everyone
to produce next spec draft</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
- Expression language - Comments from only you so far</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
- Property precedence - Any more comments/discussion</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
- UML for DFDL schema - status update</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
- Entity proposal - I should have updated as a result of last weeks
discussion but haven't had time</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
Discussion for this call</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
- White space</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
- Your items. We did discuss them a bit but mostly in the context
of white space. <br>
<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</font><font size=3 face="Times New Roman"><br>
</font><font size=1 color=#800080 face="Arial"><br>
----- Forwarded by Alan Powell/UK/IBM on 29/01/2008 17:19 -----</font><font size=3 face="Times New Roman">
</font>
<p>
<table width=100%>
<tr valign=top>
<td width=29%><font size=1 face="Arial"><b>Steve Hanson/UK/IBM@IBMGB</b>
<br>
Sent by: dfdl-wg-bounces@ogf.org</font><font size=3 face="Times New Roman">
</font>
<p><font size=1 face="Arial">28/01/2008 08:51</font><font size=3 face="Times New Roman">
</font>
<td width=70%>
<br>
<table width=100%>
<tr valign=top>
<td width=8%>
<div align=right><font size=1 face="Arial">To</font></div>
<td width=91%><font size=1 face="Arial">dfdl-wg@ogf.org</font><font size=3 face="Times New Roman">
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="Arial">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="Arial">Subject</font></div>
<td><font size=1 face="Arial">Re: [DFDL-WG] DFDL: Minutes from OGF WG call,
23 Jan 2007 *CORRECTED*</font></table>
<br><font size=3 face="Times New Roman"> </font>
<p>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br></table>
<br><font size=3 face="Times New Roman"><br>
<br>
</font><font size=2 face="Arial"><br>
<br>
Sorry I couldn't make the call. Some comments:</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
a) we need both WSP and OWSP if DFDL delimiter properties can only specify
a single value. If they can specify a list of values then you can get away
with only needing WSP</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
eg, </font><font size=2 face="Courier New">dfdl:terminator="@
@%WSP;"</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
b) if we make WSP mean a single white space character, we need a second
entity for multiple white space characters.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
It doesn't look like you got round to discussing the other items I sent
in (below)? Let's do that next call.</font><font size=3 face="Times New Roman">
</font><font size=2 color=blue face="Arial"><br>
<br>
1) One way to handle the situation where the terminator can vary is to
allow the DFDL markup properties (dfdl:terminator, dfdl:separator, etc)
to be lists, just like we already do for dfdl:nullValues. (IBM's WTX has
this capability).</font><font size=3 color=blue face="Times New Roman">
</font><font size=2 color=blue face="Arial"><br>
<br>
2) We've allowed the prefix of a prefixed length to be explicitly described
as a non-event field using dfdl:lengthPrefixType. Should we permit this
for markup properties? Instead of supplying a list of possible values,
you supply a simple type with enums for the values. This could be viewed
as an alternative/complementary to 1). There is a limitations - because
we are using XSDL enumeration facet, we are constrained by its syntax so
I don't see how we could use our own entity scheme or expressions. Also,
I suspect that enums are inherently unordered so we'd need a way of saying
which to use on output (use an element of simple type and use XSDL default
attribute?). Lastly, we should not force a user to model an initiator
as an element/type - most users just see it as a piece of text so just
entering the value must still be allowed. <br>
<br>
3) Let's say my delimiter is dynamically defined at the start of the data,
like EDI allows. We would handle that in DFDL using an expression or variable.
However, EDI also allows random white space to appear after the delimiter.
Can our expression/entity syntaxes handle this? Does this preclude
use of 1) or 2)? </font><font size=3 color=blue face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
Regards, Steve<br>
<br>
Steve Hanson<br>
WebSphere Message Brokers<br>
Hursley, UK<br>
Internet: smh@uk.ibm.com<br>
Phone (+44)/(0) 1962-815848</font><font size=3 face="Times New Roman">
</font>
<p>
<table width=100%>
<tr valign=top>
<td width=31%><font size=1 face="Arial"><b>Ian W Parkinson/UK/IBM@IBMGB</b>
<br>
Sent by: dfdl-wg-bounces@ogf.org</font><font size=3 face="Times New Roman">
</font>
<p><font size=1 face="Arial">24/01/2008 16:19</font><font size=3 face="Times New Roman">
</font>
<td width=68%><font size=3 face="Times New Roman"> </font>
<p>
<br>
<table width=100%>
<tr valign=top>
<td width=9%>
<div align=right><font size=1 face="Arial">To</font></div>
<td width=90%><font size=1 face="Arial">dfdl-wg@ogf.org</font><font size=3 face="Times New Roman">
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="Arial">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="Arial">Subject</font></div>
<td><font size=1 face="Arial">[DFDL-WG] DFDL: Minutes from OGF WG call,
23 Jan 2007 *CORRECTED*</font></table>
<br><font size=3 face="Times New Roman"> </font>
<p>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br></table>
<br><font size=3 face="Times New Roman"><br>
<br>
</font><font size=2 face="Arial"><br>
<br>
<br>
A small correction. with thanks to Simon - it was Steve (rather than Simon)
who had previously attracted a reasonable audience at the OGF conference.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
Ian</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><b><br>
<br>
<br>
Open Grid Forum: Data Format Description Language Working Group</b></font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><b><br>
<br>
Weekly Working Group Conference Call</b></font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><b><br>
17:00 GMT, 23 Jan 2008</b></font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><b><br>
<br>
<br>
Attendees</b></font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Mike Beckerle (Oco)</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Simon Parker (PolarLake)</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Ian Parkinson (IBM)</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Alan Powell (IBM)</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><b><br>
<br>
Apologies</b></font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Steve Hanson (IBM), Suman Kalia (IBM)</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><b><br>
<br>
1. OGF22</b></font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
The DFDL session at OGF22 is now booked for the Monday afternoon, and Mike
has registered to attend. Mike will present our updated status, and Alan
promised to upload the last set of presented slides to GridForge so that
Mike can update them. Alan asked whether we should attempt to drum up interest
in the DFDL session to encourage attendence; Simon thought that advertising
may not make much difference and that Steve had a reasonable audience when
he presented.</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><b><br>
<br>
2. Specification drafts</b></font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
Steve and Alan had previously assigned ownership of individual items from
Mike's plan of contents for the next few drafts. Alan will assemble the
next draft, due at the end of the month, and asked for input as soon as
possible.</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
<br>
Looking at the plan for the next, "vX+1", draft, the group reported
the following status:</font><font size=3 face="Times New Roman"> </font>
<ul>
<li><font size=2 face="Arial"><b>Nulls/default/optionals</b> - Mike reported
no update.</font><font size=3 face="Times New Roman"> </font>
<li><font size=2 face="Arial"><b>Description of schema components</b> -
Simon is still working on this.</font><font size=3 face="Times New Roman">
</font>
<li><font size=2 face="Arial"><b>Regular expressions for lengths</b> -
Alan reported no progress.</font><font size=3 face="Times New Roman"> </font>
<li><font size=2 face="Arial"><b>Expression language</b> - Alan will shortly
distribute a new version of the proposal for review.</font><font size=3 face="Times New Roman">
</font>
<li><font size=2 face="Arial"><b>valueCalc</b> - Mike is still to write
this.</font><font size=3 face="Times New Roman"> </font>
<li><font size=2 face="Arial"><b>Property precedence</b> - Following a
discussion on the call last week, please provide review comments. Mike
will add this to the agenda for next week.</font><font size=3 face="Times New Roman">
</font>
<li><font size=2 face="Arial"><b>Entities</b> - Alan's recent proposal
is to be discussed on the current call.</font><font size=3 face="Times New Roman">
</font>
<li><font size=2 face="Arial"><b>White space handling</b> - Discussion
is ongoing, and Steve is to make a proposal.</font></ul><font size=2 face="Arial"><br>
The plan calls for subsequent versions of the specification, including
the following items with status:</font><font size=3 face="Times New Roman">
</font>
<ul>
<li><font size=2 face="Arial"><b>Supplements</b> - Steve is working to
update the supplements</font><font size=3 face="Times New Roman"> </font>
<li><font size=2 face="Arial"><b>Speculative parsing</b> - IBM has internally
been discussing and reviewing WTX function, though no documentation presently
exists covering this.</font></ul><font size=2 face="Arial"><b><br>
3. UML diagrams</b></font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Simon is revising the UML diagrams which describe the DFDL schema components.
The previous meeting minutes included a number of comments on these diagrams,
and the group took this opportunity to look at some of those comments:</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><i><br>
<br>
"...I think it would be better to use the open source XML schema model
as source model and show relationship of DFDL Annotations attached to the
XSD schema model"</i> - Mike noted that DFDL makes use of annotations
on objects which are absent from the XSD schema model, and hence that it
may be unnatural to base the DFDL schema model directly on the XSD model.
Simon suggested that it would be cleanest to describe a modified version
the XSD model including those XSD elements that we need to annotate, and
use this as a basis for the DFDL model.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><i><br>
<br>
"The current diagram suggests that 'variable definition' can both
be part of a format base or as a standalone annotation (outside of a format).
Is this true?" </i>- Mike suggested that variable definitions don't
have to be part of a format block: so, yes, this is true.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
Mike agreed to respond further to the set of comments by email.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><b><br>
<br>
4. Review of Entities proposal</b></font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
Alan has distributed a proposal covering entities in DFDL, intended to
allow characters which are disallowed by XML1.0 (or XML1.1) to be included
in DFDL schemas. These follow a similar syntax to XML, using % instead
of & as an escape, with an additional mechanism for specifying raw
data. This latter is intended to supplant the escaping mechanism described
in current versions of the specification (which also uses % as an escape).</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
The group felt that the description of the raw data entities should not
be cast in terms of characters and character sets, but rather in terms
of bytes. If treated as characters, schemas may need to be written when
moving from single-byte to double-byte character sets; further, this incorrectly
implies some codepage conversion is involved.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
The proposal also introduces a list of predefined names for certain common
control characters. Mike asked whether these are the existing XML names
- Alan replied that XML does not define names for control characters. <br>
<br>
Ian asked how we should represent the literal % character in strings given
this form of escaping. The present draft of the specification uses "%%"
to handle this; Simon suggested a string like "%pc;". The meeting
felt that %% might be marginally preferable.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
Finally, the proposal defines some labels which aim to reduce the complexity
of dealing with whitespace and newlines. The %NL; entity represents a newline
on "the target platform" - Mike observed that DFDL presently
does not have a concept of a target platform. Alan felt it important that
a single DFDL schema be able to generate output documents targetted at
different platforms. Mike proposed that we introduce a new property, "generatedNewLine",
which describes the meaning of %NL; during unparse, and that %NL; should
be tolerant of any common new line representation during parse. The group
discussed whether this could instead be handled using a list of optional
new line values, however this would not support schema portability. Simon
suggested we introduce another new property to mean that %NL; should be
the conventional new line representation on the platform on which an engine
is running, however Mike pointed out that this simply requires appropriate
configuration of the generatedNewLine property.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
%WSP; and %OWSP; are introduced to mean any whitespace, and optional whitespace.
This will be useful in describing some formats which allow arbitrary whitespace,
such as MIME. Mike pointed out that we could model such whitespace using
hidden fields, but that these entities may make a schema clearer. PolarLake
have found that only one such label is necessary, which means, "one
or more whitespace characters", and that this needs only to be made
available as a delimiter - Mike agreed that this label may represent a
special type of delimiter rather than a general purpose entity. Alan would
like to work through the potential use cases to see if we can restrict
it in this fashion, and will update the proposal to specify that these
relate to just one character. Simon suggested we could introduce an extra
label, perhaps %WPS*; to match multiple whitespace characters.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><b><br>
<br>
Meeting closed, 18:15</b></font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
<br>
<br>
Ian Parkinson<br>
WebSphere ESB Development<br>
Mail Point 211, Hursley Park, Hursley, Winchester, SO21 2JN, UK</font><font size=3 face="Arial"><br>
</font>
<div align=center>
<br>
<hr></div>
<p><font size=2 face="Arial"><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><font size=3 face="Times New Roman"> </font>
<p><font size=3 face="Times New Roman"><br>
</font><font size=3 face="Arial"><br>
</font><font size=2 face="Courier New"><br>
<br>
--<br>
dfdl-wg mailing list<br>
dfdl-wg@ogf.org<br>
http://www.ogf.org/mailman/listinfo/dfdl-wg</font><font size=3 face="Times New Roman">
<br>
<br>
</font>
<div align=center>
<br>
<hr></div>
<br><font size=3 face="Times New Roman"> </font>
<p><font size=2 face="Arial"><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><font size=3 face="Times New Roman"> </font>
<p><font size=3 face="Times New Roman"><br>
<br>
</font><font size=3 face="Arial"><br>
</font><font size=2 face="Courier New"><br>
--<br>
dfdl-wg mailing list<br>
dfdl-wg@ogf.org<br>
http://www.ogf.org/mailman/listinfo/dfdl-wg</font><font size=3 face="Arial"><br>
</font>
<div align=center>
<br>
<hr></div>
<br><font size=3 face="Times New Roman"> </font>
<p><font size=2 face="Arial"><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><font size=3 face="Times New Roman"> </font>
<p><font size=3 face="Arial"><br>
</font><font size=3 face="Times New Roman"><br>
<br>
</font><tt><font size=2>--<br>
dfdl-wg mailing list<br>
dfdl-wg@ogf.org<br>
http://www.ogf.org/mailman/listinfo/dfdl-wg</font></tt>
<br><font size=3 face="sans-serif"><br>
</font>
<br><font size=3 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>
</font><font size=3 face="sans-serif"><br>
</font>
<br>
<br><font size=3 face="sans-serif"><br>
</font>