 |
A MathML for CSS profile
This profile, a subset of MathML 3.0, facilitates the use of MathML in Web browsers.
|
| |
AVDL v1.0 (Application Vulnerability Description Language)
AVDL describes a standard XML format that allows entities (such as applications or organizations) to communicate information regarding Web application security vulnerabilities.
|
| |
Advanced XML Schema Patterns for Databinding Version 1.0
This specification provides an advanced set of example XML Schema 1.0 constructs in the form of XPath 2.0 expressions. These patterns are in widespread use and are considered to be compatible with databinding implementations.
|
| |
Associating Stylesheets with XML Documents 1.0
This specification defines how stylesheets are associated with XML documents.
|
| |
Atom
Extending RSS into a new specification, Atom makes it possible for developers to have a consistent, tightly-specified, well-documented XML format for both syndication and authoring of content.
|
| |
Atom Syndication Format
The Atom Syndication Format helps developers to
format Web feeds, which communicate news and updates of episodic
information on Web sites. Learn more about this standard designed as a
refinement of RSS formats.
|
| |
Authoring Techniques for XHTML and HTML Internationalization: Characters and Encodings 1.0
This reference provides HTML authors with techniques for developing internationalized HTML using XHTML 1.0 or HTML 4.01, supported by CSS1, CSS2 and some aspects of CSS3.
|
| |
BTP 1.0 (Business Transaction Protocol)
BTP defines a standard protocol for autonomous organizations (both consumers and business providers) to make, manage, and terminate commitments.
|
| |
Basic XML Schema Patterns for Databinding Version 1.0
This specification provides example XML Schema structures and types to exchange commonly used data structures independent of programming language, database, or modeling environment.
|
| |
Behavioral Extensions to CSS
This specification provides a way to link to binding technologies, such as XBL, using CSS, taking advantage of the benefits of stylesheets, cascading selections, and transparency to the user.
|
| |
Best Practices for XML Internationalization
This document describes best practices for developing XML documents and schemas that are internationalized properly and is a companion to Internationalization Tag Set.
|
| |
Building a Tokenizer for XPath or XQuery
This document describes possible strategies for tokenizing the XPath 2.0 and XQuery 1.0 languages.
|
| |
Business Information Conformance Statements (BICS) 2
The Business Information Conformance Statement specifications define information constraints for service information exchanged by business-to-business (B2B) communications in a Service-Oriented Architecture (SOA) environment.
|
| |
Business Information Conformance Statements (BICS) 2
The Business Information Conformance Statement (BICS) specifications define information constraints for service information exchanged by business-to-business (B2B) communications in a Service-Oriented Architecture (SOA) environment. The BICS 2 specifications describe the core XML framework (BICS 2 core framework) and three constraint mechanisms: W3C XML Schema Constraint Mechanism (WXSCM), Schematron Schema Constraint Mechanism (SSCM), and MIME Constraint Mechanism (MCM).
|
| |
Business Integration - Information Conformance Statements (BI-ICS)
BI-ICS provides the ability to declare that business information is conformant with type systems such as XML Schema and MIME and processes such XPath. BI-ICS is also extensible for alternate type systems, process mechanisms, and conformance models.
|
| |
CAP (Common Alerting Protocol) v1.1
The Common Alerting Protocol is a general format for exchanging emergency alerts, hazard notifications, and other public warnings over any network. CAP also identifies best practices based on research and real-world experience.
|
| |
CAP v1.0 (Common Alerting Protocol)
The Common Alerting Protocol (CAP) allows a consistent emergency warning or public alert message to be disseminated, through XML or other coding schemes, simultaneously over many different warning systems.
|
| |
CCXML 1.0 (Voice Browser Call Control)
CCXML is designed to provide telephony call control support for dialog systems. CCXML has been designed to complement and integrate with the distinct features of the VoiceXML language and its systems.
|
| |
CPPA v2 (Collaborative Partner Profile Agreement)
This specification contains the detailed definitions of the Collaboration-Protocol Profile (CPP) and the Collaboration-Protocol Agreement (CPA) for the eBusiness community. A CPP defines one business partner's technical capabilities to engage in electronic business collaborations with other partners. A CPA documents the technical agreement between collaborating business partners.
|
| |
CSS Advanced Layout Module
This module contains features to describe layouts and tasks such as the positioning and alignment of controls and sections in a graphical user interface or the layout grid for a page or a window, regardless of the order of the elements in the source document.
|
| |
CSS Grid Positioning Module Level 3
This module describes using CSS for grid-based layouts, similar to the grids traditionally used in book and newspaper formatting.
|
| |
CSS Mobile Profile 2.0
A subset of CSS 2.1, this profile is considered a baseline for interoperability between implementations of CSS on constrained devices such as mobile phones.
|
| |
CSS Module: Namespaces
This specification defines the syntax for using namespaces in CSS, introducing the @namespace rule for declaring a default namespace and for binding namespaces to namespace prefixes.
|
| |
CSS Print Profile
This CSS3 module is designed for printing from mobile devices to low-cost devices, where it is not feasible or desirable to install printer-specific drivers, and for situations where some variability in the formatting of the output is acceptable.
|
| |
CSS TV Profile 1.0
This CSS profile identifies a minimum set of properties, values, and rules for TV devices such as set top boxes or integrated interactive television sets that display their output on a television screen.
|
| |
CSS Text Level 3
This CSS3 module defines properties for text manipulation, such as line breaks, justification and alignment, white space handling, text decoration and text transformation.
|
| |
CSS basic box model
This CSS3 module describes the formatting model of CSS for visual media, which is based on a "flow" of rectangular boxes that are either juxtaposed or nested, according to certain rules.
|
| |
CSS3 Backgrounds and Borders Module
This CSS3 module describe borders and backgrounds, including borders consisting of images and backgrounds with multiple images.
|
| |
CSS3 Basic User Interface Module
This CSS3 module describes selectors and CSS properties which enable authors to style user interface states, element fragments, properties, and values.
|
| |
CSS3 Color Module
This CSS3 module describes properties that specify the foreground color, opacity of an element, and allow specification of the ICC color profile and rendering intent of image content.
|
| |
CSS3 Generated and Replaced Content Module
This CSS3 module describes how to insert and move content around a document in order to create footnotes, endnotes, and section notes, as well as how to scale, crop, and replace images.
|
| |
CSS3 Hyperlink Presentation Module
This CSS3 module contains the functionality required to describe the presentation of hyperlink source anchors and the effects of hyperlink activation.
|
| |
CSS3 Ruby Module
This CSS3 module describes a set of properties associated with 'Ruby' elements, which are short runs of text typically used in East Asian documents to indicate pronunciation or to annotate a particular base text.
|
| |
CSS3 Speech Module
This CSS3 module defines aural properties that give control over rendering XML to speech, preserving the structure of the document for text-to-speech applications. This module is also designed to match the model described in the Speech Synthesis Markup Language (SSML).
|
| |
CSS3 Values and Units
This CSS3 module defines common values and units that CSS properties accept and to which other modules can refer.
|
| |
CSS3 module: Cascading and inheritance
This CSS3 module describes how to select one among several conflicting declarations. When no declaration attempts to set the value of an element/property combination, the value will either be inherited from the parent element or set to the property's initial value.
|
| |
CSS3 module: Fonts
This CSS3 module allows font specification by a user agent as well as additional font decoration such as font effects, emphasis, and smoothing.
|
| |
CSS3 module: Generated Content for Paged Media
This module -- along with Paged Media and Multicolumn Layout -- describes how style sheets can express print publication details such as footnotes, headers and footers, and lists.
|
| |
CSS3 module: Lists
This CSS3 module describes how lists are styled.
|
| |
CSS3 module: Multi-column layout
This CSS3 module builds on the CSS3 Box model module and adds functionality to flow the content of an element into multiple columns.
|
| |
CSS3 module: Paged Media
This module defines a page model that specifies how a document flow is formatted within a finite page display. It adds functionality for pagination, page margins, page size and orientation, headers and footers, widows and orphans, and image orientation.
|
| |
CSS3 module: Presentation Levels
This CSS3 module describes presentation levels, integer values attached to elements in a document, for such purposes as styling presentation effects and outline views of documents.
|
| |
CSS3 module: Syntax
This CSS3 module describes the basic structure of CSS style sheets, details of the syntax, the rules for parsing CSS style sheets, and how to attach stylesheets to documents.
|
| |
CSS3 module: Web Fonts
This CSS3 module allows font specification by a user agent.
|
| |
CSS3 module: line
This CSS3 module defines line formatting properties, baseline alignment features, and related functions such as initial line and initial letter effect.
|
| |
CURIE Syntax 1.0
CURIE is a syntax for expressing URIs in a generic, abbreviated syntax whose purpose is to avoid the problems inherent in the definition of QNames, which insists on the valid use of XML element names.
|
| |
Canonical XML (c14n)
Canonical XML lets you create a physical representation of
an XML document that allows for the variations in XML syntax without
changing the meaning. Discover more about this standard method, which is
useful for testing and digital signatures, among other things.
|
| |
Cascading Style Sheets (CSS)
Cascading Style Sheets (CSS) is a system for applying
presentation style to markup. CSS is best known for its use in styling
HTML Web pages, but it is also well suited to presenting XML documents
on the Web and on other media. Effective use of CSS is the key to
separating the content from its presentation.
|
| |
Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification
CSS 2.1 corrects errors in CSS2: a new definition of the height/width of absolutely positioned elements; more influence for HTML's "style" attribute; a new calculation of the 'clip' property; and a few highly widely implemented features. In general, CSS 2.1 represents a "snapshot" of CSS implementation, use, and direction at the date of publication.
|
| |
Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0
Based on RDF, CC/PP profiles contain attribute names and associated values used by a server to adapt content to the user's presentation device.
|
| |
Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 2.0
2.0 updates CC/PP to the latest version of RDF. CC/PP profiles describe device capabilities and user preferences in the presentation of content.
|
| |
Compound Document Use Cases and Requirements Version 2.0
This document describes the use cases for the combining of separate component languages, with an emphasis on user interface mark up languages. Issues addressed include the propagation of events across markups, the combination of rendering or the user interaction model with a combined document.
|
| |
Compound Document by Reference Framework 1.0
This document defines a generic framework that defines a language-independent processing model for combining arbitrary document formats.
|
| |
Content Assembly Mechanism Specification Version 1.1
This specification uses business rules to define, validate and compose business documents from generalized schema elements and structures. CAM also provides the foundation for creating industry libraries and dictionaries of schema elements and business document structures.
|
| |
Content Selection Primer 1.0
This primer describes how DISelect can be used by authors to choose between different versions of content for different circumstances. It also describes DISelect in relation to other methods of content selection and further illustrates its use in a variety of scenarios.
|
| |
Content Selection for Device Independence (DISelect) 1.0
This document specifies a syntax and processing model for general purpose content selection or filtering, using XML-friendly syntax and XPath expressions, and requiring from the receiving device only modest processor capabilities.
|
| |
DIAL Part 0: Primer
The Device Independent Authoring Language (DIAL) is an XML language profile of XHTML version 2, XForms, and Content Selection for Device Independence (DISelect). The goal of DIAL is to deliver a harmonized user experience across multiple delivery contexts.
|
| |
DOM (Document Object Model) Level 1
The DOM Level 1 specification describes an interface that enables programs to access and update the structure, style, and contents of documents.
|
| |
DOM (Document Object Model) Level 2 Core
DOM Level 2 builds on DOM Level 1. It contains interfaces for creating a document, object models for ranges, cascading style sheets, and events, filters and iterators, support for XML namespaces, and methods for associating stylesheets with documents.
|
| |
DOM (Document Object Model) Level 2 Events
Events defines a platform- and language-neutral interface for programs and scripts.
|
| |
DOM (Document Object Model) Level 2 HTML
This specification defines 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.
|
| |
DOM (Document Object Model) Level 2 Style
Style allows programs and scripts to dynamically access and update style sheets.
|
| |
DOM (Document Object Model) Level 2 Traversal and Range
Traversal and Range allows programs and scripts to dynamically traverse and identify a range of content in a document.
|
| |
DOM (Document Object Model) Level 2 Views
Views allows programs and scripts to dynamically access and update the content of a document representation
|
| |
DOM (Document Object Model) Level 3 Core
DOM Level 3 allows programs and scripts to dynamically access and update the content, structure, and style of documents.
|
| |
DOM (Document Object Model) Level 3 Events
This event system allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event.
|
| |
DOM (Document Object Model) Level 3 Load and Save
This specification defines a platform-neutral and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure, and style of documents.
|
| |
DOM (Document Object Model) Level 3 Validation
This specification defines the level 3 interface which allows programs and scripts to dynamically access and update the content, structure and style of documents by providing APIs to query information about the XML document and its associated grammar.
|
| |
DOM (Document Object Model) Level 3 Views and Formatting
This specification allows a DOM application access to a view's computed layout and presentation and functions independently from any specific styling system that may have been applied.
|
| |
DOM (Document Object Model) Level 3 XPath
DOM Level 3 XPath provides simple functionalities to access a DOM tree using XPath 1.0.
|
| |
DSML 2.0 (Directory Services Markup Language)
DSML provides a means for representing directory structural information and a method for expressing directory queries, updates, and their results as XML documents.
|
| |
Darwin Information Typing Architecture (DITA)
Darwin Information Typing Architecture (DITA) is a
system of Document Type Definitions (DTDs) and conventions for authoring
and delivering technical information. Learn more about this standard
that IBM produced to help organize its vast amount of data.
|
| |
Decryption Transform for XML Signature
This document enables XML Signature applications to distinguish between 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.
|
| |
Delivery Context: Client Interfaces (DCCI) 1.0
This document defines platform and language neutral interfaces that provide Web applications access to dynamic properties representing device capabilities, configurations, user preferences, and environmental conditions, such as power status, device location, or network bandwidth.
|
| |
Delivery Context: XPath Access Functions 1.0
This document specifies a set of XPath functions that can be used to manipulate the Delivery Context associated with a request for an item of content.
|
| |
Device Independent Authoring Language (DIAL)
W3C: Working Draft: Device Independent Authoring Language (DIAL) provides a markup language for the authoring, generation, filtering, and presentation of Web page content across different delivery contexts with a primary focus on functional user experiences.
|
| |
Digital Signature Services v1.0
This document defines XML request/response protocols for signing and verifying XML documents and other data. DSS consists of its core protocols (including elements and bindings), along with nine profiles: DSS German Signature Law Profile; DSS Advanced Electronic Signature Profiles; DSS Asynchronous Processing Abstract Profile; DSS J2ME Code-Signing Profile; DSS Abstract Code-Signing Profile; DSS Electronic PostMark (EPM) Profile; DSS Entity Seal Profile; DSS Signature Gateway Profile; and DSS XML Timestamping Profile.
|
| |
DocBook
DocBook, an XML (and SGML) application for authoring
technical books and documentation, has been around more than most XML
formats. Read about the history of this format, and discover another,
simpler version.
|
| |
Document Object Model (DOM)
Learn to use the Document Object Model (DOM), a tree
API that provides direct access to parts of an XML document. DOM is
probably the most popular means of accessing XML documents, offering
convenience at the expense of performance.
|
| |
Document Schema Definition Languages (DSDL)
Document Schema Definition Languages (DSDL) is a framework
approach to XML validation and core processing comprising individual
specifications from expert individuals or small groups, each of which
addresses a well-defined and well-bounded problem domain. Discover the
parts of DSDL, including RELAX NG and Schematron, that already have
traction on their own, and the ones that are still works in progress.
|
| |
EMMA (Extensible MultiModal Annotation markup language)
EMMA is an XML markup language for describing the interpretation of user input, such as a raw signal's transcription into words from a speech or pen input, a set of attribute/value pairs describing their meaning, or a set of attribute/value pairs describing a gesture. Components that may generate EMMA markup include: speech recognizers, handwriting recognizers, natural language understanding engines, and other input media interpreters.
|
| |
Efficient XML Interchange (EXI) Format 1.0
EXI is a very compact representation for XML Infoset that is intended to simultaneously optimize performance and the utilization of computational resources, producing efficient encodings of XML event streams.
|
| |
Election Markup Language (EML) v4.0
EML v4.0 enables data exchanges for public and private election services and contains 2 documents: EML Process and Data Requirements, which describes the electoral processes from which EML derives its structure and its security and audit mechanisms, and EML Schema Descriptions, which contains the core schemas and definitions of the simple an complex datatypes.
|
| |
Election Markup Language (EML) v5.0
Election Markup Language provides a structured interchange to support election and voting services. The EML specification details the core EML schemas as well as its simple and complex datatypes.
|
| |
ElementTraversal Specification
This specification provides a convenient alternative to existing DOM navigation elements. It allows script navigation of the elements of a DOM tree, excluding all other nodes in the DOM, such as text nodes. It also provides a way to expose the number of child elements of an element.
|
| |
Emergency Data Exchange Language Distribution Element (EDXL-DE) v1.0
This specification describes a standard message distribution framework for data sharing among emergency information systems.
|
| |
Evaluation and Report Language (EARL) 1.0 Schema
This language expresses test results such as bug reports, test suite evaluations, and conformance claims. The test subject might be a Web site, an authoring tool, a user agent, or some other entity. Broadly, any person, entity, or organization may state test results for any thing tested against any set of criteria.
|
| |
Extensible Forms Description Language (XFDL) 7.6 Specification
This document describes an XML syntax for the Extensible Forms Description Language (XFDL). The purpose of XFDL is to solve the body of problems associated with digitally representing complex forms such as those found in business and government. The requirements include support for high precision layout, supporting documentation, integrated computations and input validation, multiple overlapping digital signatures, and legally binding auditable transaction records, by maintaining the whole form as a single unit such that digital signatures can capture the entire context of transactions.
|
| |
Extensible Markup Language (XML)
Extensible Markup Language (XML), which is based on
Standard Generalized Markup Language (SGML), features strict syntax
rules and a language -- Document Type Definition (DTD) -- for defining
structural constraints. Learn about XML 1.0 and its Unicode foundation,
as well as all the new features that XML 1.1 offers, and the controversy
surrounding this latest version.
|
| |
Extensible Stylesheet Language (XSL) Version 1.1
XSL defines a language and vocabulary for expressing stylesheets. The language is defined as XSLT which transforms XML documents. The vocabulary describes the formatting semantics for the many objects within a document. New functionality supports change marks, indexes, multiple flows, and bookmarks. In addition, XSL 1.1 extends 1.0 in graphics scaling, markers and their retrieval in tables to support, for example, partial sums and page number referencing.
|
| |
Extensible Stylesheet Language Formatting Objects (XSL-FO)
With Extensible Stylesheet Language Formatting
Objects (XSL-FO), an XML application for presentation, any user agent
can render content to the exact specifications given by the developer.
Discover the relationships between XSL-FO, XHTML, Cascading Style Sheets
(CSS), and Extensible Stylesheet Language Transformations (XSLT).
|
| |
Extensible Stylesheet Language Transformations
(XSLT)
Extensible Stylesheet Language Transformations (XSLT)
allows you to describe transforms from an input XML document to an
output tree, such as XML, HTML, or text. You can use it for
sophisticated presentation of XML documents or for transforms from one
XML format to another. Delve further into this successful language and
discover what it, as well what EXSLT, can do for you.
|
| |
GRDDL Primer
GRDDL -- Gleaning Resource Descriptions from Dialects of Languages -- is a mechanism for extracting RDF data from XML documents by way of transformation algorithms, typically represented in XSLT.
|
| |
GRDDL Test Cases
This document describes test cases for software agents that extract RDF from XML source documents, demonstrating the expected behavior of a GRDDL-aware agent.
|
| |
GRDDL Use Cases: Scenarios of extracting RDF data from XML documents
GRDDL -- Gleaning Resource Descriptions from Dialects of Languages -- is a mechanism for extracting RDF data from XML documents by way of transformation algorithms, typically represented in XSLT. This document collects a number of motivating use cases, their goals and requirements
|
| |
Gleaning Resource Descriptions from Dialects of Languages (GRDDL)
Gleaning Resource Descriptions from Dialects of Languages (GRDDL) introduces markup for declaring that an XML document includes gleanable data and for linking to an algorithm, typically represented in XSLT, for gleaning the resource descriptions from the document.
|
| |
Guide to Versioning XML Languages using XML Schema 1.1
This guide provides a description of the versioning features in the XML Schema definition language and focuses on describing the different ways extra content can be added to create new versions of a schema.
|
| |
HLink: Link recognition for the XHTML Family
For the XHTML the Family, HLink specifies which element attributes represent hyperlinks, how those hyperlinks should be traversed, and extends XLink use to a wider class of languages.
|
| |
HTTP Vocabulary in RDF
The terms defined by this document allow HTTP(S) headers that have been exchanged between a client and a server to be recorded in RDF format.
|
| |
InkML (Ink Markup Language)
Representing ink entered with an electronic pen or stylus, the InkML data format allows for the input and processing of handwriting, gestures, sketches, music and other notational languages in Web-based applications.
|
| |
Internationalization Best Practices: Handling Right-to-left Scripts in XHTML and HTML Content
This document provides page creation advice on the use of XHTML or HTML markup and CSS for languages that use or behave like right-to-left scripts, such as Arabic and Hebrew.
|
| |
Internationalization Best Practices: Specifying Language in XHTML and HTML Content
Specifying the language of content is useful for a wide number of applications, from linguistically sensitive searching to applying language-specific display properties. This document is one of a series of documents providing HTML authors with techniques for developing internationalized HTML using XHTML 1.0 or HTML 4.01, supported by CSS1, CSS2, and some aspects of CSS3.
|
| |
Internationalization Tag Set (ITS) Version 1.0
This specification supports the internationalization, localization, and translatability of schemas and documents. Implementations are provided for XML DTD, XML Schema, and RELAX NG.
|
| |
Internationalization and Localization Markup Requirements
These requirements form a list of guidelines and a set of recommended approaches to developing schemas which address issues related to international use of document formats and localization of XML content.
|
| |
Introduction to CSS3
CSS3 has been split into modules to reduce the size of the specification and help implementers to decide which modules to support. The introduction gives an overview of each module.
|
| |
JAXP (Java API for XML Parsing) 1.3
The JAXP specification allows developers to easily use XML Parsers in their applications through SAX and DOM APIs.
|
| |
Java API for XML-Based Web Services (JAX-WS) 2.0
JAX-WS replaces JAX-RPC. Like JAX-RPC, it defines APIs and conventions for supporting XML-based protocols in Java(TM) programming, with support for JAXB, and the SOAP and WSDL standards. JAX-WS further supports asynchronous operations and improves the separation between XML message formats and transport mechanisms.
|
| |
Language Bindings for DOM Specifications
This specification defines an Interface Definition Language (IDL) to be used by specifications that define a Document Object Model (DOM). Precise language bindings for ECMAScript 3rd Edition and Java are also included.
|
| |
MTOM Serialization Policy Assertion 1.1
This specification describes a domain-specific policy assertion for the SOAP Message Transmission Optimization Mechanism (MTOM) which can be specified within a policy alternative as defined in Web Services Policy 1.5 - Framework.
|
| |
Mathematical Markup Language (MathML)
Learn about Mathematical Markup Language (MathML), an
XML application for expressing mathematical and scientific content. Use
MathML for mixing mathematical content into other vocabularies such as
XHTML and Scalable Vector Graphics (SVG).
|
| |
Metadata Extension for SAML V2.0 and V1.x Query Requesters
The extension defines role descriptor types that describe a standalone Security Assertion Markup Language (SAML) V1.x or V2.0 query requester for each of the three predefined query types in the SAML V2.0 specification.
|
| |
Metadata Profile for the OASIS Security Assertion Markup Language (SAML) V1.x
This specification defines a profile of the SAML V2.0 metadata specification for use in describing SAML V1.0 and V1.1 entities and profiles.
|
| |
Natural Language Semantics Markup Language for the Speech Interface Framework
This document is part of a set of specifications for accessing the Web using spoken interaction, and details an XML markup language for describing the meanings of individual natural language utterances.
|
| |
OWL (Web Ontology Language) Overview
This document outlines a first-hand impression of the capabilities of OWL. The OWL Web Ontology Language allows greater machine readability of Web content than that supported by XML, RDF, and RDF Schema by providing an additional vocabulary along with a formal semantics.
|
| |
Open Document Format (ODF) for Office Applications (OpenDocument)
Learn about Open Document Format (ODF) for Office
Applications (OpenDocument), an XML application that allows you to
represent the information and formatting for office suite applications.
It covers word processors, spreadsheets, basic drawings, presentation
formats, and more.
|
| |
Platform for Privacy Preferences 1.0 (P3P1.0)
P3P version 1.0 is a protocol designed to inform Web users of the data-collection practices of Web sites, and provides a way for a Web site to encode its data-collection and data-use practices in a machine-readable XML format known as a P3P policy.
|
| |
Platform for Privacy Preferences 1.1 (P3P1.1)
P3P 1.1 adds features using the P3P 1.0 Extension mechanism and contains a new binding mechanism that can be used to bind policies for XML applications beyond HTTP transactions.
|
| |
Progress Events 1.0
This document describes event types for monitoring the progress of an operation, primarily for contexts such as data transfer operations specified by XMLHTTPRequest. Types include: loadstart, progress, error, abort, and load (completed).
|
| |
Pronunciation Lexicon Specification (PLS) Version 1.0
This document defines the syntax for specifying accurate, application-specific pronunciation lexicons to be used by Automatic Speech Recognition and Text-to-Speech engines in voice browser applications.
|
| |
Protocol for Web Description Resources (POWDER): Description Resources
POWDER provides a means of describing a group of resources through the publication of machine-readable metadata. Examples include identifying content for appropriate audience consumption or for greater personalization. This document details the creation and lifecycle of Description Resources (DRs), which encapsulate such metadata.
|
| |
Protocol for Web Description Resources (POWDER): Grouping of Resources
This specification facilitates the publication of descriptions of sets of multiple resources such as all those available from a Web site. POWDER provides a means of describing a group of resources through the publication of machine-readable metadata. Examples include identifying content for appropriate audience consumption or for greater personalization.
|
| |
Protocol for Web Description Resources (POWDER): Web Description Resources (WDR) Vocabulary
This is the namespace document for the POWDER vocabulary. POWDER provides a means of describing a group of resources through the publication of machine-readable metadata. Examples include identifying content for appropriate audience consumption or for greater personalization.
|
| |
Protocol for Web Description Resources (POWDER): Web Description Resources Datatypes (WDRD)
This document describes POWDER's XML Schema, its datatypes and structure. POWDER provides a means of describing a group of resources through the publication of machine-readable metadata. Examples include identifying content for appropriate audience consumption or for greater personalization.
|
| |
RDDL (Resource Directory Description Language)
RDDL is an extension of XHTML Basic 1.0, adding an resource element that contains a description of the resource along with machine-readable links that describe the purpose of the link and the nature of the linked resource.
|
| |
RDFa Primer 1.0
This syntax expresses metadata about a Web document using a set of elements and attributes that embed RDF in XHTML.
|
| |
RDFa in XHTML: Syntax and Processing
This specification defines a syntax -- rather than a specific vocabulary -- for attributes to be expressed in structured data. Rendered, XHTML hypertext data is reused by RDFa markup to avoid repeating significant data in a document's content.
|
| |
RELAX NG
RELAX NG is a grammar-based XML schema language used to
describe, define, and limit XML vocabularies. Find out why some people
dislike Document Type Definition (DTD), and discover how RELAX NG aims
to improve upon it.
|
| |
Reference Model for Service Oriented Architecture v1.0 (SOA-RM v1.0)
This Reference Model for Service Oriented Architecture is an abstract framework for understanding entities and the relationships between them within a service-oriented environment. The reference model is intended to guide the development of consistent standards or specifications supporting the SOA environment.
|
| |
Remote Events for XML (REX)
Remote Events for XML (REX) is used to represent
events relating to the access and mutation of XML documents. Check out
this specification to find out more details about this emerging standard.
|
| |
Resource Description Framework (RDF)
Resource Description Framework (RDF) is a model for
describing collections of formalized statements about a Web resource.
You can also think of RDF as a metadata system for the Web. Learn about
this standard and about its relationship with the Semantic Web, Web
Ontology Language (OWL), and more.
|
| |
Resource Description Framework (RDF) Data Access Use Cases and Requirements
This document specifies use cases, requirements, and objectives for an RDF query language and data access protocol.
|
| |
Resource Description Framework (RDF) Semantics
This specifies a precise semantics for RDF and RDFS, and corresponding entailment and inference rules.
|
| |
Resource Description Framework (RDF) Test Cases
This document contains a set of machine-processable test cases corresponding to ambiguities in the RDFMS and RDF-Schema.
|
| |
Resource Representation SOAP Header Block
The SOAP header block allows applications to carry a representation of a Web resource in a SOAP message to a processing SOAP node.
|
| |
Ruby Annotation
"Ruby" consists of 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 as an XHTML module.
|
| |
SKOS Core Guide
This guide provides recommended usage guidelines to the SKOS Core Vocabulary specification.
|
| |
SKOS Core Vocabulary Specification
The SKOS (Simple Knowledge Organization System) Core Vocabulary is a set of RDF properties and RDFS classes for expressing the content and structure of a concept scheme (such as taxonomies, glossaries, controlled vocabulary) as an RDF graph.
|
| |
SOAP
The SOAP protocol allows you to use XML to
communicate between systems that are connected using lower-level
Internet protocols. It provides a standard envelope for XML information
to be transmitted through network messages, and optional conventions for
the body of such messages. Understand the history of SOAP, as well as
its relation to Web services, Service-Oriented Architecture (SOA), and
Representational State Transfer (REST).
|
| |
SOAP 1.2 Part 0: Primer
Simple Object Access Protocol (SOAP) 1.2 describes a protocol for exchanging structured information in a decentralized, distributed environment.
|
| |
SOAP 1.2 Part 1: Messaging Framework
This defined extensible messaging framework contains a message construct that can be exchanged over a variety of underlying protocols.
|
| |
SOAP 1.2 Part 2: Adjuncts
Contains a set of adjuncts that may be used with SOAP's Messaging Framework.
|
| |
SOAP 1.2 Part 3: One-Way MEP
Complimentary to SOAP 1.2 Part 2, which defines a request-response Message Exchange Pattern (MEP), Part 3 of SOAP 1.2 defines an abstract presentation of a one-way MEP.
|
| |
SOAP 1.2 Specification Assertions and Test Collection
This specification provides a set of tests in order to show whether assertions are implemented in a SOAP processor. A SOAP 1.2 implementation that passes all of the tests specified in this document may only claim to conform to the SOAP 1.2 Test Suite
|
| |
SOAP Message Transmission Optimization Mechanism
This document describes the transmission and wire format of SOAP messages by selectively re-encoding portions of the message, while still presenting an XML Infoset to the SOAP application.
|
| |
SOAP Optimized Serialization Use Cases and Requirements
This draft outlines the use cases and specifies the requirements for optimizing the processing and serialization of SOAP messages.
|
| |
SPARQL Protocol for RDF
This document describes SPARQL, a protocol for conveying RDF queries from query clients to query processors.
|
| |
SPARQL Query Language for RDF
RDF is a flexible, extensible way to represent information about World Wide Web resources, such as personal information or digital music and images. A standardized query language for RDF data with multiple implementations offers developers and end users a way to write and to consume the results of queries across this wide range of information.
|
| |
SPARQL Query Results XML Format
This document defines an XML serialization for encoding variable binding results made by the SPARQL Query Language for RDF.
|
| |
SPML 1.0 (Service Provisioning Markup Language)
SPML V1.0 provides both a synchronous and asynchronous batch request model whereby a Requesting Authority (RA) issues an SPML request describing a provisioning operation to be performed at a Provisioning Service Point (PSP) for the purpose of digital or non-digital resource management.
|
| |
SPML 2.0 (Service Provisioning Markup Language)
This provisioning request-and-response protocol contains the main specification, SPML v2, and two profiles: SPML v2 - DSML v2 Profile and SPML v2 - XSD Profile.
|
| |
SQL with XML extensions (SQL/XML)
SQL/XML is a series of XML-related modules for the
SQL database query language. Learn how this standard began, and read
about the specifications that it covers.
|
| |
SSML (Speech Synthesis Markup Language 1.0)
SSML provides a standard way to control aspects of speech in Web and other applications, for characteristics such as pronunciation, volume, pitch, and rate.
|
| |
SVG's XML Binding Language (sXBL)
sXBL defines the presentation and interactive behavior of elements described in a namespace. Bindings can be attached to elements using either cascading stylesheets or the document object model. sXBL is intended to develop into a more general-purpose XBL specification.
|
| |
Scalable Vector Graphics (SVG)
Use Scalable Vector Graphics (SVG), a vector graphics
language, to describe two-dimensional vector graphics. Discover what's
included in the SVG feature set, and learn about its relationship to
Document Object Model (DOM), Cascading Style Sheets (CSS), XHTML, and
more.
|
| |
Scalable Vector Graphics (SVG) Tiny 1.2
SVG Tiny 1.2 is the baseline profile of SVG (and the core of SVG 1.2) for a range of devices from cell phones and PDAs to desktop and laptop computers.
|
| |
Schema Centric XML Canonicalization 1.0
This specification details limitations in the algorithms within Canonical XML and Exclusive XML Canonicalization, which significantly limit their utility in many XML applications, particularly those that validate and process XML data according to the rules and flexibilities of XML Schema.
|
| |
Schematron
Schematron is a rules-based XML schema language used to
define and limit XML vocabularies. Discover the benefits of using the
Schematron standard, either on its own or in conjunction with other
schema languages.
|
| |
Security Assertion Markup Language (SAML) v1.0
SAML is an XML framework for exchanging authentication and authorization information.
|
| |
Security Assertion Markup Language (SAML) v1.1
SAML is an XML-based framework for exchanging authentication and authorization information, enabling single sign-on use of Internet resources.
|
| |
Security Assertion Markup Language (SAML) v2.0
SAML 2.0 adds session support, the exchange of metadata to ensure interoperable interactions, and the collection of credentials for identity federation.
|
| |
Selectors
This document describes extensions to the selectors in CSS level 2 that will be will be used by CSS level 3. Selectors -- optimized for use in HTML and XML-- are patterns that match against elements in a tree.
|
| |
Selectors API
Primarily used in CSS, this specification defines two methods for retrieving elements from the DOM using a group of Selectors.
|
| |
Semantic Annotations for WSDL - Usage Guide
This usage guide illustrates how to associate semantic annotations with a Web service that could be used for classifying, discovering, matching, composing, and invoking Web services.
|
| |
Semantic Annotations for WSDL and XML
Semantic Annotations for WSDL defines how to add semantic annotations to various parts of a WSDL document such as input and output message structures, interfaces and operations.
|
| |
Semantic Interpretation for Speech Recognition (SISR) Version 1.0
This specification defines the syntax and semantics of Tags in Speech Recognition Grammar 1.0 and describes how a semantic interpretation grammar processor converts a voiced utterance into an ECMAScript which can be encoded into VoiceXML forms.
|
| |
Service Modeling Language
This specification defines the Service Modeling Language (SML) used to model complex IT services and systems, including their structure, constraints, policies, and best practices. These models typically include information about configuration, deployment, monitoring, policy, health, capacity planning, target operating range, service level agreements, and so on. SML is based on a profile on XML Schema and Schematron.
|
| |
Service Modeling Language Interchange Format Version 1.1
The SML Interchange specification is used to identify the model, to distinguish between documents containing the model definition and model instance, and to bind rule documents with other documents in the interchange set.
|
| |
Service Modeling Language, Version 1.1
This specification provides a rich set of constructs for creating models of complex services and systems. Constructs include configuration, deployment, monitoring, policy, health, capacity planning, target operating range, service level agreements. SML uses XML Schema and a profile of Schematron.
|
| |
Simple API for XML (SAX)
Simple API for XML (SAX), an event-driven XML API,
defines a stream of events specifying XML structure as handed from the
parser to the specialized handler code. Discover how SAX originated, and
learn why it's considered to be one of the most efficient, yet one of
the most difficult, ways to process XML.
|
| |
Speech Recognition Grammar 1.0
This document defines grammar syntax for use in speech recognition. Developers can specify the words and patterns for which a speech recognizer will listen. The specification makes two representations mappable to allow for automatic transformations: an Augmented BNF Form and an XML Form.
|
| |
Speech Synthesis Markup Language (SSML) Version 1.1
SSML provides a standard way to control aspects of speech in Web and other applications, for characteristics such as pronunciation, volume, pitch, and rate.
|
| |
State Chart XML (SCXML)
State Chart XML (SCXML) is an XML application for
expressing state machines. Learn how it came into being, and discover
its relationship to voice technologies.
|
| |
Synchronized Multimedia Integration Language
(SMIL)
Synchronized Multimedia Integration Language (SMIL)
is an application for the simple authoring of rich media or multimedia
(audio/visual) presentations. Learn more about this XML standard often
used for animation features in other languages.
|
| |
Synchronized Multimedia Integration Language (SMIL) 3.0
SMIL 3.0 seeks to define an XML-based language that allows authors to write interactive multimedia presentations, which describe timing and synchronizing behaviors, associate hyperlinks with media objects, and describe layout. In particular, SMIL 3.0 modularizes some SMIL 2.1 components and allows for the reuse of syntax and semantics in other XML-based languages that need to represent timing and synchronization.
|
| |
Synchronized Multimedia Integration Language (SMIL) Animation
While animation is also a subset of SMIL 2.0, SMIL Animation is a separate W3C Recommendation, which provides an animation framework as well as a set of base XML animation elements suitable for integration with XML documents.
|
| |
TMX 1.4b
TMX provides a standard method to describe translation memory data exchanged among tools and translators, with little or no loss of critical data during the process. The specification consists of two parts: A container format for higher-level elements and a low-level meta-markup format for segment content.
|
| |
The CSS 'Reader' Media Type
This CSS3 document defines a Media Query that includes the 'reader' keyword, which when attached to a style sheet is designed to be used by a "reader" device that both displays and speaks a document.
|
| |
The Disposition of Names in an XML Namespace
This document discusses defining of additional names in a published namespace and the policies related to their extension.
|
| |
The XMLHttpRequest Object
XMLHttpRequest is an interface exposed by a scripting engine that allows scripts to perform HTTP client functionality, such as submitting form data or loading data from a server.
|
| |
Timed Text (TT) Authoring Format 1.0 - Distribution Format Exchange Profile (DFXP)
The timed text authoring format is a content type for representing text media for interchange among authoring systems that is associated with timing information. The Distribution Format Exchange Profile is for transcoding or exchanging timed text information among legacy distribution content formats presently in use for subtitling and captioning.
|
| |
UBL 1.0 (Universal Business Language)
UBL defines a common XML library of business documents, such as purchase orders and invoices, as well as reusable data components, such as address and payment, from which any number of other documents can be constructed to integrate with established commercial and legal practices.
|
| |
UBL NDR V1.0 (Naming and Design Rules)
These rules provide for the UBL library a normative set of XML schema design rules and naming conventions for the creation of XML schema for business documents.
|
| |
UDDI v2 (Universal Description, Discovery and Integration)
UDDI defines a set of services supporting the description and discovery of: businesses, organizations, and other Web services providers, the Web services they make available, and the technical interfaces that may be used to access those services.
|
| |
UDDI v3.0.2 (Universal Description, Discovery and Integration)
UDDI defines a set of services supporting the description and discovery of: businesses, organizations, and other Web services providers, the Web services they make available, and the technical interfaces that may be used to access those services
|
| |
Uniform Resource Identifiers (URIs) and Internationalized
Resource Identifiers (IRIs)
Uniform Resource Identifiers (URIs) define a standard
system for identifying resources on the Web, including HTML pages, XML
documents, images, multimedia files, and more. Get to know how URIs,
Uniform Resource Names (URNs), and URLs are related, discover the
difference between absolute and relative URIs, and learn about
Internationalized Resource Identifiers (IRIs), an enhanced version of
URIs with better support for non-English speakers.
|
| |
Universal Business Language (UBL) v2.0
UBL is designed to provide a universally understood and recognized commercial syntax for legally binding business documents and to operate within a standard business framework.
|
| |
User Agent Accessibility Guidelines 1.0
This document provides guidelines for designing user agents that lower barriers to the Web for people with disabilities (visual, hearing, physical, cognitive, and neurological). User agents include HTML browsers and other types of software that retrieve and render Web content.
|
| |
Voice Extensible Markup Language (VoiceXML)
Voice Extensible Markup Language (VoiceXML) is an XML
application for creating audio, speech, and telephony applications.
Learn more about its features, as well as the enhancements that Version
2.1 is planning to offer.
|
| |
W3C XML Schema (WXS)
W3C XML Schema (WXS), a grammar-based XML schema language,
is used to define and limit XML vocabularies. It is the foundation of
some other standards in areas from XML messaging to data binding. Learn
about its relationship to other schema language technologies.
|
| |
WICD Core 1.0
WICD Core is a device-independent, compound document (multiple-format document) profile based on XHTML, CSS, and SVG.
|
| |
WICD Full 1.0
WICD Full is designed to enable rich multimedia content on desktop devices and may also be appropriate for high-capability handheld devices with a pointing device.
|
| |
WICD Mobile 1.0
WICD Mobile addresses the unique requirements of one-handed operation devices and enables rich media publishers to target these devices without evaluating their user agent identification strings.
|
| |
WS Choreography Model Overview
While WSDL outlines the format and structure of exchangeable messages, WS Choreography defines the sequence and conditions in which those messages are exchanged.
|
| |
WS-Notification v1.3 (WSN v1.3)
WS-Notification is a set of related specifications (Web Services Base Notification v1.3, Web Services Brokered Notification v1.3, and Web Services Topics v1.3) that defines a Web services approach to notification using a topic-based, publish/subscribe pattern.
|
| |
WS-Reliability v1.1
WS-Reliability, also known as WSRM (Web Services Reliable Messaging), defines methods to guarantee the delivery of a Web service message, to eliminate duplicate messages, and to guarantee the ordering of Web service messages.
|
| |
WS-ReliableMessaging 1.1
This specification describes a protocol that allows messages to be transferred reliably between nodes during software, system, or network failures.
|
| |
WS-SecureConversation v1.3
This specification defines extensions for WS-Security to allow security context establishment and sharing, and session key derivation.
|
| |
WS-SecurityPolicy v1.2
This document indicates the policy assertions for use with [WS-Policy] which apply to WSS: SOAP Message Security [WSS10, WSS11], [WS-Trust] and [WS-SecureConversation]. This document defines a set of security policy assertions for use with the WS-Policy framework regarding security features provided in WSS: SOAP Message Security, WS-Trust, WS-SecureConversation.
|
| |
WS-Trust v1.3
This specification defines extensions for WS-Security for requesting and issuing security tokens, and for determining the trust of the issued security tokens.
|
| |
Web Services Addressing 1.0 - Core
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Core defines a family of message addressing properties that convey end-to-end message characteristics, including references for source and destination endpoints and transport-independent message identity.
|
| |
Web Services Addressing 1.0 - Metadata
This specification defines how the abstract properties of Web Services Addressing 1.0 - Core are described using WSDL. It also includes WSDL metadata in endpoint references, and how WS-Policy can be used to indicate WS-Addressing by a Web service.
|
| |
Web Services Addressing 1.0 - SOAP Binding
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. SOAP Binding defines the binding of the abstract properties defined in the Core specification.
|
| |
Web Services Addressing 1.0 - WSDL Binding
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. WSDL Binding describes, using WSDL, the abstract properties in the Core specification.
|
| |
Web Services Business Process Execution Language v2.0
This specification is intended to be used to model the behavior of both executable and abstract (that is, descriptive) processes.
|
| |
Web Services Choreography Description Language Version 1.0 (WS-CDL)
This language describes the peer-to-peer collaborations between participating Web services within or across the trusted domains of an organization, where ordered message exchanges result in accomplishing a common business goal. This collaboration is accomplished regardless of platform or programming model.
|
| |
Web Services Choreography Description Language: Primer
This primer presents an easy to understand tutorial on the uses and the features of the Web Services Choreography Description Language, a language for specifying peer-to-peer protocols where each party wishes to remain autonomous and in which no party is master over any other.
|
| |
Web Services Context (WS-Context) v1.0
WS-Context provides a definition, a structuring mechanism, and a software service definition for organizing and sharing context across multiple endpoints. The context service defines the scope of an activity and how you can reference the context in a distributed environment.
|
| |
Web Services Description Language (WSDL) Version 2.0 Part 0: Primer
This companion is an easier, less technical introduction to the main features of the Web Services Description Language.
|
| |
Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language
This language describes Web services based on an abstract model of what the service offers. The messages exchanged between the service provider and requestor are described abstractly and then bound to a concrete network protocol and message format.
|
| |
Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts
Part 2 of WSDL extends the syntax and component model by providing extensions and features such as message exchange patterns, which define the sequence, direction, and cardinality of abstract messages sent or received by an operation.
|
| |
Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding
This document details the use of WSDL in conjunction with the SOAP protocol, and provides the binding extension for SOAP 1.1.
|
| |
Web Services Description Language (WSDL) Version 2.0: RDF Mapping
This specification provides a representation of WSDL in the Resource Description Framework language (RDF) and in the Web Ontology Language (OWL), and also a RDF mapping procedure.
|
| |
Web Services Distributed Management (WSDM) v1.1
WSDM enables management applications to be built using Web services, allowing resources to be controlled by many managers through a single interface.
|
| |
Web Services Distributed Management: Management Using Web Services (MUWS 1.0)
Web Services Distributed Management: Management Using Web Services defines the application foundation of how to represent and access the manageability interfaces of resources as Web services.
|
| |
Web Services Distributed Management: Management of Web Services (WSDM-MOWS) 1.0
Web Services Distributed Management: Management Of Web Services defines the model for managing Web services as a resource and how to describe and access that manageability.
|
| |
Web Services Internationalization (WS-I18N)
Using enhancements to SOAP messaging, WS-I18N provides internationalized and localized operation throughlocale and international preference negotiation. This model has been extended to Web-based applications by having Web servers infer their internal locale from the user agent's Accept-Language header or from some form of user identity management.
|
| |
Web Services Policy 1.5 - Attachment
Web Services Policy is a machine-readable language for representing the policies, defined as capabilities and requirements, of a Web service. Attachment defines two general-purpose mechanisms for associating policies with the subjects to which they apply: as part of existing metadata about the subject or independently associated through an external binding.
|
| |
Web Services Policy 1.5 - Framework
Web Services Policy is a machine-readable language for representing the policies, defined as capabilities and requirements, of a Web service. The Framework provides a general purpose model and corresponding syntax to describe these.
|
| |
Web Services Policy 1.5 - Guidelines for Policy Assertion Authors
This guide is intended to provide direction for assertion authors working with the Web Services Policy 1.5 - Framework and Web Services Policy 1.5 - Attachment specifications to create domain specific assertions.
|
| |
Web Services Policy 1.5 - Primer
Web Services Policy is a machine-readable language for representing the policies, defined as capabilities and requirements, of a Web service. This offers mechanisms to represent consistent combinations of those capabilities and requirements, to determine the compatibility of policies, to name and reference policies, and to associate policies with Web service metadata constructs.
|
| |
Web Services Resource Framework (WSRF) v1.2
This framework contains five specifications related to Web services and their relationship within the framework: WS-Resource v1.2, WS-ResourceProperties v1.2, WS-ResourceLifetime v1.2, WS-ServiceGroup v1.2, and WS-BaseFaults v1.2.
|
| |
Web Services Security SAML Token Profile v1.0 and REL Token Profile v1.0
Both token profiles describe how to interact with the Web Services Security: SOAP Message Security specification, with either SAML 1.1 or the ISO/IEC 21000-5 Rights Expression Language (REL).
|
| |
Web Services Security v1.0
WSS can be used to accommodate a wide variety of security models and encryption technologies and is composed of five parts: SOAP Message Security, Username Token Profile, X.509 Certificate Token Profile, and two XML schema documents, namely secext.xsd and utility.xsd.
|
| |
Web Services Security v1.1
Web Services Security version 1.1 provides security functions in messages implementing higher-level Web services applications and includes the following specifications, which are considered collectively as WSS v1.1: WS-Security 1.1, Username Token Profile 1.1, X.509 Token Profile 1.1, Kerberos Token Profile 1.1, SAML Token Profile 1.1, REL Token Profile 1.1, SOAP With Attachments (SWA) Profile 1.1, and Schema 1.1.
|
| |
Web Services Transaction v1.1
This specification enables existing transaction processing, workflow, and other systems for coordination to hide their proprietary protocols and to operate in a heterogeneous environment. WS-Transaction consists of three documents: Web Services Coordination v1.1; Web Services Atomic Transaction v1.1; and Web Services Business Activity v1.1.
|
| |
Web Services for Remote Portlets (WSRP) v1.0
WSRP provides standard application logic and presentation logic for web services interfaces, standardizing the integration for portals, aggregating applications, and other diverse intermediary applications.
|
| |
WebCGM 2.0
WebCGM contains three components for the representation of 2D graphical content within Web documents: a profile of the ISO Computer Graphics Metafile (CGM) standard for scalable 2D vector graphics on the World Wide Web, a WebCGM DOM, and a definition of a standard WebCGM XML Companion File to externalize non-graphical metadata. WebCGM 2.0 is also a ratified OASIS standard: http://www.oasis-open.org/specs/index.php#webcgmv2.0
|
| |
Widgets 1.0
This document describes widgets, small client-side applications for displaying and updating remote data, packaged in a way to allow a single download and installation on a client machine. Widgets may execute outside of the typical Web browser interface. This document covers the packaging format, the config.xml file, and scripting interfaces for working with widgets.
|
| |
X+V 1.1 ---XHTML+Voice
X+V brings spoken interaction to standard WWW content by integrating a set of mature WWW technologies such as XHTML and XML Events with XML vocabularies developed as part of the W3C Speech Interface Framework. X+V brings together voice modules that support speech synthesis, speech dialogs, command and control, speech grammars, and the ability to attach Voice handlers for responding to specific DOM events, thereby re-using the event model familiar to web developers. Voice interaction features are integrated directly with XHTML and CSS, and can consequently be used directly within XHTML content.
|
| |
X-BULK (XML Key Management Specification Bulk Operation)
This document extends XKMS (XML Key Management Specification) to encompass the bulk registration operations necessary for systems such as smart card management systems.
|
| |
XACML 1.0 (eXtensible Access Control Markup Language)
The XACML standard describes a policy language for general access control requirements and an access control decision request/response language.
|
| |
XACML v2.0 (eXtensible Access Control Markup Language)
XACML defines an XML-based method for expressing well-established ideas in the field of access-control policy. V2.0 includes a Core Specification and the following profiles: SAML 2.0, XML Digital Signature, Privacy Policy, Hierarchical Resource, Multiple Resource, and Core and Hierarchical Role Based Access Control (RBAC).
|
| |
XBRL 2.1
XBRL defines XML elements and attributes that can be used to express information used in the creation and exchange of tasks relating to financial reporting.
|
| |
XCBF 1.1 (XML Common Biometric Format)
This specification defines a common set of secure XML encodings for biometrics, automated methods of recognizing a person based on physiological or behavioral characteristics.
|
| |
XCIL 2.0 (Extensible Customer Information Language)
xCIL describes a common structure for representing customer information, such as telephone numbers, email addresses, and customer IDs, in a standard format as outlined in a DTD (Document Type Definition).
|
| |
XCRL 2.0 (Extensible Customer Relationships Language)
This document outlines simple guidelines to allow customers and organizations to exchange information with a minimum of misinterpretation and misuse.
|
| |
XForms
XForms, a specification of Web forms for XML data
processing, allows you to separate a form's purpose from its look. Find
out how XML technologies make it easy to create Web applications with
user input.
|
| |
XFrames
XFrames replaces HTML Frames, and is an XML application for composing documents into a single view.
|
| |
XHTML
XHTML is a Web presentation language based on HTML but
recast in well-formed XML. It's designed to continue the trend in HTML
4.01 of encouraging the separation of content from presentation.
Discover the many changes that XHTML 2.0 will offer, including features
that will improve the ability of authors to express content structure
and meaning.
|
| |
XHTML + MathML + SVG Profile
This profile enables mixing XHTML, MathML and SVG in the same document using XML namespaces while allowing validation of such a mixed-namespace document.
|
| |
XHTML Document Profile Requirements
Document Profiles are designed to describe a class of environment in which a document might be processed. An author building a document with a particular document profile in mind can be confident that any user agent built for the same profile will render the document exactly as intended. This document outlines the requirements for this technology.
|
| |
XHTML Role Attribute Module
This specification provides XML languages with the ability to integrate a "role" attribute into any markup language based on Modularization of XHTML 1.1.
|
| |
XHTML-Print
XHTML-Print, defined by the Modularization of XHTML, improves printing from mobile devices to low-cost printers and printing in environments where printer-specific drivers are not present.
|
| |
XLIFF 1.1 (XML Localization Interchange File Format)
XLIFF provides a single interchange file format that can be understood by any localization provider and is loosely based on OpenTag and TMX 1.2.
|
| |
XLIFF Version 1.2
XML Localization Interchange File Format (XLIFF) provides a single interchange file format -- in "strict" and "transitional" (downwardly compatible) variants -- that can be understood by any localization provider.
|
| |
XMI v2.1 (XML Metadata Interchange)
XMI enables the interchange of metadata between modeling tools (based on OMG-UML) and metadata repositories (based on OMG-MOF) in distributed heterogeneous environments.
|
| |
XML - Signature Requirements
This document describes the requirements for creating digital signatures for XML documents. It is a joint effort of the W3C and the IETF.
|
| |
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.
|
| |
XML - Signature XPath Filter 2.0
This specification defines a new XML Signature transform to facilitate implementations which specify a subset of a given XML document as the content to be signed.
|
| |
XML 1.0 Second Edition Conformance Test Suite
This Test Suit contains over 2000 test files and an associated test report, as well as background information on conformance testing for XML and test descriptions for each of the included test files.
|
| |
XML Accessibility Guidelines
This document provides guidelines for designing with XML and lowering barriers to Web accessibility for people with disabilities.
|
| |
XML Base
XML Base provides a means of associating XML elements with
Uniform Resource Identifiers (URIs). Learn how to more precisely specify
how relative URIs are resolved in relevant XML processing actions.
|
| |
XML Binding Language (XBL)
XML Binding Language (XBL) allows you to define
behaviors, possibly in the form of handler scripts, related to XML
elements. Learn how XBL opens up a declarative means of developing XML-based applications.
|
| |
XML Blueberry Requirements
This document lists the design principles and requirements for the Blueberry revision, a limited revision of XML 1.0 to address character set issues.
|
| |
XML Bookmark Exchange Language (XBEL)
XML Bookmark Exchange Language (XBEL) is a format for
expressing bookmarks and other such collections of Web links. It is used
as the basic storage for bookmarks in several Web browsers.
|
| |
XML Catalogs
XML Catalogs provides instructions on how an XML processor
resolves XML entity or URL requests, and it allows you to substitute one
resource with another. Learn more about this standard and when you
should consider using it.
|
| |
XML Encryption Syntax and Processing
This document specifies a process for encrypting data and representing the result in XML.
|
| |
XML Events 2
XML Events uniformly integrates event listeners and associated event handlers with DOM Level 2 event interfaces.
|
| |
XML Fragment Interchange
"XML Fragment Interchange defines a way to send fragments of an XML document -- regardless of whether or not the fragments are predetermined entities -- without having to send all of the containing document up to the part in question.
|
| |
XML Inclusions (XInclude)
XML Inclusions (XInclude) is a system for merging XML
documents, similar to built-in XML external entities, but with added
features. Learn how to assemble one large document from one or more
smaller ones, and even to pick and choose parts of the component
documents using XPointer.
|
| |
XML Information Set (Infoset)
XML Information Set (Infoset) allows you to describe an XML
document as a series of objects with specialized properties. Read about
this abstract data to better understand the basic structure of XML.
|
| |
XML Key Management Specification (XKMS 2.0)
This document specifies protocols for distributing and registering public keys in conjunction with XML-SIG and XML-ENC. The XML Key Management Specification (XKMS) consists of two parts, the XML Key Information Service Specification (X-KISS) and the XML Key Registration Service Specification (X-KRSS).
|
| |
XML Key Management Specification (XKMS 2.0) Bindings
This document details protocol bindings with security characteristics for XKMS.
|
| |
XML Linking Language (XLink)
XML Linking Language (XLink) is a generic framework for
expressing links in XML documents, to complete its placement in
hypertext systems such as the Web. It can be used to create simple
links, such as those that are an essential part of HTML documents, or
more complex types of links, such as multiended links and link databases.
|
| |
XML Namespaces
XML Namespaces allow you to provide universal names for
elements and attributes in XML documents. Discover why and when you
should take advantage of XML Namespaces, and learn about the importance
of Resource Directory Description Language (RDDL).
|
| |
XML Path Language (XPath)
XML Path Language (XPath), one of the most successful XML
technologies, is a syntax and data model for addressing parts of an XML
document. Learn more about this XML standard, which includes some
features of a general-purpose expression language.
|
| |
XML Processing Model (XProc)
Learn about XML Processing Model (XProc), a language
for orchestrating the individual operations that can be combined during
XML processing. Learn how to build XML applications from declarations of
simple interactions and transformations of documents.
|
| |
XML Schema 1.1 Part 2: Datatypes
This datatype language, which is itself represented in XML, provides a superset of the capabilities found in XML Document Type Definitions (DTDs) for specifying datatypes on elements and attributes in XML Schemas as well other XML specifications.
|
| |
XML Schema 1.1 Requirements
This document contains the requirements that should, must, and may be met in an XML Schema 1.1.
|
| |
XML Schema Definition Language (XSDL) 1.1 Part 1: Structures
The XML Schema definition language describes the structure and constrains the contents of XML documents, including those which exploit the XML Namespace facility. It also provides a detailed mapping between the elements and attribute vocabulary of this representation and the components and properties of the abstract model.
|
| |
XML Schema Part 0: Primer Second Edition
The Primer provides an easily readable description of the XML Schema facilities.
|
| |
XML Schema Part 1: Structures Second Edition
The XML Schema definition language, which is itself represented in XML 1.0, provides a means to describe the structure and contents of XML 1.0 documents, and provides a superset of the capabilities found in XML 1.0 document type definitions (DTDs). See also http://www.w3.org/TR/xmlschema-2/ for XML Schema Part 2: Datatypes. For an excellent introduction to XML Schema, see http://www.w3.org/TR/xmlschema-0/ for XML Schema Part 0: Primer.
|
| |
XML Schema Part 2: Datatypes Second Edition
Part 2 of the XML Schema definition language addresses the specification of datatypes in XML 1.0 documents. See also http://www.w3.org/TR/xmlschema-1/ for XML Schema Part 1: Structures. For an excellent introduction to XML Schema, see http://www.w3.org/TR/xmlschema-0/ for XML Schema Part 0: Primer.
|
| |
XML Schema: Component Designators
XML Schema components are divided into three classes: primary components, secondary components, and helper components. There is also a master schema component, representing the schema as a whole.
|
| |
XML Schema: Formal Description
This document provides a formal description of XML types and validity as specified by XML Schema Part 1: Structures.
|
| |
XOP (XML-binary Optimized Packaging)
XOP conveys a means of more efficiently serializing XML Infosets that have certain types of content. Under this specification, only elements can be optimized. This excludes attributes, non-base64-compatible character data, and data not in the canonical representation.
|
| |
XPointer Framework
The framework is 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.
|
| |
XPointer Framework
XPointer, a language for referring to locations of
fragments of an XML document, brings similar (but more expansive)
capabilities to using URLs with hashes in order to link to a particular
point in an HTML document. Learn more about this language, including the
controversy it has stirred up and the alternative schemes it has spawned.
|
| |
XPointer element() Scheme
The XPointer element() scheme is used with the XPointer Framework to allow basic addressing of XML elements.
|
| |
XPointer xmlns() Scheme
This scheme is used with the XPointer Framework to allow correct interpretation of namespace prefixes in pointers.
|
| |
XPointer xpointer() Scheme
Used with the XPointer Framework, this scheme provides a high level of functionality for addressing portions of XML documents, adding the ability to address strings, points, and ranges in accordance with DOM2: Range definitions.
|
| |
XQuery 1.0 and XPath 2.0 Data Model (XDM)
This data model defines the information contained in the input to an XSLT or XQuery processor and also defines all permissible values of expressions in the XSLT, XQuery, and XPath languages.
|
| |
XQuery 1.0 and XPath 2.0 Formal Semantics
This document defines a precise, formal meaning to each of the expressions of the XPath/XQuery specification set.
|
| |
XQuery 1.0 and XPath 2.0 Full-Text 1.0 Requirements
This document describes the set of requirements for Full Text Search (FTS) in XQuery and XPath.
|
| |
XQuery 1.0 and XPath 2.0 Full-Text Use Cases
This document illustrates important applications of full-text querying. Each use case demonstrates a specific function relevant to full-text querying.
|
| |
XQuery 1.0 and XPath 2.0 Functions and Operators
This document catalogs the functions and operators required for XPath 2.0, XML Query 1.0, and XSLT 2.0.
|
| |
XQuery 1.0: An XML Query Language
This specification describes a query language designed to be broadly applicable across many types of XML data sources.
|
| |
XQuery 1.0: An XML Query Language
XQuery, a specification for querying XML data sources
such as documents and databases, is a superset of XPath. Learn more
about this programming language, including its numerous specifications
that cover semantics, syntax, and core library functions.
|
| |
XQuery Requirements
This document specifies the goals, requirements, and usage scenarios of XQuery.
|
| |
XQuery Update Facility Use Cases
This document presents various use cases of the XQuery Update Facility, including updating relational data, synchronizing address books, and modifying a SOAP message.
|
| |
XQueryX (XML Syntax for XQuery 1.0)
XQueryX is an XML representation of an XQuery. While not particularly convenient for humans to read and write, it is easy for programs to parse, and standard XML tools can be used to create, interpret, or modify queries.
|
| |
XSLT 1.0 (XSL Transformations)
XSLT is an XML vocabulary for defining templates that describe how XML content should be transformed. It has a wide variety of operators and matching rules, and defines which rule should be invoked if more than one rule applies to a given XML element.
|
| |
XSLT 2.0 and XQuery 1.0 Serialization
This standard defines the serialization of XQuery 1.0 and XPath 2.0 Data Model, which is the data model of standards such as XPath 2.0, XSLT 2.0, and XQuery 1.0.
|
| |
XUpdate
XUpdate is an instruction language that lets you
modify XML documents. Discover how XUpdate works with regular XML
documents, XML in database collections, and virtual XML data models, as
well as its relationship to XSLT.
|
| |
eContracts Version 1.0
This specification describes the generic hierarchical structure of a wide range of contract documents, including negotiated business contracts, ticket contracts, standard form business and consumer contracts, and click-through agreements.
|
| |
ebXML Business Process Specification Schema Technical Specification v2.0.4
BPSS (or ebBP) provides capabilities to drive collaborative business processes, including standard and extensible business transaction patterns, semantic tailoring for processes and documents, support for modular definitions and complex nested activities, and support for the use of web service, hybrid, and ebXML assets.
|
| |
ebXML MSG V2.0 (Message Service Specification)
The Messaging Service (MS) specification provides a secure method for the exchange -- transport, routing, and packaging -- of electronic business transactions using the Internet.
|
| |
ebXML Messaging Services Version 3.0: Part 1, Core Features
This specification defines a method for exchanging electronic business messages, most particularly Web Services-based enveloping constructs that support reliable, secure delivery of business information. Version 3.0 extends the specification to better address the diversity of back-end binding models, as well as the emerging trend in business activity monitoring.
|
| |
ebXML RIM v3.0
The ebXML Registry Information Model (RIM) specification defines the types of metadata and content that can be stored in an ebXML Registry. Electronic content includes XML documents, text documents, images, sound and video and its related metadata. Version 3.0 adds federated and secure information management capabilities.
|
| |
ebXML RS v2.0 (Registry Services)
ebRS allows the sharing of information between interested parties for process integration. The shared information is managed and maintained as objects in a repository.
|
| |
ebXML RS v3.0
ebXML Registry Services and Protocols (RS) defines the services provided by an ebXML Registry and the protocols used by clients of the registry to interact with these services. Version 3.0 adds federated and secure information management capabilities.
|
| |
ebXML Registry Information Model (RIM) v2.0 [OASIS 200203]
The Registry Information Model provides implementers of ebXML Registries with a schema for both the type of metadata stored in the Registry and the organizing relationships among metadata Classes.
|
| |
xNAL 2.0 (Extensible Name and Address Language)
This specification defines a global name and address standard that is vendor neutral, open, and application independent, and is detailed in a DTD (Document Type Definition). xNL and xAL are the name and address components of xNAL.
|
| |
xml:id
xml:id provides a formal convention for attributes
expressing unique identifiers for elements in XML documents. Discover
how it avoids the pitfalls of Document Type Definition (DTD) ID types
while providing a refreshing simplicity.
|
| |
