<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Mike,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Looks like I neglected to include the Text node type (I meant
to). I would think they should operate exactly the same as in XDM. That is, almost
all actual content ends up in text nodes and is aggregated and typed by the containing
element nodes as appropriate. The XDM specification is pretty specific on the
relationship between string-value (aggregated child text nodes) and typed-value
– I would suggest we just follow the same convention.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Not sure how well (or not) this whole scheme fits in with the grammar
though.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dave<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Mike Beckerle
[mailto:mbeckerle.dfdl@gmail.com] <br>
<b>Sent:</b> Tuesday, May 12, 2009 9:47 AM<br>
<b>To:</b> Dave Glick; 'Steve Hanson'<br>
<b>Cc:</b> dfdl-wg@ogf.org<br>
<b>Subject:</b> RE: [DFDL-WG] DFDL Data Model Recommendations<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>In my initial skim my first thought is "what about the text
nodes?" This is a very major feature of the XML infoset that we dropped
from the DFDL infoset as in the current draft, but I see no mention
of text nodes in your document.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>...mike</span><o:p></o:p></p>
</div>
<p><a name=""><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Mike Beckerle | OGF DFDL WG Co-Chair | CTO | Oco, Inc.</span></b></a><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>Tel:
781-810-2125 | 100 Fifth Ave., 4th Floor, Waltham MA 02451 |</span> <a
href="mailto:mbeckerle.dfdl@gmail.com"><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:gray'>mbeckerle.dfdl@gmail.com</span></a><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'> </span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> dfdl-wg-bounces@ogf.org
[mailto:dfdl-wg-bounces@ogf.org] <b>On Behalf Of </b>Dave Glick<br>
<b>Sent:</b> Monday, May 11, 2009 8:22 PM<br>
<b>To:</b> Steve Hanson<br>
<b>Cc:</b> dfdl-wg@ogf.org<br>
<b>Subject:</b> [DFDL-WG] DFDL Data Model Recommendations</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>All,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have attached my first draft of recommendations for the DFDL
Data Model. It is based heavily on XDM and should be mostly compatible. Where
there are incompatibilities, they are by convention and not related to the
actual representation so I believe a system that is set up to work with XDM
should be easily adaptable to work with DFDL. This was important to me –
in my project I would be using DFDL as part of a pipeline process that also
involved transforming the results of parsing using XSLT and then unparsing the
results of transformation. I imagine many other potential users of DFDL will be
engaging in similar XML pipeline scenarios. In these situations, the closer the
DFDL model is to those used by other XML technologies, the better. Hopefully
the recommendation meets the requirements Steve mentions below – it turns
out most of the existing infoset could be mapped directly to XDM concepts. I
introduced a new node type for the unresolvable concept to match the existing
infoset, but discuss how it is related to XDM and other XML technologies.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This exercise brought to major questions to mind:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>- Must an instance of the XML Infoset (and XML document) be
valid against a given DFDL Schema (as determined by an XML Schema validation
engine) to be available for unparsing? If not, is it up to the DFDL
implementation to determine the suitability of the XML Infoset Character
Information Items for their given unparsed data type? The real question is: for
the unparsing process can a DFDL Data Model be constructed from an XML Infoset
directly or only from a PVSI (where does the data for unparsing really come
from)? It would seem to me that if the input XML isn't valid against the DFDL
Schema, then it probably can't be unparsable - otherwise, how would the invalid
portions be handled (such as strings that should be numeric or a structure that
doesn't match)?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>- I am confused by the notion of the "augmented
infoset". The regular infoset appears to be based on the logical structure
of the data post-parsing. In other words, choices are resolved and the result
looks something like an XML Infoset, PSVI, or XDM tree might following
something like XSLT transformation. The augmented infoset on the other hand
appears to be based on the logical structure of the DFDL Schema being used for
processing and therefore contains branches for all choice possibilities, etc.
It is "filled in" as parsing takes place. This doesn't make a lot of
sense to me - what about the branches for which there was no data to "fill-in"
(such as choice branches that weren't followed)? Are they dropped following
parsing? If not, then there are a lot of information items in the final tree
that have no value. It made more sense to me to consider the DFDL Data Model as
being constructed during parsing and at any given time in the parsing process a
portion of the model (that which has already been parsed) is available.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hopefully those questions made sense... I should (finally) be on
the call this Wednesday to discuss.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dave<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Steve Hanson [mailto:smh@uk.ibm.com]
<br>
<b>Sent:</b> Wednesday, May 06, 2009 11:15 AM<br>
<b>To:</b> Dave Glick<br>
<b>Cc:</b> Alan Powell; dfdl-wg@ogf.org<br>
<b>Subject:</b> Re: [DFDL-WG] Agenda for OGF WG call 6 May 2009<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Dave</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Two intents of
the infoset was that it should be a) simple and b) easily related to the
grammar in 11.3, so whatever you come up with needs to take those requirements
into account.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>"</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Parts of XDM that
have no relevance to DFDL but are also not conflicting should probably be left
in for conciseness and compatibility.</span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>" - a) above would imply the opposite.</span>
<br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The XDM spec
defines the rules for how an XDM can be created from an XML Infoset or a PSVI.
We can do a similar exercise for DFDL Infoset, for those users who want
to use XSL for any post-DFDL transformation.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Regards<br>
<br>
Steve Hanson<br>
Programming Model Architect<br>
WebSphere Message Brokers<br>
Hursley, UK<br>
Internet: smh@uk.ibm.com<br>
Phone (+44)/(0) 1962-815848</span> <o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td width="40%" valign=top style='width:40.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Dave
Glick <dglick@dracorp.com></span></b><span style='font-size:7.5pt;
font-family:"Arial","sans-serif"'> </span><br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Sent by:
dfdl-wg-bounces@ogf.org</span> <o:p></o:p></p>
<p><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>06/05/2009
13:55</span> <o:p></o:p></p>
</td>
<td width="59%" valign=top style='width:59.0%;padding:.75pt .75pt .75pt .75pt'>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>To</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Alan
Powell/UK/IBM@IBMGB, "dfdl-wg@ogf.org" <dfdl-wg@ogf.org></span>
<o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Subject</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Re:
[DFDL-WG] Agenda for OGF WG call 6 May 2009</span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><o:p> </o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
</table>
<p class=MsoNormal><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><br>
<br>
<br>
<span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>All,</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>My apologies,
but I will be unable to make the call again this week. I was hoping to have
some suggestions regarding the infoset/data model for discussion today, but
it's not quite ready (I still have a little more digging to do through the rest
of the spec to make sure what I'm suggesting can adequately capture all the
representation cases in DFDL). I'll try to get something out by the end of the
day for review and discussion on next week's call.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>In general, it
appears to me (and I'm admittedly not as versed in the various XML standards as
the other members of the group) that we can bring the DFDL Infoset very closely
in line with the XDM. Specifically, I've been looking at the way XSLT 2.0
treats XDM as it's data model. It states clearly that XDM is the model for XSLT
with certain explicit caveats and additions. This follows the XDM guidance of how
it should be used by other standards (specifically in XDM Section 7 and
Appendix A). The task for DFDL therefore consists of two parts: what parts of
the XDM are in conflict with DFDL and should be explicitly excluded, and what
parts of DFDL have no corresponding support in XDM and should be appended.
Parts of XDM that have no relevance to DFDL but are also not conflicting should
probably be left in for conciseness and compatibility.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>My biggest
concern is over the use of two different types of Element Information Items in
the DFDL specification as this seems so contrary to convention in XDM. My
recommendations include treating all element nodes similarly to XDM as complex
and those element nodes that actually only contain simple content should have a
single child of the XDM text node type or a new DFDL value node type (not sure
the best way to go here).</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>In any case,
I'll pass along a full recommendation soon.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Dave</span> <br>
<o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
dfdl-wg-bounces@ogf.org [dfdl-wg-bounces@ogf.org] On Behalf Of Alan Powell
[alan_powell@uk.ibm.com]<b><br>
Sent:</b> Wednesday, May 06, 2009 6:01 AM<b><br>
To:</b> dfdl-wg@ogf.org<b><br>
Subject:</b> [DFDL-WG] Agenda for OGF WG call 6 May 2009</span><br>
<br>
<b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
<br>
Agenda:</span></b> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
<br>
1. Go through actions.</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
<br>
2. LengthKind on Sequences and choices.</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
LengthKind on sequences and choices and their parent element has proved
confusing to new users of DFDL. It is proposed that lengthKind is removed from
groups and only allow it to be set on parent element. See email from SH</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
<br>
3. Discuss UnorderedInitated email from SH</span> <span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
<br>
4. Infoset codepage and encoding</span> <span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
<br>
The spec does not say what codepage and encoding is used for string fields.</span>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
<br>
5. AOB</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
Next version (034)</span> <br>
<br>
<b><span style='font-family:"Arial","sans-serif"'><br>
Current Actions:</span></b> <o:p></o:p></p>
<table class=MsoNormalTable border=1 cellpadding=0 width="100%"
style='width:100.0%;border:outset 3.0pt'>
<tr>
<td width="11%" valign=top style='width:11.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>No</span></b><o:p></o:p></p>
</td>
<td width="88%" valign=top style='width:88.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Action
</span></b><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>012</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>AP/SH:
Update decimalCalendarScheme</span> <span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'><br>
10/9: Not allocated yet</span> <span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'><br>
17/9: No update</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
24/9: Add calendar binary formats to actions</span> <span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><br>
22/10: No progress</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
16/1: proposal distributed and discussed. Will be redistributed</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
21/1: add locale, <br>
04/02: changed from locale to specific properties</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
18/2: Need more investigation of ICU strict/lax behaviour.</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
08/04: Not discussed</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: AP to complete asap once the ICU strict/lax behaviour is understood. <br>
29/04: No progress</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>020</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SH:
Resolve packedDecimalSignCodes<b> </b>behaviour depends on NumberCheckPolicy <br>
22/10: No progress</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
10/12: added how to decide to overpunch and sign position</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
11/02: proposal largely agreed. SH to make minor changes</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
18/02: AP to document unsigned type behaviour</span> <span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><br>
25/02: no progress</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
08/04: Not discussed</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: SH to complete last remaining issue, which is the behaviour when
logical type is signed/unsigned and the physical type is unsigned/signed.</span>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
29/04: SH had identified a problem with definition values and types in the
infoset and will email proposal. DG to be asked to accelerate action
032 to see if helps</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>024</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><No
owner> String XML type</span> <span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'><br>
08/04: Not discussed</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: Need to allocate owner. Work is to describe the semantics of using
dfdl:representation="xml" to model a well-formed XML fragment in an
overall non-XML document described by a DFDL schema.</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
29/04: As no resource availbel to progress this action agreed to defer from
V1. Will close next week if no objections</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>026</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SH:
Envelopes and Payloads</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
08/04: Not discussed explicity, but recursive use of DFDL is tied up with
this</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: Two aspects. Firstly compositional - do sufficient mechanisms exist to
model an envelope with a payload that varies. Secondly markup syntax - this
might be defined in the envelope. <br>
The second of these is very much tied up with the variable markup action 028,
so will be considered there. SH to verify the composition aspect.</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
29/04: SH and AP working on proposal. related to Action 028</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>027</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SH:
Property precedence tables</span> <span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'><br>
08/04: Not discussed</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: Two things missing from the existing precedence trees. Firstly, does
not show alternates (eg, initiator v initiatorkind). Secondly, need a tree
per concrete DFDL object (eg, element). SH to update.</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
29/04: No progress</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>028</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SH:
Variable markup <br>
08/04: Discussed briefly at end of call, IBM to see whether there any use
cases that require recursive use of DFDL.</span> <span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
15/04: Use case was distributed and will be discussed on next call.</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: The use case in question is EDI where the terminating markup for the
payload segments is defined in the ISA envelope segment. The markup is
modelled as an element of simple type where the allowable markup values are
defined as enums on the type. But we need to handle two cases - firstly where
the envelope is present, so the value used by the payload is taken from the
envelope. Secondly where only the payload is present. Here we need a way of
scanning for all the enum values, and adopting the one we actually find, when
parsing. And using a default when unparsing. SH to explore use of a DFDL
variable, where the variable has a default, but also has a type that is the
same as the markup element - that way we get to use the enums without
defining everything twice.</span> <span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'><br>
29/04: SH and AP working on proposal.</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>029</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>MB:
valueCalc (output length calculation)</span> <span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
08/04: Not discussed</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: Action allocated to MB, this is to complete the work started at the
Hursley WG F2F meeting.</span> <span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'><br>
29/04: No progress</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>032</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>DG:
Investigate compatibility between DFDL infoset and XDM</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
08/04: No update</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: No update</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
29/04: No update</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>033</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>AP/TK:
Assert/Discriminator semantics. AP to document. TK to check uses of
discriminator besides choice.</span> <span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
08/04: In progress within IBM</span> <span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
22/04: Waiting for TK to return from leave to complete. <br>
29/04: TK has sent examples shown need for discriminators beyond choice. Agreed.
MB to respond to TK </span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>036</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SH:
Provide use case for floating component in a sequence</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
08/04: Raised</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
15/04: Use case sent and discussed. SH to do further investigation</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: IBM feedback from WTX team is that alternate suggested ways of
modelling the EDI floating NTE segment have significant usability issues. The
DFDL principle is that for a problem that can be expressed as two-layered,
then two DFDL models are needed. The EDI NTE segment does not fall into
this though, as its use is on a per sequence basis. Ongoing. <br>
29/04: Agreed that need to be in V1. SH to make a proposal</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>037</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>All:
Approach for XML Schema 1.0 UPA checks.</span> <span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
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: <br>
a)DFDL parser/unparser will not implement some/all UPA checks (exact checks
tbd)</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
b) XML Schema editors that implement UPA checks will not be suitable for all
DFDL models</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
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)</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
Ongoing in case another solution can be found.</span> <span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><br>
29/04: Will ask DG and S Gao for oppinion before closing</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>038</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>MB:
Submit response to OMG RFI for non-XML standardization</span> <span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
22/04: First step is for MB to mail the OGF Data Area chair to say that we
want to submit</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
29/04: MB has been in contact with OMG and will sunbit dfdl.</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>039</span></b><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SKK:
Approach for creating Schema-For-DFDL xsds. <br>
22/04: Resolve issue around multiple declarations needed for DFDL properties,
perhaps using MB's meta approach</span> <span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
29/04: Don't like qualified attributes in long form. SKK to check there are
no code gen implications, eg EMF.</span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><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</span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<i><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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</span></i>
<br>
<br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>--</tt><br>
<tt>dfdl-wg mailing list</tt><br>
<tt>dfdl-wg@ogf.org</tt><br>
</span><a href="http://www.ogf.org/mailman/listinfo/dfdl-wg" target="_blank"><tt><span
style='font-size:10.0pt'>http://www.ogf.org/mailman/listinfo/dfdl-wg</span></tt></a>
<o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><i><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><br>
</span></i><br>
<i><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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</span></i>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
</span><br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
</span><tt><span style='font-size:10.0pt'>--</span></tt><span style='font-size:
10.0pt;font-family:"Courier New"'><br>
<tt> dfdl-wg mailing list</tt><br>
<tt> dfdl-wg@ogf.org</tt><br>
<tt> http://www.ogf.org/mailman/listinfo/dfdl-wg</tt></span> <br>
<br>
<o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<p><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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</span></i>
<o:p></o:p></p>
<p style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
<br>
<br>
</span><o:p></o:p></p>
</div>
</body>
</html>