ECMAScript for XML Specification(Ecma-357)(2)

A conforming implementation of this Standard shall conform to the ECMAScript Language Specfication, ISO/IEC 16262:2001.

A conforming implementation of this Standard shall interpret characters in conformance with the Unicode Standard, Version 2.1 or later, and ISO/IEC 10646-1 with either UCS-2 or UTF-16 as the adopted encoding form, implementation level 3. If the adopted ISO/IEC 10646-1 subset is not otherwise specified, it is presumed to be the BMP subset, collection 300. If the adopted encoding form is not otherwise specified, it presumed to be the UTF-16 encoding form.

A conforming implementation of E4X may provide additional types, values, objects, properties, and functions beyond those described in this specification. In particular, a conforming implementation of E4X may provide properties not described in this specification, and values for those properties, for objects that are described in this specification. A conforming implementation of E4X shall not provide methods for XML.prototype and XMLList.prototype other than those described in this specification.

3 References

3.1 Normative References

Document Object Model (DOM) Level 2 Specifications, W3C Recommendation, 13 November 2000. ECMA-262, 1999, ECMAScript Language Specification – 3rd edition.

Extensible Markup Language 1.0 (Second Edition), W3C Recommendation 6 October 2000. Namespaces in XML, W3C Recommendation, 14 January 1999.

ISO/IEC 10646:2003, Information Technology – Universal Multiple-Octet Coded Character Set (UCS).

Unicode Inc. (1996), The Unicode StandardTM, Version 2.0. ISBN: 0-201-48345-9, Addison-Wesley Publishing Co., Menlo Park, California.

Unicode Inc. (1998), Unicode Technical Report #8: The Unicode StandardTM, Version 2.1. Unicode Inc. (1998), Unicode Technical Report #15: Unicode Normalization Forms. XML Information Set, W3C Recommendation 24 October 2001.

XML Path Language (XPath) Version 1.0, W3C Recommendation 16 November 1999. XML Schema Part 1: Structures, W3C Recommendation, 2 May 2001. XML Schema Part 2: Datatypes, W3C Recommendation, 2 May 2001.

3.2 Informative References

XSL Transformations (XSLT), W3C Recommendation 16 November 1999.

- 1-

欧洲计算机制造商协会(ECMA)标准文档

4 Definitions

For the purpose of this Ecma Standard the following definitions apply:

4.1 XML

The Extensible Markup Language (XML) is an information encoding standard endorsed by the World Wide Web Consortium (W3C) for sending, receiving, and processing data across the World Wide Web. XML comprises a series of characters that contains not only substantive information, called character data, but also meta-information about the structure and layout of the character data, called markup.

4.2 Markup

One of the two basic constituents of XML data (the other is character data). Markup is a series of characters that provides information about the structure or layout of character data. Common forms of markup are start-tags, end-tags, empty-element tags, comments, CDATA tag delimiters, and processing instructions.

4.3 Character data

One of the two basic constituents of XML data (the other is markup). Character data is a series of

characters that represents substantive data encapsulated by XML markup. Character data is defined as any series of characters that are not markup.

4.4 Tag

A single markup entity that acts as a delimiter for character data. A tag can be a start-tag, an end-tag, or an empty-element tag. Start-tags begin with a less than (<) character and end with a greater than (>) character. End-tags begin with a pairing of the less than and slash characters (</) and end with a greater than (>) character. Empty-element begin with a less than (<) character and end with a pairing of the slash and greater than (/>) characters.

4.5 Element

A data construct comprising two tags (a start-tag and an end-tag) that delimit character data or nested elements. If neither character data nor nested elements exist for a given element, then the element can be defined by a single empty-element tag. Every well-formed XML document contains at least one element, called the root or document element.

4.6 Attribute

An optional name-value pair, separated by an equal sign (=), that can appear inside a tag. Attributes can store information about an element or actual data that would otherwise be stored as character data.

4.7 Namespace

A group of identifiers for elements and attributes that are collectively bound to a Uniform Resource Identifier (URI) such that their use will not cause naming conflicts when used with identically named identifiers that are in a different namespace.

4.8 processing-instruction

A markup entity that contains instructions or information for the application that is processing the XML. Processing-instruction tags begin with a combination of the less than (<) character and a question mark (?) character (<?) and end with the same combination of characters but in reverse order (?>).

4.9 Type

A set of data values.

- 2-

欧洲计算机制造商协会(ECMA)标准文档

5 Motivation

This section contains a non-normative overview of the motivation behind ECMAScript for XML.

5.1 The Rise of XML Processing

Developing software to create, navigate and manipulate XML data is a significant part of every developer’s job. Developers are inundated with data encoded in the eXtensible Markup Language (XML). Web pages are increasingly encoded using XML vocabularies, including XHTML and Scalable Vector Graphics (SVG). On mobile devices, data is encoded using the Wireless Markup Language (WML). Web services interact using the Simple Object Access Protocol (SOAP) and are described using the Web Service Description Language (WSDL). Deployment descriptors, project mak …… 此处隐藏：5828字，全部文档内容请下载后查看。喜欢就下载吧 ……