Advertisement and Discovery of Services ADS is comparable to other discovery mechanisms proposed by Microsoft in their DISCO specification, and CommerceNet in their eCo Framework, in that they all offer means to advertise locations of service descriptions. The ADS method utilizes the Well-Defined Service description documents.More Information
Business Transaction Protocol The BTP Technical Committee develops an XML-based protocol for managing complex B2B transactions over the Internet Access the specification ...
Canonical XML Any XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 and Namespaces in XML. This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes. Except for limitations regarding a few unusual cases, if two documents have the same canonical form, then the two documents are logically equivalent within the given application context. The canonical form of an XML document is physical representation of the document produced by the method described in this specification.The term canonical XML refers to XML that is in canonical form. The XML canonicalization method is the algorithm defined by this specification that generates the canonical form of a given XML document or document subset. The term XML canonicalization refers to the process of applying the XML canonicalization method to an XML document or document subset. Access the specification ...
Cold Fusion Markup Language CFML is the server side markup language used by Alliare's application server Cold Fusion. CFML allows one to connect databases to the World Wide Web, generate active web pages on demand, manage structured and semi-structured data with nothing more than a web browser, gather data from web forms, and operate interactive web sites.More Information
Chemical Markup Language CML is a new approach to managing molecular information. It has a large scope as it covers disciplines from macromolecular sequences to inorganic molecules and quantum chemistry. CML is new in bringing the power of XML to the management of chemical information. In simple terms it is "HTML for Molecules", but there is a great deal more to it than that. CML and associated tools allows for the conversion of current files without semantic loss into structured documents, including chemical publications, and provides for the precise location of information within files.
CML has been designed carefully so that it is as easy as possible for the 'average chemist' to understand it. Like a lot of chemistry it's not trivial, but it's no harder than Cahn-Ingold-Prelog chirality rules, and easier than Huckel theory. It helps if you know something about HTML and have tried to transfer data files between sites or programs. It's not magic, and doesn't do anything that isn't really just common sense, but it hides a lot of the inconvenience that we have at present.More Information
CRML Either expanded to Customer Relationships Markup Language a language for Customer Profile/Information Management or to Content Request Markup Language which denotes a language for specifying distributed XML processing at the content level. Furthermore, IBM has released a Correctly Rounding Math Library for Java, but that's off topic here.
The Customer Relationships Markup Language is no longer under development, it has been submitted to OASIS and is now known as xCRL.
DARPA Agent Markup Language The W3C Note DAML (DARPA Agent Markup Language)+OIL (Ontology Inference Layer) is a semantic markup language for Web resources. It builds on earlier W3C standards such as RDF and RDF Schema, and extends these languages with richer modelling primitives. DAML+OIL provides modelling primitives commonly found in frame-based languages. DAML+OIL (March 2001) extends DAML+OIL (December 2000) with values from XML Schema datatypes. DAML+OIL was built from the original DAML ontology language DAML-ONT (October 2000) in an effort to combine many of the language components of OIL. The language has a clean and well defined semantics.Access the specification ... ... DAML Homepage ... W3C DAML+OIL Note
Decryption Transform for XML Signature This document specifies an XML Signature "decryption transform" that enables XML Signature applications to distinguish between those XML Encryption structures that were encrypted before signing (and must not be decrypted) and those that were encrypted after signing (and must be decrypted) for the signature to validate. Access the specification ...
Direct Internet Message Encapsulation Direct Internet Message Encapsulation (DIME) is a lightweight, binary message format that can be used to encapsulate one or more application-defined payloads of arbitrary type and size into a single message construct. Each payload is described by a type, a length, and an optional identifier. Both URIs and MIME media type constructs are supported as type identifiers. The payload length is an integer indicating the number of octets of the payload. The optional payload identifier is a URI enabling cross-referencing between payloads. DIME payloads may include nested DIME messages or chains of linked chunks of unknown length at the time the data is generated. DIME is strictly a message format: it provides no concept of a connection or of a logical circuit, nor does it address head-of-line problems. Access the specification ...
Document Object Model The Document Object Model (DOM) is an application programming interface (API) for valid HTML and well-formed XML documents. It defines the logical structure of documents and the way a document is accessed and manipulated. In the DOM specification, the term "document" is used in the broad sense - increasingly, XML is being used as a way of representing many different kinds of information that may be stored in diverse systems, and much of this would traditionally be seen as data rather than as documents. Nevertheless, XML presents this data as documents, and the DOM may be used to manage this data. With the Document Object Model, programmers can build documents, navigate their structure, and add, modify, or delete elements and content. Anything found in an HTML or XML document can be accessed, changed, deleted, or added using the Document Object Model, with a few exceptions - in particular, the DOM interfaces for the XML internal and external subsets have not yet been specified.Access the specification ... ... DOM Level 2 Core Specification ... DOM Level 2 Views Specification ... DOM Level 2 Events Specification ... DOM Level 2 Style Specification ... DOM Level 2 Traversal and Range Specification ... DOM Level 1
Electronic Commerce Modeling Language ECML will describes the syntax of a class of data objects called Payment Processing Objects. This will involve the development of a hierarchically organized set of data elements and an XML syntax for payment transaction information for both electronic wallets and Business to Business (B2B) payment types such as credit card, electronic check, line of credit, ACH (Automated Clearing House), Mobile Phone Payments, and PDA Payments. Access the specification ...
Exclusive XML Canonicalization Canonical XML (XML-C14N) specifies a standard serialization of XML that, when applied to a subdocument, includes the subdocument's ancestor context including all of the namespace declarations and attributes in the "xml:" namespace. However, some applications require a method which, to the extent practical, excludes unused ancestor context from a canonicalized subdocument. For example, one might require a digital signature over an XML payload (subdocument) in an XML message that will not break when that subdocument is removed from its original message and/or inserted into a different context. This requirement is satisfied by Exclusive XML Canonicalization. Access the specification ...
Human Resources XML The HR-XML Consortium is an independent, non-profit organization dedicated to the development and promotion of a standard suite of XML specifications to enable e-business and the automation of human resources-related data exchanges.More Information
Reliable HTTP HTTPR is a protocol for the reliable transport of messages from one application program to another over the Internet, even in the presence of failures either of the network or the agents on either end. It is layered on top of HTTP. Specifically, HTTPR defines how metadata and application messages are encapsulated within the payload of HTTP requests and responses. HTTPR also provides protocol rules which make it possible to ensure that each message is delivered to its destination application exactly once or is reliably reported as undeliverable. HTTP/1.1 serves as the base on which HTTPR builds. As such, all of the facilities of HTTP/1.1 are available. Access the specification ...
Information Content Exchange The ICE specification provides businesses with an XML-based common language and architecture that facilitates automatic exchanging, updating, supplying and controlling of assets in a trusted fashion without manual packaging or knowledge of remote Web site structures. For consumer Web sites, end users benefit from more complete, easier-to-use Web destinations that reduce the frustration of having to surf through many inadequate narrowly focused Web sites to find what they need. ICE v1.0 is a W3C NoteMore Information
XML Information Set The XML Information Set (Infoset) is an abstract data set for XML documents. An XML document has an information set if it is well-formed and satisfies the namespace constraints. There is no requirement for an XML document to be valid in order to have an information set. An XML document's information set consists of a number of information items; the information set for any well-formed XML document will contain at least a document information item and several others. An information item is an abstract description of some part of an XML document: each information item has a set of associated named properties.
Access the specification ...
Incident Object Description and Exchange Format The purpose of the Incident Object Description and Exchange Format is to define a common data format for describing and exchanging incident information between collaborating Computer Security Incident Response Teams (CSIRTs). The specific goals and requirements of the IODEF are described in RFC 3067. One of the design principles in the IODEF is compatibility with the Intrusion Detection Message Exchange Format (IDMEF) developed for intrusion detection systems. For this reason, IODEF is heavily based on the IDMEF and provides upward compatibility with it. Access the specification ...
Java Application Programming Interface for RELAX Verifiers
Java Application Programming Interface for RELAX Verifiers JARV was originally developed for Regular Language Description for XML (RELAX), but can be used with other schema languages or with multiple schema languages. To employ JARV the user needs the International Organization for Standardization (ISO) RELAX package and a compatible application for validating documents against a schema, such as Jing, Sun Multi-Schema XML Validator (MSV) or Swift RELAX Verifier. Xerces-2 can be used with JARV driver for Xerces-2 for W3C schema validation. Access the specification ...
Java Markup Language An XML representation for Java source code.More Information
JXBRL The JXBRL project channels the developments for an OpenSource XBRL support environment written in Java. XBRL is an XML-based language and an acronym for eXtendible Business Reporting Language.More Information
Mathematical Markup Language MathML is an XML application for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for text. MathML can be used to encode both mathematical notation and mathematical content. About thirty of the MathML tags describe abstract notational structures, while another about one hundred and fifty provide a way of unambiguously specifying the intended meaning of an expression. Additionally the MathML specification discusses how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers.Access the specification ... ... MathML ... MathML2
Namespaces in XML A single XML document may contain elements and attributes that are defined for and used by multiple software modules. If such a markup vocabulary exists which is well-understood and for which there is useful software available, it is better to re-use this markup rather than re-invent it. Such documents, containing multiple markup vocabularies, pose problems of recognition and collision. Software modules need to be able to recognize the tags and attributes which they are designed to process, even in the face of "collisions" occurring when markup intended for some other software package uses the same element type or attribute name. These considerations require that document constructs should have universal names, whose scope extends beyond their containing document. The XML namespaces mechanism accomplishes this. An XML namespace is a collection of names, identified by a URI reference (RFC2396), which are used in XML documents as element types and attribute names. XML namespaces differ from the "namespaces" conventionally used in computing disciplines in that the XML version has internal structure and is not, mathematically speaking, a set. These issues are discussed in "A. The Internal Structure of XML Namespaces". Access the specification ...
NASSL An Interface Definition Language (IDL), based on XML, that describes the interfaces necessary to access a service. NASSL does not describe the service itself; that responsibility is left to the WDS.
News Markup Language NewsML represents an XML-based standard to represent and manage news throughout its lifecycle, including production, interchange, and consumer use. NewsML, initiated by Reuters in 1998, was ratified as an official standard by the International Press Telecommunications Council (IPTC) on the 6th October 2000. NewsML can be applied at all stages in the (electronic) news life cycle. Typical uses would include: in and between editorial systems; between news agencies and their customers; between publishers and news aggregators; and between news service providers and end users. NewsML takes the form of an XML document, which has a series of components, or elements, that are used to structure and process the actual news content. These elements may have attributes to specify their properties and can carry content in the form of other elements (subelements) and/or character data or external references. Access the specification ... NewsML Homepage
Platform for Privacy Preferences The Platform for Privacy Preferences Project (P3P) enables Web sites to express their privacy practices in a standard format that can be retrieved automatically and interpreted easily by user agents. Access the specification ...
Resource Description Framework The World Wide Web was originally built for human consumption, and although everything on it is machine-readable, this data is not machine-understandable. It is very hard to automate anything on the Web, and because of the volume of information the Web contains, it is not possible to manage it manually. The solution proposed here is to use metadata to describe the data contained on the Web. Metadata is "data about data" (for example, a library catalog is metadata, since it describes publications) or specifically in the context of this specification "data describing Web resources". The distinction between "data" and "metadata" is not an absolute one; it is a distinction created primarily by a particular application, and many times the same resource will be interpreted in both ways simultaneously. Resource Description Framework (RDF) is a foundation for processing metadata; it provides interoperability between applications that exchange machine-understandable information on the Web. RDF emphasizes facilities to enable automated processing of Web resources. RDF can be used in a variety of application areas; for example: in resource discovery to provide better search engine capabilities, in cataloging for describing the content and content relationships available at a particular Web site, page, or digital library, by intelligent software agents to facilitate knowledge sharing and exchange, in content rating, in describing collections of pages that represent a single logical "document", for describing intellectual property rights of Web pages, and for expressing the privacy preferences of a user as well as the privacy policies of a Web site. RDF with digital signatures will be key to building the "Web of Trust" for electronic commerce, collaboration, and other applications. Access the specification ...
Resource Description Framework (RDF) Model and Syntax
Resource Description Framework (RDF) Model and Syntax Resource Description Framework (RDF) is a foundation for processing metadata; it provides interoperability between applications that exchange machine-understandable information on the Web. RDF emphasizes facilities to enable automated processing of Web resources. RDF can be used in a variety of application areas; for example: in resource discovery to provide better search engine capabilities, in cataloging for describing the content and content relationships available at a particular Web site, page, or digital library, by intelligent software agents to facilitate knowledge sharing and exchange, in content rating, in describing collections of pages that represent a single logical "document", for describing intellectual property rights of Web pages, and for expressing the privacy preferences of a user as well as the privacy policies of a Web site. RDF with digital signatures will be key to building the "Web of Trust" for electronic commerce, collaboration, and other applications.
RDFMS introduces a model for representing RDF metadata as well as a syntax for encoding and transporting this metadata in a manner that maximizes the interoperability of independently developed Web servers and clients. The syntax uses the Extensible Markup Language (XML): one of the goals of RDF is to make it possible to specify semantics for data based on XML in a standardized, interoperable manner. RDF and XML are complementary: RDF is a model of metadata and only addresses by reference many of the encoding issues that transportation and file storage require (such as internationalization, character sets, etc.). For these issues, RDF relies on the support of XML. It is also important to understand that this XML syntax is only one possible syntax for RDF and that alternate ways to represent the same RDF data model may emerge. Access the specification ...
Resource Description Framework (RDF) Model Theory A model-theoretic semantics for a language assumes that the language refers to a 'world', and describes the minimal conditions that a world must satisfy in order to assign an appropriate meaning for every expression in the language. A particular world is called an interpretation, so that model theory might be better called 'interpretation theory'. The idea is to provide an abstract, mathematical account of the properties that any such interpretation must have, making as few assumptions as possible about its actual nature or intrinsic structure. Model theory tries to be metaphysically and ontologically neutral. It is typically couched in the language of set theory simply because that is the normal language of mathematics - for example, this semantics assumes that names denote things in a set IR called the 'universe' - but the use of set-theoretic language here is not supposed to imply that the things in the universe are set-theoretic in nature.
RDFMT describes a model theory for RDF and RDFS which treats the language as simple assertional language, in which each triple makes a distinct assertion and the meaning of any triple is not changed by adding other triples. This imposes a fairly strict monotonic discipline on the language, so that it cannot express closed world assumptions, local default preferences, and several other commonly-used non-monotonic constructs. There are several aspects of meaning in RDF which are ignored by this semantics; in particular, it treats URIs as simple names, ignoring aspects of meaning encoded in particular URI forms (RFC 2396) and does not provide any analysis of time-varying data or of changes to URI denotations. Access the specification ...
RDF Vocabulary Description Language The Resource Description Framework Schema represents a mechanism to use RDF to describe RDF vocabularies. The specification defines a basic vocabulary for this purpose, as well as an extensibility mechanism to anticipate future additions to RDF. The RDF data model, as specified in RDFMS, defines a simple model for describing interrelationships among resources in terms of named properties and values. RDF properties may be thought of as attributes of resources and in this sense correspond to traditional attribute-value pairs. RDF properties also represent relationships between resources. As such, the RDF data model can therefore resemble an entity-relationship diagram. The RDF data model, however, provides no mechanisms for declaring these properties, nor does it provide any mechanisms for defining the relationships between these properties and other resources. That is the role of RDF Schema. Access the specification ...
Regular Language Description for XML The OASIS Technical Committee dealing with relax calls it a next generation schema language for XML: clean, simple and powerful. Access the specification ...
Representational State Transfer REST represents an architectural style that describes the architectural model of the current Web. Developed by Roy Thomas Fielding in his PhD dissertation, it is currently often referred to in technical discussions. More Information
REXML REXML is an XML parser written in and for the Ruby programming language. REXML is inspired by the Electric XML Java library (from TheMind), and aims to be small and fast with an intuitive API. It may be used according to your choice of either the Ruby license or the GPL.More Information
RDF Site Summary RDF Site Summary is a lightweight multipurpose extensible metadata description and syndication format. RSS is an XML application, conforms to the W3C's RDF Specification and is extensible via XML-namespace and/or RDF based modularization. Access the specification ...
Ruby "Ruby" are short runs of text alongside the base text, typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This specification defines markup for ruby, in the form of an XHTML module. Ruby is the term used for a run of text that is associated with another run of text, referred to as the base text. Ruby text is used to provide a short annotation of the associated base text. It is most often used to provide a reading (pronunciation guide). Ruby annotations are used frequently in Japan in many kinds of publications, including books and magazines. Ruby is also used in China, especially in schoolbooks. Access the specification ...
Rule Markup Language RuleML is an effort to develop an industry standard for exchange of rules in XML. It basically represets an XML sytax for rule knowledge representation, thus enabling interoperability among major commercial rule systems. RuleML permits forward (bottom-up) and backward (top-down) rules in XML for deduction, rewriting and further inferential-transformational tasks. Access the specification ... RuleML Homepage
Security Assertions Markup Language The purpose of SAML is to facilitate the exchange of authentication and authorization information. Access the specification ...
SOAP Contract Language Much like SDL, the SOAP Contract Language is designed to expose the capabilities of a service, but also goes much farther. Microsoft has published the SCL specification with the following comment, We published the SCL specification so we could solicit broad feedback from the industry. We’ll update the public toolkit to use SCL once the specification takes into consideration the feedback we’re going to get and is in a reasonably stable state. Until then it (the toolkit) will continue to use a form of SDL. Because of the extended capabilities of SCL, it will replace SDL once it matures.
In addition to describing a service’s capabilities, SCL goes much further by defining the actual contract by which endpoints (the server and the client) communicate. This contract contains both a description of the endpoint and the messages it will accept, and optional orchestration information that describes the flow of messages between endpoints.
Microsoft Service Description Language In order to utilize a service on a remote server using SOAP, the client needs to understand what the remote service is capable of. Using SDL, SOAP provides a way to query the remote service and learn about its capabilities, such as how it represents data types and commands. For example, using SDL one could learn that a particular service accepts two strings, searches for first string inside second, and returns true or false.
SDL is an XML document, and is very similar in concept as IDL (Interface Definition Language) except that IDL is platform specific and SDL is platform independent.
Synchronized Multimedia Integration Language The Synchronized Multimedia Integration Language (SMIL, pronounced "smile") SMIL 2.0 has the following two design goals: a) Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL 2.0, an author can describe the temporal behavior of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. b) Allow reusing of SMIL 2.0 syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL 2.0 components are used for integrating timing into XHTML and into SVG. SMIL 2.0 is defined as a set of markup modules, which define the semantics and an XML syntax for certain areas of SMIL functionality. Access the specification ...
SMIL Animation SMIL Animation incorporates animation onto a time line and represents a mechanism for composing the effects of multiple animations. A set of basic animation elements are also described that can be applied to any XML-based language. Animation is inherently time-based. SMIL Animation is defined in terms of the SMIL timing model. The animation capabilities are described by new elements with associated attributes and semantics, as well as the SMIL timing attributes. Animation is modeled as a function that changes the presented value of a specific attribute over time. Access the specification ...
Simple Object Access Protocol SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this specification describe how to use SOAP in combination with HTTP and HTTP Extension Framework.
SOAP provides a simple and lightweight mechanism for exchanging structured and typed information between peers in a decentralized, distributed environment using XML. SOAP does not itself define any application semantics such as a programming model or implementation specific semantics; rather it defines a simple mechanism for expressing application semantics by providing a modular packaging model and encoding mechanisms for encoding data within modules. This allows SOAP to be used in a large variety of systems ranging from messaging systems to RPC. Note: Since version 1.2 SOAP forms an unexpanded acronym and bears no meaning behind the capitalized characters. Access the specification ...
SOAP Security Extensions: Digital Signature The W3C Note "SOAP Security Extensions: Digital Signature" specifies the syntax and processing rules of a SOAP header entry to carry digital signature information within a SOAP 1.1 Envelope. The motivation is to propose a standard way to use the XML Digital Signature syntax to sign SOAP 1.1 messages. A SOAP header entry <SOAP-SEC:Signature/> is defined for this purpose. Access the specification ...
Scalable Vector Graphics SVG is a language for describing two-dimensional graphics in XML. SVG allows for three types of graphic objects: vector graphic shapes (e.g., paths consisting of straight lines and curves), images and text. Graphical objects can be grouped, styled, transformed and composited into previously rendered objects. The feature set includes nested transformations, clipping paths, alpha masks, filter effects and template objects. SVG drawings can be interactive and dynamic. Animations can be defined and triggered either declaratively (i.e., by embedding SVG animation elements in SVG content) or via scripting. Access the specification ...
Mobile SVG Profiles: SVG Tiny and SVG Basic Two mobile profiles of SVG 1.1. The first profile, SVG Tiny, is defined to be suitable for cellphones; the second profile, SVG Basic, is suitable for PDAs. Access the specification ...
Soap Messages with Attachments The W3C Note "SOAP Messages with Attachments" defines a binding for a SOAP 1.1 message to be carried within a MIME multipart/related message in such a way that the processing rules for the SOAP 1.1 message are preserved. The MIME multipart mechanism for encapsulation of compound documents can be used to bundle entities related to the SOAP 1.1 message such as attachments. Rules for the usage of URI references to refer to entities bundled within the MIME package are specified. Access the specification ...
Semantic Web Advanced Development Not actually a XML language nor a W3C Specification.
The Acronym summarizes some activities around the Semantic Web movements.More Information
Trading Partner Agreement Markup Language The Trading Partner Agreement Markup Language has been designed for governing electronic contracts. Developed by IBM, the tpaML specification uses XML to define and implement electronic contracts. The foundation of tpaML is the Trading Partner Agreement (TPA), which defines how trading partners will interact at the transport, document exchange and business protocol layers. A TPA contains the general contract terms and conditions, participant roles (buyers, sellers), communication and security protocols and business processes, (valid actions, sequencing rules, etc.). XML-based TPA documents capture the essential information upon which trading partners must agree in order for their applications and business processes to communicate. tpaML is a complementary technology to ebXML, the Electronic Business XML initiative, which is a joint effort of the United Nations/CEFACT and OASIS to establish a global framework for the exchange of electronic business data. Access the specification ...
Transformations for XML TRaX is the result of collaboration by many XSLT processor developers and is thus likely to be adopted quite quickly. This will allow developers to produce XSLT-based applications that are not tied to particular XSLT implementations, circumventing one significant problem with the current state of affairs.
In the meantime TRaX has been incorporated into SUN's JSR 63.More Information
Tree Regular Expressions for XML A TREX pattern specifies a pattern for the structure and content of an XML document. A TREX pattern thus identifies a class of XML documents consisting of those documents that match the pattern. A TREX pattern is itself an XML document.
TREX has been merged with RELAX to create RELAX NG. All future development of TREX will take place as part of the RELAX NG effort. Access the specification ...
Universal Description, Discovery and Integration Universal Description, Discovery and Integration (UDDI) is a specification for distributed Web-based information registries of Web services. UDDI is also a publicly accessible set of implementations of the specification that allow businesses to register information about the Web services they offer so that other businesses can find them. The core component of the UDDI project is the UDDI business registration, an XML file used to describe a business entity and its Web services. Conceptually, the information provided in a UDDI business registration consists of three components: white pages including address, contact, and known identifiers; yellow pages including industrial categorizations based on standard taxonomies; and green pages, the technical information about services that are exposed by the business. Green pages include references to specifications for Web services, as well as support for pointers to various file and URL based discovery mechanisms if required. Access the specification ...
Vector Markup Language VML is an application of Extensible Markup Language (XML) 1.0 which defines a format for the encoding of vector information together with additional markup to describe how that information may be displayed and edited. Access the specification ...
Web Distributed Data eXchange WDDX is an XML-based technology that enables the exchange of complex data between Web programming languages, creating what some refer to as Web syndicate networks. WDDX consists of a language-independent representation of data based on an XML 1.0 DTD, and a set of modules for a wide variety of languages that use WDDX. WDDX can be used with HTTP, SMTP, POP, FTP and other Internet protocols that support transferring textual data.More Information
Well-Defined Service A Well-Defined Service (WDS) document describes nonoperational service information, such as service category, service description, and expiration date, as well as business information about the service provider, such as company name, address, and contact information.
Web Interface Definition Language WIDL is a metalanguage that implements a service-based architecture over the document-based resources of the World Wide Web. WIDL is an application of the eXtensible Markup Language (XML); it allows interactions with Web servers to be defined as functional interfaces that can be accessed by remote systems over standard Web protocols, and provides the structure necessary for generating client code in languages such as Java, C/C++, COBOL, and Visual Basic. WIDL enables a practical and cost-effective means for diverse systems to be rapidly integrated across corporate intranets, extranets, and the Internet. Access the specification ...
Web Services Inspection Language WS-Inspection represents an XML format for assisting in the inspection of a site for available services and a set of rules for how inspection related information should be made available for consumption. A WS-Inspection document provides a means for aggregating references to pre-existing service description documents which have been authored in any number of formats. These inspection documents are then made available at the point-of-offering for the service as well as through references which may be placed within a content medium such as HTML. Access the specification ...
Web Services Referral Protocol WS-Referral is a protocol that enables the routing strategies used by SOAP nodes in a message path to be dynamically configured. SOAP itself provides a distributed processing model where SOAP messages can have content destined for specific processing nodes. WS-Routing adds to SOAP the capability of describing the actual message path. WS-Referral provides a mechanism to dynamically configure SOAP nodes in a message path to define how they should handle a SOAP message. It is a configuration protocol that enables SOAP nodes to delegate part or all of their processing responsibility to other SOAP nodes. Access the specification ...
Web Services Routing Protocol WS-Routing is a simple, stateless, SOAP-based protocol for routing SOAP messages in an asynchronous manner over a variety of transports like TCP, UDP, and HTTP. With WS-Routing, the entire message path for a SOAP message (as well as its return path) can be described directly within the SOAP envelope. It supports one-way messaging, two-way messaging such as request/response and peer-to-peer conversations, and long running dialogs. Access the specification ...
Web Services Security Language Microsoft's WS-Security describes additional mechanisms to SOAP messaging to provide message integrity, message confidentiality, and single message authentication. These mechanisms can be used to accommodate a wide variety of security models and encryption technologies. WS-Security also provides a general-purpose mechanism for associating security tokens with messages. No specific type of security token is required by WS-Security. It is designed to be extensible (e.g. support multiple security token formats). For example, a client might provide proof of identity and proof that they have a particular business certification. Access the specification ...
Web Services Conversation Language WSCL allows the abstract interfaces of Web services, i.e. the business level conversations or public processess supported by a Web service, to be defined. WSCL specifies the XML documents being exchanged, and the allowed sequencing of these document exchanges. WSCL conversation definitions are themselves XML documents and can therefore be interpreted by Web services infrastructures and edevelopment tools. WSCL may be used in conjunction with other service description languages like WSDL; for example, to provide protocol binding information for abstract interfaces, or to specify the abstract interfaces supported by a concrete service.Access the specification ... ... W3C WSCL Note ... UDDI Document
Web Services Component Model The Web Services Component Model (WSCM) represents an XML and web services centric component model for interactive web applications; WSCM is aimed to harmonize as far as practical with existing web application programming models, with the work of the W3C, emerging web services standards, and with the work of other appropriate business information bodies. The Oasis WSCM Technical Commitee's aim is to ensure that WSCM applications can be deployed on any tier on the network and remain target device and output markup neutral; and promote WSCM to the status of an international standard for the conduct of XML and Web Services based web application development, deployment and management. Access the specification ...
Web Services Description Language The W3C Note WSDL defines an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate, however, the only bindings described in this document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME. Access the specification ...
Web Services Flow Language The Web Services Flow Language (WSFL) is an XML language for the description of Web
Services compositions. WSFL considers two types of Web Services compositions: * The first type specifies the appropriate usage pattern of a collection of Web Services, in such a way that the resulting composition describes how to achieve a particular business goal; typically, the result is a description of a business process. * The second type specifies the interaction pattern of a collection of Web Services; in this case, the result is a description of the overall partner interactions. The guiding principle behind WSFL is to fit naturally into the Web Services computing stack. It is layered on top of the Web Services Description Language. Access the specification ...
Web Services Invocation Framework A tool that provides a standard API for invoking services described in Web Services Description Language (WSDL), no matter how or where the services are provided. The architecture allows new bindings to be added at run time.
WSIF currently provides developers with a standard interface for working with representations of any Web service as an alternative to working directly with a SOAP API. In the WSIF architecture, services are invoked by using WSDL documents. WSIF works with services regardless of how they were implemented or where they reside. Services may be invoked dynamically and without generating stubs.More Information
Web Service Meta Language A WSML file provides information that maps the operations of a service (as described in the WSDL file) to specific methods in the COM object. The WSML file determines which COM object to load to service the request for each operation.More Information
Web Services Experience Language WSXL (Web Services Experience Language) is a Web services centric component model for interactive Web applications, that is, for applications that provide a user experience across the Internet. WSXL is designed to achieve two main goals: enable businesses to deliver interactive Web applications through multiple distribution channels and enable new services or applications to be created by leveraging other interactive applications across the Web. To accomplish these goals, all WSXL component services implement a set of base operations for life cycle management, accepting user input, and producing presentation markup. More sophisticated WSXL component services may be specialized to represent data, presentation, and control. WSXL also introduces a new description language to guide the adaptation of user experience to new distribution channels. Access the specification ...
extensible Address Standard The vocabulary is part of OASIS's Customer Information Quality technical committee developing the xCRL language.More Information
XML Transaction Authority Markup Language The XAML initiative addresses coordinated processing of transaction-supporting web services between internal fulfillment services (the chemical provider's inventory system) and external services such as:
(1) An insurance policy service to insure the product being shipped; (2) A financing service to ensure payment according to vendor terms; (3) A transportation service to guarantee timely shipment/delivery of product; (4) A regulatory service to ensure compliance with government safety requirements.
extensible Customer Information Standard The vocabulary is part of OASIS's Customer Information Quality technical committee developing the xCRL language.More Information
extensible Customer Relationships Language The objective is to deliver XML standards for customer profile/information management to the industry.
A global customer standard is becoming a necessity in today's competitive global customer-centric business culture to understand customer data, maintain quality and integrity of customer data and to exchange/share customer information across systems, tools, databases and platforms. This helps in building successful Customer Information Systems such as Data Warehouses, Operational Data Marts, CRM/e-CRM, and Single/360 degree Customer View. The developed standards should provide a common format to represent your customer-centric information/data (eg. name and address data, relationships data, non-name and address customer-centric data such as e-mail, ID, URL, Tel. no., etc). These XML Standards are designed to be application independent, vendor neutral, open and importantly, "Global". The OASIS committee will not address the following: validation and verification of the customer data, privacy, permissioning, transportation, messaging, routing and security of the data. Many other standard groups worldwide are working on this. The language was formerly known as CRML and has been renamed by OASIS's QIC technical committee.More Information
XML Data Reduced The XML-Data submission contained many new ideas that an XML schema language could support. XDR refines and subsets those ideas down to a more manageable size in order to allow faster progress toward adopting a new schema language for XML. Some of the inconsistencies in the XML-Data submission are cleaned up, and some changes have been made based on comments received since the XML-Data submission was posted.
Note XDR also serves as abbreviation for the IETF External Data Representation Standard according to RFC 1014. Access the specification ...
XMethods Filesyste The XMethods filesystem service enables you to post and read files via a SOAP interface. This system enables developers to create services that utilize centralized, persistent data. Ideally, this type of filesystem can be used to centralize the storage of information which can be accessed by multiple nodes. For example, one could use this space to support automatic patch updates.More Information
Extensible HyperText Markup Language XHTML is the reformulation of HTML 4 as an application of XML. XHTML 1.0 specifies three XML document types that correspond to the three HTML 4 DTDs: Strict, Transitional, and Frameset. XHTML 1.0 is the basis for a family of document types that subset and extend HTML. XHTML 1.1 defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 that was brought forward into the XHTML 1.0 document types. This document type is essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. With the introduction of the XHTML family of modules and document types, the W3C has helped move the Internet content-development community from the days of malformed, non-standard markup into the well formed, valid world of XML. In XHTML 1.0, this move was moderated by a goal of providing for easy migration of existing, HTML 4 (or earlier) based content to XHTML and XML. With the advent of the XHTML modules defined in Modularization of XHTML, the W3C has removed support for deprecated elements and attributes from the XHTML family. These elements and attributes were largely presentation oriented functionality that is better handled via style sheets or client-specific default behavior. Going forward, XHTML family document types will be based upon this new, more structural functional collection. In this specification, the W3C's HTML Working Group has defined an initial document type based solely upon modules. This document type is designed to be portable to a broad collection of client devices, and applicable to the majority of Internet content. Content developers who base their content upon the functionality expressed in this specification can be confident that it will be consistently portable across XHTML family conforming user agents.Access the specification ... ... XHTML 1.1 ... XHTML 1.0 ... XHTML Basic ... XHTML Modularization
XML Inclusions Many programming languages provide an inclusion mechanism to facilitate modularity. Markup languages also often have need of such a mechanism. XML Inclusions represent a generic mechanism for merging XML documents (as represented by their information sets) for use by applications that need such a facility. The syntax leverages existing XML constructs - elements, attributes, and URI references. The XML Inclusion Specification defines a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite Infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references). Access the specification ...
XML Key Management Specification XKMS specifies protocols for distributing and registering public keys, suitable for use in conjunction with the proposed standard for XML Signature developed by the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF) and an anticipated companion standard for XML encryption. The XML Key Management Specification (XKMS) comprises two parts -- the XML Key Information Service Specification (X-KISS) and the XML Key Registration Service Specification (X-KRSS). Access the specification ...
Web Services for Business Process Design Automation of business processes based on web services requires a notation for the specification of message exchange behavior among participating web services. XLANG represents such a notation. It can serve as the basis for automated protocol engines that can track the state of process instances and help enforce protocol correctness in message flows. The building block standard that XLANG is most dependent on is WSDL. WSDL specifies a number of fundamental concepts that form the starting point for defining an XLANG service. XLANG has a two-fold relationship with WSDL. An XLANG service description is a WSDL service description with an extension element that describes the behavior of the service as a part of a business process. XLANG service behavior may also rely on simple WSDL services as providers of basic functionality for the implementation of the business process. Access the specification ...
XML Linking Language The XML Linking Language (XLink) allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links. The XLink set of characteristics is powerful, but the model that underlies them limits the range of possible hyperlink functionality. The model defined in this specification shares with HTML the use of URI technology, but goes beyond HTML in offering features, previously available only in dedicated hypermedia systems, that make hyperlinking more scalable and flexible. Along with providing linking data structures, XLink provides a minimal link behavior model; higher-level applications layered on XLink will often specify alternate or more sophisticated rendering and processing treatments.
Access the specification ...
XML Metadata Interchange The main purpose of XMI is to enable easy interchange of metadata between modeling tools (based on the OMG-UML) and metadata repositories (OMG-MOF based) in distributed heterogeneous environments. XMI integrates the three industry standards XML, UML and MOF. XMI supports the interchange of any kind of metadata that can be expressed using the MOF specification, including both model and metamodel information, whereas the encoding of metadata can consist of both complete models and model fragments, as well as tool-specific extension metadata. Access the specification ...
Extensible Markup Language The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML XML has been designed for ease of implementation and for interoperability with both SGML and HTML. Extensible Markup Language, abbreviated XML, describes a class of data objects called XML documents and partially describes the behavior of computer programs which process them. XML is an application profile or restricted form of SGML, the Standard Generalized Markup Language (ISO 8879). By construction, XML documents are conforming SGML documents. XML documents are made up of storage units called entities, which contain either parsed or unparsed data. Parsed data is made up of characters, some of which form character data, and some of which form markup. Markup encodes a description of the document's storage layout and logical structure. XML provides a mechanism to impose constraints on the storage layout and logical structure. Access the specification ...
XML Base The XML Linking Language XLink defines Extensible Markup Language (XML) 1.0 constructs to describe links between resources. One of the stated requirements on XLink is to support HTML linking constructs in a generic way. The HTML BASE element is one such construct which the XLink Working Group has considered. BASE allows authors to explicitly specify a document's base URI for the purpose of resolving relative URIs in links to external images, applets, form-processing programs, style sheets, and so on. The XML Base Specification describes a mechanism for providing base URI services to XLink, but as a modular specification so that other XML applications benefiting from additional control over relative URIs but not built upon XLink can also make use of it. The syntax consists of a single XML attribute named xml:base. The deployment of XML Base is through normative reference by new specifications, for example XLink and the XML Infoset. Applications and specifications built upon these new technologies will natively support XML Base. The behavior of xml:base attributes in applications based on specifications that do not have direct or indirect normative reference to XML Base is undefined. Access the specification ...
XML Encryption Syntax and Processing XML Encryption Syntax and Processing represents a process for encrypting data and representing the result in XML. The data may be arbitrary data (including an XML document), an XML element, or XML element content. The result of encrypting data is an XML Encryption EncryptedData element which contains (via one of its children's content) or identifies (via a URI reference) the cipher data. When encrypting an XML element or element content the EncryptedData element replaces the element or content (respectively) in the encrypted version of the XML document. When encrypting arbitrary data (including entire XML documents), the EncryptedData element may become the root of a new XML document or become a child element in an application-chosen XML document. Access the specification ...
XML Fragment Interchange The XML standard supports logical documents composed of possibly several entities. It may be desirable to view or edit one or more of the entities or parts of entities while having no interest, need, or ability to view or edit the entire document. The problem, then, is how to provide to a recipient of such a fragment the appropriate information about the context that fragment had in the larger document that is not available to the recipient. In the case of many XML documents, it is suboptimal to have to receive and parse the entire document when only a fragment of it is desired. If the user asked to look at chapter 20, one shouldn't need to parse 19 whole chapters before getting to the part of interest. XML Fragment Interchange defines a way to enable processing of small parts of an XML document without having to process everything up to the part in question. This can be done regardless of whether the parts are entities or not, and the parts can either be viewed immediately or accumulated for later use, assembly, or other processing. Access the specification ...
XML Remote Procedue Call Protocol XML-RPC is a Remote Procedure Calling protocol that works over the Internet.
An XML-RPC message is an HTTP-POST request. The body of the request is in XML. A procedure executes on the server and the value it returns is also formatted in XML. Procedure parameters can be scalars, numbers, strings, dates, etc.; and can also be complex record and list structures. Access the specification ...
The purpose of a schema is to define a class of XML documents, and so the term "instance document" is often used to describe an XML document that conforms to a particular schema. The schema language, which is itself represented in XML 1.0 and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML 1.0 document type definitions (DTDs). The XML Schema specification addresses several topics relevant to users of XML: * Primitive Data Typing * Structural Schemas * Conformance The XML Schema specification is provided in three parts: XML Schema Part 0: Primer is a non-normative document intended to provide an easily readable description of the XML Schema facilities, and is oriented towards quickly understanding how to create schemas using the XML Schema language. The purpose of XML Schema Part 1: Structures is to define the nature of XML schemas and their component parts, provide an inventory of XML markup constructs with which to represent schemas, and define the application of schemas to XML documents. XML Schema Part 2: Datatypes discusses datatypes that can be used in an XML Schema. Access the specification ... ... XML Schema Part 0: Primer ... XML Schema Part 1: Structures ... XML Schema Part 2: Datatypes
Associating Style Sheets with XML documents A style sheet can be associated with an XML document by including one or more processing instructions with a target of xml-stylesheet in the document's prolog. This processing instruction follows the behaviour of the HTML 4.0. The xml-stylesheet processing instruction is allowed only in the prolog of an XML document. The syntax of XML constrains where processing instructions are allowed in the prolog; the xml-stylesheet processing instruction is allowed anywhere in the prolog that meets these constraints.
The xml-stylesheet processing instruction is parsed in the same way as a start-tag, with the exception that entities other than predefined entities must not be referenced. Access the specification ...
XML Digital Signature The XML Signature is a method of associating a key with referenced data (octets). XML Signatures can be applied to arbitrary digital content (data objects), including XML, via an indirection. An XML Signature may be applied to the content of one or more resources. Data objects are digested, the resulting value is placed in an element (with other information) and that element is then digested and cryptographically signed.Access the specification ... ... at W3C ... at IETF
extensible Name and Address Standard The vocabulary is part of OASIS's Customer Information Quality technical committee developing the xCRL language.More Information
extensible Name Standard The vocabulary is part of OASIS's Customer Information Quality technical committee developing the xCRL language.More Information
XML Path Language XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer. XPath is the result of an effort to provide a common syntax and semantics for functionality shared between XSL Transformations (XSLT) and XPointer. The primary purpose of XPath is to address parts of an XML document. In support of this primary purpose, it also provides basic facilities for manipulation of strings, numbers and booleans. XPath uses a compact, non-XML syntax to facilitate use of XPath within URIs and XML attribute values. XPath operates on the abstract, logical structure of an XML document, rather than its surface syntax. XPath gets its name from its use of a path notation as in URLs for navigating through the hierarchical structure of an XML document. In addition to its use for addressing, XPath is also designed so that it has a natural subset that can be used for matching (testing whether or not a node matches a pattern); this use of XPath is described in XSLT. Access the specification ...
XML Pointer Language The XML Pointer Language (XPointer) represents the language to be used as the basis for a fragment identifier for any URI reference that locates a resource whose Internet media type is one of text/xml, application/xml, text/xml-external-parsed-entity, or application/xml-external-parsed-entity. XPointer, which is based on the XML Path Language (XPath), supports addressing into the internal structures of XML documents and external parsed entities. It allows for examination of a hierarchical document structure and choice of its internal parts based on various properties, such as element types, attribute values, character content, and relative position. Access the specification ...
Extensible Stylesheet Language XSL is a language for expressing stylesheets. Given a class of arbitrarily structured XML documents or data files, designers use an XSL stylesheet to express their intentions about how that structured content should be presented; that is, how the source content should be styled, laid out, and paginated onto some presentation medium, such as a window in a Web browser or a hand-held device, or a set of physical pages in a catalog, report, pamphlet, or book. Access the specification ...
XSL Formatting Objects XSL Formatting Objects represents an XML vocabulary for specifying formatting semantics. It is part of the W3C XSL Specification. Formatting is the process of turning the result of an XSL transformation into a tangible form for the reader or listener.
XSL-FO Processor: INPUT ---> |XSL Transformer| ---> |XSL Formatter| --->OUTPUT Access the specification ... ... XSL-FO Chapter within XSL Specification ... Complete XSL Specification
XSL Transformations XSLT is a language for transforming XML documents into other XML documents. A transformation expressed in XSLT describes rules for transforming a source tree into a result tree. The transformation is achieved by associating patterns with templates. A pattern is matched against elements in the source tree. A template is instantiated to create part of the result tree. The result tree is separate from the source tree. The structure of the result tree can be completely different from the structure of the source tree. In constructing the result tree, elements from the source tree can be filtered and reordered, and arbitrary structure can be added. A transformation expressed in XSLT is called a stylesheet. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. XSL specifies the styling of an XML document by using XSLT to describe how the document is transformed into another XML document that uses the formatting vocabulary. XSLT is also designed to be used independently of XSL. A transformation in the XSLT language is expressed as a well-formed XML document conforming to the Namespaces in XML Recommendation, which may include both elements that are defined by XSLT and elements that are not defined by XSLT. Access the specification ...
XML Topic Maps XTM provides a model and grammar for representing the structure of information resources used to define topics, and the associations (relationships) between topics. Names, resources, and relationships are said to be characteristics of abstract subjects, which are called topics. Topics have their characteristics within scopes: i.e. the limited contexts within which the names and resources are regarded as their name, resource, and relationship characteristics. One or more interrelated documents employing this grammar is called a topic map. Access the specification ...
