glossary.xml 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534
  1. <?xml version="1.0" ?>
  2. <glossary>
  3. <title>Glossary</title>
  4. <glossentry><glossterm>chameleon design</glossterm>
  5. <glossdef>
  6. <para>Specifying a namespace in <literal>include</literal>, <literal>externalRef</literal> or <literal>parentRef</literal> to give a namespace to grammars or patterns defined without a namespace is known as &quot;chameleon
  7. design.&quot; This is because the imported grammar or pattern takes
  8. the new namespace like a
  9. chameleon takes the color of the environment in which it is placed.
  10. </para>
  11. </glossdef>
  12. </glossentry>
  13. <glossentry><glossterm>character class</glossterm>
  14. <glossdef>
  15. <para>In a regular expression, a character class is an atom matching a set
  16. of characters. Character classes may be classical Perl character
  17. classes, Unicode character classes, or user-defined character
  18. classes.
  19. </para>
  20. </glossdef>
  21. </glossentry>
  22. <glossentry><glossterm>classical Perl character class</glossterm>
  23. <glossdef>
  24. <para>A set of character classes designated by a single letter, for which
  25. upper- and lowercases of the same letter are complementary (for
  26. instance, &quot;\d&quot; is all the decimal
  27. digits, and &quot;\D&quot; is all the
  28. characters that are not decimal digits).
  29. </para>
  30. </glossdef>
  31. </glossentry>
  32. <glossentry><glossterm>content model</glossterm>
  33. <glossdef>
  34. <para>A description of the structure of children elements and text nodes
  35. (independent of attributes). The content model is
  36. &quot;simple&quot; when there is a text node
  37. but no elements, &quot;complex&quot; when
  38. there are element nodes but no text,
  39. &quot;mixed&quot; when there are text and
  40. element nodes, and &quot;empty&quot; when
  41. there are neither text nor element nodes. </para>
  42. </glossdef>
  43. </glossentry>
  44. <glossentry><glossterm>datatype</glossterm>
  45. <glossdef>
  46. <para>A term used by Relax NG to qualify both the content of a simple content element or attribute. Datatypes
  47. should not be confused with XML 1.0 element types, which are called
  48. element names by Relax NG.
  49. </para>
  50. </glossdef>
  51. </glossentry>
  52. <glossentry><glossterm>DOM</glossterm>
  53. <glossdef>
  54. <para>Document Object Model. An object-oriented model of XML documents,
  55. including the definition of the API allowing its manipulation. The
  56. third version of DOM (DOM Level 3) will include an API named
  57. &quot;Abstract Schemas&quot; to facilitate
  58. schema-guided editions of XML documents (see <systemitem>http://www.w3.org/TR/DOM-Level-3-Core</systemitem>).
  59. </para>
  60. </glossdef>
  61. </glossentry>
  62. <glossentry><glossterm>DSDL</glossterm>
  63. <glossdef>
  64. <para>Document Schema Definition Languages (DSDL) is a project undertaken by
  65. the ISO (ISO/IEC JTC 1/SC 34/WG 1, to be precise) whose objective is
  66. &quot;to create a framework within which multiple
  67. validation tasks of different types can be applied to an XML document
  68. in order to achieve more complete validation results than just the
  69. application of a single technology&quot; (see <systemitem>http://dsdl.org</systemitem>).
  70. </para>
  71. </glossdef>
  72. </glossentry>
  73. <glossentry><glossterm>DTD</glossterm>
  74. <glossdef>
  75. <para>Document Type Definition. XML 1.0 DTDs are inherited from SGML, in
  76. which rules were included that allow the customization of the markup
  77. itself and played a very central role. Because of the syntactical
  78. rules included in their DTDs, SGML applications need a DTD to be able
  79. to read an SGML document. One of the simplifications of XML is to
  80. state that a XML parser should be able to read a document without
  81. needing a DTD. DTDs have therefore been simplified over their SGML
  82. ancestors and remain the first incarnation of what is today called a
  83. XML Schema language.
  84. </para>
  85. </glossdef>
  86. </glossentry>
  87. <glossentry><glossterm>element</glossterm>
  88. <glossdef>
  89. <para>One of the basic type of nodes in the tree represented by a XML
  90. document. An element is delimited by start and end tags. In the
  91. corresponding tree, an element is a nonterminal node, which may have
  92. subnodes of type element, character (text), and namespace and
  93. attribute, as well as comment and processing instruction nodes.
  94. </para>
  95. </glossdef>
  96. </glossentry>
  97. <glossentry><glossterm>element type</glossterm>
  98. <glossdef>
  99. <para>Term used in the XML 1.0 Recommendation, which is equivalent to the
  100. notion of element names in W3C XML Schema and should not be confused
  101. with the simple or complex datatype of an element.
  102. </para>
  103. </glossdef>
  104. </glossentry>
  105. <glossentry><glossterm>empty content</glossterm>
  106. <glossdef>
  107. <para>An element that has neither child element nor text nodes (with or
  108. without attributes).
  109. </para>
  110. </glossdef>
  111. </glossentry>
  112. <glossentry><glossterm>facet</glossterm>
  113. <glossdef>
  114. <para>A constraint added to the lexical or value space of a simple datatype
  115. of the W3C XML Schema datatype system. The list of facets that can be
  116. used depends on the simple datatype. W3C XML Schema's facets can be used as parameters in Relax NG <literal>data</literal> patterns.
  117. </para>
  118. </glossdef>
  119. </glossentry>
  120. <glossentry><glossterm>Infoset</glossterm>
  121. <glossdef>
  122. <para>XML Information Set. A formal description of the information that may
  123. be found in a well-formed XML document.
  124. </para>
  125. </glossdef>
  126. </glossentry>
  127. <glossentry><glossterm>instance document</glossterm>
  128. <glossdef>
  129. <para>A XML document that is a candidate to be validated by a schema. Any
  130. well-formed XML 1.0 document that conforms to the Namespaces in XML
  131. 1.0 Recommendation can be considered a valid or invalid instance
  132. document.
  133. </para>
  134. </glossdef>
  135. </glossentry>
  136. <glossentry><glossterm>lexical space</glossterm>
  137. <glossdef>
  138. <para>The set of all representations (after parsing and whitespace
  139. processing) allowed for a simple datatype.
  140. </para>
  141. </glossdef>
  142. </glossentry>
  143. <glossentry><glossterm>local name</glossterm>
  144. <glossdef>
  145. <para>The name of a component in its namespace, i.e., the part of the
  146. qualified name that comes after the namespace prefix.
  147. </para>
  148. </glossdef>
  149. </glossentry>
  150. <glossentry><glossterm>mixed content</glossterm>
  151. <glossdef>
  152. <para>The content of an element that contains both child element and text
  153. nodes.
  154. </para>
  155. </glossdef>
  156. </glossentry>
  157. <glossentry>
  158. <glossterm>namespace</glossterm>
  159. <glossdef>
  160. <para>A unique identifier that can be associated with a set of XML elements
  161. and attributes. This identifier is a URI, which is not required to
  162. point to an actual resource but must
  163. &quot;belong&quot; to the author of these
  164. elements and attributes. Since this full URI can't
  165. be included in the name of each element and attribute, a namespace
  166. prefix is assigned to the namespace URI through a namespace
  167. declaration. This prefix is added to the local name of the elements
  168. and attributes to form a qualified name. Namespaces are optional and
  169. elements and attributes may have no namespaces attached.
  170. </para>
  171. </glossdef>
  172. </glossentry>
  173. <glossentry><glossterm>piece</glossterm>
  174. <glossdef>
  175. <para>Regular expressions (or patterns) are composed of pieces. Each piece
  176. is itself composed of an atom describing a condition on a substring
  177. and an optional quantifier defining the expected number of
  178. occurrences of the atom.
  179. </para>
  180. </glossdef>
  181. </glossentry>
  182. <glossentry><glossterm>qualified name</glossterm>
  183. <glossdef>
  184. <para>The complete name of a component, including the prefix associated to
  185. its target namespace if one is defined.
  186. </para>
  187. </glossdef>
  188. </glossentry>
  189. <glossentry><glossterm>regular expression</glossterm>
  190. <glossdef>
  191. <para>A syntax to express conditions on strings. The syntax used by the W3C
  192. XML Schema for its patterns is very close to the syntax introduced by
  193. the Perl programming language. A regular expression is composed of
  194. elementary &quot;pieces.&quot;
  195. </para>
  196. </glossdef>
  197. </glossentry>
  198. <glossentry><glossterm>RELAX</glossterm>
  199. <glossdef>
  200. <para>A grammar-based XML Schema language developed by Murata Makoto and
  201. published in March 2000 as a Japanese ISO Standard (see <systemitem>http://www.xml.gr.jp/relax</systemitem>).
  202. </para>
  203. </glossdef>
  204. </glossentry>
  205. <glossentry><glossterm>RELAX NG</glossterm>
  206. <glossdef>
  207. <para>A grammar-based XML Schema language resulting from a merger between
  208. RELAX and TREX (see <systemitem>http://relaxng.org</systemitem>).
  209. </para>
  210. </glossdef>
  211. </glossentry>
  212. <glossentry><glossterm>SAX</glossterm>
  213. <glossdef>
  214. <para>Simple API for XML. A streaming event-based API used between parsers
  215. and applications. Its streaming nature means that pipelines of XML
  216. processing may be created using SAX (see <systemitem>http://www.saxproject.org</systemitem>).
  217. </para>
  218. </glossdef>
  219. </glossentry>
  220. <glossentry><glossterm>Schematron</glossterm>
  221. <glossdef>
  222. <para>A rule-based XML Schema language, developed by Rick Jelliffe, using
  223. XPath expressions to describe validation rules (see <systemitem>http://www.ascc.net/xml/resource/schematron/schematron.html</systemitem>).
  224. </para>
  225. </glossdef>
  226. </glossentry>
  227. <glossentry><glossterm>SGML</glossterm>
  228. <glossdef>
  229. <para>Standard Generalized Markup Language. Created in 1980, the ancestor
  230. of XML. XML was designed as a simplified subset of SGML to be used on
  231. the Web.
  232. </para>
  233. </glossdef>
  234. </glossentry>
  235. <glossentry><glossterm>simple content</glossterm>
  236. <glossdef>
  237. <para>An element has a simple content model when it has a child text node
  238. only (and no subelements). A simple content element has a simple type
  239. if it has no attributes, and it has a complex type if it has any
  240. attributes.
  241. </para>
  242. </glossdef>
  243. </glossentry>
  244. <glossentry><glossterm>special character</glossterm>
  245. <glossdef>
  246. <para>A character that may be used as an atom after a
  247. &quot;\&quot; to accept a specific character,
  248. either for convenience or because this character is interpreted
  249. differently in the context of a regular expression.
  250. </para>
  251. </glossdef>
  252. </glossentry>
  253. <glossentry><glossterm>TREX</glossterm>
  254. <glossdef>
  255. <para>A grammar-based XML Schema language developed by James Clark (see
  256. <systemitem>http://www.thaiopensource.com/trex</systemitem>).
  257. </para>
  258. </glossdef>
  259. </glossentry>
  260. <glossentry><glossterm>Unicode block</glossterm>
  261. <glossdef>
  262. <para>A set of characters classified by their
  263. &quot;localization&quot; (Latin, Arabic,
  264. Hebrew, Tibetan, and even Gothic or musical symbols).
  265. </para>
  266. </glossdef>
  267. </glossentry>
  268. <glossentry><glossterm>Unicode category</glossterm>
  269. <glossdef>
  270. <para>A set of characters classified by their usage (letters, uppercase,
  271. digit, punctuation, etc.).
  272. </para>
  273. </glossdef>
  274. </glossentry>
  275. <glossentry><glossterm>Unicode character class</glossterm>
  276. <glossdef>
  277. <para>A set of character classes defined based on the Unicode blocks and
  278. categories.
  279. </para>
  280. </glossdef>
  281. </glossentry>
  282. <glossentry><glossterm>URI</glossterm>
  283. <glossdef>
  284. <para>Uniform Resource Identifier. Defined by the RFCs 2396 and 2732. URIs
  285. were created to extend the notion of URLs (Uniform Resource Locators)
  286. to include abstract identifiers that do not necessarily need to
  287. &quot;locate&quot; a resource.
  288. </para>
  289. </glossdef>
  290. </glossentry>
  291. <glossentry><glossterm>URL</glossterm>
  292. <glossdef>
  293. <para>Uniform Resource Locator, a common identifier used on the Web. URLs
  294. are absolute when the full path to the resource is indicated, and
  295. relative when a partial path is given that needs to be evaluated in
  296. relation with a base URL.
  297. </para>
  298. </glossdef>
  299. </glossentry>
  300. <glossentry><glossterm>valid</glossterm>
  301. <glossdef>
  302. <para>A XML document that is well-formed and conforms to a schema (Relax NG, DTD, W3C
  303. XML Schema, etc.) of some kind.
  304. </para>
  305. </glossdef>
  306. </glossentry>
  307. <glossentry><glossterm>value space</glossterm>
  308. <glossdef>
  309. <para>The set of all the possible values for a simple datatype, independent
  310. of their actual representation in the instance documents.
  311. </para>
  312. </glossdef>
  313. </glossentry>
  314. <glossentry><glossterm>W3C</glossterm>
  315. <glossdef>
  316. <para>World Wide Web Consortium. Originally created to settle HTML and HTTP
  317. as de facto standards. The main specification body for the core
  318. specifications of the World Wide Web and the keeper of the core XML
  319. specifications (see <systemitem>http://www.w3.org</systemitem>).
  320. </para>
  321. </glossdef>
  322. </glossentry>
  323. <glossentry><glossterm>well-formed</glossterm>
  324. <glossdef>
  325. <para>An XML document that meets the conditions defined in the XML 1.0
  326. Recommendation: it must be readable without ambiguity. Syntax errors
  327. will be detected by a XML parser without schema of any type.
  328. </para>
  329. </glossdef>
  330. </glossentry>
  331. <glossentry><glossterm>whitespace</glossterm>
  332. <glossdef>
  333. <para>Characters <literal>#x9</literal> (tab), <literal>#xA</literal>
  334. (linefeed), <literal>#xD</literal> (carriage return), and
  335. <literal>#x20</literal> (space). These are often used to indent the
  336. XML documents to give them a more readable aspect, and are filtered
  337. by an operation named &quot;whitespace
  338. processing.&quot;
  339. </para>
  340. </glossdef>
  341. </glossentry>
  342. <glossentry><glossterm>XInclude</glossterm>
  343. <glossdef>
  344. <para>A W3C specification defining a general purpose inclusion mechanism
  345. for XML documents (see <systemitem>http://www.w3.org/TR/xinclude</systemitem>).
  346. </para>
  347. </glossdef>
  348. </glossentry>
  349. <glossentry><glossterm>XML</glossterm>
  350. <glossdef>
  351. <para>Extensible Markup Language. A subset of SGML created to be used on
  352. the Web. Its core specification (XML 1.0) was published by the W3C in
  353. February 1998. New specifications have been added since this date,
  354. and the W3C considers that, with the addition of W3C XML Schema, the
  355. core specifications are now complete.
  356. </para>
  357. </glossdef>
  358. </glossentry>
  359. <glossentry><glossterm>XPath</glossterm>
  360. <glossdef>
  361. <para>A query language used to identify a set of nodes within a XML
  362. document. Originally defined to be used with XSLT, it is also used by
  363. other specifications such as Schematron, XPointer, W3C XML Schema or XForms (see
  364. <systemitem>http://www.w3.org/TR/xpath</systemitem>).
  365. </para>
  366. </glossdef>
  367. </glossentry>
  368. <glossentry><glossterm>XSLT</glossterm>
  369. <glossdef>
  370. <para>Extensible Stylesheet Language Transformations. A programming
  371. language specialized for the transformation of XML documents (see
  372. <systemitem>http://www.w3.org/TR/xslt</systemitem>).
  373. </para>
  374. </glossdef>
  375. </glossentry>
  376. <glossentry><glossterm>pattern</glossterm>
  377. <glossdef>
  378. <para>Any part of a Relax NG schema that can be matched against a set of attributes and a sequence of elements and strings is a pattern. With the exception of name classes, all parts (including the whole schema) of a Relax NG schema are patterns.</para>
  379. </glossdef>
  380. </glossentry>
  381. <glossentry><glossterm>Russian doll design</glossterm>
  382. <glossdef>
  383. <para>A schema where the definitions of elements and attributes are embedded one in each other without using named patterns is often refered as having a "Russian doll design".</para>
  384. </glossdef>
  385. </glossentry>
  386. <glossentry><glossterm>Named pattern</glossterm>
  387. <glossdef>
  388. <para>Named patterns are globally defined in a grammar and may be refered from anywhere in this grammar or in the children grammars.</para>
  389. </glossdef>
  390. </glossentry>
  391. <glossentry><glossterm>Grammar</glossterm>
  392. <glossdef>
  393. <para>A grammar is a pattern which is a container for a start pattern and any number of named patterns.</para>
  394. </glossdef>
  395. </glossentry>
  396. <glossentry><glossterm>Start pattern</glossterm>
  397. <glossdef>
  398. <para>When a grammar is used to validate an instance document, its start pattern is matched against the root element of the instance document. When a grammar is embedded in another grammar, the embedded grammar is replaced by its start pattern during the simplication of the schema.</para>
  399. </glossdef>
  400. </glossentry>
  401. <glossentry><glossterm>Simplification</glossterm>
  402. <glossdef>
  403. <para>Action of simplifying and normalizing a Relax NG schema to remove the syntactical variations and use a few number of basic patterns and name classes. The simplification of Relax NG is described in its specification to.</para>
  404. </glossdef>
  405. </glossentry>
  406. <glossentry><glossterm>Recursive content models</glossterm>
  407. <glossdef>
  408. <para>Recursive content models are content models in which elements can be included directly or indirectly within themselves (such as XHTML "div" or "span" elements).</para>
  409. </glossdef>
  410. </glossentry>
  411. <glossentry><glossterm>recursive patterns</glossterm>
  412. <glossdef>
  413. <para>Recursive patterns are named patterns including directly or indirectly references to themselves. Relax NG only allows recursive patterns which describe recursive content models, i.e. for which the definition of the named pattern is isolated from its reference by an element pattern.</para>
  414. </glossdef>
  415. </glossentry>
  416. <glossentry><glossterm>compositor</glossterm>
  417. <glossdef>
  418. <para>A compositor is a pattern which can be used combine other patterns. Relax NG has three basic compositors: <literal>group</literal>, <literal>choice</literal> and <literal>interleave</literal>. A fourth compositor, <literal>mixed</literal>, which is a shortcup for <literal>interleave</literal> with an embedded <literal>text</literal> pattern.</para>
  419. </glossdef>
  420. </glossentry>
  421. <glossentry><glossterm>ambiguous</glossterm>
  422. <glossdef>
  423. <para>A pattern is ambiguous when a fragment of an instance document may be valid through several alternatives in its <literal>choice</literal> patterns. Relax NG allows ambiguous patterns but they can be a problem for annotation and datatype assigment.</para>
  424. </glossdef>
  425. </glossentry>
  426. <glossentry><glossterm>unambiguous</glossterm>
  427. <glossdef>
  428. <para>A pattern is unambiguous when any fragment of instance document which is valid per this pattern is only valid for one of each alternatives. Relax NG does not require unambiguous patterns but they can be considered a good practice for annotation and datatype assigment.</para>
  429. </glossdef>
  430. </glossentry>
  431. <glossentry><glossterm>deterministic</glossterm>
  432. <glossdef>
  433. <para>A pattern is deterministic if a schema processor can always determine which alternative to follow looking only at the current element under validation. Unlike W3C XML Schema, Relax NG does not require deterministic patterns.</para>
  434. </glossdef>
  435. </glossentry>
  436. <!--
  437. <glossentry><glossterm></glossterm>
  438. <glossdef>
  439. <para> </para>
  440. </glossdef>
  441. </glossentry>
  442. <glossentry><glossterm></glossterm>
  443. <glossdef>
  444. <para> </para>
  445. </glossdef>
  446. </glossentry>
  447. <glossentry><glossterm></glossterm>
  448. <glossdef>
  449. <para> </para>
  450. </glossdef>
  451. </glossentry>
  452. <glossentry><glossterm></glossterm>
  453. <glossdef>
  454. <para> </para>
  455. </glossdef>
  456. </glossentry>
  457. <glossentry><glossterm></glossterm>
  458. <glossdef>
  459. <para> </para>
  460. </glossdef>
  461. </glossentry>
  462. <glossentry><glossterm></glossterm>
  463. <glossdef>
  464. <para> </para>
  465. </glossdef>
  466. </glossentry>
  467. -->
  468. </glossary>