Saxon Documentation. The open-source Saxon-HE product does not require any license key. For Saxon-PE and Saxon-EE, however, you need to obtain a license key from Saxonica. You can order a free license key for a 30-day evaluation, or purchase an unrestricted license key, from the Saxonica web site. Since Saxon 9.2, newly issued license keys are compatible across the Java and .NET platforms. The older .NET license keys (named saxon-license.xml) are no longer accepted. The license key will arrive in the form of a file named saxon-license.lic attached to an email message. The location specified using the configuration property FeatureKeys.LICENSE_FILE_LOCATION, as described below.
It is also possible to force Saxon to read the license file from a specific location by setting the Configuration property FeatureKeys.LICENSE_FILE_LOCATION (a constant representing the string " Using Stylesheets. Using Stylesheets This page describes how to use SAXON XSLT Stylesheets, either from the command line, or from the Java API, or as an Applet in the browser. Using Saxon from the Command Line The Java class com.icl.saxon.StyleSheet has a main program that may be used to apply a given style sheet to a given source XML document. The form of command is: java com.icl.saxon.StyleSheet [options] source-document stylesheet [ params…] The options must come first, then the two file names, then the params.
If you are using JDK 1.2 or later, you can use the simpler form of command: java -jar dir/saxon.jar [options] source-document stylesheet [ params…] The options are as follows (in any order): A param takes the form name=value, name being the name of the parameter, and value the value of the parameter. Under Windows it is possible to supply a value containing spaces by enclosing it in double quotes, for example name="John Smith". If the -a option is used, the name of the stylesheet is omitted. XSD - ScoLOMFR. Consultation des vocabulaires - ScoLOMFR. La version 2.0 du profil d'application ScoLOMFR est disponible à partir du 25/02/2016. Vous trouverez ci-dessous les différents vocabulaires de la version 2.0 du profil d'application ScoLOMFR et ce, dans les différents formats d'exports retenus. Dans le tableau, les vocabulaires sont présentés à l'unité.
Sous ce même tableau, sont accessibles les documents d'accompagnement XML et VDEX ainsi que l'ensemble des vocabulaires aux formats SKOS et RDF. Une documentation liée à la maintenance de ces vocabulaires est mise à votre disposition ici. Nous attirons votre attention sur l'utilisation des signes diacritiques (', -, ^, etc.) notamment à la recherche. La version 2.0 du profil d'application ScoLOMFR est publiée le 25/02/2016. N'hésitez pas à nous faire part de vos remarques, questions, suggestions concernant ces différents vocabulaires et leurs formats d'exports à l'adresse suivante : scolomfr-contact@reseau-canope.fr. Tableau contenant les vocabulaires validés. DTD des fichiers XML. Saxonica Developer Community. The SAXON XSLT and XQuery Processor. SAXON Documentation.
Validation from the Command Line. XML Path Language (XPath) 2.0 (Second Edition) XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition) See [Working With Timezones] for a disquisition on working with date and time values with and without timezones. 10.1 Duration, Date and Time Types The operators described in this section are defined on the following date and time types: xs:dateTimexs:datexs:timexs:gYearMonthxs:gYearxs:gMonthDayxs:gMonthxs:gDay Note that only equality is defined on xs:gYearMonth, xs:gYear, xs:gMonthDay, xs:gMonth and xs:gDay values. In addition, operators are defined on: xs:duration and on the 10.3 Two Totally Ordered Subtypes of Duration: xs:yearMonthDurationxs:dayTimeDuration Note that no ordering relation is defined on xs:duration values.Two xs:duration values may however be compared for equality. 10.1.1 Limits and Precision All minimally conforming processors ·must· support positive year values with a minimum of 4 digits (i.e., YYYY) and a minimum fractional second precision of 1 millisecond or three digits (i.e., s.sss). 10.2 Date/time datatype values 10.2.1 Examples Note: 10.4.1 op:yearMonthDuration-less-than.
ODF Application: XLST Transformation. Download version of 28 Mar 2006 This is an alpha version of a stylesheet that converts the content.xml of an OpenDocument text file to XHTML. It is intended to give you a reasonable idea of what the file looks like, not to do a completely accurate job of rendering the file. Limitations Because this stylesheet looks only at the content.xml file, it cannot completely represent the style information of the document, some of which resides in the styles.xml file. Because it is constructing only a single XHTML output file, it does not include images. Using the Stylesheet You can’t just run this stylesheet against an .odt file with a typical transformation program because the OpenDocument file is in a .zip format. To convert the file testfile.odt to testfile.xhtml, you would enter this at the command line: .
FYI: Here are the usage instructions for the ODTransform program. See list of changes. L'essentiel de XML. NISO Standard DTD and CSS files. Skip to Main Content Search form Login | Contact Us Creating the best way to read and publish DAISY/NISO Standard DTD and CSS files List of most current DTDs List of CSS files dtbook.2005.basic.css Printer-friendly version Home | Accessibility | DAISYpedia | Site Map | Terms of Use | Contact Us © 2014 DAISY Consortium. C QA - Recommended list of Doctype declarations you can use in your Web document.
Warning The list is informative and does not try to be exhaustive (there are many other proper declarations you could use), but it has most of the declarations commonly used on the Web at the moment. Recommended Doctype Declarations to use in your Web document. When authoring document is HTML or XHTML, it is important to Add a Doctype declaration. The doctype declaration must be exact (both in spelling and in case) to have the desired effect, which makes it sometimes difficult. To ease the work, below is a list of recommended doctype declarations that you can use in your Web documents. Template Use the following markup as a template to create a new XHTML 1.0 document using a proper Doctype declaration. <! (X)HTML Doctype Declarations List Strict Transitional Frameset Strict (quick reference) Transitional Frameset XHTML Basic 1.1 (quick reference): HTML 5 [NOT a standard yet] MathML Doctype Declarations MathML 2.0 - DTD: MathML 1.01 - DTD: Compound documents doctype declarations SVG 1.1 Full - DTD:
UTS #18: Unicode Regular Expressions. Unicode Technical Standard #18 Summary This document describes guidelines for how to adapt regular expression engines to use Unicode. Status This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. This is a stable document and may be used as reference material or cited as a normative reference by other specifications.
A Unicode Technical Standard (UTS) is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS. Please submit corrigenda and other comments with the online reporting form [Feedback]. Contents 0 Introduction The following describes general guidelines for extending regular expression engines (Regex) to handle Unicode. Unicode is a large character set—regular expression engines that are only adapted to handle small character sets will not scale well. Level 1: Basic Unicode Support. In particular: 0.1 Notation Examples: 0.2 Conformance 1.1 Hex Notation. #regular-expressions. This section provides a checklist of progress against the published XSLT 2.0 Requirements document (see [XSLT 2.0 Requirements]).
Requirement 1 must Maintain Backwards Compatibility with XSLT 1.1 [Read this as "with XSLT 1.0"] Any stylesheet whose behavior is fully defined in XSLT 1.0 and which generates no errors will produce the same result tree under XSLT 2.0 Response See J.1 Incompatible Changes Requirement 2 must Match Elements with Null Values A stylesheet should be able to match elements and attributes whose value is explicitly null. This has been handled as an XPath 2.0 requirement. Requirement 3 should Allow Included Documents to "Encapsulate" Local Stylesheets XSLT 2.0 should define a mechanism to allow the templates in a stylesheet associated with a secondary source document, to be imported and used to format the included fragment, taking precedence over any applicable templates in the current stylesheet.
Requirement 4 Could Support Accessing Infoset Items for XML Declaration. #regex-syntax. See [Working With Timezones] for a disquisition on working with date and time values with and without timezones. 10.1 Duration, Date and Time Types The operators described in this section are defined on the following date and time types: xs:dateTimexs:datexs:timexs:gYearMonthxs:gYearxs:gMonthDayxs:gMonthxs:gDay Note that only equality is defined on xs:gYearMonth, xs:gYear, xs:gMonthDay, xs:gMonth and xs:gDay values. In addition, operators are defined on: xs:duration and on the 10.3 Two Totally Ordered Subtypes of Duration: xs:yearMonthDurationxs:dayTimeDuration Note that no ordering relation is defined on xs:duration values.Two xs:duration values may however be compared for equality. 10.1.1 Limits and Precision All minimally conforming processors ·must· support positive year values with a minimum of 4 digits (i.e., YYYY) and a minimum fractional second precision of 1 millisecond or three digits (i.e., s.sss). 10.2 Date/time datatype values 10.2.1 Examples Note: 10.4.1 op:yearMonthDuration-less-than.
XSLT 2.0. This section provides a checklist of progress against the published XSLT 2.0 Requirements document (see [XSLT 2.0 Requirements]). Requirement 1 must Maintain Backwards Compatibility with XSLT 1.1 [Read this as "with XSLT 1.0"] Any stylesheet whose behavior is fully defined in XSLT 1.0 and which generates no errors will produce the same result tree under XSLT 2.0 Response See J.1 Incompatible Changes Requirement 2 must Match Elements with Null Values A stylesheet should be able to match elements and attributes whose value is explicitly null. This has been handled as an XPath 2.0 requirement. Requirement 3 should Allow Included Documents to "Encapsulate" Local Stylesheets XSLT 2.0 should define a mechanism to allow the templates in a stylesheet associated with a secondary source document, to be imported and used to format the included fragment, taking precedence over any applicable templates in the current stylesheet.
Requirement 4 Could Support Accessing Infoset Items for XML Declaration.