|
Composite Capability/Preference Profiles (CC/PP):
Structure and Vocabularies
This document describes CC/PP (Composite Capabilities/Preference Profiles) structure and vocabularies. A CC/PP profile is a description of device capabilities and user preferences that can be used to guide the adaptation of content presented to that device.
|
|
Voice Browser Call Control: CCXML Version 1.0
This document describes CCXML, or the Call Control eXtensible Markup Language. CCXML is designed to provide telephony call control support for VoiceXML or other dialog systems
|
|
Cascading Style Sheets, level 1
This document is a W3C Recommendation. It has been reviewed by W3C (http://www.w3.org/) Members and general consensus that the specification is appropriate for use has been reached. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C promotes widespread deployment of this Recommendation
|
|
Cascading Style Sheets, level 2
CSS2 Specification
This specification defines Cascading Style Sheets, level 2 (CSS2). CSS2 is a style sheet language that allows authors and users to attach style (e.g., fonts, spacing, and aural cues) to structured documents (e.g., HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS2 simplifies Web authoring and site maintenance.
|
|
Cascading Style Sheets, level 2 revision 1
CSS 2.1 Specification
This specification defines Cascading Style Sheets, level 2 revision 1 (CSS 2.1). CSS 2.1 is a style sheet language that allows authors and users to attach style (e.g., fonts, spacing, and aural cues) to structured documents (e.g., HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS 2.1 simplifies Web authoring and site maintenance.
|
|
Document Definition Markup Language (DDML) Specification, Version 1.0
This document is a NOTE made available by W3C for discussion only. This indicates no endorsement of its content, nor that W3C has had any editorial control in its preparation, nor that W3C has, is, or will be allocating any resources to the issues addressed by the NOTE.
|
|
Decryption Transform for XML Signature
This document specifies an XML Signature "decryption transform" that enables XML Signature applications to distinguish between those XML Encryption structures that were encrypted before signing (and must not be decrypted) and those that were encrypted after signing (and must be decrypted) for the signature to validate.
|
|
OASIS DocBook TC
The purpose of this TC is to further develop and maintain the DocBook DTD, which is particularly well suited to books and papers about computer hardware and software, in both SGML and XML.
|
|
Document Object Model (DOM) Level 1 Specification
This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
|
|
Document Object Model (DOM) Level 2 Core Specification
This specification defines the Document Object Model Level 2 Core, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content and structure of documents. The Document Object Model Level 2 Core builds on the Document Object Model Level 1 Core.
|
|
Document Object Model (DOM) Level 2 Events Specification
This specification defines the Document Object Model Level 2 Events, a platform- and language-neutral interface that gives to programs and scripts a generic event system. The Document Object Model Level 2 Events builds on the Document Object Model Level 2 Core [DOM Level 2 Core] and on Document Object Model Level 2 Views
|
|
Document Object Model (DOM) Level 2 HTML Specification
This specification defines the Document Object Model Level 2 HTML, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content and structure of [HTML 4.01] and [XHTML 1.0] documents. The Document Object Model Level 2 HTML builds on the Document Object Model Level 2 Core [DOM Level 2 Core] and is not backward compatible with DOM Level 1 HTML [DOM Level 1].
|
|
Document Object Model (DOM) Level 2 Style Specification
This specification defines the Document Object Model Level 2 Style Sheets and Cascading Style Sheets (CSS), a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content and of style sheets documents. The Document Object Model Level 2 Style builds on the Document Object Model Level 2 Core [DOM Level 2 Core] and on the Document Object Model Level 2 Views [DOM Level 2 Views].
|
|
Web Services: The Next Generation of Distributed Computing
Move over client-server. Step aside N-tier computing. Here come Web services, the latest stage in the evolution--or devolution--of applications into smaller and smaller, ever more granular components. One by one, Hewlett-Packard, Sun Microsystems, IBM, Microsoft and even Oracle have trotted out their visions for creating, deploying, managing and sharing Web services.
|
|
Document Object Model (DOM) Level 2 Traversal and Range Specification
This specification defines the Document Object Model Level 2 Traversal and Range, platform- and language-neutral interfaces that allow programs and scripts to dynamically traverse and identify a range of content in a document. The Document Object Model Level 2 Traversal and Range build on the Document Object Model Level 2 Core [DOM Level 2 Core].
|
|
Document Object Model (DOM) Level 2 Views Specification
This specification defines the Document Object Model Level 2 Views, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content of a representation of a document. The Document Object Model Level 2 Views builds on the Document Object Model Level 2 Core [DOM Level 2 Core].
|
|
Document Object Model (DOM) Level 2 Views Specification
This specification defines the Document Object Model Level 2 Views, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content of a representation of a document. The Document Object Model Level 2 Views builds on the Document Object Model Level 2 Core [DOM Level 2 Core].
|
|
Document Object Model (DOM) Level 3 Core Specification
This specification defines the Document Object Model Core Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model Core Level 3 builds on the Document Object Model Core Level 2 [DOM Level 2 Core].
|
|
Document Object Model (DOM) Level 3 Load and Save Specification
This specification defines the Document Object Model Load and Save Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically load the content of an XML document into a DOM document and serialize a DOM document into an XML document; DOM documents being defined in [DOM Level 2 Core] or newer, and XML documents being defined in [XML 1.0] or newer.
|
|
Document Object Model (DOM) Level 3 Validation Specification
This specification defines the Document Object Model Validation Level 3, a platform- and language-neutral interface. This module provides the guidance to programs and scripts to dynamically update the content and the structure of documents while ensuring that the document remains valid, or to ensure that the document becomes valid.
|
|
Document Object Model (DOM) Level 3 Views and Formatting Specification
This specification defines the Document Object Model Views and Formatting Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model Views and Formatting Level 3 builds on the Document Object Model Views Level 2.
|
|
Document Object Model (DOM) Level 3 XPath Specification
This specification defines the Document Object Model Level 3 XPath. It provides simple functionalities to access a DOM tree using [XPath 1.0].
|
|
OASIS ebXML Collaboration Protocol Profile and Agreement TC
The purpose of this TC is to continue to develop the Collaboration Protocol Profiles (CPPs) and Collaboration Protocol Agreements (CPAs), which define a business partner's technical capabilities to engage in electronic business collaborations with other partners, and the technical agreement between two (or more) partners to engage in electronic business collaboration.
|
|
OASIS ebXML Implementation, Interoperability and Conformance TC
The purpose of this TC is to provide a means for software vendors to create infrastructure and applications which adhere to the ebXML specifications and are able to interoperate.
|
|
OASIS ebXML Messaging Services TC
The purpose of this TC is to develop and recommend technology for the transport, routing and packaging of business transactions using standard Internet technologies.
|
|
OASIS ebXML Registry TC
The OASIS ebXML Registry Technical Committee is pleased to announce that two specs were recently approved as Committee Approved Specifications according to the OASIS approved process. The documents are the OASIS/ebXML Registry Information Model Specification v2.5 and the OASIS/ebXML Registry Services Specification v2.5. These documents can be viewed from the Registry TC Home Page under the Documents link: http://www.oasis-open.org/committees/documents.php.
|
|
Link recognition for the XHTML Family
The HLink module defined in this specification provides XHTML Family Members with the ability to specify which attributes of elements represent Hyperlinks, and how those hyperlinks should be traversed, and extends XLink use to a wider class of languages than those restricted to the syntactic style allowed by XLink.
|
|
What is MathML?
MathML 2.0, a W3C Recommendation was released on 21 Feb 2001. A product of the W3C Math working group, MathML is a low-level specification for describing mathematics as a basis for machine to machine communication. It provides a much needed foundation for the inclusion of mathematical expressions in Web pages [more].
|
|
Mobile SVG Profiles: SVG Tiny and SVG Basic
This document defines two mobile profiles of SVG 1.1. The first profile, SVG Tiny, is defined to be suitable for cellphones; the second profile, SVG Basic, is suitable for PDAs.
|
|
Namespaces in XML
This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
|
|
Namespaces in XML 1.1
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 IRI references.
|
|
OWL Web Ontology Language
The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans. OWL facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. OWL has three increasingly-expressive sublanguages: OWL Lite, OWL DL, and OWL Full.
|
|
The Platform for Privacy Preferences 1.0 (P3P1.0) Specification
This is the specification of the Platform for Privacy Preferences (P3P). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P applications.
|
|
Resource Description Framework
(RDF) Model and Syntax Specification
This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from other documents. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
|
|
RDF Primer
The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. It is particularly intended for representing metadata about Web resources, such as the title, author, and modification date of a Web page, copyright and licensing information about a Web document, or the availability schedule for some shared resource. However, by generalizing the concept of a "Web resource", RDF can also be used to represent information about things that can be identified on the Web, even when they can't be directly retrieved on the Web. RDF provides a common framework for expressing this information so it can be exchanged between applications without loss of meaning.
|
|
RDF Semantics
This is a specification of a precise semantics for RDF and RDFS, and of corresponding entailment and inference rules which are sanctioned by the semantics.
|
|
RDF Test Cases
This document describes the RDF Test Cases deliverable for the RDF Core Working Group as defined in the WG's Charter.
|
|
http://www.w3.org/TR/rdf-schema/
The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. This specification describes how to use RDF to describe RDF vocabularies. This specification defines a vocabulary for this purpose and defines other built-in RDF vocabulary initially specified in the RDF Model and Syntax Specification.
|
|
Resource Description Framework (RDF):
The Resource Description Framework (RDF) is a framework for representing information in the Web.
This document defines an abstract syntax on which RDF is based, and which serves to link its concrete syntax to its formal semantics. It also includes discussion of design goals, meaning of RDF documents, key concepts, datatyping, character normalization and handling of URI references.
|
|
RDF/XML Syntax Specification (Revised)
The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web.
|
|
OASIS RELAX NG TC
The purpose of this TC is to create a specification for a schema language that is simple, easy to learn, and uses XML syntax.
|
|
Ruby Annotation
This is part one of a 4 part series on how to use SOAP with Visual Age and WebSphere. All lot of this articles just show how to install and configure the SOAP engine with VAJ/WAS. Part 2 will be useful to anybody using SOAP regardless of which server you're using as it shows how to write the server adapter code for binding SOAP to session beans. Part 3 gets SSL working and Part 4 will get certificate based authentication working.
|
|
Ruby Annotation
Ruby" are short runs of text alongside the base text, typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This specification defines markup for ruby, in the form of an XHTML module [XHTMLMOD].
|
|
XML Standards
|
|
Synchronized Multimedia Integration Language (SMIL) 1.0 Specification
This document specifies version 1 of the Synchronized Multimedia Integration Language (SMIL 1.0, pronounced "smile"). SMIL allows integrating a set of independent multimedia objects into a synchronized multimedia presentation.
|
|
Synchronized Multimedia Integration Language (SMIL 2.0)
This document specifies the second version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile").
|
|
SMIL 2.0 Extension for Professional Multimedia Authoring - Preliminary Investigation
We are investigating the possibilities of SMIL 2.0 for professional multimedia content authoring. In this document we itemize requirements for content description capabilities of professional multimedia production and verify how much SMIL 2.0 can satisfy them. The requirements are categorized in terms of material identification and content description, which include issues not only about media synchronization but also about audiovisual special effects. Finally we propose several possible extensions to SMIL 2.0 function modules clarifying the limitations of current SMIL 2.0.
|
|
SMIL Animation
This is a W3C Recommendation of a specification of animation functionality for XML documents. It describes an animation framework as well as a set of base XML animation elements suitable for integration with XML documents. It is based upon the SMIL 1.0 timing model, with some extensions, and is a true subset of SMIL 2.0. This provides an intermediate stepping stone in terms of implementation complexity, for applications that wish to have SMIL-compatible animation but do not need or want time containers.
|
|
SOAP 1.2 Attachment Feature
This document defines a SOAP feature that represents an abstract model for SOAP attachments. It provides the basis for the creation of SOAP bindings that transmit such attachments along with a SOAP envelope, and provides for reference of those attachments from the envelope. SOAP attachments are described using the notion of a compound document structure consisting of a primary SOAP message part and zero or more related documents parts known as attachments.
|
|
SOAP Version 1.2 Message Normalization
SOAP 1.2 intermediaries have some license when reserializing messages that pass through them. This document defines a transformation algorithm that renders all semantically equivalent SOAP messages identically. The transformation may be used in conjunction with an XML canonicalization algorithm prior to the generation of a message digest in producing XML digital signatures that are sufficiently robust to survive passage through one or more SOAP intermediaries.
|
|
SOAP Version 1.2 Part 1: Messaging Framework
SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. "Part 1: Messaging Framework" defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols.
|
|
SOAP Version 1.2 Part 2: Adjuncts
SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging Framework. This specification depends on SOAP Version 1.2 Part 1: Messaging Framework [SOAP Part 1].
|
|
SOAP Version 1.2 Usage Scenarios
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.
|
|
SOAP Version 1.2 Specification Assertions and Test Collection
This document draws on assertions found in the SOAP Version 1.2 specifications [SOAP Part1], [SOAP Part2], and provides a set of tests in order to show whether the assertions are implemented in a SOAP processor.
|
|
SOAP Version 1.2 Usage Scenarios
This document draws on assertions found in the SOAP Version 1.2 specifications [SOAP Part1], [SOAP Part2], and provides a set of tests in order to show whether the assertions are implemented in a SOAP processor.
|
|
Schema for Object-Oriented XML 2.0
This is part one of a 4 part series on how to use SOAP with Visual Age and WebSphere. All lot of this articles just show how to install and configure the SOAP engine with VAJ/WAS. Part 2 will be useful to anybody using SOAP regardless of which server you're using as it shows how to write the server adapter code for binding SOAP to session beans. Part 3 gets SSL working and Part 4 will get certificate based authentication working.
|
|
Speech Recognition Grammar Specification Version 1.0
This document defines syntax for representing grammars for use in speech recognition so that developers can specify the words and patterns of words to be listened for by a speech recognizer. The syntax of the grammar format is presented in two forms, an Augmented BNF Form and an XML Form. The specification makes the two representations mappable to allow automatic transformations between the two forms.
|
|
Speech Synthesis Markup Language Version 1.0
The Voice Browser Working Group has sought to develop standards to enable access to the Web using spoken interaction. The Speech Synthesis Markup Language Specification is part of this set of new markup specifications for voice browsers, and is designed to provide a rich, XML-based markup language for assisting the generation of synthetic speech in Web and other applications
|
|
Scalable Vector Graphics (SVG) 1.0 Specification
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.
|
|
Scalable Vector Graphics (SVG) 1.1 Specification
This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML.
|
|
User Agent Accessibility Guidelines 1.0
This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological).
|
|
Voice Extensible Markup Language (VoiceXML) Version 2.0
This document specifies VoiceXML, the Voice Extensible Markup Language. VoiceXML is designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed initiative conversations. Its major goal is to bring the advantages of web-based development and content delivery to interactive voice response applications.
|
|
Web Services Description Requirements
This document describes the Web Services Description Working Group's requirements for the Web Services Description specification.
|
|
Integrating Apache SOAP with an EJB Server
CGM (Computer Graphics Metafile) has been an ISO standard for vector and composite vector/raster picture definition since 1987. It has been a registered MIME type since 1995. CGM has a significant following in technical illustration, electronic documentation, geophysical data visualization, amongst other application areas
|
|
Web Services Description Language (WSDL) Version 1.2 Part 3: Bindings
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. WSDL Version 1.2 Bindings describes how to use WSDL in conjunction with SOAP 1.2 [SOAP 1.2 Part 1: Messaging Framework], HTTP/1.1 GET/POST [IETF RFC 2616], and MIME [IETF RFC 2045]. This specification depends on WSDL Version 1.2 [WSDL 1.2 Core Language].
|
|
XML Key Management Specification Bulk Operation (X-BULK)
This document extends the XML Key Management Specification [XKMS] protocol to encompass the bulk registration operations necessary for interfacing with such systems as smart card management systems.
|
|
When is SOAP a good idea in a project.
Yet another technology to work in to your project. This article tries to provide practical information on using SOAP so that you can see through the hype and decide whether SOAP is appropriate in your project or not.
|
|
XML Advanced Electronic Signatures (XAdES)
This note (XAdES) extends the IETF/W3CXML-Signature Syntax and Processing specification [XMLDSIG] into the domain of non-repudiation by defining XML formats for advanced electronic signatures that remain valid over long periods and are compliant with the European "Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures" [EU-DIR-ESIG] (also denoted as "the Directive" or the "European Directive" in the rest of the present document) and incorporate additional useful information in common uses cases.
|
|
XForms 1.0
XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts—XForms model, instance data, and user interface—it separates presentation from content, allows reuse, gives strong typing—reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting.
|
|
XFrames
XFrames, an XML application for composing documents together, replacing HTML Frames.
|
|
Modularization of XHTML™
This Recommendation specifies an abstract modularization of XHTML and an implementation of the abstraction using XML Document Type Definitions (DTDs). This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms.
|
|
An XHTML + MathML + SVG Profile
An XHTML+MathML+SVG profile is a profile that combines XHTML 1.1 [XHTML11], MathML 2.0 [MathML2] and SVG 1.1 [SVG11] together. This profile enables mixing XHTML, MathML and SVG in the same document using XML namespaces [XMLNS] mechanism, while allowing validation of such a mixed-namespace document. An XHTML 1.1 + MathML 2.0 + SVG 1.1 DTD driver is provided. An XHTML version of this document is conforming to this DTD.
|
|
XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)
This specification defines the Second Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics
|
|
XHTML™ 1.1 - Module-based XHTML
This Recommendation defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML [XHTMLMOD]. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 [HTML4] that was brought forward into the XHTML 1.0 [XHTML1] document types.
|
|
XHTML™ 2.0
XHTML 2 is a general purpose markup language designed for representing documents for a wide range of purposes across the World Wide Web. To this end it does not attempt to be all things to all people, supplying every possible markup idiom, but to supply a generally useful set of elements.
|
|
XHTML™ Basic
The XHTML Basic document type includes the minimal set of modules required to be an XHTML host language document type, and in addition it includes images, forms, basic tables, and object support. It is designed for Web clients that do not support the full set of XHTML features; for example, Web clients such as mobile phones, PDAs, pagers, and settop boxes. The document type is rich enough for content authoring
|
|
XHTML™ Document Profile Requirements
The increasing disparities between the capabilities of different kinds of Web user agents present challenges to Web content developers wishing to reach a wide audience. A promising approach is to formally describe profiles for documents intended for broad groups of user agents, for instance, separate document profiles for user agents running on desktops, television, handhelds, cellphones and voice user agents. Document profiles provide a basis for interoperability guarantees
|
|
XML Inclusions (XInclude) Version 1.0
This document specifies a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite Infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references).
|
|
When is SOAP a good idea in a project.
Yet another technology to work in to your project. This article tries to provide practical information on using SOAP so that you can see through the hype and decide whether SOAP is appropriate in your project or not.
|
|
XML Key Management Specification (XKMS)
2]This document specifies protocols for distributing and registering public keys, suitable for use in conjunction with the proposed standard for XML Signature [XML-SIG] and XML Encryption [XML-Enc]. The XML Key Management Specification (XKMS) comprises two parts — the XML Key Information Service Specification (X-KISS) and the XML Key Registration Service Specification (X-KRSS).
|
|
XML Key Management (XKMS 2.0) Requirements
This document lists the design principles, scope and requirements for XML Key Management specifications and trust server key management implementations. It includes requirements as they relate to the key management syntax, processing, security and coordination with other standards activities.
|
|
XML Key Management Specification (XKMS) Bindings
This is part one of a 4 part series on how to use SOAP with Visual Age and WebSphere. All lot of this articles just show how to install and configure the SOAP engine with VAJ/WAS. Part 2 will be useful to anybody using SOAP regardless of which server you're using as it shows how to write the server adapter code for binding SOAP to session beans. Part 3 gets SSL working and Part 4 will get certificate based authentication working.
|
|
XML Linking Language (XLink) Version 1.0
This specification defines the XML Linking Language (XLink), which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links.
|
|
XML Metadata Interchange (XMI)
For your convenience we have provided you with the complete XML Metadata Interchange (XMI) specifications as single downloadable files.
|
|
Associating Style Sheets with XML documents
This document allows a style sheet to be associated with an XML document by including one or more processing instructions with a target of xml-stylesheet in the document's prolog.
|
|
Canonical XML Version 1.0
Any XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 [XML] and Namespaces in XML [Names]
|
|
XML-Data
This document is a NOTE made available by the World Wide Web Consortium for discussion only. This indicates no endorsement of its content, nor that the Consortium has, is, or will be allocating any resources to the issues addressed by the NOTE. A list of current NOTEs can be found at: http://www.w3.org/TR/.
|
|
Exclusive XML Canonicalization Version 1.0
Canonical XML [XML-C14N] specifies a standard serialization of XML that, when applied to a subdocument, includes the subdocument's ancestor context including all of the namespace declarations and attributes in the "xml:" namespace. However, some applications require a method which, to the extent practical, excludes ancestor context from a canonicalized subdocument
|
|
XML-Signature Requirements
This document lists the design principles, scope, and requirements for the XML Digital Signature specification. It includes requirements as they relate to the signature syntax, data model, format, cryptographic processing, and external requirements and coordination.
|
|
XML-Signature Syntax and Processing
This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere.
|
|
XML-Signature XPath Filter 2.0
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.
|
|
Extensible Markup Language (XML) 1.1
This document describes XML 1.1, a deliverable of the XML Core Working Group as defined in the XML Blueberry Requirements. XML 1.1 was formerly known as XML Blueberry.
|
|
XML Accessibility Guidelines
This document provides guidelines for designing Extensible Markup Language (XML) applications that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). XML, used to design applications such as XHTML, SMIL, and SVG, provides no intrinsic guarantee of the accessibility of those applications. This document explains how to include features in XML applications that promote accessibility.
|
|
XML Base
This document proposes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents.
|
|
XML Blueberry Requirements
This document lists the design principles and requirements for the Blueberry revision of the XML Recommendation, a limited revision of XML 1.0 being developed by the World Wide Web Consortium's XML Core Working Group solely to address character set issues.
|
|
XML Encryption Syntax and Processing
This document specifies a process for encrypting data and representing the result in XML. The data may be arbitrary data (including an XML document), an XML element, or XML element content. The result of encrypting data is an XML Encryption element which contains or references the cipher data.
|
|
XML Events
The XML Events module defined in this specification provides XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces [DOM2EVENTS]. The result is to provide an interoperable way of associating behaviors with document-level markup.
|
|
XML Fragment Interchange
The XML standard supports logical documents composed of possibly several entities. It may be desirable to view or edit one or more of the entities or parts of entities while having no interest, need, or ability to view or edit the entire document.
|
|
XML Information Set
Yet another technology to work in to your project. This article tries to provide practical information on using SOAP so that you can see through the hype and decide whether SOAP is appropriate in your project or not.
|
|
Requirements for XML Schema 1.1
This document contains a list of requirements and desiderata for version 1.1 of XML Schema.
|
|
XML Schema Part 0: Primer
XML Schema Part 0: Primer is a non-normative document intended to provide an easily readable description of the XML Schema facilities, and is oriented towards quickly understanding how to create schemas using the XML Schema language. XML Schema Part 1: Structures and XML Schema Part 2: Datatypes provide the complete normative description of the XML Schema language. This primer describes the language features through numerous examples which are complemented by extensive references to the normative texts.
|
|
XML Schema Part 1: Structures
XML Schema: Structures 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). This specification depends on XML Schema Part 2: Datatypes.
|
|
XML Schema Part 2: Datatypes
XML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML 1.0, provides a superset of the capabilities found in XML 1.0 document type definitions (DTDs) for specifying datatypes on elements and attributes.
|
|
XML Schema: Component Designators
XML Schema: Component Designators defines a scheme for identifying the XML Schema components specified by XML Schema Part 1: Structures and XML Schema Part 2: Datatypes.
|
|
XML Schema: Formal Description
XML Schema: Formal Description is a formal description of XML types and validity as specified by XML Schema Part 1: Structures.
|
|
XML Protocol Abstract Model
The challenge of crafting a protocol specification is to create a description of behaviour that is not tied to any particular approach to implementation. There is a need to abstract away from some of the messy implementation details of buffer management, data representation and specific APIs. However, in order to describe the behaviour of a protocol one has to establish a set of (useful) concepts that can be used in that description. An abstract model is one way to establish a consistent set of concepts. An abstract model is a tool for the description of complex behaviour — it is not a template for an implementation... although it should not stray so far away from reality that it is impossible to recognise how the required behaviours would be implemented.
|
|
XML Protocol (XMLP) Requirements
This document describes the XML Protocol Working Group's requirements for the XML Protocol (XMLP) specification.
|
|
XML Path Language (XPath) Version 1.0
XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.
|
|
XML Path Language (XPath) 2.0
The primary purpose of XPath is to address parts of an [XML] document. XPath uses a compact, non-XML syntax to facilitate use of XPath within URIs and XML attribute values. XPath gets its name from its use of a path notation as in URLs for navigating through the hierarchical structure of an XML document.
|
|
XPointer element() Scheme
The XPointer element() scheme is intended to be used with the XPointer Framework [XPtrFrame] to allow basic addressing of XML elements.
|
|
XPointer Framework
This specification defines the XML Pointer Language (XPointer) Framework, an extensible system for XML addressing that underlies additional XPointer scheme specifications. The framework is intended to be used as a basis for fragment identifiers for any resource whose Internet media type is one of text/xml, application/xml, text/xml-external-parsed-entity, or application/xml-external-parsed-entity. Other XML-based media types are also encouraged to use this framework in defining their own fragment identifier languages.
|
|
XPointer xmlns() Scheme
The XPointer xmlns() scheme is intended to be used with the XPointer Framework [XPtrFrame] to allow correct interpretation of namespace prefixes in pointers, for instance, namespace-qualified scheme names and namespace-qualified element or attribute names appearing within scheme data.
|
|
XPointer xpointer() Scheme
The XPointer xpointer() scheme is intended to be used with the XPointer Framework [XPtrFrame] to provide a high level of functionality for addressing portions of XML documents. It is based on XPath [XPath], and adds the ability to address strings, points, and ranges in accordance with definitions provided in DOM 2: Range.[DOM2]
|
|
XQuery 1.0: An XML Query Language
XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources.
|
|
XQuery 1.0 and XPath 2.0 Data Model
This document defines the W3C XQuery 1.0 and XPath 2.0 Data Model, which is the data model of at least [XPath 2.0], [XSLT 2.0], and [XQuery 1.0: A Query Language for XML], and any other specifications that reference it. This data model is based on the [XPath 1.0] data model and earlier work on an [XML Query Data Model]. This document is the result of joint work by the [XSL Working Group] and the [XML Query Working Group].
|
|
XQuery 1.0 and XPath 2.0 Formal Semantics
This document defines formally the semantics of XQuery 1.0 [XQuery 1.0: A Query Language for XML] and XPath 2.0 [XML Path Language (XPath) 2.0].
|
|
XQuery 1.0 and XPath 2.0 Functions and Operators
This document defines basic operators and functions on the datatypes defined in [XML Schema Part 2: Datatypes] for use in XQuery, XPath, XSLT and other related XML standards. It also discusses operators and functions on nodes and node sequences as defined in the [XQuery 1.0 and XPath 2.0 Data Model] for use in XQuery, XPath, XSLT and other related XML standards.
|
|
XQuery and XPath Full-Text Requirements
The document specifies requirements for Full-Text search for use in XQuery [XQuery] and XPath [XPath].
|
|
When is SOAP a good idea in a project.
Yet another technology to work in to your project. This article tries to provide practical information on using SOAP so that you can see through the hype and decide whether SOAP is appropriate in your project or not.
|
|
XQuery and XPath Full-Text Use Cases
This document specifies usage scenarios for full-text queries as part of XML Query [XQuery] and XPath [XPath].
|
|
XML Query (XQuery) Requirements
This document specifies goals, requirements, and usage scenarios for the W3C XML Query (XQuery) data model, algebra, and query language. It also includes, for each requirement, a corresponding status, indicating the current situation of the requirement in the XML Query family of specifications.
|
|
XML Query Use Cases
This document specifies usage scenarios for XQuery.
|
|
XML Syntax for XQuery 1.0 (XQueryX)
This paper presents an XML Syntax for [XQuery Working Draft].
|
|
Extensible Stylesheet Language (XSL)
Version 1.0
This specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets.
|
|
XSL Transformations (XSLT) Version 1.0
This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents.
|
|
XSL Transformations (XSLT) Version 2.0
This specification defines the syntax and semantics of XSLT 2.0, which is a language for transforming XML documents into other XML documents.
|
|
XSLT 2.0 and XQuery 1.0 Serialization
This document defines serialization for the [XSLT 2.0] and [XQuery 1.0] specifications and any other specifications that reference it.
|