Xml application collection

1. XHTML

XHTML 1.0 [W3C recommendation standard] is basically a rewrite of HTML 4, making it a well-structured XML. HTML is a SGML application. When XML is developed as a simplified and standardized SGML Web application, HTML is a common Web language) it becomes the preferred target for adopting XML. As a result, there is a variant of HTML called XHTML. The goal of XHTML research is an HTML language that is easier to parse (because the XML syntax is more rigorous. XHTML is easy to process with ready-made XML tools, and strives to better separate content and representation. XHTML is one of the oldest XML applications, and many interest groups have played a role in different parts and versions. I will try my best to summarize most of them.

Corresponds to three types of HTML 4 DTD: Strict, Transitional, and Frameset. XHTML 1.0 defines different DTD and namespace. Modularization of XHTML [W3C recommendation standard] provides a framework for breaking XHTML into separate modules as different DTD definitions. For example, all elements and attributes used to define a list constitute a module, and the element types related to the representation are placed in another module. In this way, you can develop and redefine XHTML by adding, reducing, and modifying general independent modules. Along this line, the first step is XHTML Basic [W3C recommendation standard], which defines the minimum XHTML module set that any language as XHTML must have. XHTML Basic can be used as the content language of Web customers, such as mobile phones, PDAs, pagers, and folders. XHTML 1.1 [W3C recommendation standard] is basically the XHTML 1.0 Strict DTD decomposed by the module framework.

XHTML 2.0 [under development] is a rewriting of XHTML, without considering backward compatibility with HTML. This idea is almost like writing a brand new content language for the Web, learning the past experience without being bound to the past. Major changes include:

Removed <br/>, , and other elements that are considered too representative-oriented.
Cancel the HTML-style form and change it to support XForm (as described earlier in this series)
Cancel the HTML style link and change it to HLink (as described earlier in this series)
Replacing many JavaScript-Driven Dynamic Tasks with XML events
Use XFrame instead of HTML framework

More importantly, XHTML 2.0 has made many extensions, enhancing the author's ability to express the content structure and meaning. Breaking backward compatibility has caused controversy. Some reviewers think that keeping (X) the HTML name only modifies the version number will cause confusion. Others say that these changes are necessary, while XHTML is still a scalable markup language, so it is appropriate to retain the original name.

XHTML is often used with other embedded formats, such as MathML, RDF, SVG, SMIL, and VoiceXML (which will be described later ). This type of hybrid document is called multimode or non-monolithic. W3C, ISO, and other organizations are making great efforts to encourage strong support for such documents.

2. Docbook

Docbook is a popular SGML format used to compile books and documents, especially documents with many technical features. Later, an XML version was added. DocBook XML V4.2 [OASIS Committee specification] was the latest achievement. Docbook is very popular and has been supported by many tools, many of which are very mature. It is respected as an example to avoid Mixed Representation of problems and content formats. Recently, some developers began to complain that it has inherited too many burdens from past versions and discussed them one after another (and even its main developer Norm Walsh) re-develop a new Incompatible version for this format.

Text Encoding Initiative (TEI) is even older than Docbook. This document format is somewhat similar to the application scope of Docbook, the difference is that it generally deals with text in the humanities rather than non-text. TEI itself is not a SGML or XML application, but a set of guidelines for the construction language (DTD. The most common TEI variant is TEI Lite [community standard]. TEI is well-known for its complexity, which restricts its use to a certain extent, but it is well maintained and has enthusiastic users in some communities.

3. XSL-FO

Extensible Stylesheet Language Formatting Objects (XSL-FO) [W3C recommendation standard] is a representation Language defined using XML. (Note that the title of the link specification is "Extensible Stylesheet Language (XSL)", but the content only covers the formatting object of XSL .) XSL-FO is an XML format that can be used by any user agent to present content according to the precise specification given by developers. Its role is similar to XHTML in the Web user interface, but it is more complex to express formatting details suitable for printing. These details are no different from what is specified in Cascading Style Sheets (CSS-as described earlier in this series), but in XSL-FO, these details constitute an instance of the markup language itself, rather than displaying a single markup instruction.

XSL-FO is commonly used as the output format of XSLT (described earlier in this series. In fact, originally XSLT and XSL-FO were a system called XSL, but the Working Group wisely divided these two parts into two different specifications. There are a variety of open-source or commercial tools that can convert XSL-FO into TeX, Adobe PDF, and other (non-XML) output formats suitable for printing and formatting. This application pattern makes XSL-FO very popular, but XSL-FO has always wanted to be the native rendering format of WYSIWYG tool or similar tools, and this application is also being promoted. XSL-FO 1.1 [in Development] is an upgrade to this language, adding features such as annotation, indexing, bookmarks, and enhancing image processing capabilities.

4. SVG

Scalable Vector Graphics (SVG) 1.1 [W3C recommendation standard] is a language used to describe two-dimensional images. It is mainly a vector graphics language, although it also supports some raster graphics features. The extraordinary ambition of SVG is to provide a practical, flexible, used (well-known) XML Representation of the image format, and at this point it has been very successful. SVG has the following features: Nested conversion, editing path, alpha mask, grating filter effect, template object, and scalability. SVG also supports animation, scaling, and moving views, various graphic primitives, groups, scripts, hyperlinks, structured metadata, CSS, and a dedicated DOM superset (previously described in DOM and CSS), it is easy to embed other XML documents. Some design decisions of SVG have gone through a heated debate, including vector paths represented by a list of numbers separated by spaces in a single attribute, however, SVG has become the most widely used and popular XML application. This specification has been translated into multiple languages.

SVG 1.1 is an update to SVG 1.0 [W3C recommendation standard]. It adds some new features and includes some corrections. The biggest difference is that SVG 1.1 is modularized in a way similar to XHTML 1.1 +. This modularization enables SVG to be scalable and even streamlined, just like Mobile SVG Profiles: SVG Tiny and SVG Basic [W3C recommendation standard. The latter defines the simplified set of the SVG module for mobile phones and PDAs. SVG 1.2 [under development] is committed to adding many new tools, making SVG not only an image format, but also a platform with broad application prospects.

5. VoiceXML

Voice Extensible Markup Language (VoiceXML) Version 2.0 [under development] is a Language for creating audio, Voice, and telephone applications. The audio dialog box contains the following features: speech synthesis, digital audio, voice recognition, and dialing input and recording of telephone sound quality. It seeks to bring the advantages of Web-based development and content delivery into interactive voice response applications. VoiceXML is part of W3C Speech Interface Framework [under development]. The latter also includes other standards, which are not discussed here because of their vague boundaries with the telephone industry. VoiceXML 2.0 marks the transition of the VoiceXML specification from VoiceXML Forum to W3C. The former is still working to improve this technology. VoiceXML has some patent claims, some of which mean that VoiceXML users will be subject to copyright and license fees.

6. MathML

Mathematical Markup Language (MathML) 2.0 [W3C recommendation standard] is an XML Language. According to this standard, it aims to "promote mathematics and scientific content on the Web, and other applications such as computer algebra systems, print and typographical applications, and use and reuse in speech synthesis. MathML can be used to represent and encode mathematical symbols that can be displayed with high quality. It can also be used to encode mathematical content for applications that play a more important role in semantics, such as scientific software or speech synthesis ." MathML is often used to represent equations, formulas, or similar information in fields such as education, scientific papers, industrial regulations, and regulations. This version adds some relatively new features to the [W3C recommendation standard] of MathML 1.01. MathML is often used with XHTML, SVG, and other applications.

7. Synchronized Multimedia Integration Language (SMIL)

SMIL 2.0 [W3C specifications], according to W3C, "supports simple editing of interactive [Audio/Video] presentations. Generally, SMIL is used for ['rich media' or multimedia] presentations, which integrate streaming audio and video, image, text, or any other media type. SMIL is a simple and easy-to-learn HTML-like language. Many SMIL presentations are written in a simple [Text Editor ." SMIL is a W3C Synchronized Multimedia activity product that has been upgraded to SMIL 1.0 [W3C recommendation standard], added features related to animations, metadata, content control, links, timing and synchronization, event processing, and transition effect.

8. RDF

Almost as far as W3C is committed to the next generation of tag technology represented by XML, it has also started research on the next generation of Web Resource formal description technology. Resource Description Framework (RDF) [W3C recommendation standard] is a model used to describe a set of Web Resource declarations. These declarations are conceived as triple, each containing a subject (a URI-as described earlier in this series), a predicate (also a URI) and object (a URI or literal data value ). To understand the meaning of such a statement, consider the HTML meta tag that describes the Web page. If it is applied to RDF, the subject is the URI of the Web page. The predicate is a standard URI that represents a general description, and the object is the actual text of the description. By using a large number of URIs, RDF wants to minimize the ambiguity of these declarative component identifiers so that they can be more formal for machine processing. It is still controversial whether or not RDF can achieve this goal, but it is well known for its very active communities and a wide range of tools.

RDF is the pillar of W3C Semantic Web activity. Semantic Web is a kind of Web video, not only the representation of content, but also the annotation of content to help express its meaning. For example, when describing Web Resources in Semantic Web, you can distinguish between "python" (a snake) and "python" (a computer programming language. RDF standardization consists of a large number of specifications, including:

Resource Description Framework (RDF): Concepts and Abstract Syntax [W3C recommendation standard] puts forward objectives, core Concepts, basic data models, and Abstract Syntax of RDF.
RDF/XML Syntax Specification [W3C recommendation standard] defines a common XML Representation of RDF. Many observers, including myself, complain about the poor tag design of the RDF/XML syntax.
RDF Vocabulary Description Language 1.0: the RDF Schema [W3C recommendation standard] defines an RDF Vocabulary that can be used to define other RDF Vocabulary.
The [W3C recommendation standard] of RDF Semantics is not for those who lack courage. It explores the bottom-layer formal mathematical theory of the RDF data model.
Web Ontology Language (OWL) [W3C recommendation standard] is an application of RDF. It is usually encoded in RDF/XML. A wide range of vocabulary is added for formal classification and Induction of RDF resources.

9. XML Topic Maps

Topic Maps [ISO International Standard, No. 13250] provides a system for organizing information. In some respects, it is a Semantic Web technology competing with RDF. Specifically, XML Topic Maps [part of ISO 13250] is a Web-friendly version of Topic Maps. It uses XML syntax and uses URI as the identifier. Similar to RDF, Topic Maps defines a graph-like model, but more subtle differences are related to such a fact, that is, an important rule of Topic Maps is the distinction between actual concepts and computer representations. Topic Maps is a basic tool of Semantic Web, or adds unnecessary complexity. This debate between Topic Maps and RDF supporters will never end up. XML Topic Maps uses a clear XML syntax based on XLink.

-- Refer to IBM developworks