POX - Plain Old XML: High-impact Strategies - What You Need to Know: Definitions, Adoptions, Impact, Benefits, Maturity, Vendors

Kevin Roebuck

Description

The Knowledge Solution. Stop Searching, Stand Out and Pay Off. The #1 ALL ENCOMPASSING Guide to POX - Plain Old XML.

An Important Message for ANYONE who wants to learn about POX - Plain Old XML Quickly and Easily...

""Here's Your Chance To Skip The Struggle and Master POX - Plain Old XML, With the Least Amount of Effort, In 2 Days Or Less...""

Plain Old XML (POX) is a term used to describe basic XML, sometimes mixed in with other, blendable specifications like XML Namespaces, Dublin Core, XInclude and XLink. People typically use the term as a contrast with complicated, multilayered XML specifications like those for web services or RDF. The term may have been derived from or inspired by the expression plain old telephone service (a.k.a. POTS) and, similarly Plain Old Java Object.

Get the edge, learn EVERYTHING you need to know about POX - Plain Old XML, and ace any discussion, proposal and implementation with the ultimate book - guaranteed to give you the education that you need, faster than you ever dreamed possible!

The information in this book can show you how to be an expert in the field of POX - Plain Old XML.

Are you looking to learn more about POX - Plain Old XML? You're about to discover the most spectacular gold mine of POX - Plain Old XML materials ever created, this book is a unique collection to help you become a master of POX - Plain Old XML.

This book is your ultimate resource for POX - Plain Old XML. Here you will find the most up-to-date information, analysis, background and everything you need to know.

In easy to read chapters, with extensive references and links to get you to know all there is to know about POX - Plain Old XML right away. A quick look inside: Plain Old XML, QName, Water Data Transfer Format, XML, XML Configuration Access Protocol, Arbortext Command Language, BaseX, Billion laughs, Binary XML, Business Process Definition Metamodel, CCTRL, CDATA, CDuce, Character entity reference, CodeSynthesis XSD, D3L, Darwin Information Typing Architecture, DITA Open Toolkit, Document Structure Description, Document-oriented database, Dynamic XML, ECMAScript for XML, Efficient XML Interchange, EXchangeable Faceted Metadata Language, EXtensible Server Pages, Fast Infoset, FLWOR, FuseDocs (programming), FXG, Global listings format, GMX, GMX-V, Head-Body Pattern, HyTime, Intel SOA Products Division, Interactive Financial Exchange, Internationalization Tag Set, Klip, List of XML and HTML character entity references, Mallard (documentation), MAREC, Media Object Server, METS, Numeric character reference, NZB, Office Open XML, Office Open XML file formats, OIOXML, Open XML Paper Specification, OpenSearch, PCDATA, People Finder Interchange Format, Portable Application Description, Processing Instruction, Publishing Requirements for Industry Standard Metadata, QTI, RailML, Requirements Interchange Format, Resource Description Framework, Resources of a Resource, RoadXML, Root element, Schema for Object-Oriented XML, Schematron, Simple Outline XML, Simple XML, SpeakRight Framework, Streaming XML, Styled Layer Descriptor, Tag omission, UJML, Unique Particle Attribution, Valid characters in XML, Valid XML document, VTD-XML, Well-formed document, X-expression, XBRLS, Xdos, XDR Schema, XEE (Starlight), XEP, XFDesigner, XidML, XML and MIME, XML appliance, XML Base, XML Catalog, XML Certification Program, XML data binding, XML database, XML editor, XML Enabled Directory, XML Encryption, XML Events, XML framework, XML Literals, XML namespace, XML Protocol, XML schema, XML Schema Editor, XML Schema Language comparison, XML stanza...and Much, Much More!

This book explains in-depth the real drivers and workings of POX - Plain Old XML. It reduces the risk of your technology, time and resources investment decisions by enabling you to compare your understanding of POX - Plain Old XML with the objectivity of experienced professionals - Grab your copy now, while you still can.

Sujets

• General
• General officer
• Informatique
• COMPUTERS

Informations

• Publié par: Emereo Publishing
• Date de parution: 24 octobre 2012
• Nombre de lectures: 0
• EAN13: 9781743380062
• Langue: English
• Poids de l'ouvrage: 5 Mo

Extrait

Topic relevant selected content from the highest rated entries, typeset, printed and shipped.

