There should hopefully be some index entries to follow
21 |This pipeline executes an XSpec test suite with the Saxon embedded in Calabash.
25 |Primary input: A XSpec test suite document.
26 |Primary output: A formatted HTML XSpec report.
27 |
13 | An O'Reilly Media Publication
19 |All Rights Reserved
23 |
24 | This is the Preface
29 |SVG element:
30 | 31 |You must know…
34 |Here come a couple sect1s
39 |Here's an image
42 |
44 | Here's a MathML element
46 | 47 |Here come a couple sect2s
48 |Here's another image
51 |
53 | Here come a couple sect3s
55 |Here's an image we used once before:
58 |
59 | SVG element:
60 | 61 |Here come a couple sect4s
62 |Here come a couple sect5s
65 |This is one sect5
68 |This is another sect5
72 |This is another sect4
77 |This is another sect3
82 |This is another sect2
87 |This is another sect1
92 |For good measure
95 |Throwing in another sect1 for fun
101 |Getting tired of a complete lack of content here?
104 |Important appendix material
109 |Here's a MathML element
110 | 111 |Subsection
114 |Sub-subsection
117 |Sub-sub-subsection
120 |This would be a glossary, if it had any content!
129 |This would be a bibliography, if it had any content!
133 |This pipeline executes an XSpec test suite with the Saxon embedded in Calabash.
23 |Primary input: A XSpec test suite document.
24 |Primary output: A formatted HTML XSpec report.
25 |The dir where you unzipped the XSpec archive on your filesystem is passed 26 | in the option 'xspec-home'.
27 |This pipeline executes an XSpec test suite on a MarkLogic instance.
26 |Primary input: A XSpec test suite document.
27 |Primary output: A formatted HTML XSpec report.
28 |The XQuery library module to test must already be on the MarkLogic 29 | instance. The instance endpoint is passed in the option 'endpoint'. The 30 | runtime utils library (also known as generate-query-utils.xql) must also 31 | be on the instance (its location hint, that is the 'at' clause to use) is 32 | passed in the option 'utils-lib'. The dir where you unzipped the XSpec 33 | archive on your filesystem is passed in the option 'xspec-home'.
34 |This pipeline executes an XSpec test suite on an eXist instance.
26 |Primary input: A XSpec test suite document.
27 |Primary output: A formatted HTML XSpec report.
28 |The XQuery library module to test must already be on the eXist instance 29 | (its URI is passed through the option 'query-at'). The instance endpoint 30 | is passed in the option 'endpoint'. The runtime utils library (also known 31 | as generate-query-utils.xql) must also be on the instance (its location 32 | hint, that is the 'at' clause to use) is passed in the option 'utils-lib'. 33 | The dir where you unzipped the XSpec archive on your filesystem is passed 34 | in the option 'xspec-home'.
35 |This pipeline executes an XSpec test suite with BaseX standalone.
26 |Primary input: A XSpec test suite document.
27 |Primary output: A formatted HTML XSpec report.
28 |The dir where you unzipped the XSpec archive on your filesystem is passed 29 | in the option 'xspec-home'. The compiled test suite (the XQuery file to be 30 | actually evaluated) is saved on the filesystem to be passed to BaseX. The 31 | name of this file is passed in the option 'compiled-file' (it defaults to a 32 | file in /tmp). The BaseX JAR file is passed through 'basex-jar'.
33 |This pipeline executes an XSpec test suite with Zorba.
26 |Primary input: A XSpec test suite document.
27 |Primary output: A formatted HTML XSpec report.
28 |The dir where you unzipped the XSpec archive on your filesystem is passed 29 | in the option 'xspec-home'. The compiled test suite (the XQuery file to be 30 | actually evaluated) is saved on the filesystem to be passed to Zorba. The 31 | name of this file is passed in the option 'compiled-file' (it defaults to a 32 | file in /tmp). It relies on a script called 'zorba' being available in the 33 | system's $PATH.
34 |This pipeline executes an XSpec test suite on a BaseX server instance.
26 |Primary input: A XSpec test suite document.
27 |Primary output: A formatted HTML XSpec report.
28 |The XQuery library module to test must already be on the BaseX instance 29 | (its URI is passed through the option 'query-at'). The instance endpoint 30 | is passed in the option 'endpoint'. The runtime utils library (also known 31 | as generate-query-utils.xql) must also be on the instance (its location 32 | hint, that is the 'at' clause to use) is passed in the option 'utils-lib'. 33 | The dir where you unzipped the XSpec archive on your filesystem is passed 34 | in the option 'xspec-home'. User credentials are passed through options 35 | 'username' and 'password'.
36 ||
84 | |
87 |
88 | |
92 |
|---|---|
|
110 | |
122 |
123 | |
127 |
15 | This schema document describes the XML namespace, in a form 16 | suitable for import by other schema documents. 17 |
18 |19 | See 20 | http://www.w3.org/XML/1998/namespace.html and 21 | 22 | http://www.w3.org/TR/REC-xml for information 23 | about this namespace. 24 |
25 |26 | Note that local names in this namespace are intended to be 27 | defined only by the World Wide Web Consortium or its subgroups. 28 | The names currently defined in this namespace are listed below. 29 | They should not be used with conflicting semantics by any Working 30 | Group, specification, or document instance. 31 |
32 |33 | See further below in this document for more information about how to refer to this schema document from your own 35 | XSD schema documents and about the 36 | namespace-versioning policy governing this schema document. 37 |
38 |50 | denotes an attribute whose value 51 | is a language code for the natural language of the content of 52 | any element; its value is inherited. This name is reserved 53 | by virtue of its definition in the XML specification.
54 | 55 |59 | Attempting to install the relevant ISO 2- and 3-letter 60 | codes as the enumerated possible values is probably never 61 | going to be a realistic possibility. 62 |
63 |64 | See BCP 47 at 65 | http://www.rfc-editor.org/rfc/bcp/bcp47.txt 66 | and the IANA language subtag registry at 67 | 68 | http://www.iana.org/assignments/language-subtag-registry 69 | for further information. 70 |
71 |72 | The union allows for the 'un-declaration' of xml:lang with 73 | the empty string. 74 |
75 |96 | denotes an attribute whose 97 | value is a keyword indicating what whitespace processing 98 | discipline is intended for the content of the element; its 99 | value is inherited. This name is reserved by virtue of its 100 | definition in the XML specification.
101 | 102 |119 | denotes an attribute whose value 120 | provides a URI to be used as the base for interpreting any 121 | relative URIs in the scope of the element on which it 122 | appears; its value is inherited. This name is reserved 123 | by virtue of its definition in the XML Base specification.
124 | 125 |126 | See http://www.w3.org/TR/xmlbase/ 128 | for information about this attribute. 129 |
130 |142 | denotes an attribute whose value 143 | should be interpreted as if declared to be of type ID. 144 | This name is reserved by virtue of its definition in the 145 | xml:id specification.
146 | 147 |148 | See http://www.w3.org/TR/xml-id/ 150 | for information about this attribute. 151 |
152 |172 | denotes Jon Bosak, the chair of 173 | the original XML Working Group. This name is reserved by 174 | the following decision of the W3C XML Plenary and 175 | XML Coordination groups: 176 |
177 |178 |185 |179 | In appreciation for his vision, leadership and 180 | dedication the W3C XML Plenary on this 10th day of 181 | February, 2000, reserves for Jon Bosak in perpetuity 182 | the XML name "xml:Father". 183 |
184 |
197 | This schema defines attributes and an attribute group suitable
198 | for use by schemas wishing to allow xml:base,
199 | xml:lang, xml:space or
200 | xml:id attributes on elements they define.
201 |
203 | To enable this, such a schema must import this schema for 204 | the XML namespace, e.g. as follows: 205 |
206 |207 | <schema . . .> 208 | . . . 209 | <import namespace="http://www.w3.org/XML/1998/namespace" 210 | schemaLocation="http://www.w3.org/2001/xml.xsd"/> 211 |212 |
213 | or 214 |
215 |216 | <import namespace="http://www.w3.org/XML/1998/namespace" 217 | schemaLocation="http://www.w3.org/2009/01/xml.xsd"/> 218 |219 |
220 | Subsequently, qualified reference to any of the attributes or the 221 | group defined below will have the desired effect, e.g. 222 |
223 |224 | <type . . .> 225 | . . . 226 | <attributeGroup ref="xml:specialAttrs"/> 227 |228 |
229 | will define a type which will schema-validate an instance element 230 | with any of those attributes. 231 |
232 |243 | In keeping with the XML Schema WG's standard versioning 244 | policy, this schema document will persist at 245 | 246 | http://www.w3.org/2009/01/xml.xsd. 247 |
248 |249 | At the date of issue it can also be found at 250 | 251 | http://www.w3.org/2001/xml.xsd. 252 |
253 |254 | The schema document at that URI may however change in the future, 255 | in order to remain compatible with the latest version of XML 256 | Schema itself, or with the XML namespace itself. In other words, 257 | if the XML Schema or XML namespaces change, the version of this 258 | document at 259 | http://www.w3.org/2001/xml.xsd 260 | 261 | will change accordingly; the version at 262 | 263 | http://www.w3.org/2009/01/xml.xsd 264 | 265 | will not change. 266 |
267 |268 | Previous dated (and unchanging) versions of this schema 269 | document are at: 270 |
271 | 281 |It was the best of times!
85 |It was the worst of times!
98 |Two roads diverged in a wood
101 |One fish, two fish, red fish, blue fish
104 |No NCX TOC entry for this section
108 |It was a dark and stormy night
114 |It was the best of times!
138 |This section shouldn't show up in the TOC
152 |It was the best of times!
157 |Notes should not get navPoints!!!
167 |Read me, please!
205 |Read me, please!
242 |