From: Susan Lesch <lesch@w3.org>

Date: Sun, 28 Jan 2001 02:01:49 -0800

Message-Id: <p0501040ab6999a216234@[204.210.33.45]>

To: www-math@w3.org

Date: Sun, 28 Jan 2001 02:01:49 -0800

Message-Id: <p0501040ab6999a216234@[204.210.33.45]>

To: www-math@w3.org

Here are comments on the MathML 2.0 Proposed Recommendation [1]. I used a better spell checking method and found more typos (a few of which are holdovers from the Candidate Recommendation). Please use these suggestions, or not, as you see fit. Two small structural changes are needed. First, a conformance chapter should be evident from the front table of contents. I would break out the relevant parts of section 7.2.1 into a separate page called "Conformance." Second, Appendix K needs a normative section. Especially to help the conformance chapter, and also to be clear, you could make RFC 2119 a normative reference and quote this part: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Please see RFC 2119 at http://www.ietf.org/rfc/rfc2119.txt. If you don't wish to use this RFC, then these words need definitions. If you don't like the RFC-style caps, then here is an alternate idea: <p>The key words <strong>must,</strong> <strong>must not</strong>, <strong>required</strong>, <strong>shall</strong>, <strong>shall not</strong>, <strong>should</strong>, <strong>should not</strong>, <strong>recommended</strong>, <strong>may</strong>, and <strong>optional</strong> in this document are to be interpreted as described in [<a href="appendixk.html#RFC2119">RFC2119</a>].</p> Globally, "whitespace" is two words, "white space" (see http://www.w3.org/TR/REC-xml#sec-white-space). Also globally, "braces" are "curly brackets," and "blanks" are "spaces" (see http://www.unicode.org/charts/PDF/U0000.pdf). 3.2.5.2 par. after table is repeated, for the most part, in 3.3.4.2 (mstyle). All six paragraphs of 3.2.2.2 Color-related attributes are repeated in 3.3.4.2 except the mention of mathcolor. They should only appear in one place. From here on a section number is followed by a quote and a suggestion. 2.3.1 par. 3 code point for under consideration code point under consideration 2.4.4.1 second par. after table dicussion discussion 2.4.4.1 third par. after table needs ending period. 2.4.4.3 par. 2 stylesheets style sheets 3.2.1.1 par. 2 and 3, and 3.2.2 pars. 6 and 7 Is "Math Alphabet" a proper noun? http://www.unicode.org/unicode/alloc/Pipeline.html and http://www.egt.ie/standards/iso10646/plane1-roadmap-table.html say "Mathematical Alphanumeric Symbols." From here on, I adopt that. 3.2.1.1 par. 3 in Section 6.2.3 [Mathematical Alphabetic Symbol Characters.]. in Section 6.2.3 [Mathematical Alphanumeric Symbols]. 3.2.2 par. 5 renderers have a complete freedom renderers have complete freedom 3.2.2 third to last par. Tokens elements Token elements 3.2.2.1 par. 2 Math Alphabetic character Mathematical Alphanumeric Symbol 3.2.2.2 par. 1 depreciated color deprecated color 3.2.3.2 last par. Math Alphabet characters Mathematical Alphanumeric Symbols [Mathematical Alphabetic Symbol Characters.] [Mathematical Alphanumeric Symbols] 3.2.5.1 par. 1 braces curly brackets 3.2.6.4 par. 2 in the sum (see Section 3.2.3 [Identifier (mi)], mi). in the sum; (see Section 3.2.3 [Identifier (mi)]). 3.5.5.10 par. 1 a MathML applications a MathML application 3.6.1.1 par. 2 "described in Section 7.2.2 [Handling of Errors] on the treatment of MathML errors." can be cut to "described in Section 7.2.2 [Handling of Errors]." 4.2.3.2 int If both lowlimit and uplimit schema If both lowlimit and uplimit schemata [or schemas] conjuction conjunction 4.3.2.8 ionored ignored 4.4.2.8 par. 4 is a the object is the object 4.4.2.16 par. 3 to ba taken to be taken 4.4.3.6 par. 3 arithemtic arithmetic 4.4.3.18 conjuction conjunction 4.4.5.3 par. 4 contaioning containing 4.4.5.11 laplacian [could be capitalized if Cartesian is] Laplacian 4.4.5.3 par. 5 differentation differentiation 4.4.12.5 [Discussion is repeated under an extra "Example" heading.] 5.1 par. 6 style-sheet style sheet 5.2.1 par. 4 somtimes sometimes 5.3.3 par. 1 accomodate accommodate 5.4.3 par. 2 frought fraught 5.4.3 last par. style-sheet style sheet 6. TOC and heading 6.2.3 Mathematical Alphabetic Symbol Characters. [note ending period needs cutting too] 6.2.3 Mathematical Alphanumeric Symbols 6. TOC and heading (and thus all links), and 6.2.3 par. 2 (twice) and par. 3 and last par. 6.3.6 Mathematical Alphabetic Characters 6.3.6 Mathematical Alphanumeric Symbols ["Mathematical Alphanumeric Symbols" in 6.4.4 list item 2 looks right.] 6. MathML Specification MathML specification 6.2.1 list item 2 Numeric numeric 6.2.1 list item 3 well formed well-formed 6.2.3 par. 2 expected Unicode 3.1 expected in Unicode 3.1 Supplemental Multilingual Plane Secondary Multilingual Plane 6.2.3 last par. acessibility accessibility 6.3 par. 1 Universal Character Set (UCS) UCS [It was expanded in 6.1 par. 4.] evolve Section 6.4.4 evolve, see Section 6.4.4 the Home Page of the W3C Math WG should be consulted (can link again) the W3C Math Working Group home page should be consulted 6.3.2 par. 1 Mathematics mathematics 6.3.3, status in Key for 000.html through 1D7.html not given a MathMl name not given a MathML name 6.4.4 par. 1 UCS (Universal Character Set) UCS [Twice. It was expanded in 6.1 par. 4.] 6.4.4 first list item [Unicode 3.0] and [ISO/IEC 10646-1:2000] need links to Appendix K, and the last one needs a reference. 6.4.4 last list item in September in September 2000 [?] 7. last par. working group [twice] Working Group 7.1.3 par. 4 can be revised and link to [RFC3023] and http://www.ietf.org/rfc/rfc3023.txt can be added in Appendix K (as I imagine you are aware). 8.1.2.2 par. 1 usefullness usefulness C.1 par. 1 (An index to the definitions is provided later in this document.) [Where? Could you link to it here?] C.1.2 signature square braces square brackets C.1.2 function nary n-ary C.2 The Description of MMLdefinitions in C.2.x all say "See also . [?] C.2.2.9 par. 2 itsself itself C.2.3.7 itsself itself C.2.3.22 (compex)->real (complex)->real C.2.4.8 par. 1 quantites quantities C.2.5.6 par. 1 quantifiy quantify C.2.5.8 par. 3 implicitely implicitly C.2.5.10 par. 3 respectivly respectively C.2.8.1 through C.2.8.27 and C.2.11.14 as described in Abramowitz and Stegun, section xx These need to be links, maybe "see [A&S] section xx", to a normative reference in a new "Normative" section of Appendix K. Abramowitz, Milton, Irene A. Stegun (editors), Handbook of Mathematical Fuctions: With Formulas, Graphs, and Mathmetical Tables, Dover Publications Inc., December 1977, ISBN: 0-486-61272-4 C.2.9.1 through C.2.10.7 See CRC Standard Mathematical Tables and Formulae, editor: Dan Zwillinger, CRC Press Inc., 1996, section xx Same here, need to be links, maybe "see [Zwillinger] section xx", to a normative reference in Appendix K. Daniel Zwillinger (editor), Standard Mathematical Tables and Formulae, CRC Press LLC, January 1996, ISBN: 0-849-32479-3 C.2.9.6 par. 1 and C.2.10.6 par. 1 (three times) ith i'th [or use ith globally] D.1.2 MathMLContainer and D.1.3.3 MathMLPresentationContainer arbitarily arbitrarily D.1.3.4 MathMLMultiScriptsElement setSubScriptAt return value chlid child G. Rules desling with Rules dealing with H. Cascading Style Sheets (CSS) A mechanism that allows A language that allows H. MIME multi-media multimedia I. Dave Raggett, W3C (Hewlett Packard), Bristol, UK [twice] Dave Raggett, W3C (Openwave) [I don't know his city.] [If you wish to make historical reference to HP, it is hyphenated, Hewlett-Packard.] I.2 The working group The Working Group K. DOM Level 2 Core is now a Recommendation, with different editors. XLink is now a Proposed Recommendation, with different editors. XPointer is now a Working Draft. Unicode can link to http://www.unicode.org/unicode/standard/standard.html. Also, several references need punctuation between the editor or author's name and the title, and again between the title and publisher. [1] http://www.w3.org/TR/2001/PR-MathML2-20010108/ Best wishes for your project, -- Susan Lesch - mailto:lesch@w3.org tel:+1.858.483.4819 World Wide Web Consortium (W3C) - http://www.w3.org/Received on Sunday, 28 January 2001 05:02:03 UTC

*
This archive was generated by hypermail 2.3.1
: Tuesday, 6 January 2015 21:27:31 UTC
*