Combine the advantages of up-to-date and in-depth knowledge with the con- venience of printed books.

A portion of the proceeds of each book will be donated to the Wikimedia Foundation to support their mission: to empower and engage people around the world to collect and develop educational content under a free license or in the public domain, and to disseminate it eectively and globally.

e content within this book was generated collaboratively by volunteers. Please be advised that nothing found here has necessarily been reviewed by people with the expertise required to provide you with complete, accurate or reliable information. Some information in this book maybe misleading or simply wrong. e publisher does not guarantee the validity of the infor- mation found here. If you need specic advice (for example, medical, legal, nancial, or risk management) please seek a professional who is licensed or knowledgeable in that area.

Sources, licenses and contributors of the articles and images are listed in the section entitled “References”. Parts of the books may be licensed under the GNU Free Documentation License. A copy of this license is included in the section entitled “GNU Free Documentation License”

All used third-party trademarks belong to their respective owners.

Contents

Articles Plain Old XML QName Water Data Transfer Format XML XML Configuration Access Protocol Arbortext Command Language BaseX Billion laughs Binary XML Business Process Definition Metamodel CCTRL CDATA CDuce Character entity reference CodeSynthesis XSD D3L Darwin Information Typing Architecture DITA Open Toolkit Document Structure Description Document-oriented database Dynamic XML ECMAScript for XML Efficient XML Interchange eXchangeable Faceted Metadata Language eXtensible Server Pages Fast Infoset FLWOR FuseDocs (programming) FXG Global listings format GMX GMX-V Head-Body Pattern HyTime

1 2 3 3 15 17 18 20 21 22 24 25 28 29 31 32 32 35 36 37 42 43 45 46 46 47 49 51 51 52 52 53 54 54

Intel SOA Products Division Interactive Financial Exchange Internationalization Tag Set Klip List of XML and HTML character entity references Mallard (documentation) MAREC Media Object Server METS Numeric character reference

NZB Office Open XML Office Open XML file formats OIOXML Open XML Paper Specification OpenSearch PCDATA People Finder Interchange Format Portable Application Description Processing Instruction Publishing Requirements for Industry Standard Metadata

QTI RailML Requirements Interchange Format Resource Description Framework Resources of a Resource RoadXML Root element Schema for Object-Oriented XML Schematron Simple Outline XML Simple XML SpeakRight Framework Streaming XML Styled Layer Descriptor Tag omission UJML Unique Particle Attribution

56 57 58 61 62 73 74 75 75 78 80 81 91 100 101 107 109 110 112 113 114 116 121 122

123 132 133 134 135 136 138 139 140 141 141 142 143 144

Valid characters in XML Valid XML document VTD-XML Well-formed document X-expression XBRLS Xdos XDR Schema XEE (Starlight) XEP XFDesigner XidML XML and MIME XML appliance XML Base XML Catalog XML Certification Program XML data binding XML database XML editor XML Enabled Directory XML Encryption XML Events XML framework XML Literals XML namespace XML Protocol XML schema XML Schema Editor XML Schema Language comparison XML stanza XML Telemetric and Command Exchange XML tree

XML validation XML-Enabled Networking XML-Retrieval XMLHttpRequest XMLSocket

145 146 147 153 154 154 156 156 157 158 160 161 164 165 167 167 169 174 175 177 180 181 181 183 183 184 186 187 190 193 198 198 200 200 201 203 205 211

XPath XPath 2.0 Xs3p

References Article Sources and Contributors Image Sources, Licenses and Contributors

Article Licenses License

213 214 217

218 223

224

Plain Old XML

Plain Old XML

Plain Old XML(POX) is a term used to describe basic XML, sometimes mixed in with other, blendable specifications like XML Namespaces, Dublin Core, XInclude and XLink. People typically use the term as a contrast with complicated, multilayered XML specifications like those for web services or RDF. The term may have been derived from or inspired by the expression plain old telephone service (a.k.a. POTS) and, similarly Plain Old Java Object.

An interesting question is how POX relates to XML Schema. On the one hand, POX is completely compatible with XML Schema. However, many POX users eschew XML Schema to avoid the poor or inconsistent quality of XML Schema-to-Java tools. POX is complementary to REST: REST refers to a communication pattern, while POX refers to an information format style. The primary competitors to POX are more strictly-defined XML-based information formats such as RDF and SOAP section 5 encoding, as well as general non-XML information formats such as JSON and CSV.

