26750 2014-09-08 00:39:50 +0000 [XSLT30] Editorial: Summary of typos, link issues, errors in code examples etc 2014-09-12 10:32:54 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC Windows NT CLOSED FIXED P5 trivial --- 1 abel.braaksma mike public-qt-comments oldest_to_newest 111149 0 abel.braaksma 2014-09-08 00:39:50 +0000 This issue lists some of the editorial things I found during read-throughs of sections. I doublechecked with the latest internal Draft of Sept 5, 2014. All through the document, consistency: - implementer(s) (16x) vs implementor(s) (3x) - data type(s) (4x) vs datatype(s) (34x) - subexpression(s) (7x) vs sub-expression(s) (6x) - can not (2x) vs cannot (88x) - lookahead (1x) vs look-ahead (5x) - non-deterministic (1x) vs nondeterministic (7x) (also in XP30) - etc (6x) vs etc. (3x) (missing dot) - rfc2119 vs RFC2119 (all other RFCs are with capitals) - "Content: (sequence-constructor)" (6x) vs "Content: sequence-constructor" (58x) - "Javascript" (1x) vs "JavaScript" (2x) - "arabic" (1x) vs "Arabic" (1x) Spelling choices (I think the preferred spelling should be different) - dereferencable (1x) --> dereferenceable (based on spelling of referenceable) - zeroeth (1x) --> zeroth - judgement (5x) --> judgment Spelling errors/typos: - everywhere "a x..." --> "an x..." (10x) - everywhere "the the " --> "the " (5x) (except 19.8.4.5) - everywhere "a EQName" --> "an ..." (7x) - everywhere "a expanded QName" --> "an..." (4x) - everywhere "decribed" --> "described" (2x) - everywhere "compenenents" --> "components" (2x) - everywhere "styelsheet" --> "stylesheet" (2x) - everywhere "feaure" (3x) --> "feature" - 1.1, 2nd para and 17.1, 2nd list, 2.d: "of of" --> "of" - 2.3.6, base output URI definition, rogue space fore closing "]": "relative to this base URI. ]" - 2.10, 2nd list, 4th bullet, "classical example" --> "classic example" - 3.6.3, "an symbolic reference", "an" --> "a" - 3.6.5, 5th para "An xsl:namespace-alias declarations" --> "An xsl:namespace-alias declaration" (singular) - 3.6.3.2, 2nd para, "exposed visiblity" --> "exposed visibility" - 3.11 missing closing paren in the last para of last Note - 3.13, 1st Note, "or if is" --> "or if it is" - 5.8.2, "an value template", "an" --> "a" - 6.5, item #3, "a IntersectExceptExprP", "a" --> "an" - 6.6.1, in table, last cell, "the value private.A" --> "...private. A" (space) - 6.7.3, last Note, 1st para, missing closing quote: 'the traditional select="node() | @*' - 10, definition of "invocation constructs", "The following construct are" --> "constructs" (plural) - same in C, Glossary - 10.2.4, first bullet, "an use-attribute-sets" --> "a [...]" - 13.1.3 5th para "imlementation" --> "implementation" - 14.1, 12th para, starting with "f the group-adjacent" --> "If the group-adjacent" - 15.6, last para, "parmameters" --> "parameters" - 18.1.1, last para of Note, "analyis" --> "analysis" - 18.2.1, 2nd para after Note, "exeecution" --> "execution" - 18.2.2 last para, "a a rule" --> "a rule" - 18.2.8, 3rd example, "thenstack" --> "the stack" - 18.4, under Rules, 2nd para "seequence" --> "sequence" - 19, 7th para, "instructon" --> "instruction" - 19.4, 2nd bullet point, "(or other item). or" --> "(or other item), or" - 19.4.1, 1st example, list #3, "instrunction" --> "instruction" - 19.4.1, 2nd example, "as a inspection" --> "as inspection" - 19.8.1, item 1.c.i, "adjusted sweep" --> "adjusted sweep S'" (as elsewhere in this section) - 19.8.2, "an choice operand group", "an" --> "a" - 19.8.4.5 #3 in list, "[...]the the current mode[...]" --> "that the" - 19.8.4.10 "expresssions" --> "expressions" - 19.8.15, 1st Note, 2nd para "aread" --> "ahead" - 19.9, 3rd example, #2.c.ii, "establised" --> "established" - 19.9, 3rd example, #6, "containined" --> "contained" - 21.1.4, missing space in "[ERR XPTY0004] XP30occurs" (before "occurs") - 23.1.1, last para under Notes, "anr" --> "and" - 23.2.2, under Rules, 1st para, "the it is" --> "then it is" - C Glossary, item "potentially consuming", ends with colon ":", but nothing after it - L, item #110, "cose" --> "case" - L, item #136, "practise" --> "practice" - M, item #6, "practise" --> "practice" - XTSE3280 (2x) "has has" --> "has" Coding errors/typos (potentially not just editorial): - 3.5, "[xsl:]default-validaion" --> "[xsl:]default-validation" - 5.7.2, first ex., newline just before ">" (can be left on same line as instruction) - 6.7.x: some examples use mode="M", some don't, sometimes it is mixed for examples in one section. I think the mode="M" can be removed for all "equivalency" coding examples. - 6.7.1, built-in template rule, 2nd example, is not legal syntax: match="text()|@*|xs:anyAtomicType" - 6.7.1, para before green example block, contains function items, this is not allowed: <xsl:template match="processing-instruction()|comment()|namespace-node()|function(*)" mode="M"/> - 8.3.2 "FAOR0001" --> "FOAR0001" - 18.2.8 last example, "pap:put" --> "map:put" - 19.8.2, example "if ($gratis) then 0 else price else", remove last "else" Layout / font-choice / links etc errors: - 3.14.2, 2nd coding example, wrong indentation 2nd line. - 6.5, item #4, PredicateList is not linked (other productions in this section are) - 6.7.1, last example, just before the green block of "Example: Using a Build-in Template Rule", the grey block is connected with it. A paragraph (whiteline) seems appropriate here. - 10, definition of "invocation constructs", the link to "stylesheet functions" goes haywire (duplicated) - same in C Glossary - 15.4, 2nd para, "current-merge-group()" is not hyperlinked, other fu's are - 19.2, table under VarRef[55], 2nd col, "$V" should be in Courier - 19.8.8.14 first para "If the context posture for a cll on the last[...]", link should point to "context posture", not "posture" 111167 1 mike 2014-09-08 12:13:32 +0000 All through the document, consistency: - implementer(s) (16x) vs implementor(s) (3x) Switched to -er though I personally prefer -or. - data type(s) (4x) vs datatype(s) (34x) Switched to datatype in line with XSD part 2 - subexpression(s) (7x) vs sub-expression(s) (6x) Switched to subexpression - can not (2x) vs cannot (88x) Switched to cannot - lookahead (1x) vs look-ahead (5x) Switched to look-ahead - non-deterministic (1x) vs nondeterministic (7x) (also in XP30) Switched to nondeterministic - etc (6x) vs etc. (3x) (missing dot) SWitched to etc. - rfc2119 vs RFC2119 (all other RFCs are with capitals) Hopefully fixed (if I understand the machinery right...) - "Content: (sequence-constructor)" (6x) vs "Content: sequence-constructor" (58x) Fixed. - "Javascript" (1x) vs "JavaScript" (2x) Fixed - "arabic" (1x) vs "Arabic" (1x) I think the distinction is correct Spelling choices (I think the preferred spelling should be different) - dereferencable (1x) --> dereferenceable (based on spelling of referenceable) Fixed - zeroeth (1x) --> zeroth I prefer zeroeth but OED has zeroth, so OK. - judgement (5x) --> judgment Allthough Judgment is the american spelling, and therefore w3c-preferred (or prefered), all 5 usages refer to the XPath use of the term, which is spelt judgement. Anyway, I prefer judgement. Spelling errors/typos: - everywhere "a x..." --> "an x..." (10x) fixed - everywhere "the the " --> "the " (5x) (except 19.8.4.5) fixed - everywhere "a EQName" --> "an ..." (7x) fixed - everywhere "a expanded QName" --> "an..." (4x) fixed - everywhere "decribed" --> "described" (2x) fixed - everywhere "compenenents" --> "components" (2x) not found - everywhere "styelsheet" --> "stylesheet" (2x) fixed - everywhere "feaure" (3x) --> "feature" fixed - 1.1, 2nd para and 17.1, 2nd list, 2.d: "of of" --> "of" fixed - 2.3.6, base output URI definition, rogue space fore closing "]": "relative to this base URI. ]" fixed - 2.10, 2nd list, 4th bullet, "classical example" --> "classic example" if you insist - 3.6.3, "an symbolic reference", "an" --> "a" fixed - 3.6.5, 5th para "An xsl:namespace-alias declarations" --> "An xsl:namespace-alias declaration" (singular) fixed - 3.6.3.2, 2nd para, "exposed visiblity" --> "exposed visibility" fixed - 3.11 missing closing paren in the last para of last Note not found - 3.13, 1st Note, "or if is" --> "or if it is" fixed - 5.8.2, "an value template", "an" --> "a" fixed - 6.5, item #3, "a IntersectExceptExprP", "a" --> "an" fixed - 6.6.1, in table, last cell, "the value private.A" --> "...private. A" (space) browser rendering problem? - 6.7.3, last Note, 1st para, missing closing quote: 'the traditional select="node() | @*' fixed - 10, definition of "invocation constructs", "The following construct are" --> "constructs" (plural) already fixed - same in C, Glossary - 10.2.4, first bullet, "an use-attribute-sets" --> "a [...]" fixed - 13.1.3 5th para "imlementation" --> "implementation" fixed - 14.1, 12th para, starting with "f the group-adjacent" --> "If the group-adjacent" fixed - 15.6, last para, "parmameters" --> "parameters" fixed - 18.1.1, last para of Note, "analyis" --> "analysis" fixed - 18.2.1, 2nd para after Note, "exeecution" --> "execution" fixed - 18.2.2 last para, "a a rule" --> "a rule" fixed - 18.2.8, 3rd example, "thenstack" --> "the stack" fixed - 18.4, under Rules, 2nd para "seequence" --> "sequence" fixed - 19, 7th para, "instructon" --> "instruction" fixed - 19.4, 2nd bullet point, "(or other item). or" --> "(or other item), or" fixed - 19.4.1, 1st example, list #3, "instrunction" --> "instruction" fixed - 19.4.1, 2nd example, "as a inspection" --> "as inspection" fixed - 19.8.1, item 1.c.i, "adjusted sweep" --> "adjusted sweep S'" (as elsewhere in this section) fixed - 19.8.2, "an choice operand group", "an" --> "a" fixed - 19.8.4.5 #3 in list, "[...]the the current mode[...]" --> "that the" actually => "then the" - 19.8.4.10 "expresssions" --> "expressions" fixed - 19.8.15, 1st Note, 2nd para "aread" --> "ahead" fixed - 19.9, 3rd example, #2.c.ii, "establised" --> "established" fixed - 19.9, 3rd example, #6, "containined" --> "contained" fixed - 21.1.4, missing space in "[ERR XPTY0004] XP30occurs" (before "occurs") fixed - 23.1.1, last para under Notes, "anr" --> "and" fixed - 23.2.2, under Rules, 1st para, "the it is" --> "then it is" fixed - C Glossary, item "potentially consuming", ends with colon ":", but nothing after it tricky to fix because a term definition can't cross a paragraph boundary - L, item #110, "cose" --> "case" fixed - L, item #136, "practise" --> "practice" I must improve my knowledge of American spelling. - M, item #6, "practise" --> "practice" do. - XTSE3280 (2x) "has has" --> "has" fixed Coding errors/typos (potentially not just editorial): - 3.5, "[xsl:]default-validaion" --> "[xsl:]default-validation" fixed - 5.7.2, first ex., newline just before ">" (can be left on same line as instruction) it was intended to be this way. - 6.7.x: some examples use mode="M", some don't, sometimes it is mixed for examples in one section. I think the mode="M" can be removed for all "equivalency" coding examples. I suspect you are right. - 6.7.1, built-in template rule, 2nd example, is not legal syntax: match="text()|@*|xs:anyAtomicType" Fixed by separating this into two rules - 6.7.1, para before green example block, contains function items, this is not allowed: <xsl:template match="processing-instruction()|comment()|namespace-node()|function(*)" mode="M"/> Split this one too. - 8.3.2 "FAOR0001" --> "FOAR0001" fixed - 18.2.8 last example, "pap:put" --> "map:put" already fixed. - 19.8.2, example "if ($gratis) then 0 else price else", remove last "else" fixed. Layout / font-choice / links etc errors: - 3.14.2, 2nd coding example, wrong indentation 2nd line. already fixed - 6.5, item #4, PredicateList is not linked (other productions in this section are) fixed - 6.7.1, last example, just before the green block of "Example: Using a Build-in Template Rule", the grey block is connected with it. A paragraph (whiteline) seems appropriate here. added a non-white para, since white paras get stripped. - 10, definition of "invocation constructs", the link to "stylesheet functions" goes haywire (duplicated) - same in C Glossary fixed - 15.4, 2nd para, "current-merge-group()" is not hyperlinked, other fu's are fixed - 19.2, table under VarRef[55], 2nd col, "$V" should be in Courier fixed - 19.8.8.14 first para "If the context posture for a cll on the last[...]", link should point to "context posture", not "posture" fixed 111385 2 abel.braaksma 2014-09-11 14:12:51 +0000 > - everywhere "compenenents" --> "components" (2x) > not found it was "compenents", typo about a typo ;). > - 6.6.1, in table, last cell, "the value private.A" --> "...private. A" (space) > browser rendering problem? No, in fact the HTML source misses it too. The word "private" is within <code> tags. Anyway, I guess we have better things to do than to fix a missing space ;). > - 3.11 missing closing paren in the last para of last Note > not found I can't find it either, but on a new regex search, I saw missing closing parens in: 2.3.6 "(such as xsl:result-document are evaluated that depend on the value of the base output URI." 3.6.2 (in Note) "(to link to the implementation of these components so they can be invoked. A failure to locate a package may cause an error at either stage." 10.3.9 (in Example: a Higher-Order Function) " (for example, whether one person is among the staff managed directly or indirectly by a manager, or whether one parcel of land is contained directly or indirectly within another parcel. " 12.2 (before examples, also note typo in "the is then") " (the is then converted into a string using the effective values of the attributes specified in 12.3 Number to String Conversion Attributes; each of these attributes is interpreted as an attribute value template. " 19.2 (Note under table) "(on the grounds that an xs:duration or xs:dateTime has no effective boolean value, and static type inference only needs to consider the type of non-error results" Note: I searched, but did not find missing opening parens. 111431 3 mike 2014-09-12 10:32:41 +0000 I have dealt with the additional points in comment #2. Regarding the built-in template rules, I have added mode="M" to all cases where it was absent, for consistency.