 |
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.
|
| |
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.
|
| |
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.
|
| |
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 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 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 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 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 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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
XQuery Requirements
This document specifies the goals, requirements, and usage scenarios of XQuery.
|
| |
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 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 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 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 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 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.
|
| |
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.
|
| |
XPointer xmlns() Scheme
This scheme is used with the XPointer Framework to allow correct interpretation of namespace prefixes in pointers.
|
| |
XPointer element() Scheme
The XPointer element() scheme is used with the XPointer Framework to allow basic addressing of XML elements.
|
| |
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.
|
| |
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.
|
| |
XML Schema: Formal Description
This document provides a formal description of XML types and validity as specified by XML Schema Part 1: Structures.
|
| |
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 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 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 0: Primer Second Edition
The Primer provides an easily readable description of the XML Schema facilities.
|
| |
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 1.1 Requirements
This document contains the requirements that should, must, and may be met in an XML Schema 1.1.
|
| |
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 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 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 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 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 Key Management Specification (XKMS 2.0) Bindings
This document details protocol bindings with security characteristics for XKMS.
|
| |
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 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 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 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 Events 2
XML Events uniformly integrates event listeners and associated event handlers with DOM Level 2 event interfaces.
|
| |
XML Encryption Syntax and Processing
This document specifies a process for encrypting data and representing the result in XML.
|
| |
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 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 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 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 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 Accessibility Guidelines
This document provides guidelines for designing with XML and lowering barriers to Web accessibility for people with disabilities.
|
| |
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 - 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 - 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 Requirements
This document describes the requirements for creating digital signatures for XML documents. It is a joint effort of the W3C and the IETF.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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 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 + 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
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.
|
| |
XFrames
XFrames replaces HTML Frames, and is an XML application for composing documents into a single view.
|
| |
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.
|
| |
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.
|
| |
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).
|
| |
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.
|
| |
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.
|
| |
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).
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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.
|
| |
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
|
| |
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.
|
| |
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 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 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 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 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 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 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 - 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 - 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 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 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 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 (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 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 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 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 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 0: Primer
This companion is an easier, less technical introduction to the main features of the Web Services Description Language.
|
| |
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 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 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.
|
| |
