<html xmlns="http://www.w3.org/TR/REC-html40" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:11.0pt;
font-family:"Calibri","sans-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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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 vlink="purple" link="blue" lang="EN-US">
<span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; FONT-WEIGHT:Normal;">Shawn,<br>
<br>
Alex is on vacation, so in the absence of any direction from him, let's postpone it.<br>
<br>
Gareth<br>
<br>
<hr>
<span style="font-size:10pt;font-family:Tahoma; font-weight:bold">From: </span><span style="font-size:10pt;font-family:Tahoma; font-weight:normal;">Shawn Villaron <shawnv@microsoft.com></span><br>
<span style="font-size:10pt;font-family:Tahoma; font-weight:bold">Sent: </span><span style="font-size:10pt;font-family:Tahoma; font-weight:normal;">07 April 2010 12:58</span><br>
<span style="font-size:10pt;font-family:Tahoma; font-weight:bold">To: </span><span style="font-size:10pt;font-family:Tahoma; font-weight:normal;">Alex Brown <alexb@griffinbrown.co.uk>; SC 34 WG4 <e-SC34-WG4@ecma-international.org></span><br>
<span style="font-size:10pt;font-family:Tahoma; font-weight:bold">Subject: </span>
<span style="font-size:10pt;font-family:Tahoma; font-weight:normal;">RE: Custom XML on 4/8 WG4 Meeting</span><br>
<br>
</span>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">I never heard back from this request. I’m inclined to push the Custom XML defect reports until the 4/22 meeting unless I hear otherwise. We need to decide on this relatively quickly so I can let Zeyad know
if he’ll be needed during the 4/8 call.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">shawn<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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??=""> Shawn Villaron
<br>
<b>Sent:</b> Tuesday, March 30, 2010 7:02 AM<br>
<b>To:</b> 'Alex Brown'; SC 34 WG4<br>
<b>Subject:</b> RE: Custom XML on 4/8 WG4 Meeting<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks, Alex, for this feedback. It helps us determine what changes we need to make. Both points sound reasonable.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Would you prefer that we move the Custom XML discussion to the conference call on the 22<sup>nd</sup>? I think it is more important to have all of the key contributors available for resolving these defect reports
than it is to have them resolved in the next two weeks. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Again, thanks for the feedback.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">shawn<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??=""> Alex Brown [mailto:alexb@griffinbrown.co.uk]
<br>
<b>Sent:</b> Tuesday, March 30, 2010 2:18 AM<br>
<b>To:</b> Shawn Villaron; SC 34 WG4<br>
<b>Subject:</b> RE: Custom XML on 4/8 WG4 Meeting<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">Dear Shawn, all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">I still think we need to deal with the issue of content defaulting while addressing these fixes, if only to say it is application dependent.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">e.g.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">“If, as a result of validation against a schema, the infoset of the extracted XML is modified, it is application-dependent whether these modifications are included in the extraction result.”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">This then makes this clear as an interop danger area.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">And a minor point – we should not refer to this IS as “Open XML” … that’s for the marketing folks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">I will not be able to make the call on the 8<sup>th</sup>, as I will be on holiday.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">- Alex.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"></a><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<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??=""> Shawn Villaron [mailto:shawnv@microsoft.com]
<br>
<b>Sent:</b> 29 March 2010 18:57<br>
<b>To:</b> SC 34 WG4<br>
<b>Subject:</b> Custom XML on 4/8 WG4 Meeting<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal">Good morning, afternoon and evening.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">According to my count, we’re down to just over 70 active defect reports. I’d like to focus on the Custom XML defect reports for our next teleconference, April 8<sup>th</sup>. I’ve asked Zeyad to attend the call as he is the subject matter
expert for all things Custom XML. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In order to put ourselves in the best possible position to resolve the open Custom XML defect reports, I’d like to ask everyone to spend some time this week reading the attached document. If you have questions, comments or concerns, please
put them in the document or in email and send them to me. We’ll attempt to process all questions, comments and concerns that we received by EOD April 2<sup>nd</sup> in time for the teleconference.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The following defect reports are impacted by the attached document:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">09-0207 GB Request for clarification Further Consideration Required WML: Custom XML and Smart Tags<o:p></o:p></p>
<p class="MsoNormal">09-0208 GB Request for clarification Further Consideration Required WML: Custom XML and Smart Tags<o:p></o:p></p>
<p class="MsoNormal">09-0210 GB Technical defect Further Consideration Required WML: Custom XML and Smart Tags<o:p></o:p></p>
<p class="MsoNormal">09-0211 GB Technical defect Further Consideration Required WML: Custom XML and Smart Tags<o:p></o:p></p>
<p class="MsoNormal">09-0213 GB Technical defect Further Consideration Required WML: Custom XML and Smart Tags<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Time permitting, we’re hoping to have a few more defect report responses ready for everyone, too.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">shawn<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:" TimesNewRoman?,?serif??=""><br>
______________________________________________________________________<br>
This email has been scanned by the MessageLabs Email Security System.<br>
For more information please visit <a href="http://www.messagelabs.com/email">http://www.messagelabs.com/email</a>
<br>
______________________________________________________________________<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:" TimesNewRoman?,?serif??="" lang="EN-GB"><br>
______________________________________________________________________<br>
This email has been scanned by the MessageLabs Email Security System.<br>
For more information please visit <a href="http://www.messagelabs.com/email">http://www.messagelabs.com/email</a>
<br>
______________________________________________________________________<o:p></o:p></span></p>
</div>
</div>
</body>
</html>