[Bug 26750] New: [XSLT30] Editorial: Summary of typos, link issues, errors in code examples etc

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26750

            Bug ID: 26750
           Summary: [XSLT30] Editorial: Summary of typos, link issues,
                    errors in code examples etc
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

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"

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 8 September 2014 00:39:52 UTC