Scribd
Upload
16 views

XML Transformation - Requirements

The document outlines requirements for validating an XML schema, transforming XML documents to HTML and PDF using XSLT, and creating optional documentation in DocBook format. The requirements include: validating the XML schema against its namespace and structure; transforming XML to valid HTML pages with styles, images, and multiple linked files; transforming XML to PDF with headers, tables, images and page formatting; and validating optional DocBook documentation against its schema with code samples and non-overflowing content. Additional technologies beyond basic XSLT are also suggested.

Uploaded by

vigilanteuc
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
16 views

XML Transformation - Requirements

The document outlines requirements for validating an XML schema, transforming XML documents to HTML and PDF using XSLT, and creating optional documentation in DocBook format. The requirements include: validating the XML schema against its namespace and structure; transforming XML to valid HTML pages with styles, images, and multiple linked files; transforming XML to PDF with headers, tables, images and page formatting; and validating optional DocBook documentation against its schema with code samples and non-overflowing content. Additional technologies beyond basic XSLT are also suggested.

Uploaded by

vigilanteuc
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Requirements:

XML Schema (validation)

The XML schema is already present. It should be validated. Requirements:

• namespace for documents created according to the given scheme


• appropriate structure (it is recommended to use the blind Venetian approach)
• control values using constructs
o appropriately selected data types
o pattern
o enumeration
o minimum or maximum value - for numbers or dates
o referential integrity
o schematron (directly in XSD or in a separate file)

Transformation to HTML (required)

Transformation in XSLT for conversion of documents created according to the schema into
HTML 5 (or it is possible to use xHTML, but HTML 5 is preferred). Transformations will be
written in XSLT 2.0 or 3.0.

XSLT, output HTML and any attached files (CSS, images) are submitted.

• the output is valid HTML pages


o validator check at https://validator.w3.org/
o accessible and clear appearance
o at least basic styles (CSS), images
o we remind you that valid pages must contain a correctly written DOCTYPE

• output to multiple files linked to content (menu)


• suitable number of basic constructs in XSLT
o templates, cycles
o condition
o sorting
o use of parameters, variables or groupings
• appropriate detail of XPATH expressions
• the transformation must be universally applicable - it does not contain any specific
values valid only for the sample document

Transformation to PDF (required)


The second transformation is used to convert documents created according to the scheme
into formatting objects (FO), then transformed into PDF.
XSLT, output PDF, FO are submitted.

the resulting document contains:


• Header Footer
• Tables
• active content (linking)
• pictures
• appropriate adjustment - clarity, appearance, overflow of content outside the page
the output does not contain incorrect characters.

Documentation (optional)

Created in the DocBook format. The minimum scope of documentation is not specified, but
of course half a page is not enough. The documentation should contain a list of elements of
your markup language with a brief explanation of each element in the table. For each
additional technology (XML schema, XSLT transformation) should be given a brief
explanation of what it implements (in a few sentences) and at least two interesting
constraints (XML schema) and constructs used (XSLT transformation) with part of the source
code and their brief explanation .

The source file in DocBook and the results of its transformations into PDF and HTML are
submitted.

• the documentation is valid compared to the DocBook schema


• the content does not overflow outside the page
• documentation contains
o code dump sample (eg schema bit or XSLT transformation)
o content
o index

Something extra (optional)


Use a more complex construct / technology / method in the selected parts (scheme,
transformation).

Suitable variants are, for example:

• composing diagrams
• custom functions in XSLT, functions from XSLT 3.0
• transformation using Xquery
• CSS applicable directly to sample documents …

You might also like