OpenDocument 1.2v7-02: 1.5 White Space Processing

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

In Document OpenDocument-v1.2-v7-02.odt

Section 1.5 White Space Processing and EOL Handling

Suggestions: 

1. There is no reason to introduce EOL as a term or refer to it.  
1.1 Remove "and EOL Handling" from the section title
1.2 In the last sentence of the first paragraph, delete the phrase "and
end-of-line (EOL)"
1.3 Use the primary Unicode names for the capitalized names of the Unicode
C0 controls (replace HORIZONTAL TABULATION with CHARACTER TABULATION).
[Unicode 4]
1.4 Avoid C-isms and programming-language-isms and use the Unicode notation
for the code points (U+0009 or '\u0009') or the W3C EBNF notation (if using
that), eg., #x9 (or the ISO EBNF), 
1.5 Oh, and identify whichever notation is chosen.
1.6 Replace the paragraph "One of the following characters may be used to
represent line ends:" with
"Any of the following cases may be used to represent a single line end:"
(You need to decide that you mean that and not newline though.)
1.7 Replace the "All possible line ends are normalized to a single LINE FEED
character" with "The normalized representation of a single line end is a
single LINE FEED character."  (or words to that effect)

2. The statement in OpenFormula material on the same topic needs to be
reconciled with this portion of the OpenDocument specification. 
2.1 OpenFormula identifies LINE FEED with new line (NL and the '\n' C-ism,
Unix-ism), not end of line EOL.  I believe it matters which.  
2.2 There is some looseness about what "&#0D;" and "	" signify, if
anything, outside of quoted strings in OpenFormula encoded in XML attribute
values. 
 
 - Dennis

Dennis E. Hamilton
------------------
NuovoDoc: Design for Document System Interoperability 
mailto:Dennis.Hamilton@acm.org | gsm:+1-206.779.9430 
http://NuovoDoc.com http://ODMA.info/dev/ http://nfoWorks.org