 |
|
| Altova's product line supports and implements a broad range of standards that are essential for interoperability and connectivity in today's world. To ensure maximum compatibility with these standards, Altova constantly monitors standards compliance in its QA department and actively participates in various standards bodies. The following list provides an overview of the major standards implemented and supported by Altova's XMLSpy® 2008, MapForce® 2008, StyleVision® 2008, SchemaAgent® 2008, and Authentic® 2008 products.
| Standard | Description and Comments | | | XML 1.0 (3rd Ed.) | The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML. | | | Namespaces in XML | XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references. | | | Unicode 3.2 | The Unicode Standard, Version 3.2.0 is defined by The Unicode Standard, Version 3.0 (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), as amended by the Unicode Standard Annex #27: Unicode 3.1 and by the Unicode Standard Annex #28: Unicode 3.2. | | | XSLT 1.0 | XSLT 1.0 is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using XSLT to describe how the document is transformed into another XML document that uses the formatting vocabulary.
The rarely used elements xsl:strip-space and xsl:preserve-space are currently ignored. | | | XSLT 2.0 | XSLT 2.0 is the long-awaited upgrade to XSLT 1.0 and includes important new schema-aware functions, grouping, aggregation, node-set, "for" loops, and much more. For a detailed description of the new capabilities, please see this comparison.
The rarely used elements xsl:strip-space and xsl:preserve-space are currently ignored. Also the attributes input-type-annotations and inherit-namespaces are not yet supported.
| | | XPath 1.0 | XPath 1.0 is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.
| | | XPath 2.0 | XPath 2.0 is a language for addressing parts of an XML document, designed to be used by both XSLT 2.0 and XQuery1.0 - it it the long-awaited upgrade to XPath 1.0 and includes imporant new functions. For a detailed description of the new capabilities, please see this comparison.
The following two functions are currently not yet supported: fn:normalize-unicode, fn:collection.
| | | XQuery 1.0 | An extension of the XPath 2.0 specification, XQuery is a new language for extracting information from XML documents and databases.
| | | XML Schema 1.0 | XML Schema specifies the XML Schema definition language, which offers facilities for describing the structure and constraining the contents of XML 1.0 documents, including those which exploit the XML Namespace facility. The schema language, which is itself represented in XML 1.0 and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML 1.0 document type definitions (DTDs). | | | SOAP 1.1 | SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework. | | | WSDL 1.1 | WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate, however, the only bindings described in this document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME. | | | SVG 1.0 | This specification defines the features and syntax for Scalable Vector Graphics (SVG), a language for describing two-dimensional vector and mixed vector/raster graphics in XML. | | | DocBook 4.2 | DocBook is general purpose XML and SGML document type published by OASIS that is particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications). | | | P3P 1.0 | Platform for Privacy Preferences (P3P) has been created to automate the dissemination of privacy practices for a web site in Extensible Markup Language. This is a W3C specification designed to help protect privacy on the web by encoding data-collection and data-use practices, and providing flexibility for it to be both human and user agent readable. | | | XML Catalogs | In order to make optimal use of the information about an XML external resource, there needs to be some interoperable way to map the information in an XML external identifier into a URI reference for the desired resource.
This OASIS XML Catalog Standard defines an entity catalog that handles two simple cases:- Mapping an external entity's public identifier and/or system identifier to a URI reference.
- Mapping the URI reference of a resource (a namespace name, stylesheet, image, etc.) to another URI reference.
| |
By virtue of the extensible nature of XML, this list is far from being complete, since many more XML-based standards are created and published almost on a weekly basis. The ALTOVA products automatically support all these new XML-based standards, because they, too, have been designed to be extensible. Support for any new standard can be easily added through schemas, DTDs, templates, and custom stylesheets by the user. In addition, ALTOVA constantly monitors new developments in the XML community and adds "out-of-the-box" support for new standards with every new release of its products.
|
|
|
|