External links [1]  REST and POX article from the Microsoft Developer Network [2]  Plain Old XML Considered Harmful from Microformats.org [3]  Support for POX in the Java Spring Framework [4]  PlainXML on SourceForge.net

References [1] http://msdn.microsoft.com/en-us/library/aa395208.aspx [2] http://microformats.org/wiki/plain-old-xml-considered-harmful [3] http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/pox/package-summary.html [4] http://sourceforge.net/projects/plainxml/

1

QName

QName

[1] QNameswere introduced by XML Namespaces in order to be used as URI references . QName stands for "qualified name" and defines a valid identifier for elements and attributes. QNames are generally used to reference [2] particular elements or attributes within XML documents.

Motivation Since URI references can be long and may contain prohibited characters for element/attribute naming, QNames are used to create a mapping between the URI and a namespace prefix. The mapping enables the abbreviation of URIs, therefore it achieves a more convenient way to write XML documents. (see Example)

Formal definition [3] QNames are formally defined by the W3C as :

 QName ::= PrefixedName | UnprefixedName  PrefixedName ::= Prefix ':' LocalPart  UnprefixedName ::= LocalPart

Whereby the Prefix is used as placeholder for the namespace and the LocalPart as the local part of the qualified name. A local part can be an attribute name or an element name.

Example <?xml version='1.0'?> <docxmlns:x="http://example.com/ns/foo"> <x:p/> </doc>

In line two the prefix "x" is declared to be associated with the URI "http://example.com/ns/foo". This prefix can further on be used as abbreviation for this namespace. Subsequently the tag "x:p" is a valid QName because it uses the "x" as namespace reference and "p" as local part. The tag "doc" is also a valid QName, but it consists only of a [4] local part.

