Product Features

•	The SPS can use multiple schemas and/or a single database (DB) source, thus enabling the use of multiple XML document sources together with a DB source.

•	Multiple SPS designs can be open simultaneously, with one being active at any given time. Each SPS design is shown in a separate tab.

•	Template filters allow you to customize the display of the design document. With this feature you can disable the display of templates that are not currently being edited, thus increasing editing efficiency.

•	While designing the SPS, Authentic View, output views and stylesheets can be displayed by clicking the respective tabs. This enables you to quickly preview the output and the XSLT code, and test Authentic View features.

•	When an SPS is associated with an XML source document or source DB, the source document can be edited directly in the Authentic View of StyleVision.

•	DB reports can either be viewed in StyleVision or saved as HTML, RTF, PDF, and Word 2007 files.

•	Both XSLT versions (1.0 and 2.0) are supported. XSLT 2.0 provides powerful data access and manipulation features.

•

Altova Global Resources can be used to locate source files such as schema, XML, and CSS. The Global Resources mechanism enables faster and better development and testing by allowing developers to quickly change source data and to use the functionality of other Altova applications from within StyleVision.

•	In the Enterprise and Professional Editions, multiple output formats (HTML, RTF, PDF, and Word 2007) are generated from a single SPS design.

•	Conditions can be set on SPS components to process them differently for different outputs. With this level of granularity, different outputs can be flexibly structured to take in the requirements of that particular output.

•	Both XSLT files and output files can be generated and saved, either directly from within the GUI or by calling StyleVision from the command line.

Given below is a list of the main StyleVision features specific to designing the SPS.

•	The SPS can contain static text, which you enter in the SPS, and dynamic text, which is selected from the source document/s .

•	Dynamic content is inserted in the design by dragging-and-dropping nodes, including specific datatypes, from the schema sources.

•

Dynamic content can be inserted as text, or in the form of a data-entry device (such as an input field or combo box). When inserted as a data-entry device such as a combo box, additional possibilities are available. For example, the value of the node can be selected (by the Authentic View user) from a list of enumerations.

•	The structure of the design is specified and controlled in a single main template. This structure can be modified by optional templates for individual elements—known as global templates because they can be applied globally for that element.

•	Global templates can also be created for individual datatypes, thus enabling processing to be handled also on the basis of types.

•	Design Fragments enable the modularization and re-use of templates within an SPS, and also across multiple SPSs (see modular SPSs), in a manner similar to the way functions are used.

•	SPS modules can be added to other SPS modules, thus making objects defined in one SPS module available to other modules. This enables re-use of module objects across multiple SPSs and makes maintenance easier.

•

A common feature of XML documents is the repeating data structure. For example, an office department typically has several employees. The data for each employee would be stored in a data structure which is repeated for each employee. In the SPS, the processing for each such data structure is defined once and applied to each relevant node in turn (the employee node in our example).

•	Repeating data structures can also be inserted as dynamic tables. This provides looping in a structured, table format, with each loop through the data structure producing a row (or, if required, a column) of the table.

•	A repeating element can be sorted on one or more sort-keys you select, and the sorted element set is sent to the output (HTML, RTF, PDF, and Word 2007).

•	Nodes can be grouped on the basis of common data content (for example, the common value of an attribute value) and their positions.

•

The conditional templates feature enables one of a set of templates to be processed according to what conditions in the XML document or system environment are fulfilled. This enables processing that is conditional on information contained in the source document or that cannot be known to the SPS document creator at the time of creation (for example, the date of processing). The available conditions are those that can be tested using XPath 1.0 or XPath 2.0 expressions.

•

Auto-Calculations enable you to manipulate data from the source document/s and to display the result. This is useful, when you wish to perform calculations on numbers (for example, sum the prices in an invoice), manipulate strings (for example, change hyphens to slashes), generate content, etc. The available manipulations are those that can be effected using XPath 1.0 or XPath 2.0 expressions.

•	When data is edited in Authentic View, the result of Auto-Calculations can also be passed to a node in the source document. This procedure is referred to as updating the XML node (with the value of the Auto-Calculation).

•

Additional validation enables individual XML document nodes to be validated (additionally to schema validation) against an XPath expression defined for that node. In this way, Authentic View users can be alerted when the data they enter is invalid; a customized error message for the node can indicate the problem.

•	Images can be inserted in the design. The URI for the image can be static (entered in the SPS), or dynamic (taken from a node in the source document), or a combination of both static and dynamic parts.

•	Two types of lists can be created: static and dynamic. In a static list, each list item is defined in the SPS. In a dynamic list, a node is created as a list item; the values of all instances of that node are created as the items of the list.

•	Static and dynamic links can be inserted in the design. The target URI can be static (entered in the SPS), or dynamic (taken from a node in the source document), or a combination of both static and dynamic parts.

•	Static bookmarks can be inserted. These serve as anchors that can be linked to with a hyperlink.

•	Parameters can be declared globally for the entire SPS. A parameter is declared with a name and a string value, and can be used in XPath expressions in the SPS. The parameter value you declare is the default value and can be overridden by a value passed from the command line.

•	With the Input Formatting feature, the contents of numeric XML Schema datatype nodes can be formatted as required for Authentic View display and, in the case of some formats, optionally for output display. Input Formatting can also be used to format the result of an Auto-Calculation.

•	JavaScript functions can be used in the SPS to provide user-defined functionality for Authentic View and HTML output.

•	A number of predefined HTML formats are available via the GUI and can be applied to individual SPS components.

•	A large number of CSS text formatting and layout properties can be applied to individual SPS components via the Styles sidebar.

•	Additionally, CSS styles can be defined for HTML selectors at the global level of an SPS and in external CSS stylesheets. These style rules will be applied to Authentic View and HTML output, thus providing considerable formatting and layout flexibility.

•	Styles can also be assigned using XPath expressions. This enables style property values to be selected from XML documents and to set property values conditionally.

•	For paged output (typically RTF, PDF, and Word 2007), a number of page layout options, such as orientation, margins, page-numbering, and headers and footers, can be specified in the SPS.