<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:windowtext;
mso-fareast-language:EN-US;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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 bgcolor=white lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText>Svante hi<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On 1309:10 …<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The XML Rec. says “An XML processor MUST always pass all characters in a document that are not markup through to the application.” <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>This include white space characters. So the spec ODF saying that any white space characters “are ignored” is NOT in conformance with XML – quite the opposite.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If a DTD were in effect a validating processor would be able to label some space as “ignorable” as it was passed through, but it would not be ignored. However, in ODF no DTD is in use.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>As I understand it, ODF wants to invent a equivalent way of having ignorable white space without a DTD. I think my proposed wording achieves that.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>- Alex.<o:p></o:p></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><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></a></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> sc34wg6-bounces@vse.cz [mailto:sc34wg6-bounces@vse.cz] <b>On Behalf Of </b>Svante Schubert<br><b>Sent:</b> 23 June 2010 13:25<br><b>To:</b> sc34wg6@vse.cz<br><b>Subject:</b> Re: REMINDER AND DRAFT AGENDA - Teleconference meeting of WG 6, 2010-06-23 at 13:00 UTC<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Alex,<br><br>On 23.06.2010 13:37, Alex Brown wrote: <o:p></o:p></p><pre>Svante hi<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thanks for this ... a few queries:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>1309:1<o:p></o:p></pre><pre>-------<o:p></o:p></pre><pre>For 1309:1, was there not a constraint here that needed to be expressed? (that variables needed to be declared before use) Or is declaration of variable after use okay?<o:p></o:p></pre><pre> <o:p></o:p></pre><p class=MsoNormal>The current fix is<o:p></o:p></p><table class=MsoNormalTable border=1 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;border:outset black 1.0pt'><thead><tr><td width="13%" valign=top style='width:13.0%;border:inset black 1.0pt;padding:3.0pt 3.0pt 3.0pt 3.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto'>6.3<o:p></o:p></p></td><td width="15%" valign=top style='width:15.0%;border:inset black 1.0pt;padding:3.0pt 3.0pt 3.0pt 3.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto'>Variable Fields<o:p></o:p></p></td><td width="58%" valign=top style='width:58.0%;border:inset black 1.0pt;padding:3.0pt 3.0pt 3.0pt 3.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto'>Delete: <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto'>"In the OpenDocument file format, a variable must be declared at the beginning of a document".<o:p></o:p></p></td><td width="13%" valign=top style='width:13.0%;border:inset black 1.0pt;padding:3.0pt 3.0pt 3.0pt 3.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto'><a href="http://tools.oasis-open.org/issues/browse/OFFICE-2198">N1309:1</a> <o:p></o:p></p></td></tr></thead></table><p class=MsoNormal><br>The variables have to be defined before their usage, as in the schema defined.<br>I have followed Michael Brauer suggestion to remove the sentence, see<br><a href="http://tools.oasis-open.org/issues/browse/OFFICE-2198?focusedCommentId=17405&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_17405">http://tools.oasis-open.org/issues/browse/OFFICE-2198?focusedCommentId=17405&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_17405</a><br><br><o:p></o:p></p><pre>1309:10<o:p></o:p></pre><pre>---------<o:p></o:p></pre><pre>For 1309:10 the proposed new text includes the words:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>"In conformance with the W3C XML specification [XML1.0], white-space characters that are contained in elements that have element content (in other words that must contain elements only but not text) are ignored."<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I don't see how this is in conformance with XML.<o:p></o:p></pre><pre> <o:p></o:p></pre><p class=MsoNormal>Why?<br><br><o:p></o:p></p><pre><o:p> </o:p></pre><pre>I propose something like "An ODF processor shall ignore whitespace in element content for elements not declared to contain text content in the ODF schema". Is this what is meant?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre><p class=MsoNormal>ODF explicilty defines where whitespace have to be preserved and is not using the optional xml:space tag. Still I see no conflict with the XML specification.<br>Perhaps I have missed an argument of yours?<br><br><o:p></o:p></p><pre><o:p> </o:p></pre><pre>1309:7<o:p></o:p></pre><pre>-------<o:p></o:p></pre><pre>I still don't understand what "within two lines" means. Is there some text that can be referenced to help explain this? (or is this clear enough to others?)<o:p></o:p></pre><pre> <o:p></o:p></pre><p class=MsoNormal>The domain expert's opinion on this was that if someone is working on this he might know, for instance by looking up Kumimoji and Warichu.<br>For instance OpenOffice is based on the W3C working draft (see <a href="http://www.w3.org/TR/1999/WD-i18n-format-19990910/#a6-3">http://www.w3.org/TR/1999/WD-i18n-format-19990910/#a6-3</a>) , we are not able to reference by the spec, but are used for OOO to implement.<br><br>On the other hand I am open for any wording suggestion that might express this complex layout environment, without specifying it more than it was before in ODF 1.0<br><br>- Svante.<br><br><o:p></o:p></p><pre><o:p> </o:p></pre><pre>- Alex.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>______________________________________________________________________<o:p></o:p></pre><pre>This email has been scanned by the MessageLabs Email Security System.<o:p></o:p></pre><pre>For more information please visit <a href="http://www.messagelabs.com/email">http://www.messagelabs.com/email</a> <o:p></o:p></pre><pre>______________________________________________________________________<o:p></o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>sc34wg6 mailing list<o:p></o:p></pre><pre><a href="mailto:sc34wg6@vse.cz">sc34wg6@vse.cz</a><o:p></o:p></pre><pre><a href="http://mailman.vse.cz/mailman/listinfo/sc34wg6">http://mailman.vse.cz/mailman/listinfo/sc34wg6</a><o:p></o:p></pre><pre> <o:p></o:p></pre><p class=MsoNormal><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></p></div></div><BR>
______________________________________________________________________<BR>
This email has been scanned by the MessageLabs Email Security System.<BR>
For more information please visit http://www.messagelabs.com/email <BR>
______________________________________________________________________<BR>
</body></html>