<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 14 (filtered medium)">
<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: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:#6E747A;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#6E747A;}
.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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#6E747A">Interesting. I was actually worried about the producer case.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A">In Office “15” we’ve implemented the ability to save customer documents using the Strict syntax. If WG4 was to remove one of the two syntaxes you mention below, we’d then be generating non-compliant files, right?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A"><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""> Francis Cave [mailto:francis@franciscave.com]
<br>
<b>Sent:</b> Tuesday, February 21, 2012 7:15 AM<br>
<b>To:</b> e-SC34-WG4@ecma-international.org<br>
<b>Subject:</b> RE: What is or is not a legacy feature?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Hi Shawn<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Obviously these would be breaking changes for consumers, given the way we have defined Strict (i.e. everything that is currently in Part 1), but not for producers. We might wish to consider giving
some guidance to producer implementers in such cases. But let’s see what the Word guys have to say…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><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
<a href="mailto:[mailto:shawnv@microsoft.com]">[mailto:shawnv@microsoft.com]</a> <br>
<b>Sent:</b> 21 February 2012 15:09<br>
<b>To:</b> <a href="mailto:francis@franciscave.com">francis@franciscave.com</a>; <a href="mailto:e-SC34-WG4@ecma-international.org">
e-SC34-WG4@ecma-international.org</a><br>
<b>Subject:</b> RE: What is or is not a legacy feature?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A">Interesting. Let me ask the Word guys to get back to you on this.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A">I do feel compelled to point out that if we were to remove one of the constructs from Strict, it’s a breaking change, which we try to avoid. But I’m sure everyone knows that …<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A">I’ll try to get you a response by the end of the week.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#6E747A"><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""> Francis Cave
<a href="mailto:[mailto:francis@franciscave.com]">[mailto:francis@franciscave.com]</a>
<br>
<b>Sent:</b> Tuesday, February 21, 2012 7:08 AM<br>
<b>To:</b> <a href="mailto:e-SC34-WG4@ecma-international.org">e-SC34-WG4@ecma-international.org</a><br>
<b>Subject:</b> RE: What is or is not a legacy feature?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">While I think of it, the same issue arises with two run properties in WordprocessingML: w:highlight and w:shd. Although section 17.3.2.15 does document the interaction between these two elements,
as far as I can see anything that be expressed using w:highlight (which only controls background colour, and only uses colour names) can be expressed using w:shd. This suggests that any new producer implementation of WML Strict would probably not implement
both ways, and would probably choose to implement w:shd as the more powerful of the two. This in turn suggests that w:highlight could be considered to be a legacy feature.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><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""> Francis Cave
<a href="mailto:[mailto:francis@franciscave.com]">[mailto:francis@franciscave.com]</a>
<br>
<b>Sent:</b> 21 February 2012 14:58<br>
<b>To:</b> 'e-SC34-WG4@ecma-international.org'<br>
<b>Subject:</b> What is or is not a legacy feature?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I have recently needed to review the way that form controls can be represented in OOXML. It seems that there are two approaches, and both of these are documented in Part 1. The first approach is to use fields as documented
in section 17.16. The second approach is to use structured document tags as documented in section 17.5.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">There seems to be a fair amount of overlap in functionality between these two approaches, and this has caused me to wonder whether one of these (probably the use of fields) should be considered a “legacy” approach and
moved to Part 4.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">There appears to be some support for doing just that in an unlikely place: in the Microsoft Word 2007 / 2010 user interface. The tools for inserting form fields into a document are grouped together in a box labelled “Legacy
Forms”.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I’d be interested to hear expert opinions on this.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Francis<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>