29971 2016-11-01 15:44:42 +0000 [FO31] Strange sentence under "Implementation defined features" checklist 2016-12-16 19:55:20 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 3.1 Candidate Recommendation PC Windows NT CLOSED WORKSFORME P2 editorial --- 1 abel.braaksma mike public-qt-comments oldest_to_newest 128003 0 abel.braaksma 2016-11-01 15:44:42 +0000 The following sentence appears as item 19 in section E Checklist of implementation-defined features: 19. ...either a or t, to indicate alphabetic or traditional numbering respectively, the default being ·implementation-defined·. (See fn:format-integer.) 128004 1 abel.braaksma 2016-11-01 15:46:08 +0000 Actually, this happens more often: 35. ...the format token n, N, or Nn, indicating that the value of the component is to be output by name, in lower-case, upper-case, or title-case respectively. Components that can be output by name include (but are not limited to) months, days of the week, timezones, and eras. If the processor cannot output these components by name for the chosen calendar and language then it must use an ·implementation-defined· fallback representation. (See The picture string.) 36. ...indicates alphabetic or traditional numbering respectively, the default being ·implementation-defined·. This has the same meaning as in the second argument of fn:format-integer. (See The picture string.) 49. ...the processor may use ·implementation-defined· heuristics to determine the likely encoding, otherwise... (See fn:unparsed-text.) So thinking a bit about this, perhaps it is intentional. 128012 2 mike 2016-11-01 17:16:25 +0000 The checklist in appendix E is generated by extracting the "sentence" in which the keyword "implementation-defined" appears. If the "sentence" does not begin with a capital letter (typically because it is extracted from an item in a bulleted list) then it is preceded by an ellipsis. No action.