Please enable JavaScript to view this site.

Altova StyleVision 2020 Enterprise Edition

» No topics above this level «

Usage Overview

Scroll Home Prev Top Next More

Objectives

SPS documents that you create in StyleVision can be used for two broad purposes:

 

To control the display of XML source documents in Authentic View and to enable data to be entered in XML documents or DBs via the Authentic View interface.

To generate XSLT stylesheets for HTML, RTF, PDF, and Word 2007+ output.

 

In this way, the SPS can be used to enable XML document editing and to generate HTML, RTF, PDF, and Word 2007+ output from the edited XML document. Additionally, the generated XSLT stylesheets can be used to transform other XML documents based on the same schema as the SPS.

 

Steps for creating an SPS

Given below is an outline of the steps involved in creating a new SPS.

 

1.Assign a schema to the newly created empty SPS. The schema may be: (i) a schema file (DTD or XML Schema); (ii) an XML Schema generated from a DB (Enterprise and Professional editions only); (iii) a schema based on an XBRL taxonomy (Enterprise edition only); (iv) a user-defined schema (created directly in StyleVision). This is done in the Design Overview sidebar. If required, additional schemas can be added (via the Design Overview sidebar) so that nodes in multiple XML documents can be addressed. Alternatively, a new SPS can be created directly with a schema  via the File | New command.

2.Assign a Working XML File to the SPS. The Working XML File provides the XML data processed by the SPS when generating Authentic View and output previews. The Working XML File is assigned in the Design Overview sidebar.  The Working XML File enables you to preview output in StyleVision. If required, the Working XML Files for additional schemas can be assigned (via the Design Overview sidebar) to enable previews involving multiple XML documents.

3.Select the required XSLT version.

4.Select the Internet Explorer Compatibility to match the installed Internet Explorer version.

5.The SPS document is designed in Design View using the various design components available to the designer. The design process consists of creating a document structure and defining presentation properties. If print output is required, then additional print formatting properties can be specified.

6.The Authentic View and outputs are tested. If modifications to the design are required, these are made and the SPS document is re-tested.

7.If XSLT files or output files are required, these are generated.

8.If required, assign a Template XML File. The Template XML File provides the starting data for a new XML document that can be edited in Authentic View using the SPS.

9.The SPS is deployed for use among multiple Authentic View users.

 

 

 

© 2019 Altova GmbH