References [1] Namespaces in XML 1.0 (Second Edition) (http:/ /www.w3.org/TR/REC-xml-names/#dt-qualname) [2] Using Qualified Names (QNames) as Identifiers in XML Content (http:/ /www.w3.org/2001/tag/doc/qnameids.html#sec-qnames-xml) [3] Namespaces in XML 1.0 (Second Edition) (http:/ /www.w3.org/TR/REC-xml-names/#NT-QName) [4] Namespaces in XML 1.0 (Second Edition) (http:/ /www.w3.org/TR/REC-xml-names/#NT-LocalPart)

2

Water Data Transfer Format

Water Data Transfer Format

Water Data Transfer Format(WDTF) is a data delivery standard implemented by the Australian Bureau of Meteorology (BoM) that was jointly developed with the CSIRO. The standard, released in 2009, specifies both the [1] format of and the techniques used to deliver Australian water data measurements to the BoM. Some private organisations and government agencies in Australia that collect water data are mandated to deliver it to the BoM [2] according to the (Australian) Water Act 2007.

An external meteorological data source that delivers data in WDTF-compliant forms is the CSIRO Land & Water's [3] Automatic Weatherstation Network . Data from this weatherstation network can be viewed in a web browser, downloaded at text values in CSV format, downloaded in a condensed XML format for machine-to-machine communications, or downloaded as WDTF-compliant data. To see examples of these formats, visit the [4] weatherstation network project's main page at http://weather.irrigateway.net The use of WDTF is an example of work in the field of Irrigation Informatics.

References [1] (http://www.bom.gov.au/water/regulations/wdtf/index.shtml), Australian Bureau of Meteorology: Water Information: Regulations: WDTF [2] (http://www.bom.gov.au/water/about/publications/document/InfoSheet_2.pdf), The Water Act 2007 and Water Regulations 2008 information sheet, Bureau of Meteorology [3] http://www.clw.csiro.au/services/weather [4] http://weather.irrigateway.net

XML

Filename extension

Internet media type

.xml

XML

[1] application/xml, [2] [3] text/xml(deprecated in an expired draft)

Uniform Type Identifierpublic.xml

UTI conforms to

Developed by

Type of format

Extended from

public.text

World Wide Web Consortium

Markup language

SGML

3

Yes

Year Started

Extensible Markup Language (XML)

Open format?

1996

Data Serialization

[6] XML 1.0

Markup and Content

Extended to

Standard(s)

The characters which make up an XML document are divided intomarkupandcontent. Markup and content may be distinguished by the application of simple syntactic rules. All strings which constitute markup either begin with the character "<" and end with a ">", or begin with the character "&" and end with a ";". Strings of characters which are not markup are content.

Published

Theprocessoranalyzes the markup and passes structured information to anapplication. The specification places requirements on what an XML processor must do and not do, but the application is outside its scope. The processor (as the specification calls it) is often referred to colloquially as anXML parser.

XML

TimBray,JeanPaoli,C.M.Sperberg-McQueen,EveMaler,FranaoisYergeau,JohnCowan

Related StandardsXML Schema

Processor and Application

XML

Current Status

Website

Extensible Markup Language(XML) is a set of rules for encoding documents in machine-readable form. It is [7] defined in the XML 1.0 Specification produced by the W3C, and several other related specifications, all gratis [8] open standards. [9] The design goals of XML emphasize simplicity, generality, and usability over the Internet. It is a textual data format with strong support via Unicode for the languages of the world. Although the design of XML focuses on documents, it is widely used for the representation of arbitrary data structures, for example in web services. Many application programming interfaces (APIs) have been developed that software developers use to process XML data, and several schema systems exist to aid in the definition of XML-based languages. [10] As of 2009, hundreds of XML-based languages have been developed, including RSS, Atom, SOAP, and XHTML. XML-based formats have become the default for most office-productivity tools, including Microsoft [11] Office (Office Open XML), OpenOffice.org (OpenDocument), and Apple's iWork.

Editors

Key terminology The material in this section is based on the XML Specification. This is not an exhaustive list of all the constructs which appear in XML; it provides an introduction to the key constructs most often encountered in day-to-day use. (Unicode) Character

By definition, an XML document is a string of characters. Almost every legal Unicode character may appear in an XML document.

Numerous, including: XHTML, RSS, Atom, KML

[4] 1.0 (Fifth Edition) November 26, 2008 [5] 1.1 (Second Edition) August 16, 2006

4

Abbreviation

Domain

XML

Tag

5

A markup construct that begins with "<" and ends with ">". Tags come in three flavors:start-tags, for example <section>,end-tags, for example</section>, andempty-element tags, for example <line-break />. Element A logical document component that either begins with a start-tag and ends with a matching end-tag or consists only of an empty-element tag. The characters between the start- and end-tags, if any, are the element'scontent, and may contain markup, including other elements, which are calledchild elements. An example of an element is<Greeting>Hello, world.</Greeting>(see hello world). Another is<line-break />. Attribute A markup construct consisting of a name/value pair that exists within a start-tag or empty-element tag. In the example (below) the elementimghas two attributes,srcandalt: <img&nbsp;src="madonna.jpg"&nbsp;alt='Foligno&nbsp;Madonna,&nbsp;by&nbsp;Raphael'&nbsp;/>. Another example would be<step number="3">Connect A to B.</step>where the name of the attribute is "number" and the value is "3". XML Declaration XML documents may begin by declaring some information about themselves, as in the following example.

<?xml version="1.0" encoding="UTF-8" ?>

Characters and escaping XML documents consist entirely of characters from the Unicode repertoire. Except for a small number of specifically excluded control characters, any character defined by Unicode may appear within the content of an XML document. The selection of characters that may appear within markup is somewhat more limited but still large. XML includes facilities for identifying theencodingof the Unicode characters that make up the document, and for expressing characters that, for one reason or another, cannot be used directly.

Valid characters [12] Unicode code points in the following ranges are valid in XML 1.0 documents:  U+0009, U+000A, U+000D: these are the only C0 controls accepted in XML 1.0;  U+0020–U+D7FF, U+E000–U+FFFD: this excludessome(not all) non-characters in the BMP (all surrogates, U+FFFE and U+FFFF are forbidden);  U+1000–0U+10FFFF: this includesallcode points in supplementary planes, including non-characters. [13] XML 1.1 extends the set of allowed characters to include all the above, plus the remaining characters in the range U+0001–U+001F. At the same time, however, it restricts the use of C0 and C1 control characters other than U+0009, U+000A, U+000D, and U+0085 by requiring them to be written in escaped form (for example U+0001 must be written as &#x01; or its equivalent). In the case of C1 characters, this restriction is a backwards incompatibility; it was introduced to allow common encoding errors to be detected. The code point U+0000 is the only character that is not permitted in any XML 1.0 or 1.1 document.