24466 2014-02-02 02:05:28 +0000 Editorial issues in XSLT 3.0 Last-call draft (missing text, missing link targets) 2014-02-24 15:10:45 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC All CLOSED FIXED P2 trivial --- 1 cmsmcq mike public-qt-comments oldest_to_newest 99576 0 cmsmcq 2014-02-02 02:05:28 +0000 Some issues in the text of the XSLT 3.0 Last Call draft have come to my attention. Missing link targets for (some occurrences of) the terms dynamic error, type error, implementation-dependent. These appear in sections 20.2.2, 21.1.2.7, 21.2.2, Appendix E, and possibly others. It may be simplest to search for XHTML 'a' elements with href="#". Missing text (and also a link with href="#") in 21.2.2 fn:json-to-xml (after "not"): "The function is not : that is, if the function is called twice with the same arguments, it is implementation-dependent whether the same node is returned on both occasions." I don't know why the link checker didn't find these. 101229 1 mike 2014-02-24 11:52:32 +0000 I think what is happening here is that the build relies on DTD-based ID/IDREF checking to ensure that termref elements refer to a matching term; but text that is incorporated (by an XSLT processing phase) from the separate function-catalog.xml file is not subjected to ID/IDREF validation, and therefore dangling references go undetected. Because the generated HTML links to '#'. which is a valid link, the HTML link checker doesn't catch it either. I have added a stylesheet to the pipeline to check these internal references. Interestingly, this finds quite a few errors where the link target is present but is of the wrong kind; e.g. a termref that is satisfied by a section ID rather than by a termdef ID. ID/IDREF checking of course won't spot this problem. I have fixed the errors this finds without making a specific list and without change highlighting.