The Extensible Markup Language (XML) is an open, general-purpose specification for creating markup languages. Its primary purpose is to help information systems share structured data, particularly via the Internet, and it is used both to encode documents and to serialize data. It is used in a wide variety of technical communication document formats, including Microsoft Word, OpenOffice, XHTML, DITA, DocBook, and RSS, among others.
This XML introduction is geared toward newcomers who have heard the buzz, but don't know what all the fuss is about. The article briefly surveys a number of new Web technologies such as XLL, XSL, RDF, DOM, MathML, SMIL, PGML, and how they relate to XML. Benefits of XML are stressed, as are potential applications in diverse fields. A reference section provides links to key XML resources, as well as to collections of other introductory articles.
XMLmind is a great introductory tool for technical writers entering the world of structured authoring and DocBook. It successfully hides the esoterics of XML markup from the author, so that the focus can be on the words, rather than the code. At no cost (yes, absolutely free) for the Standard edition, and USD220 for a single user licence for the Professional Edition, XMLmind offers excellent value. The software is available for Linux, Windows and Mac. There are two main problems with XMLmind XML Editor: it does not currently support DITA schemas, and it does not incorporate a (Notepad-like) text editor in case you do need to patch up your code.
Relational database systems (and the related standards body ANSI/INCITS H2) are busy adding XML support. One of the main components of such XML extensions will be support for the upcoming XML query language XQuery. The presentation will outline how XQuery and XML conceptually fit into a relational database environment. It will cover the organization of the XML in the database, how to type it using W3C XML Schema, how to query it both in conjunction with SQL and using top-level XQuery. It will present the concepts, talk about new developments in the ISO/ANSI SQL/XML standards and present some demos of XQuery in the upcoming Microsoft® SQL Server 2005.
XQuery, the query language for XML, can be used to modify XML. In this article, learn about the various ways to modify XML, including XML stored in memory or in a DB2® pureXML™ database. Explore the different ways to modify XML in four different use cases: health care, business, financial derivatives, and information technology, while utilizing DB2 pureXML. Finally, examine guidelines for when to use XQuery to perform either sub-document updates or full document replacement and versioning of the stored XML.
New office document standards like the OpenDocument Format(ODF) and Office Open XML (OOXML), however, are making office document integration in business processes a reality. A key benefit of ODF and OOXML for developers is the reuse of existing standards.
XQuery speeds up the process of finding information contained in an XML document -- which is very handy when dealing with long XML documents. This article, the second of two parts, will teach you how to write XQuery expressions.
Vous êtes rédacteur technique ou gestionnaire d’un portfolio documentaire écrit en XML ? Vous avez devant vous des dizaines de milliers de lignes de XML et c’est souvent dur de rechercher une information précise ? Alors XQuery est fait pour vous!
XQuery is a language that operates on XML in its native data model, using the type system of XML Schema. By the time of the XML 2006 conference, XQuery Version 1.0 will probably be adopted as a W3C Recommendation. Like SQL, XQuery is declarative and functional, which makes it well-suited for automatic optimization. XQuery Version 1.0 is designed for querying and transforming XML data, and W3C has published a working draft of an XQuery extension for updating XML data. With an additional small extension, XQuery could be turned into a native application development language for XML, eliminating the impedance mismatch problem. An earlier paper briefly outlined such an extension, called XQueryP. This paper expands on the XQueryP proposal, adding more details, additional features such as error handling, and some use cases that illustrate the use of the extended language in various different environments.
With the publication of XrML 2.0, ContentGuard provides an open, flexible, and extensible means of expressing digital rights that not only addresses copy protection, but, as importantly, offers a much broader and powerful means for publishers to experiment with and deploy new business models.
The XSL stylesheets used at PubMed Central for data conversion present a particular challenge because documentation is needed not only for the reference of developers, but also for digital archivists to ensure that the conversion process conforms to accepted archiving standards. The choices that developers make in writing conversion filters need to be transparent and reviewable. To meet this need, we defined a format for inserting documentation into XSL stylesheets. The documentation had to be easy to maintain and needed to be capable of generating documentation for developers, archivists, and other stakeholders.
Since many of the XSLT processors are written in Java, they can be directly invoked from a Java application or servlet. This chapter is devoted to Java and XSLT programming techniques that work for both standalone applications as well as servlets, with a particular emphasis on Sun's Java API for XML Processing (JAXP) API.
XSL stands for EXtensible Stylesheet Language, and is a style sheet language for XML documents. XSLT stands for XSL Transformations. In this tutorial you will learn how to use XSLT to transform XML documents into other formats, like XHTML.
This paper describes the design of a new language to formally specify constraints over Topic Maps. This language allows to express contextual conditions on classes of Topic Maps and the corresponding processing syntem. With XTche, a topic map designer defines a set of restrictions that enables to verify if a particular topic map is semantically valid. As the manual checking of large topic maps (frequent in real cases) is impossible, it is mandatory to provide an automatic validator.
In Mozilla-based applications, the yellow screen of death is the screen displayed when they encounter an XML parsing error. This typically happens when the XML document that the browser is trying to access is not well-formed, for example when it does not nest tags properly.
Рано или поздно созданный вами XML-документ кто-то захочет перевести на другой язык. В действительности XML-документы переводить гораздо легче нежели другие электронные документы, т. к. они разделяют форму и содержание и соответствуют строгому стандарту и установленному синтаксису.