#Processed by Id: cwm.py,v 1.197 2007/12/13 15:38:39 syosi Exp # using base file:///home/roessler/WWW/2012/06/tr2adms/ # Notation3 generation by # notation3.py,v 1.200 2007/12/11 21:18:08 syosi Exp # Base was: file:///home/roessler/WWW/2012/06/tr2adms/ @prefix : . @prefix cat: . @prefix data: . @prefix radion: . @prefix rdfs: . @prefix xhv: . @prefix xsd: . a :SemanticAsset, :SemanticAssetDistribution; "1999-05-24"^^xsd:date; """ In characterizing the structure and content of the Web, it is necessary to establish precise semantics for Web concepts. The Web has proceeded for a surprisingly long time without consistent definitions for concepts which have become part of the common vernacular, such as "Web site" or "Web page". This can lead to a great deal of confusion when attempting to develop, interpret, and compare Web metrics. This document represents an effort on the part of the W3C Web Characterization Activity to establish a shared understanding of key Web concepts. The primary goal in preparing this document was to develop a common interpretation for terminology related to Web characterization research. However, it is hoped that the Web community at large will also benefit from the enumeration and definition of important Web concepts. """@en; ; cat:DocLicense; data:W3C; "Web Characterization Terminology & Definitions Sheet"; ; xhv:last ; rdfs:label "Web Characterization Terminology & Definitions Sheet"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-07-27"^^xsd:date; """In this note we describe a method for using RDF, the Resource Description Format of the W3C, to create a general, yet extensible framework for describing user preferences and device capabilities. This information can be provided by the user to servers and content providers. The servers can use this information describing the user's preferences to customize the service or content provided. The ability of RDF to reference profile information via URLs assists in minimizing the number of network transactions required to adapt content to a device, while the framework fits well into the current and future protocols being developed a the W3C and the WAP Forum."""@en; ; cat:DocLicense; data:W3C; "Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation"; ; xhv:last ; rdfs:label "Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-07-07"^^xsd:date; """This specification defines the Mathematical Markup Language, or MathML. 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 Web, just as HTML has enabled this functionality for text.This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document.This document begins with background information on mathematical notation, the problems it poses, and the philosophy underlying the solutions MathML proposes. MathML can be used to encode both mathematical notation and mathematical content. Twenty-eight of the MathML tags describe abstract notational structures, while another seventy-five provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of MathML entities (extended characters) and their relation to fonts.While MathML is human-readable it is anticipated that, in all but the simplest cases, authors will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several early versions of such MathML tools already exist, and a number of others, both freely available software and commercial products, are under development."""@en; ; cat:DocLicense; data:W3C; "Mathematical Markup Language (MathML) 1.01 Specification"; ; xhv:last ; rdfs:label "Mathematical Markup Language (MathML) 1.01 Specification"; :accessURL ; :status ; radion:distribution . cat:DocLicense a ; rdfs:label "W3C Document License"@en; . a :SemanticAsset, :SemanticAssetDistribution; "1996-06-02"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "A Proposed Convention for Embedding Metadata in HTML"; ; xhv:last ; rdfs:label "A Proposed Convention for Embedding Metadata in HTML"; :accessURL ; :status ; radion:distribution . a :SemanticAssetRepository; "1996-03-07"^^xsd:date; "All standards and drafts published by the World Wide Web Consotrium (W3C)"@en; data:W3C; "W3C Standards and Technical Reports"@en; rdfs:label "W3C Standards and Technical Reports"@en . a :SemanticAsset, :SemanticAssetDistribution; "1998-12-10"^^xsd:date; """ This Note attempts to document all the features that have been suggested for CSS, and that are not part of CSS2. The fact that a feature has been listed here does not mean it will be in some future version of CSS; some of the suggestions do not fit in CSS or are better handled elsewhere (e.g., in HTML, SMIL, or RDF). The purpose of the list is to make sure suggestions are neither forgotten nor suggested over and over again. Many suggestions are just listed without further comment. If the CSS working group has discussed a feature, some remarks may be added. Comments on this draft are welcome and should be sent to the www-style@w3.org mailing list (recommended) or the CSS & FP WG (only for W3C members), or to the editors if neither of the above is suitable. Please, give feedback before the 5th of February 1999. """@en; ; cat:DocLicense; data:W3C; "List of suggested extensions to CSS"; ; xhv:last ; rdfs:label "List of suggested extensions to CSS"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-07-10"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Design of HTTP-ng Testbed"; ; xhv:last ; rdfs:label "Design of HTTP-ng Testbed"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-03-24"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "P3P Protocol and Data Transport Working Group Draft White Paper"; ; xhv:last ; rdfs:label "P3P Protocol and Data Transport Working Group Draft White Paper"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-07-21"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "P3P Guiding Principles"; ; xhv:last ; rdfs:label "P3P Guiding Principles"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-11-23"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XML Fragment Interchange Requirements, Version 1.0"; ; xhv:last ; rdfs:label "XML Fragment Interchange Requirements, Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-03-13"^^xsd:date; """ In HTML elements, the lang attribute specifies the natural language. This document is mostly concerned with how to specify the primary language(s) (there could be more than one) and the base language (there is only one) in HTML documents. """@en; ; cat:DocLicense; data:W3C; "Primary Language in HTML"; ; xhv:last ; rdfs:label "Primary Language in HTML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-08-04"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "A Discussion of the Relationship Between RDF-Schema and UML"; ; xhv:last ; rdfs:label "A Discussion of the Relationship Between RDF-Schema and UML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-01-28"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Voice Browsers"; ; xhv:last ; rdfs:label "Voice Browsers"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-05-11"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XML in HTML Meeting Report"; ; xhv:last ; rdfs:label "XML in HTML Meeting Report"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-03-03"^^xsd:date; """ This document explicates the design principles behind the XLink language and its related XPointer language. XML Linking Language (XLink) Design Principles Version 1.0 """@en; ; cat:DocLicense; data:W3C; "XML Linking Language (XLink) Design Principles"; ; xhv:last ; rdfs:label "XML Linking Language (XLink) Design Principles"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-10-01"^^xsd:date; """ This specification defines the Document Object Model Level 1, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model provides a standard set of objects for representing HTML and XML documents, a standard model of how these objects can be combined, and a standard interface for accessing and manipulating them. Vendors can support the DOM as an interface to their proprietary data structures and APIs, and content authors can write to the standard DOM interfaces rather than product-specific APIs, thus increasing interoperability on the Web. The goal of the DOM specification is to define a programmatic interface for XML and HTML. The DOM Level 1 specification is separated into two parts: Core and HTML. The Core DOM Level 1 section provides a low-level set of fundamental interfaces that can represent any structured document, as well as defining extended interfaces for representing an XML document. These extended XML interfaces need not be implemented by a DOM implementation that only provides access to HTML documents; all of the fundamental interfaces in the Core section must be implemented. A compliant DOM implementation that implements the extended XML interfaces is required to also implement the fundamental Core interfaces, but not the HTML interfaces. The HTML Level 1 section provides additional, higher-level interfaces that are used with the fundamental interfaces defined in the Core Level 1 section to provide a more convenient view of an HTML document. A compliant implementation of the HTML DOM implements all of the fundamental Core interfaces as well as the HTML interfaces. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 1"; ; xhv:last ; rdfs:label "Document Object Model (DOM) Level 1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-04-07"^^xsd:date; """ This specification defines the Mathematical Markup Language, or MathML. 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 Web, just as HTML has enabled this functionality for text. This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document. This document begins with background information on mathematical notation, the problems it poses, and the philosophy underlying the solutions MathML proposes. MathML can be used to encode both mathematical notation and mathematical content. Twenty-eight of the MathML tags describe abstract notational structures, while another seventy-five provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of MathML entities (extended characters) and their relation to fonts. While MathML is human-readable it is anticipated that, in all but the simplest cases, authors will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several early versions of such MathML tools already exist, and a number of others, both freely available software and commercial products, are under development. """@en; ; cat:DocLicense; data:W3C; "Mathematical Markup Language (MathML) 1.0 Specification"; ; xhv:last ; rdfs:label "Mathematical Markup Language (MathML) 1.0 Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-04-24"^^xsd:date; """ This specification defines the HyperText Markup Language (HTML), version 4.0, the publishing language of the World Wide Web. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML, HTML 4.0 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4.0 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4.0 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879]. """@en; ; cat:DocLicense; data:W3C; "HTML 4.0 Specification"; ; xhv:last ; rdfs:label "HTML 4.0 Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-06-15"^^xsd:date; """ This document specifies version 1 of the Synchronized Multimedia Integration Language (SMIL 1.0, pronounced "smile"). SMIL allows integrating a set of independent multimedia objects into a synchronized multimedia presentation. Using SMIL, an author can describe the temporal behavior of the presentationdescribe the layout of the presentation on a screenassociate hyperlinks with media objects This specification is structured as follows: Section 1 presents the specification approach. Section 2 defines the "smil" element. Section 3 defines the elements that can be contained in the head part of a SMIL document. Section 4 defines the elements that can be contained in the body part of a SMIL document. In particular, this Section defines the time model used in SMIL. Section 5 describes the SMIL DTD. """@en; ; cat:DocLicense; data:W3C; "Synchronized Multimedia Integration Language (SMIL) 1.0 Specification"; ; xhv:last ; rdfs:label "Synchronized Multimedia Integration Language (SMIL) 1.0 Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-02-10"^^xsd:date; """ 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. """@en; ; cat:DocLicense; data:W3C; "XML 1.0 Recommendation"; ; xhv:last ; rdfs:label "XML 1.0 Recommendation"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-07-10"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "HTTP-ng Architectural Model"; ; xhv:last ; rdfs:label "HTTP-ng Architectural Model"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-03-27"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Short- and Long-Term Goals for the HTTP-NG Project"; ; xhv:last ; rdfs:label "Short- and Long-Term Goals for the HTTP-NG Project"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-07-10"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "HTTP-ng Web Interfaces"; ; xhv:last ; rdfs:label "HTTP-ng Web Interfaces"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-07-10"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "HTTP-ng Binary Wire Protocol"; ; xhv:last ; rdfs:label "HTTP-ng Binary Wire Protocol"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-10-29"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Scalable Vector Graphics (SVG) Requirements"; ; xhv:last ; rdfs:label "Scalable Vector Graphics (SVG) Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-05-11"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XSL Requirements Summary"; ; xhv:last ; rdfs:label "XSL Requirements Summary"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1998-07-10"^^xsd:date; """ This document defines the experimental multiplexing protocol referred to as "SMUX". SMUX is a session management protocol separating the underlying transport from the upper level application protocols. It provides a lightweight communication channel to the application layer by multiplexing data streams on top of a reliable stream oriented transport. By supporting coexistence of multiple application level protocols (e.g. HTTP and HTTP/NG), SMUX should ease transitions to future Web protocols, and communications of client applets using private protocols with servers over the same TCP connection as the HTTP conversation. """@en; ; cat:DocLicense; data:W3C; "SMUX Protocol Specification"; ; xhv:last ; rdfs:label "SMUX Protocol Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-02-23"^^xsd:date; """This document describes a proposed modularization of synchronized multimedia functionality, based upon the SMIL 1.0 Recommendation. The proposed modules complement HTML/CSS modules to support the definition of multimedia profiles that combine SYMM and HTML/CSS modules, as well as other XML-based languages. A set of example profiles for multimedia use is described. The document is intended to form a basis for work by a future SYMM Working Group."""@en; ; cat:DocLicense; data:W3C; "Synchronized Multimedia Modules based upon SMIL 1.0"; ; xhv:last ; rdfs:label "Synchronized Multimedia Modules based upon SMIL 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-10-21"^^xsd:date; """ This document is an informational document and discusses the requirements posed to URI schemes for identifying resources in Television (TV) Broadcast environments. The document is the outcome of discussions on this subject by the W3C TV-Web Interest Group [TVWebIG, TVWebMail]. Typical use cases are summarized where TV Broadcast URIs are involved. A distinction is made between Global and Local usage. Also, a hierarchy of resource types is identified. Requirements related to the Global usage case are listed. """@en; ; cat:DocLicense; data:W3C; "TV Broadcast URI Schemes Requirements"; ; xhv:last ; rdfs:label "TV Broadcast URI Schemes Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-03-19"^^xsd:date; """ This document describes the experiences and results that came out of the Web Characterization Group as part of the W3C HTTP-NG Activity, and how that work is now continued in the Web Characterization Activity. The HTTP-NG Working Group created a series of scenarios for the HTTP-NG protocol design group, which were implemented in the scope of the HTTP-NG testbed, and used to optimize its design. The WCA started in November 1998, and will bring that work model to a wider audience. """@en; ; cat:DocLicense; data:W3C; "Web Characterization: From working group to activity"; ; xhv:last ; rdfs:label "Web Characterization: From working group to activity"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-03-15"^^xsd:date; """This document describes guidelines for content authors how to create HTML 4.0 contents to be acceptable to mobile devices as much as possible."""@en; ; cat:DocLicense; data:W3C; "HTML 4.0 Guidelines for Mobile Access"; ; xhv:last ; rdfs:label "HTML 4.0 Guidelines for Mobile Access"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-10-07"^^xsd:date; """ This document is a report of the results of a meeting of a group of W3C Members involved in XML and RDF to advance the general understanding of a unified approach to the expression of Web data models. This document is one response to the Web data architecture discussed in "Web Architecture: Describing and Exchanging Data". """@en; ; cat:DocLicense; data:W3C; "The Cambridge Communiqué"; ; xhv:last ; rdfs:label "The Cambridge Communiqué"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-02-24"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XML XLink Requirements Version 1.0"; ; xhv:last ; rdfs:label "XML XLink Requirements Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-06-05"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XML Canonicalization Requirements"; ; xhv:last ; rdfs:label "XML Canonicalization Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-02-18"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XML Information Set Requirements"; ; xhv:last ; rdfs:label "XML Information Set Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-02-15"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XML Schema Requirements"; ; xhv:last ; rdfs:label "XML Schema Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-02-24"^^xsd:date; """ This document is a liaison statement from XML Linking Working Group to the XML Information Set working group. Because the XPointer specification under development in the XML Linking WG must refer to structural parts of XML documents, the structure it addresses must be explicit. Document structure specifications such as DOM and the XML Information Set may wish to consider the XPointer requirements in order to insure interoperability when used with XPointer and XLink. Thus we have set out in this document, some constraints we believe XPointer has, for its use with a system representing XML information structures. """@en; ; cat:DocLicense; data:W3C; "XPointer-Information Set Liaison Statement Version 1.0"; ; xhv:last ; rdfs:label "XPointer-Information Set Liaison Statement Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-02-24"^^xsd:date; """This document presents requirements for the XPointer language. XPointer provides ways to directly identify any node, data, or selection in any XML document by describing its structure and context. An identified data location is called a "target." The XPointer specification is particularly meant to enable hyperlinks to identify any such data, regardless of whether there is (or even could be) an ID on the target or not. The XPointer specification is now being developed in the XML-Linking Working Group, building on Working Drafts developed in the XML Working Group.Because the XPointer language must refer to structural parts of XML documents, those structures must be explicit. Document structure specifications such as DOM and the XML Information Set may wish to consider the XPointer requirements in order to insure interoperability when used with XPointer and XLink."""@en; ; cat:DocLicense; data:W3C; "XML XPointer Requirements Version 1.0"; ; xhv:last ; rdfs:label "XML XPointer Requirements Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-01-21"^^xsd:date; """ CGM (Computer Graphics Metafile) has been an ISO standard for vector and composite vector/raster picture definition since 1987. It has been a registered MIME type since 1995. CGM has a significant following in technical illustration, electronic documentation, geophysical data visualization, amongst other application areas. WebCGM is a profile for the effective application of CGM in Web electronic documents. WebCGM has been a joint effort of the CGM Open Consortium, in collaboration with W3C staff and supported by the European Commission Esprit project. It represents an important interoperability agreement amongst major users and implementors of CGM, and thereby unifies current diverse approaches to CGM utilization in Web document applications. WebCGM's clear and unambiguous conformance requirements will enhance interoperability of implementations, and it should be possible to leverage existing CGM validation tools, test suites, and the product certification testing services for application to WebCGM . While WebCGM is a binary file format and is not "stylable", nevertheless WebCGM follows published W3C requirements for a scalable graphics format where such are applicable. The design criteria for the graphical content of WebCGM aimed at a balance between graphical expressive power on the one hand, and simplicity and implementability on the other. A small but powerful set of metadata elements is standardized in WebCGM, to support the functionalities of: hyperlinking and document navigation; picture structuring and layering; and, search and query on WebCGM picture content. """@en; ; cat:DocLicense; data:W3C; "WebCGM Profile Recommendation"; ; xhv:last ; rdfs:label "WebCGM Profile Recommendation"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-12-24"^^xsd:date; """ This specification defines the HyperText Markup Language (HTML), the publishing language of the World Wide Web. This specification defines HTML 4.01, which is a subversion of HTML 4. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML (HTML 3.2 [HTML32] and HTML 2.0 [RFC1866]), HTML 4 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879]. """@en; ; cat:DocLicense; data:W3C; "HTML 4.01 Specification"; ; xhv:last ; rdfs:label "HTML 4.01 Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-02-22"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Resource Description Framework (RDF) Model and Syntax Specification"; ; xhv:last ; rdfs:label "Resource Description Framework (RDF) Model and Syntax Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-01-14"^^xsd:date; """ XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references. """@en; ; cat:DocLicense; data:W3C; "Namespaces in XML"; ; xhv:last ; rdfs:label "Namespaces in XML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-11-16"^^xsd:date; """ XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer. """@en; ; cat:DocLicense; data:W3C; "XML Path Language (XPath) Version 1.0"; ; xhv:last ; rdfs:label "XML Path Language (XPath) Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-11-16"^^xsd:date; """ This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. 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. However, XSLT is not intended as a completely general-purpose XML transformation language. Rather it is designed primarily for the kinds of transformations that are needed when XSLT is used as part of XSL. """@en; ; cat:DocLicense; data:W3C; "XSL Transformations (XSLT) Version 1.0"; ; xhv:last ; rdfs:label "XSL Transformations (XSLT) Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-05-05"^^xsd:date; """These guidelines explain how to make Web content accessible to people with disabilities. The guidelines are intended for all Web content developers (page authors and site designers) and for developers of authoring tools. The primary goal of these guidelines is to promote accessibility. However, following them will also make Web content more available to all users, whatever user agent they are using (e.g., desktop browser, voice browser, mobile phone, automobile-based personal computer, etc.) or constraints they may be operating under (e.g., noisy surroundings, under- or over-illuminated rooms, in a hands-free environment, etc.). Following these guidelines will also help people find information on the Web more quickly. These guidelines do not discourage content developers from using images, video, etc., but rather explain how to make multimedia content more accessible to a wide audience.This is a reference document for accessibility principles and design ideas. Some of the strategies discussed in this document address certain Web internationalization and mobile access concerns. However, this document focuses on accessibility and does not fully address the related concerns of other W3C Activities. Please consult the W3C Mobile Access Activity home page and the W3C Internationalization Activity home page for more information.This document is meant to be stable and therefore does not provide specific information about browser support for different technologies as that information changes rapidly. Instead, the Web Accessibility Initiative (WAI) Web site provides such information (refer to [WAI-UA-SUPPORT]).This document includes an appendix that organizes all of the checkpoints by topic and priority. The checkpoints in the appendix link to their definitions in the current document. The topics identified in the appendix include images, multimedia, tables, frames, forms, and scripts. The appendix is available as either a tabular summary of checkpoints or as a simple list of checkpoints.A separate document, entitled "Techniques for Web Content Accessibility Guidelines 1.0" ([TECHNIQUES]), explains how to implement the checkpoints defined in the current document. The Techniques Document discusses each checkpoint in more detail and provides examples using the Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), Synchronized Multimedia Integration Language (SMIL), and the Mathematical Markup Language (MathML). The Techniques Document also includes techniques for document validation and testing, and an index of HTML elements and attributes (and which techniques use them). The Techniques Document has been designed to track changes in technology and is expected to be updated more frequently than the current document. Note. Not all browsers or multimedia tools may support the features described in the guidelines. In particular, new features of HTML 4.0 or CSS 1 or CSS 2 may not be supported."Web Content Accessibility Guidelines 1.0" is part of a series of accessibility guidelines published by the Web Accessibility Initiative. The series also includes User Agent Accessibility Guidelines ([WAI-USERAGENT]) and Authoring Tool Accessibility Guidelines ([WAI-AUTOOLS])."""@en; ; cat:DocLicense; data:W3C; "Web Content Accessibility Guidelines 1.0"; ; xhv:last ; rdfs:label "Web Content Accessibility Guidelines 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-08-25"^^xsd:date; """This specification provides an extensible way to embed in a Web page all the information necessary to initialize a micropayment (amounts and currencies, payment systems, etc). This embedding allows different micropayment electronic wallets to coexist in a interoperable manner."""@en; ; cat:DocLicense; data:W3C; "Common Markup for micropayment per-fee-links"; ; xhv:last ; rdfs:label "Common Markup for micropayment per-fee-links"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-09-02"^^xsd:date; """This document describes style sheet properties for rendering Web documents as synthesized speech. Using style sheets rather than HTML tag extensions allows the same document to be read with visual, aural, or mulitmodal presentation without cluttering up the document or having to produce three (or more) separate parallel documents - which has been shown to result in consistency and update problems. This approach provides greatly improved document accessibility for visually disabled people (the information is better presented and is just as up-to-date as the visual version) without requiring compromises in the visual design of the document."""@en; ; cat:DocLicense; data:W3C; "Aural Cascading Style Sheets (ACSS) Specification"; ; xhv:last ; rdfs:label "Aural Cascading Style Sheets (ACSS) Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-09-02"^^xsd:date; """This specification extends the font mechanisms in CSS1 to define a new 'at-rule', @font-face which permits improved client-side matching of fonts, enables font synthesis and progressive rendering, and enables fonts to be downloaded over the Web. This provides greater typographic richness for HTML pages and improves the internationalisation of the Web."""@en; ; cat:DocLicense; data:W3C; "Web Fonts"; ; xhv:last ; rdfs:label "Web Fonts"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-09-02"^^xsd:date; """The HyperText Markup Language (HTML) is a simple markup language used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of applications. CSS (Cascading Style Sheets) is a style sheets language that can be applied to HTML to control the style of a document: which fonts and colors to use, how much white space to insert, etc. The following specification extends CSS to support the positioning and visibility of HTML elements in three-dimensional space. Familiarity with both CSS1 and HTML 3.2 are assumed."""@en; ; cat:DocLicense; data:W3C; "Positioning HTML Elements with Cascading Style Sheets"; ; xhv:last ; rdfs:label "Positioning HTML Elements with Cascading Style Sheets"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-09-02"^^xsd:date; """This specification describes a set of extensions to Cascading Style Sheets (CSS) to better support printing from the Web. These extensions let style sheets express page breaks, page boxes, and media dependencies. Also, a way to point to an alternate print document is described. This is a first pass at a rather formidable problem, but one which can yield good results in the near term."""@en; ; cat:DocLicense; data:W3C; "CSS Printing Extensions"; ; xhv:last ; rdfs:label "CSS Printing Extensions"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-12-23"^^xsd:date; """ The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirements studies for voice browsers, and provides a model architecture for processing speech within voice browsers. """@en; ; cat:DocLicense; data:W3C; "Model Architecture for Voice Browser Systems"; ; xhv:last ; rdfs:label "Model Architecture for Voice Browser Systems"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-12-23"^^xsd:date; """ The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirements studies for voice browsers, and provides details of the requirements for marking up spoken dialogs. """@en; ; cat:DocLicense; data:W3C; "Dialog Requirements for Voice Markup Languages"; ; xhv:last ; rdfs:label "Dialog Requirements for Voice Markup Languages"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-12-23"^^xsd:date; """ The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirements studies for voice browsers, and provides details of the requirements for grammars for speech recognition. """@en; ; cat:DocLicense; data:W3C; "Grammar Representation Requirements for Voice Markup Languages"; ; xhv:last ; rdfs:label "Grammar Representation Requirements for Voice Markup Languages"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-12-23"^^xsd:date; """ The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirements studies for voice browsers, and provides details of the requirements for natural language processing. """@en; ; cat:DocLicense; data:W3C; "Natural Language Processing Requirements for Voice Markup Languages"; ; xhv:last ; rdfs:label "Natural Language Processing Requirements for Voice Markup Languages"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-12-23"^^xsd:date; """ The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirements studies for voice browsers, and provides details of the requirements for markup used for speech synthesis. """@en; ; cat:DocLicense; data:W3C; "Speech Synthesis Markup Requirements for Voice Markup Languages"; ; xhv:last ; rdfs:label "Speech Synthesis Markup Requirements for Voice Markup Languages"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-09-06"^^xsd:date; """The increasing disparities between the capabilities of different kinds of Web user agents present challenges to Web content developers wishing to reach a wide audience. A promising approach is to formally describe profiles for documents intended for broad groups of user agents, for instance, separate document profiles for user agents running on desktops, television, handhelds, cellphones and voice user agents. Document profiles provide a basis for interoperability guarantees. If an author develops content for a given profile and a user agent supports the profile then the author may be confident that the document will be rendered as expected. The requirements for document profiles are analyzed."""@en; ; cat:DocLicense; data:W3C; "XHTML™ Document Profile Requirements"; ; xhv:last ; rdfs:label "XHTML™ Document Profile Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "1999-10-14"^^xsd:date; """ This document lists the design principles, scope, and requirements for the XML Digital Signature specification. It includes requirements as they relate to the signature syntax, data model, format, cryptographic processing, and external requirements and coordination. """@en; ; cat:DocLicense; data:W3C; "XML-Signature Requirements"; ; xhv:last ; rdfs:label "XML-Signature Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-01-07"^^xsd:date; """ This document describes the current W3C activities related to Electronic Commerce for the purpose of assessing the Consortium's future role in ecommerce-related work. It presents the work within the W3C Electronic Commerce Activity and across all W3C Activities which are directly related to Electronic Commerce. We expect this paper to serve as the basis for a discussion of W3C's role in ecommerce arena and, in particular, the future of the Electronic Commerce Interest Group. """@en; ; cat:DocLicense; data:W3C; "W3C and Electronic Commerce"; ; xhv:last ; rdfs:label "W3C and Electronic Commerce"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-06"^^xsd:date; """This document describes techniques for authoring accessible content that apply across technologies. It is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author Web content that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS]."""@en; ; cat:DocLicense; data:W3C; "Core Techniques for Web Content Accessibility Guidelines 1.0"; ; xhv:last ; rdfs:label "Core Techniques for Web Content Accessibility Guidelines 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-06"^^xsd:date; """This document describes techniques for authoring accessible Cascading Style Sheets (CSS). Cascading Style Sheets are defined by the W3C Recommendations "CSS Level 1" [CSS1] and "CSS Level 2" [CSS2]. This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author CSS that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS].Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. The deprecated examples are highlighted and readers should approach them with caution -- they are meant for illustrative purposes only."""@en; ; cat:DocLicense; data:W3C; "CSS Techniques for Web Content Accessibility Guidelines 1.0"; ; xhv:last ; rdfs:label "CSS Techniques for Web Content Accessibility Guidelines 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-06"^^xsd:date; """This document describes techniques for authoring accessible Hypertext Markup Language (HTML) content (refer to HTML 4.01 [HTML4]). This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author HTML that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS].Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. The deprecated examples are highlighted and readers should approach them with caution -- they are meant for illustrative purposes only."""@en; ; cat:DocLicense; data:W3C; "HTML Techniques for Web Content Accessibility Guidelines 1.0"; ; xhv:last ; rdfs:label "HTML Techniques for Web Content Accessibility Guidelines 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-06"^^xsd:date; """This document is the gateway to a series of related documents that provide techniques for satisfying the requirements defined in "Web Content Accessibility Guidelines 1.0" [WCAG10]. This series includes:"Techniques for Web Content Accessibility Guidelines 1.0", the current document, which is the gateway to the other documents."Core Techniques for Web Content Accessibility Guidelines 1.0" ([WCAG10-CORE-TECHNIQUES]), which discusses the accessibility themes and general techniques that apply across technologies (e.g., validation, testing, etc.)."HTML Techniques for Web Content Accessibility Guidelines 1.0" ([WCAG10-HTML-TECHNIQUES]), which provides examples and strategies for authoring accessible Hypertext Markup Language (HTML) content."CSS Techniques for Web Content Accessibility Guidelines 1.0" ([WCAG10-CSS-TECHNIQUES]), which provides examples and strategies to help authors write Cascading Style Sheets (CSS) as part of accessible content design."""@en; ; cat:DocLicense; data:W3C; "Techniques for Web Content Accessibility Guidelines 1.0"; ; xhv:last ; rdfs:label "Techniques for Web Content Accessibility Guidelines 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-08"^^xsd:date; """The HTML Working Group is chartered with the development of an extensible, sub-settable version of HTML that is compatible with XML. It is also chartered with the development of some extensions to HTML - notably in the area of forms. This group's current activities commenced in August 1998, and the group was rechartered in June 2000. The purpose of this document is to describe the activities of the HTML Working Group, define general milestones for each sub-project, and outline the inter-dependencies among the various deliverables."""@en; ; cat:DocLicense; data:W3C; "HTML Working Group Roadmap"; ; xhv:last ; rdfs:label "HTML Working Group Roadmap"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-09-29"^^xsd:date; """ Both XLink [XLink] and RDF [RDF] provide a way of asserting relations between resources. RDF is primarily for describing resources and their relations, while XLink is primarily for specifying and traversing hyperlinks. However, the overlap between the two is sufficient that a mapping from XLink links to statements in an RDF model can be defined. Such a mapping allows XLink elements to be harvested as a source of RDF statements. XLink links (hereafter, "links") thus provide an alternate syntax for RDF information that may be useful in some situations. This Note specifies such a mapping, so that links can be harvested and RDF statements generated. The purpose of this harvesting is to create RDF models that, in some sense, represent the intent of the XML document. The purpose is not to represent the XLink structure in enough detail that a set of links could be round-tripped through an RDF model. """@en; ; cat:DocLicense; data:W3C; "Harvesting RDF Statements from XLinks"; ; xhv:last ; rdfs:label "Harvesting RDF Statements from XLinks"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-02-03"^^xsd:date; """This specification provides guidelines for Web authoring tool developers. Its purpose is two-fold: to assist developers in designing authoring tools that produce accessible Web content and to assist developers in creating an accessible authoring interface.Authoring tools can enable, encourage, and assist users ("authors") in the creation of accessible Web content through prompts, alerts, checking and repair functions, help files and automated tools. It is just as important that all people be able to author content as it is for all people to have access to it. The tools used to create this information must therefore be accessible themselves. Adoption of these guidelines will contribute to the proliferation of Web content that can be read by a broader range of readers and authoring tools that can be used by a broader range of authors.This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI)."""@en; ; cat:DocLicense; data:W3C; "Authoring Tool Accessibility Guidelines 1.0"; ; xhv:last ; rdfs:label "Authoring Tool Accessibility Guidelines 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-13"^^xsd:date; """ This specification defines the Document Object Model Level 2 Core, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content and structure of documents. The Document Object Model Level 2 Core builds on the Document Object Model Level 1 Core. The DOM Level 2 Core is made of a set of core interfaces to create and manipulate the structure and contents of a document. The Core also contains specialized interfaces dedicated to XML. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 2 Core Specification"; ; xhv:last ; rdfs:label "Document Object Model (DOM) Level 2 Core Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-13"^^xsd:date; """ This specification defines the Document Object Model Level 2 Events, a platform- and language-neutral interface that gives to programs and scripts a generic event system. The Document Object Model Level 2 Events builds on the Document Object Model Level 2 Core [DOM Level 2 Core] and on Document Object Model Level 2 Views [DOM Level 2 Views]. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 2 Events Specification"; ; xhv:last ; rdfs:label "Document Object Model (DOM) Level 2 Events Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-13"^^xsd:date; """ This specification defines the Document Object Model Level 2 Style Sheets and Cascading Style Sheets (CSS), a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content and of style sheets documents. The Document Object Model Level 2 Style builds on the Document Object Model Level 2 Core [DOM Level 2 Core] and on the Document Object Model Level 2 Views [DOM Level 2 Views]. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 2 Style Specification"; ; xhv:last ; rdfs:label "Document Object Model (DOM) Level 2 Style Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-13"^^xsd:date; """ This specification defines the Document Object Model Level 2 Traversal and Range, platform- and language-neutral interfaces that allow programs and scripts to dynamically traverse and identify a range of content in a document. The Document Object Model Level 2 Traversal and Range build on the Document Object Model Level 2 Core [DOM Level 2 Core]. The DOM Level 2 Traversal and Range specification is composed of two modules. The two modules contain specialized interfaces dedicated to traversing the document structure and identifying and manipulating a range in a document. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 2 Traversal and Range Specification"; ; xhv:last ; rdfs:label "Document Object Model (DOM) Level 2 Traversal and Range Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-13"^^xsd:date; """ This specification defines the Document Object Model Level 2 Views, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content of a representation of a document. The Document Object Model Level 2 Views builds on the Document Object Model Level 2 Core [DOM Level 2 Core]. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 2 Views Specification"; ; xhv:last ; rdfs:label "Document Object Model (DOM) Level 2 Views Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-12-19"^^xsd:date; """The XHTML Basic document type includes the minimal set of modules required to be an XHTML host language document type, and in addition it includes images, forms, basic tables, and object support. It is designed for Web clients that do not support the full set of XHTML features; for example, Web clients such as mobile phones, PDAs, pagers, and settop boxes. The document type is rich enough for content authoring.XHTML Basic is designed as a common base that may be extended. For example, an event module that is more generic than the traditional HTML 4 event system could be added or it could be extended by additional modules from XHTML Modularization such as the Scripting Module. The goal of XHTML Basic is to serve as a common language supported by various kinds of user agents.The document type definition is implemented using XHTML modules as defined in "Modularization of XHTML" [XHTMLMOD]."""@en; ; cat:DocLicense; data:W3C; "XHTML™ Basic"; ; xhv:last ; rdfs:label "XHTML™ Basic"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-01-26"^^xsd:date; """This specification defines XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines."""@en; ; cat:DocLicense; data:W3C; "XHTML™ 1.0: The Extensible HyperText Markup Language - A Reformulation of HTML 4 in XML 1.0"; ; xhv:last ; rdfs:label "XHTML™ 1.0: The Extensible HyperText Markup Language - A Reformulation of HTML 4 in XML 1.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-10-06"^^xsd:date; """ 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. """@en; ; cat:DocLicense; data:W3C; "Extensible Markup Language (XML) 1.0 (Second Edition)"; ; xhv:last ; rdfs:label "Extensible Markup Language (XML) 1.0 (Second Edition)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-04-26"^^xsd:date; """ This document describes techniques that Web accessibility validation tools may use to evaluate the conformance of HTML documents to the Web Content Accessibility Guidelines 1.0 (WCAG 1.0). This document also describes techniques that Web authoring tools may use to help authors modify HTML documents to conform to WCAG 1.0. We anticipate that tool developers may develop accessibility validation and/or repair modules to be incorporated into commercial authoring tools, validation tools, and perhaps user agents. """@en; ; cat:DocLicense; data:W3C; "Techniques For Accessibility Evaluation And Repair Tools"; ; xhv:last ; rdfs:label "Techniques For Accessibility Evaluation And Repair Tools"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-07-21"^^xsd:date; """ This document outlines the requirements for a CC/PP framework, vocabulary, and trust model, and provides an overview of an architecture that satisfies these requirements. It represents the current consensus of the working group. """@en; ; cat:DocLicense; data:W3C; "Composite Capabilities/Preference Profiles: Requirements and Architecture"; ; xhv:last ; rdfs:label "Composite Capabilities/Preference Profiles: Requirements and Architecture"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-07-21"^^xsd:date; """ This document contains terminology and abbreviations that are used in other CC/PP documents. For a detailed description of CC/PP, please see [CC/PP]. """@en; ; cat:DocLicense; data:W3C; "Composite Capabilities/Preference Profiles: Terminology and Abbreviations"; ; xhv:last ; rdfs:label "Composite Capabilities/Preference Profiles: Terminology and Abbreviations"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-07-10"^^xsd:date; """ Multimodal browsers allow users to interact via a combination of modalities, for instance, speech recognition and synthesis, displays, keypads and pointing devices. The Voice Browser working group is interested in adding multimodal capabilities to voice browsers. This document sets out a prioritized list of requirements for multimodal dialog interaction, which any proposed markup language (or extension thereof) should address. """@en; ; cat:DocLicense; data:W3C; "Multimodal Requirements for Voice Markup Languages"; ; xhv:last ; rdfs:label "Multimodal Requirements for Voice Markup Languages"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-11-20"^^xsd:date; """ The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of specifications for voice browsers, and provides details of an XML markup language for describing the meanings of individual natural language utterances. It is expected to be automatically generated by semantic interpreters for use by components that act on the user's utterances, such as dialog managers. """@en; ; cat:DocLicense; data:W3C; "Natural Language Semantics Markup Language for the Speech Interface Framework"; ; xhv:last ; rdfs:label "Natural Language Semantics Markup Language for the Speech Interface Framework"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-04-26"^^xsd:date; """ The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirements studies for voice browsers, and provides details of the requirements for reusable components for spoken dialogs. """@en; ; cat:DocLicense; data:W3C; "Reusable Dialog Requirements for Voice Markup Language"; ; xhv:last ; rdfs:label "Reusable Dialog Requirements for Voice Markup Language"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-02-25"^^xsd:date; """ This specification defines the Document Object Model (DOM) specification for synchronized multimedia functionality. It is part of work in the Synchronized Multimedia Working Group (SYMM) towards a next version of the SMIL language and SMIL modules. Related documents describe the specific application of this SMIL DOM for SMIL documents and for HTML and XML documents that integrate SMIL functionality. The SMIL DOM builds upon the DOM Core functionality, adding support for timing and synchronization, media integration and other extensions to support synchronized multimedia documents. """@en; ; cat:DocLicense; data:W3C; "Synchronized Multimedia Integration Language Document Object Model"; ; xhv:last ; rdfs:label "Synchronized Multimedia Integration Language Document Object Model"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-12-04"^^xsd:date; """ The World Wide Web Consortium's Voice Browser Working Group is defining several markup languages for applications supporting speech input and output. These markup languages will enable speech applications across a range of hardware and software platforms. Specifically, the Working Group is designing markup languages for dialog, speech recognition grammar, speech synthesis, natural language semantics, and a collection of reusable dialog components. These markup languages make up the W3C Speech Interface Framework. The speech community is invited to review and comment on the working draft requirement and specification documents. """@en; ; cat:DocLicense; data:W3C; "Voice Browsers, Introduction"; ; xhv:last ; rdfs:label "Voice Browsers, Introduction"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-01-05"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Building XHTML™ Modules"; ; xhv:last ; rdfs:label "Building XHTML™ Modules"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2000-08-25"^^xsd:date; """ This document describes the requirements for the XSLT 1.1 specification. """@en; ; cat:DocLicense; data:W3C; "XSL Transformations Requirements Version 1.1"; ; xhv:last ; rdfs:label "XSL Transformations Requirements Version 1.1"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-02-12"^^xsd:date; """ 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. The XML Fragment WG is chartered with defining a way to send fragments of an XML document—regardless of whether the fragments are predetermined entities or not—without having to send all of the containing document up to the part in question. This document defines Version 1.0 of the [eventual] W3C Recommendation that addresses this issue. """@en; ; cat:DocLicense; data:W3C; "XML Fragment Interchange"; ; xhv:last ; rdfs:label "XML Fragment Interchange"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-12-20"^^xsd:date; """ This document describes how existing vocabularies for different classes of devices and user agents can be used in CC/PP components, and how to create schemas that encapsulate existing vocabularies. It discusses the results of the coordination with the IETF CONNEG Working Group, as well as the WAP Forum UAPROF Working Group and several other groups, which have related activities. It contains a number of schemas and software examples which has been contributed voluntarily by individuals. It also gives an example of heuristics, which can be used to adapt content to a CC/PP profile, thus giving some guidelines for those who want to use CC/PP to implement content adaptation. It also serves to provide vocabulary and schema designers with key guidelines regarding extensions to existing vocabularies or development of new ones. """@en; ; cat:DocLicense; data:W3C; "CC/PP Implementors Guide: Harmonization with Existing Vocabularies and Content Transformation Heuristics"; ; xhv:last ; rdfs:label "CC/PP Implementors Guide: Harmonization with Existing Vocabularies and Content Transformation Heuristics"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-12-11"^^xsd:date; """ From the early days of the World Wide Web, Web Agents had been extended to support more types of contents. The recent developments of XML and the possibility to mix mupltiple XML Namespaces in the document reiterated the need to extend implementations and relaying on add-on softwares to accomplish tasks not supported by default in the implementation. In other words, we have several XML languages to represent different parts of Web pages (XHTML, SVG, MathML, XForms, etc.), we now need a well defined mechanism that allow different specialized tools to work together and handled these compound documents. This W3C Note contains a non-exhaustive list of requirements to work on a Component Extension API. The goal of this API is to extend the ability of a Web application. Note that the Web application can be either on the server side or on a client side, and does not automatically implies interaction with a user or having a Web browser. """@en; ; cat:DocLicense; data:W3C; "Component Extension (CX) API requirements Version 1.0"; ; xhv:last ; rdfs:label "Component Extension (CX) API requirements Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-09-21"^^xsd:date; """ This paper addresses and attempts to clarify two issues pertaining to URIs, and presents recommendations. Section 1 addresses how URI space is partitioned and the relationship between URIs, URLs, and URNs. Section 2 describes how URI schemes and URN namespace ids are registered. Section 3 mentions additional unresolved issues not considered by this paper and section 4 presents recommendations. """@en; ; cat:DocLicense; data:W3C; "URIs, URLs, and URNs: Clarifications and Recommendations 1.0"; ; xhv:last ; rdfs:label "URIs, URLs, and URNs: Clarifications and Recommendations 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-04-06"^^xsd:date; """ This W3C Note defines an RDF schema for the XML Infoset. """@en; ; cat:DocLicense; data:W3C; "An RDF Schema for the XML Information Set"; ; xhv:last ; rdfs:label "An RDF Schema for the XML Information Set"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-06-05"^^xsd:date; """ The interaction of XLink linking elements and styling has not previously been carefully described. This note, the result of an XML Linking/XSL joint task force, attempts to rectify that oversight by providing a clear conceptual model for linking and styling and suggestions for the practical application of that model using current W3C Recommendations (and Working Drafts, Candidate Recommendations, and Proposed Recommendations). """@en; ; cat:DocLicense; data:W3C; "XML Linking and Style"; ; xhv:last ; rdfs:label "XML Linking and Style"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-02-21"^^xsd:date; """This specification defines the Mathematical Markup Language, or MathML. 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.This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document.This document begins with background information on mathematical notation, the problems it poses, and the philosophy underlying the solutions MathML 2.0 proposes. 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. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of MathML characters and their relation to fonts.While MathML is human-readable, it is anticipated that, in all but the simplest cases, authors will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several early versions of such MathML tools already exist, and a number of others, both freely available software and commercial products, are under development."""@en; ; cat:DocLicense; data:W3C; "Mathematical Markup Language (MathML) Version 2.0"; ; xhv:last ; rdfs:label "Mathematical Markup Language (MathML) Version 2.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-09-04"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Scalable Vector Graphics (SVG) 1.0 Specification"; ; xhv:last ; rdfs:label "Scalable Vector Graphics (SVG) 1.0 Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-12-17"^^xsd:date; """ CGM (Computer Graphics Metafile) has been an ISO standard for vector and composite vector/raster picture definition since 1987. It has been a registered MIME type since 1995. CGM has a significant following in technical illustration, electronic documentation, geophysical data visualization, amongst other application areas. WebCGM is a profile for the effective application of CGM in Web electronic documents. WebCGM has been a joint effort of the CGM Open Consortium, in collaboration with W3C staff and supported by the European Commission Esprit project. It represents an important interoperability agreement amongst major users and implementors of CGM, and thereby unifies current diverse approaches to CGM utilization in Web document applications. WebCGM's clear and unambiguous conformance requirements will enhance interoperability of implementations, and it should be possible to leverage existing CGM validation tools, test suites, and the product certification testing services for application to WebCGM . While WebCGM is a binary file format and is not "stylable", nevertheless WebCGM follows published W3C requirements for a scalable graphics format where such are applicable. The design criteria for the graphical content of WebCGM aimed at a balance between graphical expressive power on the one hand, and simplicity and implementability on the other. A small but powerful set of metadata elements is standardized in WebCGM, to support the functionalities of: hyperlinking and document navigation; picture structuring and layering; and, search and query on WebCGM picture content. """@en; ; cat:DocLicense; data:W3C; "WebCGM 1.0 Second Release"; ; xhv:last ; rdfs:label "WebCGM 1.0 Second Release"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-05-31"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Ruby Annotation"; ; xhv:last ; rdfs:label "Ruby Annotation"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-09-04"^^xsd:date; """ This is a W3C Recommendation of a specification of animation functionality for XML documents. It describes an animation framework as well as a set of base XML animation elements suitable for integration with XML documents. It is based upon the SMIL 1.0 timing model, with some extensions, and is a true subset of SMIL 2.0. This provides an intermediate stepping stone in terms of implementation complexity, for applications that wish to have SMIL-compatible animation but do not need or want time containers. """@en; ; cat:DocLicense; data:W3C; "SMIL Animation"; ; xhv:last ; rdfs:label "SMIL Animation"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-08-07"^^xsd:date; """ This document specifies the second version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL 2.0 has the following two design goals: 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.Allow reusing of SMIL 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 [XHTML10] and into SVG [SVG]. """@en; ; cat:DocLicense; data:W3C; "Synchronized Multimedia Integration Language (SMIL 2.0) Specification"; ; xhv:last ; rdfs:label "Synchronized Multimedia Integration Language (SMIL 2.0) Specification"; :accessURL ; :status , , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-05-31"^^xsd:date; ; cat:DocLicense; data:W3C; "XHTML™ 1.1 - Module-based XHTML"; ; xhv:last ; rdfs:label "XHTML™ 1.1 - Module-based XHTML"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-06-27"^^xsd:date; """ This specification defines the XML Linking Language (XLink), which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links. """@en; ; cat:DocLicense; data:W3C; "XML Linking Language (XLink) Version 1.0"; ; xhv:last ; rdfs:label "XML Linking Language (XLink) Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-03-15"^^xsd:date; """ Any XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 [XML] and Namespaces in XML [Names]. 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. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on application-specific equivalence rules for which no generalized XML specification could account. """@en; ; cat:DocLicense; data:W3C; "Canonical XML Version 1.0"; ; xhv:last ; rdfs:label "Canonical XML Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-10-24"^^xsd:date; """ This specification provides a set of definitions for use in other specifications that need to refer to the information in an XML document. """@en; ; cat:DocLicense; data:W3C; "XML Information Set"; ; xhv:last ; rdfs:label "XML Information Set"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-06-27"^^xsd:date; """ This document proposes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents. """@en; ; cat:DocLicense; data:W3C; "XML Base"; ; xhv:last ; rdfs:label "XML Base"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-05-02"^^xsd:date; """ XML Schema Part 0: Primer is a non-normative document intended to provide an easily readable description of the XML Schema facilities, and is oriented towards quickly understanding how to create schemas using the XML Schema language. XML Schema Part 1: Structures and XML Schema Part 2: Datatypes provide the complete normative description of the XML Schema language. This primer describes the language features through numerous examples which are complemented by extensive references to the normative texts. """@en; ; cat:DocLicense; data:W3C; "XML Schema Part 0: Primer"; ; xhv:last ; rdfs:label "XML Schema Part 0: Primer"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-05-02"^^xsd:date; """ XML Schema: Structures specifies the XML Schema definition language, which offers facilities for describing the structure and constraining the contents of XML 1.0 documents, including those which exploit the XML Namespace facility. The schema language, which is itself represented in XML 1.0 and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML 1.0 document type definitions (DTDs). This specification depends on XML Schema Part 2: Datatypes. """@en; ; cat:DocLicense; data:W3C; "XML Schema Part 1: Structures"; ; xhv:last ; rdfs:label "XML Schema Part 1: Structures"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-05-02"^^xsd:date; """ XML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML 1.0, provides a superset of the capabilities found in XML 1.0 document type definitions (DTDs) for specifying datatypes on elements and attributes. """@en; ; cat:DocLicense; data:W3C; "XML Schema Part 2: Datatypes"; ; xhv:last ; rdfs:label "XML Schema Part 2: Datatypes"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-10-15"^^xsd:date; """ This specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. It consists of two parts: a language for transforming XML documents, and an XML vocabulary for specifying formatting semantics. An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary. """@en; ; cat:DocLicense; data:W3C; "Extensible Stylesheet Language (XSL) Version 1.0"; ; xhv:last ; rdfs:label "Extensible Stylesheet Language (XSL) Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-12-21"^^xsd:date; """ This specification provides guidelines for Web authoring tool developers. Its purpose is two-fold: to assist developers in designing authoring tools that produce accessible Web content and to assist developers in creating an accessible authoring interface. Authoring tools can enable, encourage, and assist users ("authors") in the creation of accessible Web content through prompts, alerts, checking and repair functions, help files and automated tools. It is just as important that all people be able to author content as it is for all people to have access to it. The tools used to create this information must therefore be accessible themselves. Adoption of these guidelines will contribute to the proliferation of Web content that can be read by a broader range of readers and authoring tools that can be used by a broader range of authors. This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI). """@en; ; cat:DocLicense; data:W3C; "Authoring Tool Accessibility Guidelines \"Wombat\""; ; xhv:last ; rdfs:label "Authoring Tool Accessibility Guidelines \"Wombat\""; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-12-20"^^xsd:date; """ This document gives implementors advice on how to protect the privacy of a CC/PP user, and outlines how this can be applied using P3P in HTTP with the CC/PP Exchange protocol. """@en; ; cat:DocLicense; data:W3C; "CC/PP Implementors Guide: Privacy and Protocols"; ; xhv:last ; rdfs:label "CC/PP Implementors Guide: Privacy and Protocols"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-08-03"^^xsd:date; """This document lists the design principles and requirements for the creation of a mobile profile of the SVG specification to be developed by the W3C SVG2 working group."""@en; ; cat:DocLicense; data:W3C; "SVG Mobile Requirements"; ; xhv:last ; rdfs:label "SVG Mobile Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-04-13"^^xsd:date; """ This document describes requirements for mechanisms that enable fine-grained control of speech (signal processing) resources and telephony resources in a VoiceXML telephony platform. The scope of these language features is for controlling resources in a platform on the network edge, not for building network-based call processing applications in a telephone switching system, or for controlling an entire telecom network. """@en; ; cat:DocLicense; data:W3C; "Call Control Requirements in a Voice Browser Framework"; ; xhv:last ; rdfs:label "Call Control Requirements in a Voice Browser Framework"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-05-23"^^xsd:date; """The members of the CSS&FP Working Group have decided to modularize the CSS specification. This modularization will help to clarify the relationships between the different parts of the specification, and reduce the size of the complete document. It will also allow us to build specific tests on a per module basis and will help implementors in deciding which portions of CSS to support. Furthermore, the modular nature of the specification will make it possible for individual modules to be updated as needed, thus allowing for a more flexible and timely evolution of the specification as a whole.This document lists all the modules to be contained in the future CSS3 specification."""@en; ; cat:DocLicense; data:W3C; "CSS3 introduction"; ; xhv:last ; rdfs:label "CSS3 introduction"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-01-03"^^xsd:date; """ This document defines syntax for representing N-Gram (Markovian) stochastic grammars within the W3C Speech Interface Framework. The use of stochastic N-Gram models has a long and successful history in the research community and is now more and more effecting commercial systems, as the market asks for more robust and flexible solutions. The primary purpose of specifying a stochastic grammar format is to support large vocabulary and open vocabulary applications. In addition, stochastic grammars can be used to represent concepts or semantics. This specification defines the mechanism for combining stochastic and structured (in this case Context-Free) grammars as well as methods for combined semantic definitions. """@en; ; cat:DocLicense; data:W3C; "Stochastic Language Models (N-Gram) Specification"; ; xhv:last ; rdfs:label "Stochastic Language Models (N-Gram) Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-04-04"^^xsd:date; """ Forms were introduced into HTML in 1993. Since then they have gone on to become a critical part of the Web. The existing mechanisms in HTML for forms are now outdated, and W3C has started work on developing an effective replacement. This document outlines the requirements for "XForms", W3C's name for the next generation of Web forms. """@en; ; cat:DocLicense; data:W3C; "XForms Requirements"; ; xhv:last ; rdfs:label "XForms Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-10-04"^^xsd:date; """This specification defines the Second Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines."""@en; ; cat:DocLicense; data:W3C; "XHTML™ 1.0: The Extensible HyperText Markup Language (Second Edition)"; ; xhv:last ; rdfs:label "XHTML™ 1.0: The Extensible HyperText Markup Language (Second Edition)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-09-21"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XML Blueberry Requirements"; ; xhv:last ; rdfs:label "XML Blueberry Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-09-25"^^xsd:date; """ XML Schema: Formal Description is a formal description of XML types and validity as specified by XML Schema Part 1: Structures. """@en; ; cat:DocLicense; data:W3C; "XML Schema: Formal Description"; ; xhv:last ; rdfs:label "XML Schema: Formal Description"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-08-24"^^xsd:date; """ This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. 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. However, XSLT is not intended as a completely general-purpose XML transformation language. Rather it is designed primarily for the kinds of transformations that are needed when XSLT is used as part of XSL. """@en; ; cat:DocLicense; data:W3C; "XSL Transformations (XSLT) Version 1.1"; ; xhv:last ; rdfs:label "XSL Transformations (XSLT) Version 1.1"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2001-02-14"^^xsd:date; """ This document describes the requirements for the XSLT 2.0 specification. """@en; ; cat:DocLicense; data:W3C; "XSLT Requirements Version 2.0"; ; xhv:last ; rdfs:label "XSLT Requirements Version 2.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-10-29"^^xsd:date; """ This document provides information to authoring tool developers who wish to satisfy the checkpoints of "Authoring Tool Accessibility Guidelines 1.0" [ATAG10]. It includes suggested techniques, sample strategies in deployed tools, and references to other accessibility resources (such as platform-specific software accessibility guidelines) that provide additional information on how a tool may satisfy each checkpoint. This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI). """@en; ; cat:DocLicense; data:W3C; """Techniques for Authoring Tool Accessibility Guidelines 1.0"""; ; xhv:last ; xhv:previous ; rdfs:label """Techniques for Authoring Tool Accessibility Guidelines 1.0"""; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-07-25"^^xsd:date; """ This specification defines the Document Object Model Abstract Schemas Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. """@en; ; cat:DocLicense; data:W3C; """Document Object Model (DOM) Level 3 Abstract Schemas Specification"""; ; xhv:last ; rdfs:label """Document Object Model (DOM) Level 3 Abstract Schemas Specification"""; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-12-17"^^xsd:date; """This document provides techniques for satisfying the checkpoints defined in "User Agent Accessibility Guidelines 1.0" [UAAG10]. These techniques address key aspects of the accessibility of user interfaces, content rendering, application programming interfaces (APIs), and languages such as the Hypertext Markup Language (HTML), Cascading Style Sheets (CSS) and the Synchronized Multimedia Integration Language (SMIL).The techniques listed in this document are not required for conformance to the Guidelines. These techniques are not necessarily the only way of satisfying the checkpoint, nor are they a definitive set of requirements for satisfying a checkpoint."""@en; ; cat:DocLicense; data:W3C; """Techniques for User Agent Accessibility Guidelines 1.0"""; ; xhv:last ; xhv:previous ; rdfs:label """Techniques for User Agent Accessibility Guidelines 1.0"""; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-01-31"^^xsd:date; """ The XHTML+SMIL profile defines a set of XHTML abstract modules that support a subset of the SMIL 2.0 specification. It includes functionality from SMIL 2.0 modules providing support for animation, content control, media objects, timing and synchronization, and transition effects. The profile also integrates SMIL 2.0 features directly with XHTML and CSS, describing how SMIL can be used to manipulate XHTML and CSS features. Additional semantics are defined for some XHTML elements and CSS properties. The profile is designed for Web clients that support XHTML+SMIL markup validating to this profile's implementation DTD. The document type definition (DTD) and XML Schema [XSCHEMA] are implemented using SMIL modules as defined in "Modularization of SMIL" [SMIL-MOD-NOTE], and "The SMIL 20 Modules" [SMIL20-MOD]. """@en; ; cat:DocLicense; data:W3C; "XHTML+SMIL Profile"; ; xhv:last ; rdfs:label "XHTML+SMIL Profile"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-12-04"^^xsd:date; """ The W3C Multimodal Interaction Activity is developing specifications as a basis for a new breed of Web applications in which you can interact using multiple modes of interaction, for instance, using speech, hand writing, and key presses for input, and spoken prompts, audio and visual displays for output. This document describes several use cases for multimodal interaction and presents them in terms of varying device capabilities and the events needed by each use case to couple different components of a multimodal application. """@en; ; cat:DocLicense; data:W3C; "Multimodal Interaction Use Cases"; ; xhv:last ; rdfs:label "Multimodal Interaction Use Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-01-25"^^xsd:date; "This document describes an RDF Schema for P3P."@en; ; cat:DocLicense; data:W3C; "An RDF Schema for P3P"; ; xhv:last ; rdfs:label "An RDF Schema for P3P"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-02-11"^^xsd:date; """ This is a guide to help site operators deploy the Platform for Privacy Preferences (P3P) on their site. It provides information on the tasks required, and gives guidance on how to best complete them. """@en; ; cat:DocLicense; data:W3C; "The Platform for Privacy Preferences 1.0 Deployment Guide"; ; xhv:last ; rdfs:label "The Platform for Privacy Preferences 1.0 Deployment Guide"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-12-02"^^xsd:date; """This document is part of the of the Quality Assurance (QA) Activity. It presents examples and describes the techniques of operational aspects of quality practices within the W3C's Working Groups. It complements QA Framework: Operational Guidelines, by specifying or illustrating how Working Groups might meet the operational and process-related checkpoints of that document."""@en; ; cat:DocLicense; data:W3C; "QA Framework: Operational Examples & Techniques"; ; xhv:last ; xhv:previous ; rdfs:label "QA Framework: Operational Examples & Techniques"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-07-03"^^xsd:date; """This document is meant to be an illustration of the SOAP 1.2 Protocol Binding Framework applied to a well known internet transport mechanism, Email, specifically rfc2822."""@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Email Binding"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Email Binding"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-09-02"^^xsd:date; "This document describes XML Schemas for XHTML 1.0."@en; ; cat:DocLicense; data:W3C; "XHTML 1.0 in XML Schema"; ; xhv:last ; rdfs:label "XHTML 1.0 in XML Schema"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-03-04"^^xsd:date; """ This document lists the design principles, scope, and requirements for XML Encryption. It includes requirements as they relate to the encryption syntax, data model, format, cryptographic processing, and external requirements and coordination. """@en; ; cat:DocLicense; data:W3C; "XML Encryption Requirements"; ; xhv:last ; rdfs:label "XML Encryption Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-04-16"^^xsd:date; """ This is the specification of the Platform for Privacy Preferences (P3P). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P applications. """@en; ; cat:DocLicense; data:W3C; """The Platform for Privacy Preferences 1.0 (P3P1.0) Specification"""; ; xhv:last ; rdfs:label """The Platform for Privacy Preferences 1.0 (P3P1.0) Specification"""; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-12-17"^^xsd:date; """This document provides guidelines for designing user agents that lower barriers to Web accessibility 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. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable.In addition to helping developers of HTML browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities."""@en; ; cat:DocLicense; data:W3C; "User Agent Accessibility Guidelines 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "User Agent Accessibility Guidelines 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-08-01"^^xsd:date; """This specification defines the Second Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines."""@en; ; cat:DocLicense; data:W3C; "XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-07-18"^^xsd:date; """ Canonical XML [XML-C14N] specifies a standard serialization of XML that, when applied to a subdocument, includes the subdocument's ancestor context including all of the namespace declarations and attributes in the "xml:" namespace. However, some applications require a method which, to the extent practical, excludes ancestor context from a canonicalized subdocument. 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. """@en; ; cat:DocLicense; data:W3C; "Exclusive XML Canonicalization Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Exclusive XML Canonicalization Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-02-12"^^xsd:date; """This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere."""@en; ; cat:DocLicense; data:W3C; "XML-Signature Syntax and Processing"; ; xhv:last ; rdfs:label "XML-Signature Syntax and Processing"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-11-08"^^xsd:date; """ XML Signature [XML-DSig] recommends a standard means for specifying information content to be digitally signed and for representing the resulting digital signatures in XML. Some applications require the ability to specify a subset of a given XML document as the information content to be signed. The XML Signature specification meets this requirement with the XPath transform. However, this transform can be difficult to implement efficiently with existing technologies. This specification defines a new XML Signature transform to facilitate the development of efficient document subsetting implementations that interoperate under similar performance profiles. """@en; ; cat:DocLicense; data:W3C; "XML-Signature XPath Filter 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "XML-Signature XPath Filter 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-12-10"^^xsd:date; """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."""@en; ; cat:DocLicense; data:W3C; "Decryption Transform for XML Signature"; ; xhv:last ; xhv:previous ; rdfs:label "Decryption Transform for XML Signature"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-07-25"^^xsd:date; """ This specification defines the Document Object Model Abstract Schemas and Load and Save Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. """@en; ; cat:DocLicense; data:W3C; """Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification"""; ; xhv:last ; xhv:previous ; rdfs:label """Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification"""; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-04-15"^^xsd:date; """This document complements the P3P1.0 specification [P3P10] by specifying a language for describing collections of preferences regarding P3P policies between P3P agents. Using this language, a user can express her preferences in a set of preference-rules (called a ruleset), which can then be used by her user agent to make automated or semi-automated decisions regarding the acceptability of machine-readable privacy policies from P3P enabled Web sites."""@en; ; cat:DocLicense; data:W3C; "A P3P Preference Exchange Language 1.0 (APPEL1.0)"; ; xhv:last ; rdfs:label "A P3P Preference Exchange Language 1.0 (APPEL1.0)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-04-22"^^xsd:date; """This document lists the design principles and requirements for future versions of the SVG language, in particular versions 1.1, 1.2 and 2.0, to be developed by the W3C SVG working group. Refer to SVG 1.0 [SVG 1.0] for details on the current W3C Recommendation."""@en; ; cat:DocLicense; data:W3C; "SVG 1.1/1.2/2.0 Requirements"; ; xhv:last ; rdfs:label "SVG 1.1/1.2/2.0 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-08-09"^^xsd:date; """An XHTML+MathML+SVG profile is a profile that combines XHTML 1.1 [XHTML11], MathML 2.0 [MathML2] and SVG 1.1 [SVG11] together. This profile enables mixing XHTML, MathML and SVG in the same document using XML namespaces [XMLNS] mechanism, while allowing validation of such a mixed-namespace document. An XHTML 1.1 + MathML 2.0 + SVG 1.1 DTD driver is provided. An XHTML version of this document is conforming to this DTD."""@en; ; cat:DocLicense; data:W3C; "An XHTML + MathML + SVG Profile"; ; xhv:last ; xhv:previous ; rdfs:label "An XHTML + MathML + SVG Profile"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-11-07"^^xsd:date; """CSS (Cascading Style Sheets) is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This draft describes the functionality that is proposed for CSS level 3 to describe borders, such as border styles, border colors and border images. It includes and extends the functionality of CSS level 2 [CSS2], which builds on CSS Level 1 [CSS1]."""@en; ; cat:DocLicense; data:W3C; "CSS3 module: Border"; ; xhv:last ; rdfs:label "CSS3 module: Border"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-05-15"^^xsd:date; """This document presents a set of CSS line formatting properties. It also includes baseline alignment features as well as related functions like initial line and initial letter effect. It extends on the CSS 2 model [CSS2]."""@en; ; cat:DocLicense; data:W3C; "CSS3 module: line"; ; xhv:last ; rdfs:label "CSS3 module: line"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-08-02"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "User Interface for CSS3"; ; xhv:last ; xhv:previous ; rdfs:label "User Interface for CSS3"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-08-08"^^xsd:date; """ A voice browser provides the means for people to use their voice to interact with appropriately designed applications. Users generally connect to voice browsers by dialling an access number. The voice browser in turn retrieves markup (e.g. VoiceXML) and other resources from an application server. In some situations it is appropriate to transfer the user from one voice browser to another. In other situations, the user may start from a visual web page and then transfer to a voice browser, yet another possibility is transfer from a voice browser to a human operator. This document describes the requirements for how voice browsers and other call sites can cooperate by sharing data to create a seamless caller experience. An example of a potential resulting benefit to a caller is not having to re-enter the same information repeatedly at different call sites. A potential benefit for service providers is a flexible architecture for deploying and interconnecting disparate call sites. """@en; ; cat:DocLicense; data:W3C; "Voice Browser Interoperation: Requirements"; ; xhv:last ; rdfs:label "Voice Browser Interoperation: Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-10-28"^^xsd:date; """ This document describes the Web Services Description Working Group's requirements for the Web Services Description specification. """@en; ; cat:DocLicense; data:W3C; "Web Services Description Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Description Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-06-04"^^xsd:date; """ This document describes the Usage Scenarios guiding the development of the Web Service Description specification. """@en; ; cat:DocLicense; data:W3C; "Web Service Description Usage Scenarios"; ; xhv:last ; rdfs:label "Web Service Description Usage Scenarios"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-10-03"^^xsd:date; """This document provides guidelines for designing Extensible Markup Language (XML) applications that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). XML, used to design applications such as XHTML, SMIL, and SVG, provides no intrinsic guarantee of the accessibility of those applications. This document explains how to include features in XML applications that promote accessibility."""@en; ; cat:DocLicense; data:W3C; "XML Accessibility Guidelines"; ; xhv:last ; xhv:previous ; rdfs:label "XML Accessibility Guidelines"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-03-18"^^xsd:date; """ This document extends the XML Key Management Specification [XKMS] protocol to encompass the bulk registration operations necessary for interfacing with such systems as smart card management systems. X-BULK is defined in terms of structures expressed in the XML Schema Language [XML-Schema] and web services description language [WSDL]. """@en; ; cat:DocLicense; data:W3C; "XML Key Management Specification Bulk Operation (X-BULK)"; ; xhv:last ; rdfs:label "XML Key Management Specification Bulk Operation (X-BULK)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-04-03"^^xsd:date; """ This document contains requirements on the development of Namespaces in XML version 1.1, which is intended to have a single new feature - the ability to undeclare namespaces. In addition, all errata of version 1.0 will be incorporated. """@en; ; cat:DocLicense; data:W3C; "Namespaces in XML 1.1 Requirements"; ; xhv:last ; rdfs:label "Namespaces in XML 1.1 Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-08-16"^^xsd:date; """ This specification defines the XML Pointer Language (XPointer), 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. """@en; ; cat:DocLicense; data:W3C; "XML Pointer Language (XPointer)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Pointer Language (XPointer)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2002-12-19"^^xsd:date; """ The XPointer xpointer() scheme is intended to be used with the XPointer Framework [XPtrFrame] to provide a high level of functionality for addressing portions of XML documents. It is based on XPath [XPath], and adds the ability to address strings, points, and ranges in accordance with definitions provided in DOM 2: Range.[DOM2] """@en; ; cat:DocLicense; data:W3C; "XPointer xpointer() Scheme"; ; xhv:last ; xhv:previous ; rdfs:label "XPointer xpointer() Scheme"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-05-14"^^xsd:date; """This specification defines a subset of Cascading Style Sheets Level 2 and CSS3 Module: Color specifications tailored to the needs and constraints of TV devices."""@en; ; cat:DocLicense; data:W3C; "CSS TV Profile 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "CSS TV Profile 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-10-14"^^xsd:date; """ The XForms Basic Profile describes a minimal level of XForms processing tailored to the needs of constrained devices and environments. """@en; ; cat:DocLicense; data:W3C; "XForms 1.0 Basic Profile"; ; xhv:last ; xhv:previous ; rdfs:label "XForms 1.0 Basic Profile"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-01-13"^^xsd:date; """This document describes requirements for the Extensible MultiModal Annotation language (EMMA) specification under development in the W3C Multimodal Interaction Activity. EMMA is intended as a data format for the interface between input processors and interaction management systems. It will define the means for recognizers to annotate application specific data with information such as confidence scores, time stamps, input mode (e.g. key strokes, speech or pen), alternative recognition hypotheses, and partial recognition results, etc. EMMA is a target data format for the semantic interpretation specification being developed in the Voice Browser Activity, and which describes annotations to speech grammars for extracting application specific data as a result of speech recognition. EMMA supercedes earlier work on the natural language semantics markup language in the Voice Browser Activity."""@en; ; cat:DocLicense; data:W3C; "Requirements for EMMA"; ; xhv:last ; rdfs:label "Requirements for EMMA"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-09-01"^^xsd:date; """ This document discusses the challenges that authors commonly face when building web content and applications that can be accessed by users via a wide variety of different devices with different capabilities. The document examines the effects on authors and the implications for authoring techniques that assist in the preparation of sites that can support a wide variety of devices. As a consequence, it also derives a set of requirements for such techniques. This document is one of a series produced by the Device Independence Working Group, part of the W3C Device Independence Activity. The DIWG activity statement can be seen at http://www.w3.org/2001/di/Activity. Other documents in the series address the implementation of solutions to the requirements raised here. For example, there are documents in the series reviewing current techniques that can be used to address these requirements and exploring how future versions of existing W3C specifications can provide solutions. Details of the entire series of documents can be found on the W3C Device Independence Activity home page. """@en; ; cat:DocLicense; data:W3C; "Authoring Challenges for Device Independence"; ; xhv:last ; xhv:previous ; rdfs:label "Authoring Challenges for Device Independence"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-09-01"^^xsd:date; """ This document celebrates the vision of a device independent Web. It describes device independence principles that can lead towards the achievement of greater device independence for web content and applications. """@en; ; cat:DocLicense; data:W3C; "Device Independence Principles"; ; xhv:last ; xhv:previous ; rdfs:label "Device Independence Principles"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-01-22"^^xsd:date; """ This document describes requirements for the Ink Markup Language that will be used in the multimodal interaction framework as proposed by the W3C Multimodal Interaction Working Group. The Ink Markup Language will serve as the data format for representing ink entered with an electronic pen or stylus in a multimodal system. The markup will allow for the input and processing of handwriting, gestures, sketches, music and other notational languages in web-based multimodal applications. In the context of the W3C Multimodal Interaction Framework, the markup provides a common format for the exchange of ink data between components such as handwriting and gesture recognizers, signature verifiers, and other ink-aware modules. """@en; ; cat:DocLicense; data:W3C; "Requirements for the Ink Markup Language"; ; xhv:last ; rdfs:label "Requirements for the Ink Markup Language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-10-10"^^xsd:date; """ This document presents a framework for specifying the semantics for the languages of the Semantic Web. Some of these languages (notably RDF [RDF-PRIMER] [RDF-VOCABULARY] [RDF-SYNTAX] [RDF-CONCEPTS] [RDF-SEMANTICS], and OWL [OWL]) are currently in various stages of development and we expect others to be developed in the future. This framework is intended to provide a framework for specifying the semantics of all of these languages in a uniform and coherent way. The strategy is to translate the various languages into a common 'base' language thereby providing them with a single coherent model theory. We describe a mechanism for providing a precise semantics for the Semantic Web Languages (referred to as SWELs from now on. The purpose of this is to define clearly the consequences and allowed inferences from constructs in these languages. """@en; ; cat:DocLicense; data:W3C; "LBase: Semantics for Languages of the Semantic Web"; ; xhv:last ; xhv:previous ; rdfs:label "LBase: Semantics for Languages of the Semantic Web"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-11-10"^^xsd:date; """ This Note examines the treatment of bound variables in Content MathML. Bound variables are central representational primitives in mathematical languages. They allow one to express functions, quantification, and operators with qualifiers. The first edition of the MathML 2.0 Recommendation [MathML2] was somewhat vague about the identity conditions on bound variables, and as a consequence Content MathML applications were left to guess the exact meaning. This Note provides some of the rationale behind how this has been clarified in the second edition [MathML22e]. """@en; ; cat:DocLicense; data:W3C; "Bound Variables in MathML"; ; xhv:last ; rdfs:label "Bound Variables in MathML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-11-10"^^xsd:date; """ This Note discusses the facilities that are available in the MathML 2.0 Recommendation to facilitate the capturing of mathematical type information. It demonstrates how a combination of these features can be systematically used to provide support for general mathematical types. """@en; ; cat:DocLicense; data:W3C; "Structured Types in MathML 2.0"; ; xhv:last ; rdfs:label "Structured Types in MathML 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-11-10"^^xsd:date; """ MathML is an XML application for describing mathematical notation, capturing both its structure and content. As such, its scope does not extend to include units - determinate quantities adopted as standards of measure - which nevertheless, by their very nature, occur in an applied mathematical setting. This Note makes recommendations and suggestions for how units can be incorporated into MathML. """@en; ; cat:DocLicense; data:W3C; "Units in MathML"; ; xhv:last ; rdfs:label "Units in MathML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-05-06"^^xsd:date; """ This document introduces the W3C Multimodal Interaction Framework, and identifies the major components for multimodal systems. Each component represents a set of related functions. The framework identifies the markup languages used to describe information required by components and for data flowing among components. The W3C Multimodal Interaction Framework describes input and output modes widely used today and can be extended to include additional modes of user input and output as they become available. """@en; ; cat:DocLicense; data:W3C; "W3C Multimodal Interaction Framework"; ; xhv:last ; xhv:previous ; rdfs:label "W3C Multimodal Interaction Framework"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-01-08"^^xsd:date; """This document describes fundamental requirements for the specifications under development in the W3C Multimodal Interaction Activity. These requirements were derived from use case studies as discussed in Appendix A. They have been developed for use by the Multimodal Interaction Working Group (W3C Members only), but may also be relevant to other W3C working groups and related external standard activities.The requirements cover general issues, inputs, outputs, architecture, integration, synchronization points, runtimes and deployments, but this document does not address application or deployment conformance rules."""@en; ; cat:DocLicense; data:W3C; "Multimodal Interaction Requirements"; ; xhv:last ; rdfs:label "Multimodal Interaction Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-06-11"^^xsd:date; """This document specifies XML presentation syntax for OWL, which is defined as a dialect similar to OWL Abstract Syntax [OWL Semantics]. It is not intended to be a normative specification. Instead, it represents a suggestion of one possible XML presentation syntax for OWL."""@en; ; cat:DocLicense; data:W3C; "OWL Web Ontology Language XML Presentation Syntax"; ; xhv:last ; rdfs:label "OWL Web Ontology Language XML Presentation Syntax"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-10-08"^^xsd:date; """ SOAP 1.2 intermediaries have some license when reserializing messages that pass through them. This document defines a transformation algorithm that renders all semantically equivalent SOAP messages identically. The transformation may be used in conjunction with an XML canonicalization algorithm prior to the generation of a message digest in producing XML digital signatures that are sufficiently robust to survive passage through one or more SOAP intermediaries. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Message Normalization"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Message Normalization"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-05-05"^^xsd:date; """ This document lists the design principles, scope and requirements for XML Key Management specifications and trust server key management implementations. It includes requirements as they relate to the key management syntax, processing, security and coordination with other standards activities. """@en; ; cat:DocLicense; data:W3C; "XML Key Management (XKMS 2.0) Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "XML Key Management (XKMS 2.0) Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-09-12"^^xsd:date; """ A URI reference may include an optional fragment identifier that consists of additional reference information to be interpreted by the user agent after the URI has been successfully retrieved. The format and interpretation of fragment identifiers is dependent on the media type of the retrieval result. The XML media type can therefore specify a fragment identifier syntax that takes advantage of the XML structure to define ways to point into an XML resource. This document recommends the adoption of a specific fragment identifier syntax for use with XML resources. """@en; ; cat:DocLicense; data:W3C; "Proposal for XML Fragment Identifier Syntax 0.9"; ; xhv:last ; rdfs:label "Proposal for XML Fragment Identifier Syntax 0.9"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-07-28"^^xsd:date; """ This document describes the XML Protocol Working Group's requirements for the XML Protocol (XMLP) specification. """@en; ; cat:DocLicense; data:W3C; "XML Protocol (XMLP) Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "XML Protocol (XMLP) Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-07-30"^^xsd:date; """ This document describes the SOAP Usage Scenarios and how they may be implemented using the SOAP 1.2 specification. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Usage Scenarios"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Usage Scenarios"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-01-09"^^xsd:date; """ This specification defines the Document Object Model Level 2 HTML, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content and structure of [HTML 4.01] and [XHTML 1.0] documents. The Document Object Model Level 2 HTML builds on the Document Object Model Level 2 Core [DOM Level 2 Core] and is not backward compatible with DOM Level 1 HTML [DOM Level 1]. """@en; ; cat:DocLicense; data:W3C; """Document Object Model (DOM) Level 2 HTML Specification"""; ; xhv:last ; xhv:previous ; rdfs:label """Document Object Model (DOM) Level 2 HTML Specification"""; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-10-21"^^xsd:date; """ This specification defines the Mathematical Markup Language, or MathML. 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. This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document. This document begins with background information on mathematical notation, the problems it poses, and the philosophy underlying the solutions MathML 2.0 proposes. 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. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of MathML characters and their relation to fonts. While MathML is human-readable, it is anticipated that, in all but the simplest cases, authors will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several versions of such MathML tools already exist, and a number of others, both freely available software and commercial products, are under development. """@en; ; cat:DocLicense; data:W3C; "Mathematical Markup Language (MathML) Version 2.0 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Mathematical Markup Language (MathML) Version 2.0 (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-11-10"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Portable Network Graphics (PNG) Specification (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Portable Network Graphics (PNG) Specification (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-01-14"^^xsd:date; """ This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML. """@en; ; cat:DocLicense; data:W3C; "Scalable Vector Graphics (SVG) 1.1 Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Scalable Vector Graphics (SVG) 1.1 Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-01-14"^^xsd:date; """ This document defines two mobile profiles of SVG 1.1. The first profile, SVG Tiny, is defined to be suitable for cellphones; the second profile, SVG Basic, is suitable for PDAs. """@en; ; cat:DocLicense; data:W3C; """ Mobile SVG Profiles: SVG Tiny and SVG Basic """; ; xhv:last ; xhv:previous ; rdfs:label """ Mobile SVG Profiles: SVG Tiny and SVG Basic """; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-06-24"^^xsd:date; """ SOAP Version 1.2 Part 0: Primer is a non-normative document intended to provide an easily understandable tutorial on the features of the SOAP Version 1.2 specifications. In particular, it describes the features through various usage scenarios, and is intended to complement the normative text contained in Part 1 and Part 2 of the SOAP 1.2 specifications. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Part 0: Primer"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Part 0: Primer"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-06-24"^^xsd:date; """ SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. "Part 1: Messaging Framework" defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Part 1: Messaging Framework"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Part 1: Messaging Framework"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-06-24"^^xsd:date; """ SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging Framework. This specification depends on SOAP Version 1.2 Part 1: Messaging Framework [SOAP Part 1]. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Part 2: Adjuncts"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Part 2: Adjuncts"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-06-24"^^xsd:date; """ This document draws on assertions found in the SOAP Version 1.2 specifications [SOAP Part1], [SOAP Part2], and provides a set of tests in order to show whether the assertions are implemented in a SOAP processor. A SOAP 1.2 implementation that passes all of the tests specified in this document may claim to conform to the SOAP 1.2 Test Suite, 2003 06 24. It is incorrect to claim to be compliant with the SOAP Version 1.2 specifications merely by passing successfully all the tests provided in this test suite. It is also incorrect to claim that an implementation is non compliant with the SOAP Version 1.2 specifications based on its failure to pass one or more of the tests in this test suite. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Specification Assertions and Test Collection"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Specification Assertions and Test Collection"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-10-14"^^xsd:date; """ XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts—XForms model, instance data, and user interface—it separates presentation from content, allows reuse, gives strong typing—reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML or SVG. """@en; ; cat:DocLicense; data:W3C; "XForms 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "XForms 1.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-10-14"^^xsd:date; """The XML Events module defined in this specification provides XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces [DOM2EVENTS]. The result is to provide an interoperable way of associating behaviors with document-level markup."""@en; ; cat:DocLicense; data:W3C; "XML Events"; ; xhv:last ; xhv:previous ; rdfs:label "XML Events"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-03-25"^^xsd:date; """ The XPointer element() scheme is intended to be used with the XPointer Framework [XPtrFrame] to allow basic addressing of XML elements. """@en; ; cat:DocLicense; data:W3C; "XPointer element() Scheme"; ; xhv:last ; xhv:previous ; rdfs:label "XPointer element() Scheme"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-03-25"^^xsd:date; """ This specification defines the XML Pointer Language (XPointer) Framework, an extensible system for XML addressing that underlies additional XPointer scheme specifications. The framework is intended to be used as a basis for fragment identifiers for any resource whose Internet media type is one of text/xml, application/xml, text/xml-external-parsed-entity, or application/xml-external-parsed-entity. Other XML-based media types are also encouraged to use this framework in defining their own fragment identifier languages. """@en; ; cat:DocLicense; data:W3C; "XPointer Framework"; ; xhv:last ; xhv:previous ; rdfs:label "XPointer Framework"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-03-25"^^xsd:date; """ The XPointer xmlns() scheme is intended to be used with the XPointer Framework [XPtrFrame] to allow correct interpretation of namespace prefixes in pointers, for instance, namespace-qualified scheme names and namespace-qualified element or attribute names appearing within scheme data. """@en; ; cat:DocLicense; data:W3C; "XPointer xmlns() Scheme"; ; xhv:last ; xhv:previous ; rdfs:label "XPointer xmlns() Scheme"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-02-18"^^xsd:date; """This document lists the design principles and requirements for the creation of a SVG specification related to printing."""@en; ; cat:DocLicense; data:W3C; "SVG Printing Requirements"; ; xhv:last ; rdfs:label "SVG Printing Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-05-10"^^xsd:date; """ This document sets out the Requirements for defining a set of Core Presentation Characteristics. The purpose of defining these Core Presentation Characteristics is to provide a common set of property or attribute definitions that can be reused in many contexts in which the presentation capabilities of a presentation device need to be considered. The use of well-defined Core Presentation Characteristics will simplify the task of adapting content to a specific presentation delivery context. The document sets out what is meant by 'core' and 'presentation,' what should be included in the definition of each characteristic, what should be defined when grouped characteristics into collections, and what kind of characteristics should be included in the core. It also suggests some use cases. """@en; ; cat:DocLicense; data:W3C; "Core Presentation Characteristics: Requirements and Use Cases"; ; xhv:last ; rdfs:label "Core Presentation Characteristics: Requirements and Use Cases"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-05-14"^^xsd:date; """This CSS3 Module describes how to insert and move content around a document, in order to create footnotes, endnotes, section notes. Inserted content can also introduce counters and strings, which can be used for running headers and footers, section numbering, and lists. Finally, techniques for declaring replaced images, as well as scaling and cropping them using CSS, are described."""@en; ; cat:DocLicense; data:W3C; "CSS3 Generated and Replaced Content Module"; ; xhv:last ; rdfs:label "CSS3 Generated and Replaced Content Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-08-13"^^xsd:date; """Presentation levels are integer values attached to elements in a document. Elements that are below, at, or above a certain threshold can be styled differently. This feature has two compelling use cases. First, slide presentations with transition effects can be described. For example, list items can be progressively revealed by sliding in from the side. Second, outline views of documents, where only the headings to a certain level are visible, can be generated."""@en; ; cat:DocLicense; data:W3C; "CSS3 module: Presentation Levels"; ; xhv:last ; rdfs:label "CSS3 module: Presentation Levels"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-08-13"^^xsd:date; """This CSS3 module describes the basic structure of CSS style sheets, some of the details of the syntax, and the rules for parsing CSS style sheets. It also describes (in some cases, informatively) how stylesheets can be linked to documents and how those links can be media-dependent. Additional details of the syntax of some parts of CSS described in other modules will be described in those modules. The selectors module has a grammar for selectors. Modules that define properties give the grammar for the values of those properties, in a format described in this document."""@en; ; cat:DocLicense; data:W3C; "CSS3 module: Syntax"; ; xhv:last ; rdfs:label "CSS3 module: Syntax"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-04-17"^^xsd:date; """ This is a discussion document produced by the Guidelines, Education & Outreach Task Force (GEO) of the W3C Internationalization Working Group (I18N WG). It describes plans for producing documents that provide guidelines on internationalization of W3C technologies. The Task Force encourages feedback about the content of this document as well as participation in the development of the guidelines by people who have experience creating Web content that conforms to internationalization needs. """@en; ; cat:DocLicense; data:W3C; "Framework Document for i18n Guidelines 1.0"; ; xhv:last ; rdfs:label "Framework Document for i18n Guidelines 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-02-07"^^xsd:date; """ This is a W3C Working Draft produced by the Web Content Accessibility Guidelines Working Group (WCAG WG). It describes requirements for Checklists and Techniques described by the Web Content Accessibility Guidelines 2.0 (WCAG 2.0). These requirements are related to but different from Requirements for WCAG 2.0 in that "Requirements for WCAG 2.0 Checklists and Techniques" specifies requirements for the technology-specific documents produced by the WCAG WG while "Requirements for WCAG 2.0" specifies general requirements for the general usability of documents produced by the WCAG WG. The Working Group encourages feedback about these requirements as well as participation in the development of WCAG 2.0 by people who have experience creating Web content that conforms to Web Content Accessibility Guidelines 1.0. """@en; ; cat:DocLicense; data:W3C; "Requirements for WCAG 2.0 Checklists and Techniques"; ; xhv:last ; rdfs:label "Requirements for WCAG 2.0 Checklists and Techniques"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-08-06"^^xsd:date; """ Since XML 1.0, the ability of processors to identify an XML element by an explicit identifier ("IDness") has depended upon validation. Both DTDs and [XML Schema] have mechanisms to identify the structures containing unique identifiers. But neither XML Schema nor DTDs are required by all processors. A common processor type does not perform validation, nor fetch external resources for the purpose of acertaining whether the document contains unique identifiers. This document sets out the requirements for a mechanism for determining "IDness" applicable to all classes of XML processors. """@en; ; cat:DocLicense; data:W3C; "xml:id Requirements"; ; xhv:last ; rdfs:label "xml:id Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-02-20"^^xsd:date; """ This document describes an Abstract Model of XML Protocol. The challenge of crafting a protocol specification is to create a description of behaviour that is not tied to any particular approach to implementation. There is a need to abstract away from some of the messy implementation details of buffer management, data representation and specific APIs. However, in order to describe the behaviour of a protocol one has to establish a set of (useful) concepts that can be used in that description. An abstract model is one way to establish a consistent set of concepts. An abstract model is a tool for the description of complex behaviour — it is not a template for an implementation... although it should not stray so far away from reality that it is impossible to recognise how the required behaviours would be implemented. """@en; ; cat:DocLicense; data:W3C; "XML Protocol Abstract Model"; ; xhv:last ; xhv:previous ; rdfs:label "XML Protocol Abstract Model"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-01-21"^^xsd:date; """ This document contains a list of requirements and desiderata for version 1.1 of XML Schema. """@en; ; cat:DocLicense; data:W3C; "Requirements for XML Schema 1.1"; ; xhv:last ; rdfs:label "Requirements for XML Schema 1.1"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2003-12-17"^^xsd:date; """ The XSL 1.0 specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. This document enumerates the collected requirements for a 1.1 version of XSL. """@en; ; cat:DocLicense; data:W3C; "Extensible Stylesheet Language (XSL) Version 1.1 Requirements"; ; xhv:last ; rdfs:label "Extensible Stylesheet Language (XSL) Version 1.1 Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-11-22"^^xsd:date; """ This Architectural Specification provides authors of specifications, software developers, and content developers with a common reference for the use of resource identifiers building on the Universal Character Set, defined jointly by the Unicode Standard and ISO/IEC 10646. For topics such as use of the terms 'character', 'encoding' and 'string', a reference processing model, choice and identification of character encodings, character escaping, and string indexing, see Character Model for the World Wide Web 1.0: Fundamentals [CharMod]. For normalization and string identity matching, see Character Model for the World Wide Web 1.0: Normalization [CharNorm]. """@en; ; cat:DocLicense; data:W3C; "Character Model for the World Wide Web 1.0: Resource Identifiers"; ; xhv:last ; xhv:previous ; rdfs:label "Character Model for the World Wide Web 1.0: Resource Identifiers"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-26"^^xsd:date; """ This specification defines the Document Object Model Views and Formatting Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model Views and Formatting Level 3 builds on the Document Object Model Views Level 2. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 3 Views and Formatting Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Document Object Model (DOM) Level 3 Views and Formatting Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-26"^^xsd:date; """ This specification defines the Document Object Model Level 3 XPath. It provides simple functionalities to access a DOM tree using [XPath 1.0]. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 3 XPath Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Document Object Model (DOM) Level 3 XPath Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-26"^^xsd:date; """ This document contains the requirements for the Document Object Model, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model provides a standard set of objects for representing HTML and XML documents, a standard model of how these objects can be combined, and a standard interface for accessing and manipulating them. Vendors can support the DOM as an interface to their proprietary data structures and APIs, and content authors can write to the standard DOM interfaces rather than product-specific APIs, thus increasing interoperability on the Web. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Document Object Model (DOM) Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-18"^^xsd:date; """ The document provides a summary of several techniques and best practices that Web site authors and solution providers may employ when creating and delivering content to a diverse set of access mechanisms. """@en; ; cat:DocLicense; data:W3C; "Authoring Techniques for Device Independence"; ; xhv:last ; xhv:previous ; rdfs:label "Authoring Techniques for Device Independence"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-05-10"^^xsd:date; """ This document describes the DOM capabilities needed to support a heterogeneous multimodal environment and the current state of DOM interfaces supporting those capabilities. These DOM interfaces are used between modality components and their host environment in the W3C Multimodal Interaction Framework as proposed by the W3C Multimodal Interaction Activity. The Multimodal Interaction Framework separates multimodal systems into a set of functional units, including Input and Output components, an Interaction Mananger, Session Components, System and Environment, and Application Functions. In order for those functional components to interact with each other to form an application interpreter, the browser implementation must allow for communication and coordination between those components. This DOM interface identifies the DOM APIs used to communicate and coordinate at the browser implemention level. Multimodal browsers can be stand-alone or distributed systems. """@en; ; cat:DocLicense; data:W3C; "Modality Component to Host Environment DOM Requirements and Capabilities Assessment"; ; xhv:last ; rdfs:label "Modality Component to Host Environment DOM Requirements and Capabilities Assessment"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-01-21"^^xsd:date; """An OWL-RDF parser takes an RDF/XML file and attempts to construct an OWL ontology that corresponds to the triples represented in the RDF. This document describes a basic strategy that could be used in such a parser. Note that this is not intended as a complete specification, but hopefully provides enough information to point the way towards how one would build a parser that will deal with a majority of (valid) OWL ontologies.For example, we do not discuss the implementation or handling of owl:imports here, nor do we address in depth issues concerned with spotting some of the more obscure violations of the DL/Lite rules."""@en; ; cat:DocLicense; data:W3C; "OWL Web Ontology Language Parsing OWL in RDF/XML"; ; xhv:last ; rdfs:label "OWL Web Ontology Language Parsing OWL in RDF/XML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-04-05"^^xsd:date; """ This document contains requirements for the development of XML Processing Model and Language, which are intended to describe and specify the processing relationships between XML resources. """@en; ; cat:DocLicense; data:W3C; "XML Processing Model Requirements"; ; xhv:last ; rdfs:label "XML Processing Model Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-06-08"^^xsd:date; """ This document defines a SOAP feature that represents an abstract model for SOAP attachments. It provides the basis for the creation of SOAP bindings that transmit such attachments along with a SOAP envelope, and provides for reference of those attachments from the envelope. SOAP attachments are described using the notion of a compound document structure consisting of a primary SOAP message part and zero or more related documents parts known as attachments. """@en; ; cat:DocLicense; data:W3C; "SOAP 1.2 Attachment Feature"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP 1.2 Attachment Feature"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-11"^^xsd:date; """ This document defines the Web Services Architecture. It identifies the functional components and defines the relationships among those components to effect the desired properties of the overall architecture. """@en; ; cat:DocLicense; data:W3C; "Web Services Architecture"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Architecture"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-11"^^xsd:date; """ This document describes the Web Service Architecture use cases and Usage Scenarios. It is a collection of use cases and usage scenarios which illustrate the use of Web services. They are used to generate requirements for the Web services architecture, as well as to evaluate existing technologies. """@en; ; cat:DocLicense; data:W3C; "Web Services Architecture Usage Scenarios"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Architecture Usage Scenarios"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-11"^^xsd:date; """ This document is a glossary of Web services terms defined and used in the Web Services Architecture [WS Arch]. It is intended for use by Web services spefications in order to refer to a common coherent framework. """@en; ; cat:DocLicense; data:W3C; "Web Services Glossary"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Glossary"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-11-16"^^xsd:date; """ This document describes requirements for internationalizing Web services. """@en; ; cat:DocLicense; data:W3C; "Requirements for the Internationalization of Web Services"; ; xhv:last ; xhv:previous ; rdfs:label "Requirements for the Internationalization of Web Services"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-07-30"^^xsd:date; """ This document describes internationalization usage patterns and scenarios for Web services. It also provides guidance for implementers of Web service technologies, suggesting methods for dealing with general international interoperability issues in services and service descriptions. One goal of this document is to provide a template for Web service designers to implement international capabilities in their services. """@en; ; cat:DocLicense; data:W3C; "Web Services Internationalization Usage Scenarios"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Internationalization Usage Scenarios"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-11"^^xsd:date; """ The use of Web services on the World Wide Web is expanding rapidly as the need for application-to-application communication and interoperability grows. These services provide a standard means of communication among different software applications involved in presenting dynamic context-driven information to the user. In order to promote interoperability and extensibility among these applications, as well as to allow them to be combined in order to perform more complex operations, a standard reference architecture is needed. The Web Services Architecture Working Group at W3C is tasked with producing this reference architecture [WSARCH]. This document describes a set of requirements for a standard reference architecture for Web services developed by the Web Services Architecture Working Group. These requirements are intended to guide the development of the reference architecture and provide a set of measurable constraints on Web services implementations by which conformance can be determined. """@en; ; cat:DocLicense; data:W3C; "Web Services Architecture Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Architecture Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-11"^^xsd:date; """ This document describes the life cycle of a Web service, and of the processing of a request by a Web service. """@en; ; cat:DocLicense; data:W3C; "Web Service Management: Service Life Cycle"; ; xhv:last ; rdfs:label "Web Service Management: Service Life Cycle"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-08-31"^^xsd:date; """XForms is an XML application that represents the next generation of forms for the Web. This document specifies the requirements for XForms 1.1."""@en; ; cat:DocLicense; data:W3C; "XForms 1.1 Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "XForms 1.1 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-06-08"^^xsd:date; """This document lists and provides answers to some frequently asked questions about the design decisions behind the choice of include mechanism by the XML Protocol Working Group during construction of XML-binary Optimized Packaging (XOP). For more information about XOP, see the Working Group Home Page."""@en; ; cat:DocLicense; data:W3C; "XOP Inclusion Mechanism - Frequently Asked Questions"; ; xhv:last ; rdfs:label "XOP Inclusion Mechanism - Frequently Asked Questions"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-01-15"^^xsd:date; """ This document describes CC/PP (Composite Capabilities/Preference Profiles) structure and vocabularies. A CC/PP profile is a description of device capabilities and user preferences. This is often referred to as a device's delivery context and can be used to guide the adaptation of content presented to that device. The Resource Description Framework (RDF) is used to create profiles that describe user agent capabilities and preferences. The structure of a profile is discussed. Topics include: structure of client capability and preference descriptions, ANDuse of RDF classes to distinguish different elements of a profile, so that a schema-aware RDF processor can handle CC/PP profiles embedded in other XML document types. CC/PP vocabulary is identifiers (URIs) used to refer to specific capabilities and preferences, and covers: the types of values to which CC/PP attributes may refer,an appendix describing how to introduce new vocabularies,an appendix giving an example small client vocabulary covering print and display capabilities, andan appendix providing a survey of existing work from which new vocabularies may be derived. """@en; ; cat:DocLicense; data:W3C; "Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-04-07"^^xsd:date; """ This specification defines the Document Object Model Core Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model Core Level 3 builds on the Document Object Model Core Level 2 [DOM Level 2 Core]. This version enhances DOM Level 2 Core by completing the mapping between DOM and the XML Information Set [XML Information Set], including the support for XML Base [XML Base], adding the ability to attach user information to DOM Nodes or to bootstrap a DOM implementation, providing mechanisms to resolve namespace prefixes or to manipulate "ID" attributes, giving to type information, etc. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 3 Core Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Document Object Model (DOM) Level 3 Core Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-04-07"^^xsd:date; """ This specification defines the Document Object Model Load and Save Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically load the content of an XML document into a DOM document and serialize a DOM document into an XML document; DOM documents being defined in [DOM Level 2 Core] or newer, and XML documents being defined in [XML 1.0] or newer. It also allows filtering of content at load time and at serialization time. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 3 Load and Save Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Document Object Model (DOM) Level 3 Load and Save Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-01-27"^^xsd:date; """ This specification defines the Document Object Model Validation Level 3, a platform- and language-neutral interface. This module provides the guidance to programs and scripts to dynamically update the content and the structure of documents while ensuring that the document remains valid, or to ensure that the document becomes valid. """@en; ; cat:DocLicense; data:W3C; "Document Object Model (DOM) Level 3 Validation Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Document Object Model (DOM) Level 3 Validation Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """ The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans. OWL facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. OWL has three increasingly-expressive sublanguages: OWL Lite, OWL DL, and OWL Full. This document is written for readers who want a first impression of the capabilities of OWL. It provides an introduction to OWL by informally describing the features of each of the sublanguages of OWL. Some knowledge of RDF Schema is useful for understanding this document, but not essential. After this document, interested readers may turn to the OWL Guide for more detailed descriptions and extensive examples on the features of OWL. The normative formal definition of OWL can be found in the OWL Semantics and Abstract Syntax. """@en; ; cat:DocLicense; data:W3C; "OWL Web Ontology Language Overview"; ; xhv:last ; xhv:previous ; rdfs:label "OWL Web Ontology Language Overview"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """ The World Wide Web as it is currently constituted resembles a poorly mapped geography. Our insight into the documents and capabilities available are based on keyword searches, abetted by clever use of document connectivity and usage patterns. The sheer mass of this data is unmanageable without powerful tool support. In order to map this terrain more precisely, computational agents require machine-readable descriptions of the content and capabilities of Web accessible resources. These descriptions must be in addition to the human-readable versions of that information. The OWL Web Ontology Language is intended to provide a language that can be used to describe the classes and relations between them that are inherent in Web documents and applications. This document demonstrates the use of the OWL language to formalize a domain by defining classes and properties of those classes,define individuals and assert properties about them, andreason about these classes and individuals to the degree permitted by the formal semantics of the OWL language. The sections are organized to present an incremental definition of a set of classes, properties and individuals, beginning with the fundamentals and proceeding to more complex language components. """@en; ; cat:DocLicense; data:W3C; "OWL Web Ontology Language Guide"; ; xhv:last ; xhv:previous ; rdfs:label "OWL Web Ontology Language Guide"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """ The Web Ontology Language OWL is a semantic markup language for publishing and sharing ontologies on the World Wide Web. OWL is developed as a vocabulary extension of RDF (the Resource Description Framework) and is derived from the DAML+OIL Web Ontology Language. This document contains a structured informal description of the full set of OWL language constructs and is meant to serve as a reference for OWL users who want to construct OWL ontologies. """@en; ; cat:DocLicense; data:W3C; "OWL Web Ontology Language Reference"; ; xhv:last ; xhv:previous ; rdfs:label "OWL Web Ontology Language Reference"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """ This description of OWL, the Web Ontology Language being designed by the W3C Web Ontology Working Group, contains a high-level abstract syntax for both OWL DL and OWL Lite, sublanguages of OWL. A model-theoretic semantics is given to provide a formal meaning for OWL ontologies written in this abstract syntax. A model-theoretic semantics in the form of an extension to the RDF semantics is also given to provide a formal meaning for OWL ontologies as RDF graphs (OWL Full). A mapping from the abstract syntax to RDF graphs is given and the two model theories are shown to have the same consequences on OWL ontologies that can be written in the abstract syntax. """@en; ; cat:DocLicense; data:W3C; "OWL Web Ontology Language Semantics and Abstract Syntax"; ; xhv:last ; xhv:previous ; rdfs:label "OWL Web Ontology Language Semantics and Abstract Syntax"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """ This document contains and presents test cases for the Web Ontology Language (OWL) approved by the Web Ontology Working Group. Many of the test cases illustrate the correct usage of the Web Ontology Language (OWL), and the formal meaning of its constructs. Other test cases illustrate the resolution of issues considered by the Working Group. Conformance for OWL documents and OWL document checkers is specified. """@en; ; cat:DocLicense; data:W3C; "OWL Web Ontology Language Test Cases"; ; xhv:last ; xhv:previous ; rdfs:label "OWL Web Ontology Language Test Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """The Resource Description Framework (RDF) is a framework for representing information in the Web.RDF Concepts and Abstract Syntax defines an abstract syntax on which RDF is based, and which serves to link its concrete syntax to its formal semantics. It also includes discussion of design goals, key concepts, datatyping, character normalization and handling of URI references."""@en; ; cat:DocLicense; data:W3C; "Resource Description Framework (RDF): Concepts and Abstract Syntax"; ; xhv:last ; xhv:previous ; rdfs:label "Resource Description Framework (RDF): Concepts and Abstract Syntax"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """This is a specification of a precise semantics, and corresponding complete systems of inference rules, for the Resource Description Framework (RDF) and RDF Schema (RDFS)."""@en; ; cat:DocLicense; data:W3C; "RDF Semantics"; ; xhv:last ; xhv:previous ; rdfs:label "RDF Semantics"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """ The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. This Primer is designed to provide the reader with the basic knowledge required to effectively use RDF. It introduces the basic concepts of RDF and describes its XML syntax. It describes how to define RDF vocabularies using the RDF Vocabulary Description Language, and gives an overview of some deployed RDF applications. It also describes the content and purpose of other RDF specification documents. """@en; ; cat:DocLicense; data:W3C; "RDF Primer"; ; xhv:last ; xhv:previous ; rdfs:label "RDF Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """ The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. This specification describes how to use RDF to describe RDF vocabularies. This specification defines a vocabulary for this purpose and defines other built-in RDF vocabulary initially specified in the RDF Model and Syntax Specification. """@en; ; cat:DocLicense; data:W3C; "RDF Vocabulary Description Language 1.0: RDF Schema"; ; xhv:last ; xhv:previous ; rdfs:label "RDF Vocabulary Description Language 1.0: RDF Schema"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web.This document defines an XML syntax for RDF called RDF/XML in terms of Namespaces in XML, the XML Information Set and XML Base. The formal grammar for the syntax is annotated with actions generating triples of the RDF graph as defined in RDF Concepts and Abstract Syntax. The triples are written using the N-Triples RDF graph serializing format which enables more precise recording of the mapping in a machine processable form. The mappings are recorded as tests cases, gathered and published in RDF Test Cases."""@en; ; cat:DocLicense; data:W3C; "RDF/XML Syntax Specification (Revised)"; ; xhv:last ; xhv:previous ; rdfs:label "RDF/XML Syntax Specification (Revised)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """This document describes the RDF Test Cases deliverable for the RDF Core Working Group as defined in the Working Group's Charter."""@en; ; cat:DocLicense; data:W3C; "RDF Test Cases"; ; xhv:last ; xhv:previous ; rdfs:label "RDF Test Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-03-16"^^xsd:date; """ This document defines syntax for representing grammars for use in speech recognition so that developers can specify the words and patterns of words to be listened for by a speech recognizer. The syntax of the grammar format is presented in two forms, an Augmented BNF Form and an XML Form. The specification makes the two representations mappable to allow automatic transformations between the two forms. """@en; ; cat:DocLicense; data:W3C; "Speech Recognition Grammar Specification Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Speech Recognition Grammar Specification Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-09-07"^^xsd:date; """ The Voice Browser Working Group has sought to develop standards to enable access to the Web using spoken interaction. The Speech Synthesis Markup Language Specification is one of these standards and is designed to provide a rich, XML-based markup language for assisting the generation of synthetic speech in Web and other applications. The essential role of the markup language is to provide authors of synthesizable content a standard way to control aspects of speech such as pronunciation, volume, pitch, rate, etc. across different synthesis-capable platforms. """@en; ; cat:DocLicense; data:W3C; "Speech Synthesis Markup Language (SSML) Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Speech Synthesis Markup Language (SSML) Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-03-16"^^xsd:date; """ This document specifies VoiceXML, the Voice Extensible Markup Language. VoiceXML is designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed initiative conversations. Its major goal is to bring the advantages of Web-based development and content delivery to interactive voice response applications. """@en; ; cat:DocLicense; data:W3C; "Voice Extensible Markup Language (VoiceXML) Version 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Voice Extensible Markup Language (VoiceXML) Version 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-12-15"^^xsd:date; """ The World Wide Web uses relatively simple technologies with sufficient scalability, efficiency and utility that they have resulted in a remarkable information space of interrelated resources, growing across languages, cultures, and media. In an effort to preserve these properties of the information space as the technologies evolve, this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space. We relate core design components, constraints, and good practices to the principles and properties they support. """@en; ; cat:DocLicense; data:W3C; "Architecture of the World Wide Web, Volume One"; ; xhv:last ; xhv:previous ; rdfs:label "Architecture of the World Wide Web, Volume One"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-10"^^xsd:date; """ This document specifies usage scenarios, goals and requirements for a web ontology language. An ontology formally defines a common set of terms that are used to describe and represent a domain. Ontologies can be used by automated tools to power advanced services such as more accurate web search, intelligent software agents and knowledge management. """@en; ; cat:DocLicense; data:W3C; "OWL Web Ontology Language Use Cases and Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "OWL Web Ontology Language Use Cases and Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-12-20"^^xsd:date; """ This document specifies a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references). """@en; ; cat:DocLicense; data:W3C; "XML Inclusions (XInclude) Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "XML Inclusions (XInclude) Version 1.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-04"^^xsd:date; """ 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. """@en; ; cat:DocLicense; data:W3C; "Extensible Markup Language (XML) 1.0 (Third Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Extensible Markup Language (XML) 1.0 (Third Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-04"^^xsd:date; """ This specification provides a set of definitions for use in other specifications that need to refer to the information in an XML document. """@en; ; cat:DocLicense; data:W3C; "XML Information Set (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Information Set (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-04"^^xsd:date; """ XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by IRI references. """@en; ; cat:DocLicense; data:W3C; "Namespaces in XML 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "Namespaces in XML 1.1"; :accessURL ; :status , , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-04"^^xsd:date; """ 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. """@en; ; cat:DocLicense; data:W3C; "Extensible Markup Language (XML) 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "Extensible Markup Language (XML) 1.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-10-28"^^xsd:date; """ XML Schema Part 0: Primer is a non-normative document intended to provide an easily readable description of the XML Schema facilities, and is oriented towards quickly understanding how to create schemas using the XML Schema language. XML Schema Part 1: Structures and XML Schema Part 2: Datatypes provide the complete normative description of the XML Schema language. This primer describes the language features through numerous examples which are complemented by extensive references to the normative texts. """@en; ; cat:DocLicense; data:W3C; "XML Schema Part 0: Primer Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "XML Schema Part 0: Primer Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-10-28"^^xsd:date; """ XML Schema: Structures specifies the XML Schema definition language, which offers facilities for describing the structure and constraining the contents of XML 1.0 documents, including those which exploit the XML Namespace facility. The schema language, which is itself represented in XML 1.0 and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML 1.0 document type definitions (DTDs). This specification depends on XML Schema Part 2: Datatypes. """@en; ; cat:DocLicense; data:W3C; "XML Schema Part 1: Structures Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "XML Schema Part 1: Structures Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-10-28"^^xsd:date; """ XML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML 1.0, provides a superset of the capabilities found in XML 1.0 document type definitions (DTDs) for specifying datatypes on elements and attributes. """@en; ; cat:DocLicense; data:W3C; "XML Schema Part 2: Datatypes Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "XML Schema Part 2: Datatypes Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-24"^^xsd:date; """This is the first draft of the CSS3 Hyperlink Presentation Module. It is published to get some early feedback. The properties in it and even the scope of the draft are still very unstable. The draft may be dropped or merged with another.CSS (Cascading Style Sheets) is a simple language for describing the presentation of documents. This specification is a module of level 3 of CSS and contains the functionality required to describe the presentation of hyperlink source anchors and the effects of hyperlink activation."""@en; ; cat:DocLicense; data:W3C; "CSS3 Hyperlink Presentation Module"; ; xhv:last ; rdfs:label "CSS3 Hyperlink Presentation Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-24"^^xsd:date; """This is the first draft of the 'reader' media type. It is published to get some early feedback, especially on whether 'reader' is necessary and implementable.'Reader' is a keyword for use in Media Queries [MEDIAQ]. When a Media Query that includes the 'reader' keyword is attached to (a link to) a style sheet, it indicates that that style sheet is designed to be used by a "reader" device (typically a screen reader), that both displays and speaks a document at the same time. It may also display the document and render it in braille at the same time, or do all three.Media Queries (and thus 'reader') can be used in documents in HTML [HTML401], XML [XML10], SVG [SVG10], CSS [CSS21] and other formats, wherever they link to a style sheet, and potentially also in links to other resources. (But the latter is not treated in this specification.)"""@en; ; cat:DocLicense; data:W3C; "The CSS 'Reader' Media Type"; ; xhv:last ; rdfs:label "The CSS 'Reader' Media Type"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-05-09"^^xsd:date; """ It is important to consider character encoding matters when producing internationalization content, and further to understand how to choose and declare encodings, how and when to use character escapes, etc. 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. It focuses specifically on advice about character sets, encodings, and other character-specific matters. It is produced by the Guidelines, Education & Outreach Task Force (GEO) of the W3C Internationalization Working Group (I18N WG). The GEO Task Force encourages feedback about the content of this document as well as participation in the development of the techniques by people who have experience creating Web content that conforms to internationalization needs. """@en; ; cat:DocLicense; data:W3C; "Authoring Techniques for XHTML & HTML Internationalization: Characters and Encodings 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Authoring Techniques for XHTML & HTML Internationalization: Characters and Encodings 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-10-29"^^xsd:date; """ The W3C Voice Browser Working Group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirements studies for voice browsers, and provides details of the requirements for markup used for specifying application specific pronunciation lexicons. Application specific pronunciation lexicons are required in many situations where the default lexicon supplied with a speech recognition or speech synthesis processor does not cover the vocabulary of the application. A pronunciation lexicon is a collection of words or phrases together with their pronunciations specified using an appropriate pronunciation alphabet. """@en; ; cat:DocLicense; data:W3C; "Pronunciation Lexicon Specification (PLS) Version 1.0 Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Pronunciation Lexicon Specification (PLS) Version 1.0 Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-08-20"^^xsd:date; """The principal goal of QA Framework: Test Guidelines is to help W3C Working Groups to develop more useful and usable test materials. The material is to be presented as a set of principles and good practices. This document is one in a family of QA Framework documents of the Quality Assurance (QA) Activity. The other existing or in-progress specifications are: The QA Handbook, and Specification Guidelines."""@en; ; cat:DocLicense; data:W3C; "QA Framework: Test Guidelines"; ; xhv:last ; xhv:previous ; rdfs:label "QA Framework: Test Guidelines"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-06-08"^^xsd:date; """ This document records the use cases and specifies the requirements for optimizing the processing and serialization of SOAP messages. """@en; ; cat:DocLicense; data:W3C; "SOAP Optimized Serialization Use Cases and Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Optimized Serialization Use Cases and Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-03-24"^^xsd:date; """ It's purpose is to provide an information model that describes the data and the relationships between them that is needed to define a choreography that describes the sequence and conditions in which the data exchanged between two or more participants in order to meet some useful purpose. """@en; ; cat:DocLicense; data:W3C; "WS Choreography Model Overview"; ; xhv:last ; rdfs:label "WS Choreography Model Overview"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-03-11"^^xsd:date; """ As the momentum around Web Services grows, the need for effective mechanisms to co-ordinate the interactions among Web Services and their users becomes more pressing. The Web Services Choreography Working Group has been tasked with the development of such a mechanism in an interoperable way. This document describes a set of requirements for Web Services choreography based around a set of representative use cases, as well as general requirements for interaction among Web Services. This document is intended to be consistent with other efforts within the W3C Web Services Activity. """@en; ; cat:DocLicense; data:W3C; "Web Services Choreography Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Choreography Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2004-02-18"^^xsd:date; """This document is the second edition of Modularization of XHTML, an abstract modularization of XHTML and implementations of the abstraction using XML Document Type Definitions (DTDs), and XML Schemas. This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms. The second edition of this document provides several minor updates to provide clarifications and address errors found in the first edition."""@en; ; cat:DocLicense; data:W3C; "Modularization of XHTML™ 1.0 - Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "Modularization of XHTML™ 1.0 - Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-11-09"^^xsd:date; """ The Web Services Choreography Description Language (WS-CDL) is an XML-based language that describes peer-to-peer collaborations of participants by defining, from a global viewpoint, their common and complementary observable behavior; where ordered message exchanges result in accomplishing a common business goal. The Web Services specifications offer a communication bridge between the heterogeneous computational environments used to develop and host applications. The future of E-Business applications requires the ability to perform long-lived, peer-to-peer collaborations between the participating services, within or across the trusted domains of an organization. The Web Services Choreography specification is targeted for composing interoperable, peer-to-peer collaborations between any type of participant regardless of the supporting platform or programming model used by the implementation of the hosting environment. """@en; ; cat:DocLicense; data:W3C; "Web Services Choreography Description Language Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Choreography Description Language Version 1.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-12-19"^^xsd:date; """ This document describes the use cases for a framework that combines documents by reference and the set of requirements for such a framework. """@en; ; cat:DocLicense; data:W3C; "Compound Document by Reference Use Cases and Requirements Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Compound Document by Reference Use Cases and Requirements Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-12-20"^^xsd:date; """Web access from mobile devices suffers from problems that make the Web unattractive for most mobile users. W3C's Mobile Web Initiative (MWI ) proposes to address these issues through a concerted effort of key players in the mobile value chain, including authoring tool vendors, content providers, handset manufacturers, browser vendors and mobile operators.To help frame the development of "best practices" for the mobile Web this document - created by the members of the Mobile Web Initiative Best Practices Working Group ( BPWG) as an elaboration of its charter - identifies the nature of problems to be solved, outlines the scope of work to be undertaken and specifies the assumptions regarding the target audience and the anticipated deliverables. The BPWG has recently published the first public working draft of its initial Mobile Web Best Practices recommendations [BP]."""@en; ; cat:DocLicense; data:W3C; "Scope of Mobile Web Best Practices"; ; xhv:last ; xhv:previous ; rdfs:label "Scope of Mobile Web Best Practices"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-09-06"^^xsd:date; """The QA Handbook (QAH) is a non-normative handbook about the process and operational aspects of certain quality assurance practices of W3C's Working Groups, with particular focus on testability and test topics. It is intended for Working Group chairs and team contacts. It aims to help them to avoid known pitfalls and benefit from experiences gathered from the W3C Working Groups themselves. It provides techniques, tools, and templates that should facilitate and accelerate their work. This document is one of the QA Framework (QAF) family of documents of the Quality Assurance (QA) Activity. QAF includes the other in-progress specification, Specification Guidelines, Test Development FAQ, plus a handful of test- and other QA-related notes, advanced topics, and Wiki page collections."""@en; ; cat:DocLicense; data:W3C; "The QA Handbook"; ; xhv:last ; xhv:previous ; rdfs:label "The QA Handbook"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-09-29"^^xsd:date; """This report discusses an effort to apply the Resource Description Framework (RDF) to iCalendar data in order to integrate calendar data with other Semantic Web data such as social networking data, syndicated content, and multimedia meta-data. We demonstrate the effectiveness of a test-driven approach to vocabulary development and we discuss a number of social as well as technical issues."""@en; ; cat:DocLicense; data:W3C; "RDF Calendar - an application of the Resource Description Framework to iCalendar Data"; ; xhv:last ; rdfs:label "RDF Calendar - an application of the Resource Description Framework to iCalendar Data"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-08-31"^^xsd:date; """This document details and deepens some of the most important concepts related to conformance when designing a specification. It is a companion document of QA Specification Guidelines. It analyzes how design decisions of a specification's conformance model may affect its implementability and the interoperability of its implementations."""@en; ; cat:DocLicense; data:W3C; "Variability in Specifications"; ; xhv:last ; xhv:previous ; rdfs:label "Variability in Specifications"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-05-26"^^xsd:date; """ The say-as element in SSML 1.0 is considered one of the most useful elements of the language. However, SSML 1.0 does not define the values of the attributes of this element. This Note provides definitions for these attributes that cover many of the most common use cases for the say-as element. """@en; ; cat:DocLicense; data:W3C; "SSML 1.0 say-as attribute values"; ; xhv:last ; rdfs:label "SSML 1.0 say-as attribute values"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-04-05"^^xsd:date; """ This document addresses the issue of using classes as property values in OWL and RDF Schema. It is often convenient to put a class (e.g., Animal) as a property value (e.g., topic or book subject) when building an ontology. While OWL Full and RDF Schema do not put any restriction on using classes as property values, in OWL DL and OWL Lite most properties cannot have classes as their values. We illustrate the direct approach for representing classes as property values in OWL-Full and RDF Schema. We present various alternative mechanisms for representing the required information in OWL DL and OWL Lite. For each approach, we discuss various considerations that the users should keep in mind when choosing the best approach for their purposes. """@en; ; cat:DocLicense; data:W3C; "Representing Classes As Property Values on the Semantic Web"; ; xhv:last ; xhv:previous ; rdfs:label "Representing Classes As Property Values on the Semantic Web"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-05-17"^^xsd:date; """ Modelling various descriptive "features" (also known variously as "qualities", "attributes" or "modifiers") is a frequent requirement when creating ontologies. For example: "size" may describe persons or other physical objects and be constrained to take the values "small", "medium" or "large"; rank may describe military officers and restricted to a specific list of values depending on the military organisation. In OWL such descriptive features are modelled as properties whose range specifies the constraints on the values that the property can take on. This document describes two methods to represent such features and their specified values: 1) as partitions of classes; and 2) as enumerations of individuals. It does not discuss the use of datatypes to represent lists of values. """@en; ; cat:DocLicense; data:W3C; "Representing Specified Values in OWL: \"value partitions\" and \"value sets\""; ; xhv:last ; xhv:previous ; rdfs:label "Representing Specified Values in OWL: \"value partitions\" and \"value sets\""; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-09-14"^^xsd:date; """The definition and provision of metadata has proved helpful in a variety of ways during the test development and test execution processes. This document defines a minimal set of metadata elements that can usefully be applied to tests that are intended for publication within a test suite."""@en; ; cat:DocLicense; data:W3C; "Test Metadata"; ; xhv:last ; rdfs:label "Test Metadata"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-11-23"^^xsd:date; """A common method of limiting access to services made available over the Web is visual verification of a bitmapped image. This presents a major problem to users who are blind, have low vision, or have a learning disability such as dyslexia. This document examines a number of potential solutions that allow systems to test for human users while preserving access by users with disabilities."""@en; ; cat:DocLicense; data:W3C; "Inaccessibility of CAPTCHA"; ; xhv:last ; xhv:previous ; rdfs:label "Inaccessibility of CAPTCHA"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-08-17"^^xsd:date; """ This document captures the result of discussions by the Web Services Description Working Group regarding WSDL 2.0 type system extensibilty at the time of its publication. The Working Group normatively defines the use of XML Schema 1.0 as a type system in the WSDL 2.0 Core specification. This document sketches out the basics of extensions for Document Type Definitions (DTDs) and Relax NG. """@en; ; cat:DocLicense; data:W3C; "Discussion of Alternative Schema Languages and Type System Support in WSDL 2.0"; ; xhv:last ; rdfs:label "Discussion of Alternative Schema Languages and Type System Support in WSDL 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-03-31"^^xsd:date; """ This document describes the processes and results of the XML Binary Characterization Working Group in evaluating the need and feasibility of a "binary XML" recommendation. It includes an analysis of which properties such a format must possess. It recommends that the W3C produce a "binary XML" recommendation and enumerates the minimum requirements which this "binary XML" recommendation must meet. """@en; ; cat:DocLicense; data:W3C; "XML Binary Characterization"; ; xhv:last ; rdfs:label "XML Binary Characterization"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-03-31"^^xsd:date; """ This document describes measurement aspects, methods, caveats, test data, and test scenarios for evaluating the potential benefits of a candidate binary XML format. """@en; ; cat:DocLicense; data:W3C; "XML Binary Characterization Measurement Methodologies"; ; xhv:last ; xhv:previous ; rdfs:label "XML Binary Characterization Measurement Methodologies"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-03-31"^^xsd:date; """ This document is the result of a study to identify desirable properties in an XML format. An XML format is a format that is capable of representing the information in an XML document. The properties have been derived from requirements induced by use cases collected in the [XBC Use Cases] document. Properties are divided into two categories: algorithmic and format. Besides these two categories, Section 6 Additional Considerations lists additional considerations which, because of the difficulty to establish an accurate measurement, have not been listed as properties but are nonetheless relevant for an accurate comparison between different proposals. """@en; ; cat:DocLicense; data:W3C; "XML Binary Characterization Properties"; ; xhv:last ; xhv:previous ; rdfs:label "XML Binary Characterization Properties"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-03-31"^^xsd:date; """ This document describes use cases for evaluating the potential benefits of an efficient serialization format for XML. The use cases are documented here to understand the constraints involved in environments for which XML employment may be problematic because of one or more characteristics of XML. Desirable properties of XML and alternative formats to address the use cases are derived and discussed in a separate publication of the XML Binary Characterization Working Group (XBC WG) [XBC Properties]. """@en; ; cat:DocLicense; data:W3C; "XML Binary Characterization Use Cases"; ; xhv:last ; xhv:previous ; rdfs:label "XML Binary Characterization Use Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-12-19"^^xsd:date; """ The XML Key Management Specification (XKMS 2.0) [XKMS] aims at providing a PKI independent interface to key management. XKMS services comprise discovery and validation of keys as well as support for certain aspects of the key life cycle management, including registration, reissuance and revocation. XKMS employs XML Signature [XMLSIG] for the purpose of providing message security in the form of authentication and integrity. In addition, XKMS is based on the use of the element as a means of transporting key information used as templates for the various operations it specifies. This technical note addresses some of the issues related to the use of XKMS in conjunction with PGP [PGP]. """@en; ; cat:DocLicense; data:W3C; "Using XKMS with PGP"; ; xhv:last ; rdfs:label "Using XKMS with PGP"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-11-18"^^xsd:date; """ The XML Key Management Specification (XKMS 2.0) is a W3C Recommendation that specifies protocols for distributing and registering public keys. The XML Key Management Service (XKMS) Working Group has defined a Web Service to handle conventional PKI (public-key infrastructure) functions such as registration, revocation and status, as well as related functions such as retrieval. This note provides a sample Web Services Description Language (WSDL) 1.1 description for an XKMS service. It is intended that XKMS developers use this as a "first draft" for developing their own version. Conversion to WSDL 2.0 should be fairly straightforward, once that specification completes its Last Call. """@en; ; cat:DocLicense; data:W3C; "A WSDL 1.1 description for XKMS"; ; xhv:last ; rdfs:label "A WSDL 1.1 description for XKMS"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-01-27"^^xsd:date; """ This document describes some useful changes that could be incorporated into an XLink 1.1 Specification. """@en; ; cat:DocLicense; data:W3C; "Extending XLink 1.0"; ; xhv:last ; rdfs:label "Extending XLink 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-05-04"^^xsd:date; """ This document addresses the need to indicate the content-type associated with binary element content in an XML document and the need to specify, in XML Schema, the expected content-type(s) associated with binary element content. It is expected that the additional information about the content-type will be used for optimizing the handling of binary data that is part of a Web services message. """@en; ; cat:DocLicense; data:W3C; "Describing Media Content of Binary Data in XML"; ; xhv:last ; xhv:previous ; rdfs:label "Describing Media Content of Binary Data in XML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-05-11"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Processing XML 1.1 documents with XML Schema 1.0 processors"; ; xhv:last ; rdfs:label "Processing XML 1.1 documents with XML Schema 1.0 processors"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-12-13"^^xsd:date; """ This document specifies the second version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL 2.1 has the following design goals: Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL, an author can describe the temporal behaviour of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen.Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL components are used for integrating timing into XHTML [XHTML10] and into SVG [SVG].Extend the functionalities contained in the SMIL 2.0 [SMIL20] into new or revised SMIL 2.1 modules.Define new SMIL 2.1 Mobile Profiles incorporating features useful within the mobile industry. """@en; ; cat:DocLicense; data:W3C; "Synchronized Multimedia Integration Language (SMIL 2.1)"; ; xhv:last ; xhv:previous ; rdfs:label "Synchronized Multimedia Integration Language (SMIL 2.1)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-02-15"^^xsd:date; """ This Architectural Specification provides authors of specifications, software developers, and content developers with a common reference for interoperable text manipulation on the World Wide Web, building on the Universal Character Set, defined jointly by the Unicode Standard and ISO/IEC 10646. Topics addressed include use of the terms 'character', 'encoding' and 'string', a reference processing model, choice and identification of character encodings, character escaping, and string indexing. For normalization and string identity matching, see the companion document Character Model for the World Wide Web 1.0: Normalization [CharNorm]. For resource identifiers, see the companion document Character Model for the World Wide Web 1.0: Resource Identifiers [CharIRI]. """@en; ; cat:DocLicense; data:W3C; "Character Model for the World Wide Web 1.0: Fundamentals"; ; xhv:last ; xhv:previous ; rdfs:label "Character Model for the World Wide Web 1.0: Fundamentals"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-08-17"^^xsd:date; """The goal of this document is to help W3C editors write better specifications, by making a specification easier to interpret without ambiguity and clearer as to what is required in order to conform. It focuses on how to define and specify conformance. It also addresses how a specification might allow variation among conforming implementations. The document presents guidelines or requirements, supplemented with good practices, examples and techniques."""@en; ; cat:DocLicense; data:W3C; "QA Framework: Specification Guidelines"; ; xhv:last ; xhv:previous ; rdfs:label "QA Framework: Specification Guidelines"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-01-25"^^xsd:date; """ This document describes an abstract feature and a concrete implementation of it for optimizing the transmission and/or wire format of SOAP messages. The concrete implementation relies on the [XML-binary Optimized Packaging] format for carrying SOAP messages. """@en; ; cat:DocLicense; data:W3C; "SOAP Message Transmission Optimization Mechanism"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Message Transmission Optimization Mechanism"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-01-25"^^xsd:date; """ This document describes the semantics and serialization of a SOAP header block for carrying resource representations in SOAP messages. """@en; ; cat:DocLicense; data:W3C; "Resource Representation SOAP Header Block"; ; xhv:last ; xhv:previous ; rdfs:label "Resource Representation SOAP Header Block"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-06-28"^^xsd:date; """ [2]This document specifies protocols for distributing and registering public keys, suitable for use in conjunction with the W3C Recommendations for XML Signature [XML-SIG] and XML Encryption [XML-Enc]. The XML Key Management Specification (XKMS) comprises two parts — the XML Key Information Service Specification (X-KISS) and the XML Key Registration Service Specification (X-KRSS). """@en; ; cat:DocLicense; data:W3C; "XML Key Management Specification (XKMS 2.0)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Key Management Specification (XKMS 2.0)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-06-28"^^xsd:date; """ [2]This document specifies protocol bindings with security characteristics for the XML Key Management Specification (XKMS). """@en; ; cat:DocLicense; data:W3C; "XML Key Management Specification (XKMS 2.0) Bindings"; ; xhv:last ; xhv:previous ; rdfs:label "XML Key Management Specification (XKMS 2.0) Bindings"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-09-09"^^xsd:date; """ This document defines the meaning of the attribute xml:id as an ID attribute in XML documents and defines processing of this attribute to identify IDs in the absence of validation, without fetching external resources, and without relying on an internal subset. """@en; ; cat:DocLicense; data:W3C; "xml:id Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "xml:id Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-01-25"^^xsd:date; """ This document defines the XML-binary Optimized Packaging (XOP) convention, a means of more efficiently serializing XML Infosets that have certain types of content. """@en; ; cat:DocLicense; data:W3C; "XML-binary Optimized Packaging"; ; xhv:last ; xhv:previous ; rdfs:label "XML-binary Optimized Packaging"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-12-19"^^xsd:date; """ This document describes the use cases for a framework that combines documents and the set of requirements for such a framework. """@en; ; cat:DocLicense; data:W3C; "Compound Document Use Cases and Requirements Version 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Compound Document Use Cases and Requirements Version 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-04-13"^^xsd:date; """This specification is a placeholder for an updated draft of the Scalable Vector Graphics (SVG) Full, Version 1.2 specification. SVG is a modularized XML language for describing two-dimensional graphics with animation and interactivity, and a set of APIs upon which to build graphics-based applications. The next draft of SVG 1.2 Full will structured as a superset of the SVG 1.2 Tiny language extending the declarative, interactive and API functionality available."""@en; ; cat:DocLicense; data:W3C; "Scalable Vector Graphics (SVG) Full 1.2 Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Scalable Vector Graphics (SVG) Full 1.2 Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-12-15"^^xsd:date; """This CSS3 module describes how values are assigned to properties. CSS allows several style sheets to influence the rendering of a document, and the process of combining these style sheets is called “cascading”. If no value can be found through cascading, a value can be inherited from the parent element or the property's initial value is used."""@en; ; cat:DocLicense; data:W3C; "CSS3 module: Cascading and inheritance"; ; xhv:last ; xhv:previous ; rdfs:label "CSS3 module: Cascading and inheritance"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-01-18"^^xsd:date; """This document is a glossary of terms used in other documents produced by the Device Independence Working Group (DIWG). Details of the entire series of documents can be found on the W3C Device Independence Activity home page."""@en; ; cat:DocLicense; data:W3C; "Glossary of Terms for Device Independence"; ; xhv:last ; xhv:previous ; rdfs:label "Glossary of Terms for Device Independence"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-03-25"^^xsd:date; """ This document specifies use cases, requirements, and objectives for an RDF query language and data access protocol. It suggests how an RDF query language and data access protocol could be used in the construction of novel, useful Semantic Web applications in areas like web publishing, personal information management, transportation, and tourism. """@en; ; cat:DocLicense; data:W3C; "RDF Data Access Use Cases and Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "RDF Data Access Use Cases and Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-08-15"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "SVG's XML Binding Language (sXBL)"; ; xhv:last ; xhv:previous ; rdfs:label "SVG's XML Binding Language (sXBL)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-10-24"^^xsd:date; """ The RDF Data Access Working Group normatively defines the SPARQL Protocol for RDF via a Web Services Description Language version 2.0 (WSDL 2.0) definition. This document presents a non-normative WSDL 1.1 document defining the same protocol. """@en; ; cat:DocLicense; data:W3C; "SPARQL Protocol for RDF Using WSDL 1.1"; ; xhv:last ; rdfs:label "SPARQL Protocol for RDF Using WSDL 1.1"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-11-02"^^xsd:date; """ SKOS Core provides a model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies. The SKOS Core Vocabulary is an application of the Resource Description Framework (RDF), that can be used to express a concept scheme as an RDF graph. Using RDF allows data to be linked to and/or merged with other data, enabling data sources to be distributed across the web, but still be meaningfully composed and integrated. This document is a guide using the SKOS Core Vocabulary, for readers who already have a basic understanding of RDF concepts. This edition of the SKOS Core Guide [SKOS Core Guide] is a W3C Public Working Draft. It is the authoritative guide to recommended usage of the SKOS Core Vocabulary at the time of publication. See also the SKOS Core Vocabulary Specification [SKOS Core Spec]. """@en; ; cat:DocLicense; data:W3C; "SKOS Core Guide"; ; xhv:last ; xhv:previous ; rdfs:label "SKOS Core Guide"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-11-02"^^xsd:date; ; cat:DocLicense; data:W3C; "SKOS Core Vocabulary Specification"; ; xhv:last ; xhv:previous ; rdfs:label "SKOS Core Vocabulary Specification"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-05-17"^^xsd:date; """This document describes in brief how to express the content and structure of a thesaurus, and metadata about a thesaurus, in RDF. Using RDF allows data to be linked to and/or merged with other RDF data by semantic web applications. The Semantic Web, which is based on the Resource Description Framework (RDF), provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries."""@en; ; cat:DocLicense; data:W3C; "Quick Guide to Publishing a Thesaurus on the Semantic Web"; ; xhv:last ; xhv:previous ; rdfs:label "Quick Guide to Publishing a Thesaurus on the Semantic Web"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-06-03"^^xsd:date; """ This document describes the requirements for the XPath 2.0 specification and is annotated with their resolution in [XPath 2.0] or [XQuery 1.0 and XPath 2.0 Functions and Operators] and the [XQuery 1.0 and XPath 2.0 Data Model] specifications. """@en; ; cat:DocLicense; data:W3C; "XPath Requirements Version 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "XPath Requirements Version 2.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2005-04-04"^^xsd:date; """ This document describes possible strategies for tokenizing the [XML Path Language (XPath) 2.0] and [XQuery 1.0: An XML Query Language] languages, and is provided as a helpful guide to those who are designing an implementation for these languages, and as background material for the normative EBNF found in the language specifications. In the future this document may be expanded to cover more general parsing strategies. """@en; ; cat:DocLicense; data:W3C; "Building a Tokenizer for XPath or XQuery"; ; xhv:last ; rdfs:label "Building a Tokenizer for XPath or XQuery"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-12-20"^^xsd:date; """ This technical note addresses some of the issues related to inheritance of the XML attributes xml:base and xml:id and the W3C Recommendation for Canonical XML Version 1.0 [C14N10] (Errata). Shortcomings of C14N/1.0 are noted out and the use of a new C14N/1.1 recommendation with the XML Digital Signature 1.0 Recommendation [XMLDSIG] is discussed. """@en; ; cat:DocLicense; data:W3C; "Known Issues with Canonical XML 1.0 (C14N/1.0)"; ; xhv:last ; xhv:previous ; rdfs:label "Known Issues with Canonical XML 1.0 (C14N/1.0)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-12-20"^^xsd:date; """ This technical note describes how to use the XML Digital Signature Recommendation [XMLDSIG] in a way consistent with the present (fall 2006) XML environment. In particular, this note takes into account the recent xml:id Version 1.0 [XMLID] Recommendation, and work in progress towards a Canonical XML Version 1.1 [C14N11] Recommendation. This note suggests constraints on the use of XML Signature, and relies on extension points present in the XML Digital Signature Recommendation. This note does not override any aspect of that Recommendation. """@en; ; cat:DocLicense; data:W3C; "Using XML Digital Signatures in the 2006 XML Environment"; ; xhv:last ; xhv:previous ; rdfs:label "Using XML Digital Signatures in the 2006 XML Environment"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-11-13"^^xsd:date; """ This is the specification of the Platform for Privacy Preferences 1.1 (P3P 1.1). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P 1.1 applications. P3P 1.1 is based on the P3P 1.0 Recommendation and adds some features using the P3P 1.0 Extension mechanism. It also contains a new binding mechanism that can be used to bind policies for XML Applications beyond HTTP transactions. """@en; ; cat:DocLicense; data:W3C; "The Platform for Privacy Preferences 1.1 (P3P1.1) Specification"; ; xhv:last ; xhv:previous ; rdfs:label "The Platform for Privacy Preferences 1.1 (P3P1.1) Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-01-31"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Arabic mathematical notation"; ; xhv:last ; rdfs:label "Arabic mathematical notation"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-11-16"^^xsd:date; """ This paper introduces the concept of a "Rich Web Application Backplane" -- a set of common building blocks for web applications. We argue that submission, data models, model-view binding and behavior, and web components can provide a common infrastructure for multiple markup formats. Further, we propose a common infrastructure for both declarative and imperative web programming languages. By aligning APIs and their declarative representations, we hope to support both implementation approaches and increase interoperability between them. """@en; ; cat:DocLicense; data:W3C; "Rich Web Application Backplane"; ; xhv:last ; rdfs:label "Rich Web Application Backplane"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-03-20"^^xsd:date; """This document provides an overview of the role of delivery context in achieving a device independent Web. It describes the kind of information that may be included in the delivery context, and how it may be used. It surveys current techniques for conveying delivery context information, and identifies further developments that would enhance the ability to adapt content for different access mechanisms.This document is one of a series produced by the W3C Device Independence Working Group. Other documents in the series address the implementation of solutions to the requirements raised here. For example, there are documents in the series reviewing current techniques that can be used to address these requirements and exploring how future versions of existing W3C specifications can provide solutions.Details of the entire series of documents can be found on the W3C Device Independence Activity home page."""@en; ; cat:DocLicense; data:W3C; "Delivery Context Overview for Device Independence"; ; xhv:last ; xhv:previous ; rdfs:label "Delivery Context Overview for Device Independence"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-04-14"^^xsd:date; """Several years of multimodal application development in various business areas and on various device platforms has provided developers enough experience to provide detailed feedback about what they like, dislike, and want to see improve and continue. This experience is provided here as an input to the specifications under development in the W3C Multimodal Interaction and Voice Browser Activities."""@en; ; cat:DocLicense; data:W3C; "Multimodal Application Developer Feedback"; ; xhv:last ; rdfs:label "Multimodal Application Developer Feedback"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-09-11"^^xsd:date; """This document is based on the accumulated experience of several years of developing multimodal applications. It provides a collection of common sense advice for developers of multimodal user interfaces."""@en; ; cat:DocLicense; data:W3C; "Common Sense Suggestions for Developing Multimodal User Interfaces"; ; xhv:last ; rdfs:label "Common Sense Suggestions for Developing Multimodal User Interfaces"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-02-10"^^xsd:date; """ The Resource Description Framework (RDF) is a model developed by the W3C for representing information about resources in the World Wide Web. Topic Maps is a standard for knowledge integration developed by the ISO. This document contains a survey of existing proposals for integrating RDF and Topic Maps data and is intended to be a starting point for establishing standard guidelines for RDF/Topic Maps interoperability. """@en; ; cat:DocLicense; data:W3C; "A Survey of RDF/Topic Maps Interoperability Proposals"; ; xhv:last ; xhv:previous ; rdfs:label "A Survey of RDF/Topic Maps Interoperability Proposals"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-02-02"^^xsd:date; """ This document lists the requirements for an XML grammar intended for representing events as they are defined in DOM 3 Events, primarily but not exclusively for purposes of transmission or synchronisation of remote documents. Such a vocabulary would enable one endpoint to interact remotely with another endpoint holding a DOM representation by sending it DOM Events as if they had occurred directly at the same location. """@en; ; cat:DocLicense; data:W3C; "Remote Events for XML (REX) Requirements"; ; xhv:last ; rdfs:label "Remote Events for XML (REX) Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-03-21"^^xsd:date; """ SOAP Version 1.1 provides an HTTP binding for exchanging a request and a response. This binding provides a "request optional response" refinement that enables an HTTP response with status code 202 to have a SOAP envelope or to be empty. """@en; ; cat:DocLicense; data:W3C; "SOAP 1.1 Request Optional Response HTTP Binding"; ; xhv:last ; rdfs:label "SOAP 1.1 Request Optional Response HTTP Binding"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-03-09"^^xsd:date; """ Domain models play a central role throughout the software development cycle, from requirements analysis to design, through implementation and beyond. As such, great progress has been made in the consistent use of models throughout this process. Modern software development tools with support for the UML and code generation as well as Model-Driven Architectures allow for developers to synchronize and verify technical implementation with user requirements using models. However, the reusability of domain models is often limited because they are, by definition, domain specific and only take into consideration abstractions needed to make possible a solution within the confines of their own individual problem space. But the Web is broader than that and provides a multidimensional solution space capable of referencing an almost limitless set of domains. While much of our software becomes increasingly embedded in the Web, our development processes do not fully exploit the potential of model reuse from the Web yet. This note therefore introduces Semantic Web languages such as RDF Schema and OWL, and shows how they can be used in tandem with mainstream object-oriented languages. We show that the Semantic Web can serve as a platform on which domain models can be created, shared and reused. """@en; ; cat:DocLicense; data:W3C; "A Semantic Web Primer for Object-Oriented Software Developers"; ; xhv:last ; rdfs:label "A Semantic Web Primer for Object-Oriented Software Developers"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-04-12"^^xsd:date; """ In Semantic Web languages, such as RDF and OWL, a property is a binary relation: it is used to link two individuals or an individual and a value. However, in some cases, the natural and convenient way to represent certain concepts is to use relations to link an individual to more than just one individual or value. These relations are called n-ary relations. For example, we may want to represent properties of a relation, such as our certainty about it, severity or strength of a relation, relevance of a relation, and so on. Another example is representing relations among multiple individuals, such as a buyer, a seller, and an object that was bought when describing a purchase of a book. This document presents ontology patterns for representing n-ary relations in RDF and OWL and discusses what users must consider when choosing these patterns. """@en; ; cat:DocLicense; data:W3C; "Defining N-ary Relations on the Semantic Web"; ; xhv:last ; xhv:previous ; rdfs:label "Defining N-ary Relations on the Semantic Web"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-03-14"^^xsd:date; ; cat:DocLicense; data:W3C; "XML Schema Datatypes in RDF and OWL"; ; xhv:last ; xhv:previous ; rdfs:label "XML Schema Datatypes in RDF and OWL"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-04-27"^^xsd:date; """ This document specifies usage scenarios and requirements for a timed text authoring format. A timed text authoring format is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information. """@en; ; cat:DocLicense; data:W3C; "Timed Text (TT) Authoring Format 1.0 Use Cases and Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Timed Text (TT) Authoring Format 1.0 Use Cases and Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-04-25"^^xsd:date; """This document outlines the requirements that the Web Content Accessibility Guidelines Working Group (WCAG WG) has set for development of Web Content Accessibility Guidelines 2.0. These requirements are based on feedback from the use of WCAG 1.0 and will be used to determine if the WCAG WG has met its goals as WCAG 2.0 advances through the W3C Recommendation Track Process."""@en; ; cat:DocLicense; data:W3C; "Requirements for WCAG 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Requirements for WCAG 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-05-09"^^xsd:date; """ Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 - Core (this document) defines a set of abstract properties and an XML Infoset [XML Information Set] representation thereof to reference Web services and to facilitate end-to-end addressing of endpoints in messages. This specification enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner. """@en; ; cat:DocLicense; data:W3C; "Web Services Addressing 1.0 - Core"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Addressing 1.0 - Core"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-05-09"^^xsd:date; """ Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 - SOAP Binding (this document) defines the binding of the abstract properties defined in Web Services Addressing 1.0 - Core to SOAP Messages. """@en; ; cat:DocLicense; data:W3C; "Web Services Addressing 1.0 - SOAP Binding"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Addressing 1.0 - SOAP Binding"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-03-14"^^xsd:date; """ XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts—XForms model, instance data, and user interface—it separates presentation from content, allows reuse, gives strong typing—reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML or SVG. """@en; ; cat:DocLicense; data:W3C; "XForms 1.0 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XForms 1.0 (Second Edition)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-11-15"^^xsd:date; """ This document specifies a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references). """@en; ; cat:DocLicense; data:W3C; "XML Inclusions (XInclude) Version 1.0 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Inclusions (XInclude) Version 1.0 (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-08-16"^^xsd:date; """ 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. """@en; ; cat:DocLicense; data:W3C; "Extensible Markup Language (XML) 1.0 (Fourth Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Extensible Markup Language (XML) 1.0 (Fourth Edition)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-08-16"^^xsd:date; """ XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references. """@en; ; cat:DocLicense; data:W3C; "Namespaces in XML 1.0 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Namespaces in XML 1.0 (Second Edition)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-08-16"^^xsd:date; """ XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by IRI references. """@en; ; cat:DocLicense; data:W3C; "Namespaces in XML 1.1 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Namespaces in XML 1.1 (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-08-16"^^xsd:date; """ 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. """@en; ; cat:DocLicense; data:W3C; "Extensible Markup Language (XML) 1.1 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Extensible Markup Language (XML) 1.1 (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-12-05"^^xsd:date; """ This specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. It consists of two parts: a language for transforming XML documents (XSLT), and an XML vocabulary for specifying formatting semantics. An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary. """@en; ; cat:DocLicense; data:W3C; "Extensible Stylesheet Language (XSL) Version 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "Extensible Stylesheet Language (XSL) Version 1.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-10-13"^^xsd:date; """ This specification defines a set of DOM 3 Events [DOM3EV] compatible events and DOM APIs related to media access. The defined events and APIs enables detailed monitoring of media stream buffering and initialization. They are designed to be easily combined with the SVG Tiny 1.2 [SVGT12] uDOM but can equally well be combined with other, larger DOM APIs. """@en; ; cat:DocLicense; data:W3C; "Media Access Events"; ; xhv:last ; rdfs:label "Media Access Events"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-08-10"^^xsd:date; """This document specifies requirements for SVG Tiny 1.2, a backwardly-compatible update of SVG Tiny 1.1 which adds some new features from SVG 1.2 add adds other features based on implementor and designer feedback on SVG Tiny 1.1."""@en; ; cat:DocLicense; data:W3C; "SVGT 1.2 Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "SVGT 1.2 Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-04-07"^^xsd:date; """ This specification defines the Window object, which provides the global namespace for web scripting languages, access to other documents in a compound document by reference, navigation to other locations, and timers. The Window object is a long-standing de facto standard for HTML user agents. However, it should not be assumed based on this or the name "Window" that it is limited to HTML or to visual user agents. """@en; ; cat:DocLicense; data:W3C; "Window Object 1.0"; ; xhv:last ; rdfs:label "Window Object 1.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-10-13"^^xsd:date; """This specification defines a subset of Cascading Style Sheets Level 2, revision 1 [CSS21] and CSS3 Module: Paged Media [PAGEMEDIA] for printing to low-cost devices. It is designed for printing in situations where it is not feasible or desirable to install a printer-specific driver, and for situations were some variability in the output is acceptable.This profile is designed to work in conjunction with XHTML-Print [XHTMLPRINT] and defines a minimum level of conformance as well as an extension set that provides stronger layout control for the printing of mixed text and images, tables and image collections."""@en; ; cat:DocLicense; data:W3C; "CSS Print Profile"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Print Profile"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-10-10"^^xsd:date; """ This module describes the page model that partitions a flow into pages. It builds on the Box model module and introduces and defines the page model and paged media. It adds functionality for pagination, page margins, page size and orientation, headers and footers, widows and orphans, and image orientation. Finally it extends generated content to enable page numbering and running headers / footers. """@en; ; cat:DocLicense; data:W3C; "CSS3 Module: Paged Media"; ; xhv:last ; xhv:previous ; rdfs:label "CSS3 Module: Paged Media"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-05-18"^^xsd:date; """ When creating schemas (XML Schema, DTD, etc.), it is important to include constructs that meet the needs of content authors dealing with international audiences, and address the needs of the localization community. This document provides a list of key requirements to achieve such a goal. It will be used to provide a framework and direction for a detailed solution proposal (or set of proposals) to be developed later. """@en; ; cat:DocLicense; data:W3C; "Internationalization and Localization Markup Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Internationalization and Localization Markup Requirements"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-06-12"^^xsd:date; """ Based on [RFC 3066bis] and [RFC 3066bis Matching], this document describes mechanisms for identifying or selecting the language of content or locale preferences used to process information using Web technologies. It describes how document formats, specifications, and implementations should handle language tags, as well as data structures that extend these tags to describe international preferences. """@en; ; cat:DocLicense; data:W3C; "Language Tags and Locale Identifiers for the World Wide Web"; ; xhv:last ; xhv:previous ; rdfs:label "Language Tags and Locale Identifiers for the World Wide Web"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-03-29"^^xsd:date; """ A finding of the W3C Technical Architecture Group (TAG), this document addresses the question of whether or not adding new names to a (published) namespace is a sound practice. """@en; ; cat:DocLicense; data:W3C; "The Disposition of Names in an XML Namespace"; ; xhv:last ; rdfs:label "The Disposition of Names in an XML Namespace"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-09-27"^^xsd:date; """ This document presents an ontology of temporal concepts, OWL-Time (formerly DAML-Time) [4,10], for describing the temporal content of Web pages and the temporal properties of Web services. The ontology provides a vocabulary for expressing facts about topological relations among instants and intervals, together with information about durations, and about datetime information. We also demonstrate in detail, using the Congo.com and Bravo Air examples from OWL-S [11], how this time ontology can be used to support OWL-S, including use cases for defining input parameters and (conditional) output parameters. A use case for meeting scheduling is also shown. In the appendix we also describe a time zone resource in OWL we developed for not only the US but also the entire world, including the time zone ontology, the US time zone instances, and the world time zone instances. """@en; ; cat:DocLicense; data:W3C; "Time Ontology in OWL"; ; xhv:last ; rdfs:label "Time Ontology in OWL"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-10-13"^^xsd:date; """ Remote Events for XML (REX) 1.0 is an XML [XML] grammar for representing events as they are defined in DOM 3 Events [DOM3EV], primarily but not exclusively for purposes of transmission. It enables one endpoint to interact remotely with another endpoint holding a DOM representation by sending it DOM Events as if they had occurred directly at the same location. """@en; ; cat:DocLicense; data:W3C; "Remote Events for XML (REX) 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Remote Events for XML (REX) 1.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-03-22"^^xsd:date; """ Many applications that involve multimedia content make use of some form of metadata that describe this content. The goals of this document are (i) to explain what the advantages are of using Semantic Web languages and technologies for the creation, storage, manipulation, interchange and processing of image metadata, and (ii) to provide guidelines for doing so. The document gives a number of use cases that illustrate ways to exploit Semantic Web technologies for image annotation, an overview of RDF and OWL vocabularies developed for this task and an overview of relevant tools. """@en; ; cat:DocLicense; data:W3C; "Image Annotation on the Semantic Web"; ; xhv:last ; rdfs:label "Image Annotation on the Semantic Web"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-08-21"^^xsd:date; """ This specification defines Web Forms 2.0, an extension to the forms features found in HTML4's Forms chapter and the corresponding DOM2 HTML interfaces. Web Forms 2.0 applies to both HTML and XHTML user agents. It provides new strongly-typed input fields, new attributes for defining constraints, a repeating model for declarative repeating of form sections, new DOM interfaces, new DOM events for validation and dependency tracking, and XML submission and initialization of forms. It also standardizes and codifies existing practice in areas that have not been previously documented, and clarifies some of the interactions of HTML form controls and CSS. HTML4, XHTML1.1, and the DOM are thus extended in a manner that has a clear migration path from existing HTML forms, leveraging the knowledge authors have built up with their experience with HTML so far. """@en; ; cat:DocLicense; data:W3C; "Web Forms 2.0"; ; xhv:last ; rdfs:label "Web Forms 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-06-19"^^xsd:date; """ This document presents a standard conversion of Princeton WordNet to RDF/OWL. It describes how it was converted and gives examples of how it may be queried for use in Semantic Web applications. """@en; ; cat:DocLicense; data:W3C; "RDF/OWL Representation of WordNet"; ; xhv:last ; rdfs:label "RDF/OWL Representation of WordNet"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-06-19"^^xsd:date; """ Web Services Choreography Description Language: Primer is a non-normative document intended to provide an easy to understand tutorial on the uses and the features of the Web Services Choreography Description Language specification. """@en; ; cat:DocLicense; data:W3C; "Web Services Choreography Description Language: Primer"; ; xhv:last ; rdfs:label "Web Services Choreography Description Language: Primer"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2006-04-11"^^xsd:date; """ This document contains requirements for the development of an XML Processing Model and Language, which are intended to describe and specify the processing relationships between XML resources. """@en; ; cat:DocLicense; data:W3C; "XML Processing Model Requirements and Use Cases"; ; xhv:last ; rdfs:label "XML Processing Model Requirements and Use Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-12-17"^^xsd:date; """ This document details use cases for a Device Descriptions Repository (DDR). In order to realize these use cases, certain behaviors will be expected of a DDR: these behaviors are determined and listed as requirements. This Working Group Note forms one of the deliverables of the W3C Mobile Web Initiative Device Description Working Group. The requirements in this document are derived from the listed use-cases as well as information in the Device Description Landscape [DDLAND] and Device Description Ecosystem [DDECO] documents. """@en; ; cat:DocLicense; data:W3C; "Device Description Repository Requirements 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Device Description Repository Requirements 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-10-31"^^xsd:date; """ This W3C Note describes the business models surrounding the creation, maintenance and use of device descriptions. It identifies the main actors in the current model, explores their motivations for participating, identifies the costs associated with participation and the benefits that accrue to participants. It is shown in this Note that the current model is incomplete, partly because of the absence of a common repository that can address the needs of the various actors. A complete model is postulated, on the assumption of the existence of a common repository, from which is derived some key requirements upon such a repository to ensure the success of the model. This Note should be read in conjunction with the DDWG Landscape document, which provides details of the particular technologies and actors currently engaged in work related to device descriptions. This Note, together with the Landscape document, provides input to the DDWG Requirements document. """@en; ; cat:DocLicense; data:W3C; "Device Description Ecosystem 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Device Description Ecosystem 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-10-31"^^xsd:date; """ Developing Web content for mobile devices is more challenging than developing for the desktop Web. Compared to desktop Web clients, mobile Web devices come in a much wider range of shapes, sizes and capabilities. The mobile Web developer relies upon accurate device descriptions in order to dynamically adapt content to suit the client. This Note describes what efforts the W3C and other organizations are doing in order to provide accurate device descriptions. This Note should be read in conjunction with the DDWG Ecosystem [DDWG-Ecosystem] document. This Note, together with the Ecosystem document, provides input to the proposed DDWG Requirements document as described in the DDWG Charter [DDWG-Charter] """@en; ; cat:DocLicense; data:W3C; "Device Description Landscape 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Device Description Landscape 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-12"^^xsd:date; """The Charter of the Web Application Formats Working Group includes a deliverable titled Specification of a declarative format for applications and user interfaces. This document includes the status of this deliverable and a recommendation that the Working Group stop formal work on this deliverable and consider this Note as the one and only publication for this deliverable. This Note also includes some potential options if W3C Members choose to do related work."""@en; ; cat:DocLicense; data:W3C; "Declarative Formats for Applications and User Interfaces"; ; xhv:last ; rdfs:label "Declarative Formats for Applications and User Interfaces"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-28"^^xsd:date; """GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. It is a technique for obtaining RDF data from XML documents and in particular XHTML pages. Authors may explicitly associate documents with transformation algorithms, typically represented in XSLT, using a link element in the head of the document. Alternatively, the information needed to obtain the transformation may be held in an associated metadata profile document or namespace document. Clients reading the document can follow links across the Web using techniques described in the GRDDL specification to discover the appropriate transformations. This document uses a number of examples from the GRDDL Use Cases document to illustrate, in detail, the techniques GRDDL provides for associating documents with appropriate instructions for extracting any embedded data."""@en; ; cat:DocLicense; data:W3C; "GRDDL Primer"; ; xhv:last ; xhv:previous ; rdfs:label "GRDDL Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-04-06"^^xsd:date; """GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. The GRDDL specification introduces markup for declaring that an XML document includes gleanable data and for linking to an algorithm, typically represented in XSLT, for gleaning the RDF data from the document.The markup includes a namespace-qualified attribute for use in general-purpose XML documents and a profile-qualified link relationship for use in valid XHTML documents. The GRDDL mechanism also allows an XML namespace document (or XHTML profile document) to declare that every document associated with that namespace (or profile) includes gleanable data and for linking to an algorithm for gleaning the data.A corresponding GRDDL specification provides complete technical details. A GRDDL Primer demonstrates the mechanism on XHTML documents which include widely-deployed dialects, more recently known as microformats."""@en; ; cat:DocLicense; data:W3C; "GRDDL Use Cases: Scenarios of extracting RDF data from XML documents"; ; xhv:last ; xhv:previous ; rdfs:label "GRDDL Use Cases: Scenarios of extracting RDF data from XML documents"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-04-12"^^xsd:date; """ Specifying the language of content is useful for a wide number of applications, from linguistically-sensitive searching to applying language-specific display properties. In some cases the potential applications for language information are still waiting for implementations to catch up, whereas in others, such as detection of language by voice browsers, it is a necessity today. On the other hand, adding markup for language information to content is something that can and should be done today. Without it, it will not be possible to take advantage of any future developments. """@en; ; cat:DocLicense; data:W3C; "Internationalization Best Practices: Specifying Language in XHTML & HTML Content"; ; xhv:last ; xhv:previous ; rdfs:label "Internationalization Best Practices: Specifying Language in XHTML & HTML Content"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-10-31"^^xsd:date; """This document sets out the use cases and requirements that have motivated the development of the Protocol for Web Description Resources (POWDER). The use cases address social and commercial needs to provide information about groups of Web resources, such as those available from a Web site, to aid the annotation and/or personalization of content for end users in varying delivery contexts."""@en; ; cat:DocLicense; data:W3C; "POWDER: Use Cases and Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "POWDER: Use Cases and Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-18"^^xsd:date; """SPARQL is a query language and a protocol for RDF developed by the W3C's RDF Data Access Working Group. Included in that work is an XML vocabulary for serializing the results of two SPARQL query forms, SELECT and ASK. This document defines an alternative means of serializing the results of those SPARQL query forms using JSON, a lightweight representation format which emphasizes concision and legibility."""@en; ; cat:DocLicense; data:W3C; "Serializing SPARQL Query Results in JSON"; ; xhv:last ; xhv:previous ; rdfs:label "Serializing SPARQL Query Results in JSON"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-08-28"^^xsd:date; """Web services provide a standards-based foundation for exchanging information between distributed software systems. The W3C Recommendation Web Services Description Language (WSDL) specifies a standard way to describe the interfaces of a Web Service at a syntactic level and how to invoke it. While the syntactic descriptions provide information about the structure of input and output messages of an interface and about how to invoke the service, semantics are needed to describe what a Web service actual does. These semantics, when expressed in formal languages, disambiguate the description of Web services interfaces, paving the way for automatic discovery, composition and integration of software components. WSDL does not explicitly provide mechanisms to specify the semantics of a Web service. Semantic Annotations for WSDL and XML Schema (SAWSDL) defines mechanisms by which semantic annotations can be added to WSDL components. This usage guide is an accompanying document to SAWSDL specification. It presents examples illustrating how to associate semantic annotations with a Web service. These annotations could be used for classifying, discovering, matching, composing, and invoking Web services.Some of the examples illustrated in this document use RDF and OWL Web Ontology Language for representing ontologies. Some knowledge of RDF and OWL is useful for understanding this document, but not essential."""@en; ; cat:DocLicense; data:W3C; "Semantic Annotations for WSDL and XML Schema — Usage Guide"; ; xhv:last ; xhv:previous ; rdfs:label "Semantic Annotations for WSDL and XML Schema — Usage Guide"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-07-02"^^xsd:date; """ SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP. """@en; ; cat:DocLicense; data:W3C; "SOAP 1.2 Part 3: One-Way MEP"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP 1.2 Part 3: One-Way MEP"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-05-16"^^xsd:date; """ This document contains guidelines on the use of the Unicode Standard in conjunction with markup languages such as XML. """@en; ; cat:DocLicense; data:W3C; "Unicode in XML and other Markup Languages"; ; xhv:last ; xhv:previous ; rdfs:label "Unicode in XML and other Markup Languages"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-11-12"^^xsd:date; """ Web Services Policy 1.5 - Guidelines for Policy Assertion Authors is intended to provide guidance for Assertion Authors that will work with the Web Services Policy 1.5 - Framework [Web Services Policy Framework] and Web Services Policy 1.5 - Attachment [Web Services Policy Attachment] specifications to create domain specific assertions. The focus of this document is to provide best practices and patterns to follow as well as illustrate the care needed in using WS-Policy to achieve the best possible results for interoperability. It is a complementary guide to using the specifications. """@en; ; cat:DocLicense; data:W3C; "Web Services Policy 1.5 - Guidelines for Policy Assertion Authors"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Policy 1.5 - Guidelines for Policy Assertion Authors"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-11-12"^^xsd:date; """ Web Services Policy 1.5 - Primer is an introductory description of the Web Services Policy language. This document describes the policy language features using numerous examples. The associated Web Services Policy 1.5 - Framework and Web Services Policy 1.5 - Attachment specifications provide the complete normative description of the Web Services Policy language. """@en; ; cat:DocLicense; data:W3C; "Web Services Policy 1.5 - Primer"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Policy 1.5 - Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-11-01"^^xsd:date; """ This Note includes threat trees used to analyze the threats that the [WSC-XIT] responds to. It is a companion document to [WSC-USECASES]."""@en; ; cat:DocLicense; data:W3C; "Web User Interaction: Threat Trees"; ; xhv:last ; rdfs:label "Web User Interaction: Threat Trees"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-07-20"^^xsd:date; """ WSDL 1.1 Element Identifiers defines a syntax to identify individual elements in a WSDL 1.1 document. """@en; ; cat:DocLicense; data:W3C; "WSDL 1.1 Element Identifiers"; ; xhv:last ; xhv:previous ; rdfs:label "WSDL 1.1 Element Identifiers"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-26"^^xsd:date; """ This specification defines additional message exchange patterns (MEPs) to be used in WSDL 2.0 and are provided as examples of the extensibility of WSDL 2.0. """@en; ; cat:DocLicense; data:W3C; "Web Services Description Language (WSDL) Version 2.0: Additional MEPs"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Description Language (WSDL) Version 2.0: Additional MEPs"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-26"^^xsd:date; """Web Services Description Language (WSDL) provides a model and an XML format for describing Web services. This document describes a representation of that model in the Resource Description Language (RDF) and in the Web Ontology Language (OWL), and a mapping procedure for transforming particular WSDL descriptions into their RDF form."""@en; ; cat:DocLicense; data:W3C; "Web Services Description Language (WSDL) Version 2.0: RDF Mapping"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Description Language (WSDL) Version 2.0: RDF Mapping"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-26"^^xsd:date; """ WSDL SOAP 1.1 Binding describes the concrete details for using WSDL 2.0 in conjunction with SOAP 1.1 [SOAP11] protocol. """@en; ; cat:DocLicense; data:W3C; "Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-03-23"^^xsd:date; """ This document specifies goals, requirements, and usage scenarios for the W3C XML Query (XQuery) data model and query language. It also includes, for each requirement, a corresponding status, indicating the status of the requirement in the XQuery 1.0 family of W3C Recommendations. """@en; ; cat:DocLicense; data:W3C; "XML Query (XQuery) Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "XML Query (XQuery) Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-03-23"^^xsd:date; """ This document specifies usage scenarios for XQuery. """@en; ; cat:DocLicense; data:W3C; "XML Query Use Cases"; ; xhv:last ; xhv:previous ; rdfs:label "XML Query Use Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-11"^^xsd:date; """ GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. This GRDDL specification introduces markup based on existing standards for declaring that an XML document includes data compatible with the Resource Description Framework (RDF) and for linking to algorithms (typically represented in XSLT), for extracting this data from the document. The markup includes a namespace-qualified attribute for use in general-purpose XML documents and a profile-qualified link relationship for use in valid XHTML documents. The GRDDL mechanism also allows an XML namespace document (or XHTML profile document) to declare that every document associated with that namespace (or profile) includes gleanable data and for linking to an algorithm for gleaning the data. A corresponding GRDDL Use Case Working Draft provides motivating examples. A GRDDL Primer demonstrates the mechanism on XHTML documents which include widely-deployed dialects known as microformats. A GRDDL Test Cases document illustrates specific issues in this design and provides materials to aid in test-driven development of GRDDL-aware agents. """@en; ; cat:DocLicense; data:W3C; "Gleaning Resource Descriptions from Dialects of Languages (GRDDL)"; ; xhv:last ; xhv:previous ; rdfs:label "Gleaning Resource Descriptions from Dialects of Languages (GRDDL)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-11"^^xsd:date; """ This document describes and includes test cases for software agents that extract RDF from XML source documents by following the set of mechanisms outlined in the Gleaning Resource Description from Dialects of Language [GRDDL] specification. They demonstrate the expected behavior of a GRDDL-aware agent by specifying one (or more) RDF graph serializations which are the GRDDL results associated with a single source document. """@en; ; cat:DocLicense; data:W3C; "GRDDL Test Cases"; ; xhv:last ; xhv:previous ; rdfs:label "GRDDL Test Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-04-03"^^xsd:date; """ This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS). ITS is designed to be used with schemas to support the internationalization and localization of schemas and documents. An implementation is provided for three schema languages: XML DTD, XML Schema and RELAX NG. """@en; ; cat:DocLicense; data:W3C; "Internationalization Tag Set (ITS) Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Internationalization Tag Set (ITS) Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-08-28"^^xsd:date; """This document defines a set of extension attributes for the Web Services Description Language and XML Schema definition language that allows description of additional semantics of WSDL components. The specification defines how semantic annotation is accomplished using references to semantic models, e.g. ontologies. Semantic Annotations for WSDL and XML Schema (SAWSDL) does not specify a language for representing the semantic models. Instead it provides mechanisms by which concepts from the semantic models, typically defined outside the WSDL document, can be referenced from within WSDL and XML Schema components using annotations."""@en; ; cat:DocLicense; data:W3C; "Semantic Annotations for WSDL and XML Schema"; ; xhv:last ; xhv:previous ; rdfs:label "Semantic Annotations for WSDL and XML Schema"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-04-05"^^xsd:date; """ This document defines the process of Semantic Interpretation for Speech Recognition and the syntax and semantics of semantic interpretation tags that can be added to speech recognition grammars to compute information to return to an application on the basis of rules and tokens that were matched by the speech recognizer. In particular, it defines the syntax and semantics of the contents of Tags in the Speech Recognition Grammar Specification [SRGS]. The results of semantic interpretation describe the meaning of a natural language utterance. The current specification represents this information as an ECMAScript object, and defines a mechanism to serialize the result into [XML]. The W3C Multimodal Interaction Activity [MMI] is defining an XML data format [EMMA] for containing and annotating the information in user utterances. It is expected that the EMMA language will be able to integrate results generated by Semantic Interpretation for Speech Recognition. Semantic Interpretation may be useful in combination with other specifications, such as Stochastic Language Models [N-GRAM], but their use with N-grams has not yet been studied. """@en; ; cat:DocLicense; data:W3C; "Semantic Interpretation for Speech Recognition (SISR) Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Semantic Interpretation for Speech Recognition (SISR) Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-04-27"^^xsd:date; """ SOAP Version 1.2 Part 0: Primer (Second Edition) is a non-normative document intended to provide an easily understandable tutorial on the features of SOAP Version 1.2. In particular, it describes the features through various usage scenarios, and is intended to complement the normative text contained in Part 1 and Part 2 of the SOAP 1.2 specifications. This second edition includes additional material on the SOAP Message Transmission Optimization Mechanism (MTOM), the XML-binary Optimized Packaging (XOP) and the Resource Representation SOAP Header Block (RRSHB) specifications. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Part 0: Primer (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Part 0: Primer (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-04-27"^^xsd:date; """ SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. "Part 1: Messaging Framework" defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-04-27"^^xsd:date; """ SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging Framework. This specification depends on SOAP Version 1.2 Part 1: Messaging Framework [SOAP Part 1]. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Part 2: Adjuncts (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Part 2: Adjuncts (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-04-27"^^xsd:date; """ This document draws on assertions found in the SOAP Version 1.2 specifications [SOAP Part 1], [SOAP Part 2], and provides a set of tests in order to show whether the assertions are implemented in a SOAP processor. A SOAP 1.2 implementation that passes all of the tests specified in this document may claim to conform to the SOAP 1.2 Test Suite, 2007 04 27. It is incorrect to claim to be compliant with the SOAP Version 1.2 specifications merely by passing successfully all the tests provided in this test suite. It is also incorrect to claim that an implementation is non compliant with the SOAP Version 1.2 specifications based on its failure to pass one or more of the tests in this test suite. """@en; ; cat:DocLicense; data:W3C; "SOAP Version 1.2 Specification Assertions and Test Collection (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "SOAP Version 1.2 Specification Assertions and Test Collection (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-19"^^xsd:date; """ VoiceXML 2.1 specifies a set of features commonly implemented by Voice Extensible Markup Language platforms. This specification is designed to be fully backwards-compatible with VoiceXML 2.0 [VXML2]. This specification describes only the set of additional features. """@en; ; cat:DocLicense; data:W3C; "Voice Extensible Markup Language (VoiceXML) 2.1"; ; xhv:last ; xhv:previous ; rdfs:label "Voice Extensible Markup Language (VoiceXML) 2.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-30"^^xsd:date; """Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM, which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields. First published (1.0) in 1999 and followed by a second (errata) release in 2001, WebCGM unifies potentially diverse approaches to CGM utilization in Web document applications. It therefore represents a significant interoperability agreement amongst major users and implementers of the ISO CGM standard.WebCGM 2.0 adds a DOM (API) specification for programmatic access to WebCGM objects, and a specification of an XML Companion File (XCF) architecture, for externalization of non-graphical metadata. WebCGM 2.0, in addition, builds upon and extends the graphical and intelligent content of WebCGM 1.0, delivering functionality that was forecast for WebCGM 1.0, but was postponed in order to get the standard and its implementations to users expeditiously.The design criteria for WebCGM aim at a balance between graphical expressive power on the one hand, and simplicity and implementability on the other. A small but powerful set of standardized metadata elements supports the functionalities of hyperlinking and document navigation, picture structuring and layering, and enabling search and query of WebCGM picture content."""@en; ; cat:DocLicense; data:W3C; "WebCGM 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "WebCGM 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-04"^^xsd:date; """ Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 - Metadata (this document) defines how the abstract properties defined in Web Services Addressing 1.0 - Core are described using WSDL, how to include WSDL metadata in endpoint references, and how WS-Policy can be used to indicate the support of WS-Addressing by a Web service. """@en; ; cat:DocLicense; data:W3C; "Web Services Addressing 1.0 - Metadata"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Addressing 1.0 - Metadata"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-04"^^xsd:date; """ The Web Services Policy 1.5 - Framework provides a general purpose model and corresponding syntax to describe the policies of entities in a Web services-based system. Web Services Policy Framework defines a base set of constructs that can be used and extended by other Web services specifications to describe a broad range of service requirements and capabilities. """@en; ; cat:DocLicense; data:W3C; "Web Services Policy 1.5 - Framework"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Policy 1.5 - Framework"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-04"^^xsd:date; """ This specification, Web Services Policy 1.5 - Attachment, defines two general-purpose mechanisms for associating policies, as defined in Web Services Policy 1.5 - Framework, with the subjects to which they apply. This specification also defines how these general-purpose mechanisms may be used to associate policies with WSDL and UDDI descriptions. """@en; ; cat:DocLicense; data:W3C; "Web Services Policy 1.5 - Attachment"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Policy 1.5 - Attachment"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-26"^^xsd:date; """ This document describes the Web Services Description Language Version 2.0 (WSDL 2.0), an XML language for describing Web services. This specification defines the core language which can be used to describe Web services based on an abstract model of what the service offers. It also defines the conformance criteria for documents in this language. """@en; ; cat:DocLicense; data:W3C; "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-26"^^xsd:date; """ WSDL 2.0 is the Web Services Description Language, an XML language for describing Web services. This document, "Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts", specifies predefined extensions for use in WSDL 2.0: Message exchange patterns Operation safety Operation styles Binding extensions for SOAP and HTTP """@en; ; cat:DocLicense; data:W3C; "Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-26"^^xsd:date; """ This document is a companion to the WSDL 2.0 specification (Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language [WSDL 2.0 Core], Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts [WSDL 2.0 Adjuncts]). It is intended for readers who wish to have an easier, less technical introduction to the main features of the language. This primer is only intended to be a starting point toward use of WSDL 2.0, and hence does not describe every feature of the language. Users are expected to consult the WSDL 2.0 specification if they wish to make use of more sophisticated features or techniques. Finally, this primer is non-normative. Any specific questions of what WSDL 2.0 requires or forbids should be referred to the WSDL 2.0 specification. """@en; ; cat:DocLicense; data:W3C; "Web Services Description Language (WSDL) Version 2.0 Part 0: Primer"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Description Language (WSDL) Version 2.0 Part 0: Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-10-29"^^xsd:date; """ XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts—XForms model, instance data, and user interface—it separates presentation from content, allows reuse, gives strong typing—reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML or SVG. """@en; ; cat:DocLicense; data:W3C; "XForms 1.0 (Third Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XForms 1.0 (Third Edition)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-23"^^xsd:date; """ This document defines the W3C XQuery 1.0 and XPath 2.0 Data Model (XDM), which is the data model of [XPath 2.0], [XSLT 2.0], and [XQuery], and any other specifications that reference it. This data model is based on the [XPath 1.0] data model and earlier work on an [XML Query Data Model]. This document is the result of joint work by the [XSL Working Group] and the [XML Query Working Group]. """@en; ; cat:DocLicense; data:W3C; "XQuery 1.0 and XPath 2.0 Data Model (XDM)"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 1.0 and XPath 2.0 Data Model (XDM)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-23"^^xsd:date; """ This document defines constructor functions, operators and functions on the datatypes defined in [XML Schema Part 2: Datatypes Second Edition] and the datatypes defined in [XQuery 1.0 and XPath 2.0 Data Model]. It also discusses functions and operators on nodes and node sequences as defined in the [XQuery 1.0 and XPath 2.0 Data Model]. These functions and operators are defined for use in [XML Path Language (XPath) 2.0], [XQuery 1.0: An XML Query Language] and [XSL Transformations (XSLT) Version 2.0] and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2005/xpath-functions. """@en; ; cat:DocLicense; data:W3C; "XQuery 1.0 and XPath 2.0 Functions and Operators"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 1.0 and XPath 2.0 Functions and Operators"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-23"^^xsd:date; """ XPath 2.0 is an expression language that allows the processing of values conforming to the data model defined in [XQuery/XPath Data Model (XDM)]. The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values. The result of an XPath expression may be a selection of nodes from the input documents, or an atomic value, or more generally, any sequence allowed by the data model. The name of the language derives from its most distinctive feature, the path expression, which provides a means of hierarchic addressing of the nodes in an XML tree. XPath 2.0 is a superset of [XPath 1.0], with the added capability to support a richer set of data types, and to take advantage of the type information that becomes available when documents are validated using XML Schema. A backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 2.0; exceptions to this policy are noted in [I Backwards Compatibility with XPath 1.0]. """@en; ; cat:DocLicense; data:W3C; "XML Path Language (XPath) 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "XML Path Language (XPath) 2.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-23"^^xsd:date; """ XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources. """@en; ; cat:DocLicense; data:W3C; "XQuery 1.0: An XML Query Language"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 1.0: An XML Query Language"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-23"^^xsd:date; """ This document defines formally the semantics of XQuery 1.0 [XQuery 1.0: An XML Query Language] and XPath 2.0 [XML Path Language (XPath) 2.0]. """@en; ; cat:DocLicense; data:W3C; "XQuery 1.0 and XPath 2.0 Formal Semantics"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 1.0 and XPath 2.0 Formal Semantics"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-23"^^xsd:date; """ This document defines an XML Syntax for [XQuery 1.0: An XML Query Language]. """@en; ; cat:DocLicense; data:W3C; "XML Syntax for XQuery 1.0 (XQueryX)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Syntax for XQuery 1.0 (XQueryX)"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-23"^^xsd:date; """ This document defines serialization of an instance of the data model as defined in [XQuery 1.0 and XPath 2.0 Data Model] into a sequence of octets. Serialization is designed to be a component that can be used by other specifications such as [XSL Transformations (XSLT) Version 2.0] or [XQuery 1.0: An XML Query Language]. """@en; ; cat:DocLicense; data:W3C; "XSLT 2.0 and XQuery 1.0 Serialization"; ; xhv:last ; xhv:previous ; rdfs:label "XSLT 2.0 and XQuery 1.0 Serialization"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-01-23"^^xsd:date; """ This specification defines the syntax and semantics of XSLT 2.0, a language for transforming XML documents into other XML documents. XSLT 2.0 is a revised version of the XSLT 1.0 Recommendation [XSLT 1.0] published on 16 November 1999. XSLT 2.0 is designed to be used in conjunction with XPath 2.0, which is defined in [XPath 2.0]. XSLT shares the same data model as XPath 2.0, which is defined in [Data Model], and it uses the library of functions and operators defined in [Functions and Operators]. XSLT 2.0 also includes optional facilities to serialize the results of a transformation, by means of an interface to the serialization component described in [XSLT and XQuery Serialization]. This document contains hyperlinks to specific sections or definitions within other documents in this family of specifications. These links are indicated visually by a superscript identifying the target specification: for example XP for XPath, DM for the XDM data model, FO for Functions and Operators. """@en; ; cat:DocLicense; data:W3C; "XSL Transformations (XSLT) Version 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "XSL Transformations (XSLT) Version 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-05-01"^^xsd:date; """ SVG is language for describing vector graphics, however it's typically rendered on raster displays. SVG filter effects is a way of processing the generated raster image before it's displayed. Although originally designed for use in SVG, filter effects are defined in XML and are accessed via a presentation property, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO. This document defines the markup used by SVG filters. """@en; ; cat:DocLicense; data:W3C; "SVG Filters 1.2, Part 2: Language"; ; xhv:last ; rdfs:label "SVG Filters 1.2, Part 2: Language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-05-01"^^xsd:date; """SVG is language for describing vector graphics, however it's typically rendered on raster displays. SVG filter effects is a way of processing the generated raster image before it's displayed.Although originally designed for use in SVG, filter effects are defined in XML and are accessed via a presentation property, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO.This document introduces the features used by SVG filters."""@en; ; cat:DocLicense; data:W3C; "SVG Filters 1.2, Part 1: Primer"; ; xhv:last ; rdfs:label "SVG Filters 1.2, Part 1: Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-05-01"^^xsd:date; """This document lists the design principles and requirements for the creation of a SVG specification related to filters."""@en; ; cat:DocLicense; data:W3C; "SVG Filter Requirements"; ; xhv:last ; rdfs:label "SVG Filter Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-12-21"^^xsd:date; """ This Working Draft defines features of the Scalable Vector Graphics (SVG) Language that are specifically for printing environments. """@en; ; cat:DocLicense; data:W3C; "SVG Print 1.2, Part 2: Language"; ; xhv:last ; xhv:previous ; rdfs:label "SVG Print 1.2, Part 2: Language"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-12-21"^^xsd:date; """ This Working Draft is a primer for use of the Scalable Vector Graphics (SVG) Language for printing environments. It explains the technical background and gives guidelines on how to use the SVG Print specification with SVG 1.2 Tiny and SVG 1.2 Full modules for printing. It is purely informative and has no conformance statements. """@en; ; cat:DocLicense; data:W3C; "SVG Print 1.2, Part 1: Primer"; ; xhv:last ; xhv:previous ; rdfs:label "SVG Print 1.2, Part 1: Primer"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-10-31"^^xsd:date; """ This First Public Working Draft outlines the requirements that the User Agent Accessibility Guidelines Working Group (UAWG) has set for development of User Agent Accessibility Guidelines 2.0 (UAAG 2.0). These requirements are based on feedback from the use of UAAG 1.0 and will be used to determine if the UAWG has met its goals as UAAG 2.0 advances through the W3C Recommendation Track Process. """@en; ; cat:DocLicense; data:W3C; "User Agent Accessibility Guidelines 2.0 Requirements"; ; xhv:last ; rdfs:label "User Agent Accessibility Guidelines 2.0 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-10-19"^^xsd:date; """ Behavioral Extensions provide a way to link to binding technologies, such as XBL, from CSS style sheets. This allows bindings to be selected using the CSS cascade, and thus enables bindings to transparently benefit from the user style sheet mechanism, media selection, and alternate style sheets. """@en; ; cat:DocLicense; data:W3C; "Behavioral Extensions to CSS"; ; xhv:last ; xhv:previous ; rdfs:label "Behavioral Extensions to CSS"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-08-09"^^xsd:date; """CSS (Cascading Style Sheets) describes the rendering of documents on various media. When textual documents (e.g., HTML) are laid out on visual media (e.g., screen or print), CSS models the document as a hierarchy of boxes containing words, lines, paragraphs, tables, etc. each with properties such as size, color and font.This module describes the basic types of boxes, with their padding and margin, and the normal “flow†(i.e., the sequence of blocks of text with margins in-between). It also defines “floating†boxes, but other kinds of layout, such as tables, absolute positioning, ruby annotations, grid layouts, columns and numbered pages, are described by other modules. Also, the layout of text inside each line (including the handling of left-to-right and right-to-left scripts) is defined elsewhere.Boxes may contain either horizontal or vertical lines of text. Boxes of different orientations may be mixed in one flow. (This is a level 3 feature.)"""@en; ; cat:DocLicense; data:W3C; "CSS basic box model"; ; xhv:last ; xhv:previous ; rdfs:label "CSS basic box model"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-05"^^xsd:date; """This module describes integration of grid-based layout (similar to the grids traditionally used in books and newspapers) with CSS sizing and positioning."""@en; ; cat:DocLicense; data:W3C; "CSS Grid Positioning Module Level 3"; ; xhv:last ; rdfs:label "CSS Grid Positioning Module Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-12-19"^^xsd:date; """ The purpose of this document is to provide guidelines for the interoperable deployment of the Efficient XML Interchange (EXI) format. It provides explanations of format features and techniques to support interoperable information exchanges using EXI. While intended primarily as a practical guide for systems architects and programmers, it also presents information suitable for the general reader interested in EXI's intended role in the expanding Web. """@en; ; cat:DocLicense; data:W3C; "Efficient XML Interchange (EXI) Best Practices"; ; xhv:last ; rdfs:label "Efficient XML Interchange (EXI) Best Practices"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-07-25"^^xsd:date; """ This Working Group Note presents measurement results of various high-performance XML interchange encoding formats and their associated processors, made by the Efficient XML Interchange (EXI) Working Group. The measurements have been conducted following the recommendations of the XML Binary Characterization (XBC) Working Group. In particular, this draft covers measurements of the properties of "compactness", "processing efficiency" and "roundtrip support", as defined by the XBC WG. We start by describing the context in which this analysis is being made, and the position of an efficient format in the landscape of high performance XML strategies. Then we describe the measured quantities in detail and the test framework in which they were made, and give a short description of each format. Finally, a summary of the results and the conclusions of the group are included. The full measurements and analysis are included in an appendix and supporting documents. As a result of the measurements described here, the working group selected Efficient XML ([EffXML]) to be the basis for the proposed encoding specification to be prepared as a candidate W3C Recommendation. Follow up work has centered around integrating some features from the other measured format technologies, particularly variations for both more efficient structural and value encodings. """@en; ; cat:DocLicense; data:W3C; "Efficient XML Interchange Measurements Note"; ; xhv:last ; xhv:previous ; rdfs:label "Efficient XML Interchange Measurements Note"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-11-26"^^xsd:date; """HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. This document describes the set of guiding principles used by the HTML Working Group for the development of HTML5. The principles offer guidance for the design of HTML in the areas of compatibility, utility and interoperability."""@en; ; cat:DocLicense; data:W3C; "HTML Design Principles"; ; xhv:last ; rdfs:label "HTML Design Principles"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-25"^^xsd:date; """This is the namespace document for the POWDER vocabulary. It provides a formal definition for each class and property, acting as a companion document to POWDER's Description Resources and Grouping of Resources Recommendations."""@en; ; cat:DocLicense; data:W3C; "Protocol for Web Description Resources (POWDER): Web Description Resources (WDR) Vocabulary"; ; xhv:last ; rdfs:label "Protocol for Web Description Resources (POWDER): Web Description Resources (WDR) Vocabulary"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-25"^^xsd:date; """This is the namespace document for the XML schema used in the Protocol for Web Description resources (POWDER). It defines the datatypes used and the structure for Description Resources where these are serialized in XML."""@en; ; cat:DocLicense; data:W3C; "Protocol for Web Description Resources (POWDER): Web Description Resources Datatypes (WDRD)"; ; xhv:last ; rdfs:label "Protocol for Web Description Resources (POWDER): Web Description Resources Datatypes (WDRD)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-09-18"^^xsd:date; """ This specification describes a domain-specific policy assertion that indicates endpoint support of the optimized MIME multipart/related serialization of SOAP messages defined in section 3 of the SOAP Message Transmission Optimization Mechanism [MTOM] specification. This policy assertion can be specified within a policy alternative as defined in Web Services Policy 1.5 - Framework [WS-Policy] and attached to a WSDL description as defined in Web Services Policy 1.5 - Attachment [WS-PolicyAttachment]. """@en; ; cat:DocLicense; data:W3C; "MTOM Serialization Policy Assertion 1.1"; ; xhv:last ; rdfs:label "MTOM Serialization Policy Assertion 1.1"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-06-11"^^xsd:date; """ In 2005, 2006, and 2007 the W3C held workshops to understand the ways, if any, in which the design of SSML 1.0 limited its usefulness for authors of applications in Asian, Eastern European, and Middle Eastern languages. In 2006 an SSML subgroup of the W3C Voice Browser Working Group was formed to review this input and develop requirements for changes necessary to support those languages. This document contains those requirements. """@en; ; cat:DocLicense; data:W3C; "Speech Synthesis Markup Language Version 1.1 Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Speech Synthesis Markup Language Version 1.1 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-07-18"^^xsd:date; """This practical guide provides you with the knowledge required to effectively use the XML Binding Language 2.0. It introduces both the basic and advanced concepts of XBL and describes its syntax and scenarios that should be considered best-practice. It also describes the purpose of the language elements described in the XBL 2.0 specification.XBL describes the ability to associate elements in one document with script, event handlers, styles, and more complex content models in another document. You can use XBL to re-order and wrap content so that, for instance, simple HTML or XHTML markup can have complex CSS styles applied without requiring that the markup be polluted with multiple div elements. In addition, if you are a programmer, you can use XBL to implement new DOM interfaces, and, in conjunction with other specifications, it enables arbitrary XML tag sets to be treated as "widgets" (pluggable user interface components)."""@en; ; cat:DocLicense; data:W3C; "XBL 2.0 Primer: An Introduction for Developers"; ; xhv:last ; rdfs:label "XBL 2.0 Primer: An Introduction for Developers"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-03-30"^^xsd:date; """ Current web pages, written in HTML, contain significant inherent structured data. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites. An event on a web page can be directly imported into a user's desktop calendar. A license on a document can be detected so that the user is informed of his rights automatically. A photo's creator, camera setting information, resolution, and topic can be published as easily as the original photo itself, enabling structured search and sharing. RDFa is a syntax for expressing RDF structured data in HTML. This document provides use case scenarios for RDFa. An introduction to implementing RDFa is provided in the RDFa Primer, while the details of the syntax are explained in the RDFa Syntax (to be published). """@en; ; cat:DocLicense; data:W3C; "RDFa Use Cases: Scenarios for Embedding RDF in HTML"; ; xhv:last ; rdfs:label "RDFa Use Cases: Scenarios for Embedding RDF in HTML"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-02-16"^^xsd:date; """The XML Events module defined in this specification provides XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces [DOM2EVENTS]. The result is to provide an interoperable way of associating behaviors with document-level markup."""@en; ; cat:DocLicense; data:W3C; "XML Events 2"; ; xhv:last ; rdfs:label "XML Events 2"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-07-20"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Guide to Versioning XML Languages using new XML Schema 1.1 features"; ; xhv:last ; xhv:previous ; rdfs:label "Guide to Versioning XML Languages using new XML Schema 1.1 features"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2007-03-23"^^xsd:date; """ This document specifies goals and requirements for the XQuery Scripting Extension. """@en; ; cat:DocLicense; data:W3C; "XQuery Scripting Extension 1.0 Requirements"; ; xhv:last ; rdfs:label "XQuery Scripting Extension 1.0 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-10"^^xsd:date; """This specification defines in general a subset of CSS 2.1 [CSS21] that is to be considered a baseline for interoperability between implementations of CSS on constrained devices (e.g. mobile phones). Its intent is not to produce a profile of CSS incompatible with the complete specification, but rather to ensure that implementations that due to platform limitations cannot support the entire specification implement a common subset that is interoperable not only amongst constrained implementations but also with complete ones. Additionally, this specification aligns itself as much as possible with the OMA Wireless CSS 1.1 [WCSS11] specification. At the same time, OMA is doing alignment work in OMA Wireless CSS 1.2 [WCSS12]. It is aimed at aligning the mandatory compliance items between CSS Mobile Profile 2.0 and OMA Wireless CSS 1.2 [WCSS12]."""@en; ; cat:DocLicense; data:W3C; "CSS Mobile Profile 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Mobile Profile 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-05"^^xsd:date; """CSS describes the rendering of documents on various media. When documents (e.g., HTML) are laid out on visual media (e.g., screen or print) and the contents of some element are too large for a given area, CSS allows the designer to specify whether and how the overflow is displayed. One way, available on certain devices, is the “marquee†effect: the content is animated and moves automatically back and forth. This module defines the properties to control that effect."""@en; ; cat:DocLicense; data:W3C; "CSS Marquee Module Level 3"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Marquee Module Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-03"^^xsd:date; """The Resource Description Framework RDF allows users to describe both Web documents and concepts from the real world—people, organisations, topics, things—in a computer-processable way. Publishing such descriptions on the Web creates the Semantic Web. URIs (Uniform Resource Identifiers) are very important, providing both the core of the framework itself and the link between RDF and the Web. This document presents guidelines for their effective use. It discusses two strategies, called 303 URIs and hash URIs. It gives pointers to several Web sites that use these solutions, and briefly discusses why several other proposals have problems."""@en; ; cat:DocLicense; data:W3C; "Cool URIs for the Semantic Web"; ; xhv:last ; xhv:previous ; rdfs:label "Cool URIs for the Semantic Web"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-04-14"^^xsd:date; """ This document describes the Device Description Repository Core Vocabulary for Content Adaptation in the Mobile Web, described in the charter of the Device Descriptions Working Group, as well as the process by which the Vocabulary was defined. """@en; ; cat:DocLicense; data:W3C; "Device Description Repository Core Vocabulary"; ; xhv:last ; xhv:previous ; rdfs:label "Device Description Repository Core Vocabulary"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-06-04"^^xsd:date; """ The prototype we describe is a biomedical knowledge base, constructed for a demonstration at Banff WWW2007 , that integrates 15 distinct data sources using currently available Semantic Web technologies such as the W3C standard Web Ontology Language [OWL] and Resource Description Framework [RDF]. This report outlines which resources were integrated, how the knowledge base was constructed using free and open source triple store technology, how it can be queried using the W3C Recommended RDF query language SPARQL [SPARQL], and what resources and inferences are involved in answering complex queries. While the utility of the knowledge base is illustrated by identifying a set of genes involved in Alzheimer's Disease, the approach described here can be applied to any use case that integrates data from multiple domains. """@en; ; cat:DocLicense; data:W3C; "A Prototype Knowledge Base for the Life Sciences"; ; xhv:last ; xhv:previous ; rdfs:label "A Prototype Knowledge Base for the Life Sciences"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-06-04"^^xsd:date; """ One of the challenges facing Semantic Web for Health Care and Life Sciences is that of converting relational databases into Semantic Web format. The issues and the steps involved in such a conversion have not been well documented. To this end, we have created this document to describe the process of converting SenseLab databases into OWL. SenseLab is a collection of relational (Oracle) databases for neuroscientific research. The conversion of these databases into RDF/OWL format is an important step towards realizing the benefits of Semantic Web in integrative neuroscience research. This document describes how we represented some of the SenseLab databases in Resource Description Framework (RDF) and Web Ontology Language (OWL), and discusses the advantages and disadvantages of these representations. Our OWL representation is based on the reuse and extension of existing standard OWL ontologies developed in the biomedical ontology communities. The purpose of this document is to share our implementation experience with the community. """@en; ; cat:DocLicense; data:W3C; "Experiences with the conversion of SenseLab databases to RDF/OWL"; ; xhv:last ; xhv:previous ; rdfs:label "Experiences with the conversion of SenseLab databases to RDF/OWL"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-06-10"^^xsd:date; """ This document provides supplemental information on the 10 June 2008 working draft of the HTML 5 specification [HTML5]. It primarily documents changes that have been made to the HTML 5 draft specification since the time of its 22 January 2008 publication as a First Public Working Draft [HTML5FPWD]. """@en; ; cat:DocLicense; data:W3C; "HTML 5 Publication Notes"; ; xhv:last ; rdfs:label "HTML 5 Publication Notes"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-11-03"^^xsd:date; """ For historic reasons, some formats have allowed variants of IRIs that are somewhat less restricted in syntax, for example XML system identifiers and W3C XML Schema anyURIs. This document provides a definition and a name (Legacy Extended IRI or LEIRI) for these variants for easy reference. These variants have to be used with care; they require further processing before being fully interchangeable as IRIs. New protocols and formats should not use Legacy Extended IRIs. """@en; ; cat:DocLicense; data:W3C; "Legacy extended IRIs for XML resource identification"; ; xhv:last ; rdfs:label "Legacy extended IRIs for XML resource identification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-07-02"^^xsd:date; """ This document describes a multimodal system which implements the W3C Multimodal Architecture and gives an example of a simple multimodal application authored using various W3C markup languages, including SCXML, CCXML, VoiceXML 2.1 and HTML. """@en; ; cat:DocLicense; data:W3C; "Authoring Applications for the Multimodal Architecture"; ; xhv:last ; rdfs:label "Authoring Applications for the Multimodal Architecture"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-05-30"^^xsd:date; """HTML 5 contains several features that address the challenge of building Web applications that work while offline. This document highlights these features (SQL, offline application caching APIs as well as online/offline events, status, and the localStorage API) from HTML 5 and provides brief tutorials on how these features might be used to create Web applications that work offline. [HTML5]"""@en; ; cat:DocLicense; data:W3C; "Offline Web Applications"; ; xhv:last ; rdfs:label "Offline Web Applications"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-08-28"^^xsd:date; """This document describes best practice recipes for publishing vocabularies or ontologies on the Web (in RDF Schema or OWL). The features of each recipe are described in detail, so that vocabulary designers may choose the recipe best suited to their needs. Each recipe introduces general principles and an example configuration for use with an Apache HTTP server (which may be adapted to other environments). The recipes are all designed to be consistent with the architecture of the Web as currently specified, although the associated example configurations have been kept intentionally simple."""@en; ; cat:DocLicense; data:W3C; "Best Practice Recipes for Publishing RDF Vocabularies"; ; xhv:last ; xhv:previous ; rdfs:label "Best Practice Recipes for Publishing RDF Vocabularies"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-03-06"^^xsd:date; """ This Note refines the objectives for the Web Security Context Working Group deliverables. It elaborates upon the group's Charter [WSC-CHARTER] to explain what the group aims to achieve, what technologies may be used and how technical proposals will be evaluated. This elaboration is limited to the group's technical work and does not cover additional activities the group intends to engage in, such as ongoing outreach and education. This Note also includes an initial collection of use cases that the group expects will drive its technical work. Since this Note discusses the assumptions, goals, and processes the group will use to develop its recommendations, the intended audience is similiar to that of the charter of the Working Group; group members, the W3C community, developers of web user agents, web content providers (server administrators), and parties interested and engaged in what the Web Security Context Working Group's plans and directions are. It is explicitly not targeted at the presumed beneficiaries of the group's work, the users of the web, and it is not expected that an average user would be able to read this document and understand it. """@en; ; cat:DocLicense; data:W3C; "Web Security Experience, Indicators and Trust: Scope and Use Cases"; ; xhv:last ; xhv:previous ; rdfs:label "Web Security Experience, Indicators and Trust: Scope and Use Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-02-13"^^xsd:date; """ This document provides a set of guidelines for developing XML documents and schemas that are internationalized properly. Following the best practices describes here allow both the developer of XML applications, as well as the author of XML content to create material in different languages. """@en; ; cat:DocLicense; data:W3C; "Best Practices for XML Internationalization"; ; xhv:last ; xhv:previous ; rdfs:label "Best Practices for XML Internationalization"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-06-10"^^xsd:date; """ This document defines interoperability test cases for Canonical XML 1.1 [XML-C14N1.1] and XML Signature Syntax and Processing, Second Edition [XMLDSIG2]. The changes tested include C14N11 handling of attributes in the XML namespace, including xml:id and xml:base, appropriate C14N11 nodeset to octet stream transform processing, modifications to RFC 3986 dot segment processing for C14N11, and RFC 4514 string encoding of Distinguished Names. The tests include standalone C14N11 tests as well as tests integrated with XML signature generation and validation. This document also includes earlier test cases used in XML Signature [XMLDSIG] for regression testing. """@en; ; cat:DocLicense; data:W3C; "Test Cases for C14N 1.1 and XMLDSig Interoperability"; ; xhv:last ; rdfs:label "Test Cases for C14N 1.1 and XMLDSig Interoperability"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-04-11"^^xsd:date; """ This document specifies level 1 of the Cascading Style Sheet mechanism (CSS1). CSS1 is a simple style sheet mechanism that allows authors and readers to attach style (e.g. fonts, colors and spacing) to HTML documents. The CSS1 language is human readable and writable, and expresses style in common desktop publishing terminology. One of the fundamental features of CSS is that style sheets cascade; authors can attach a preferred style sheet, while the reader may have a personal style sheet to adjust for human or technological handicaps. The rules for resolving conflicts between different style sheets are defined in this specification. This Recommendation results from W3C activities in the area of Style Sheets. For background information on style sheets, see [1]. """@en; ; cat:DocLicense; data:W3C; "Cascading Style Sheets (CSS1) Level 1 Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Cascading Style Sheets (CSS1) Level 1 Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-05"^^xsd:date; """ Web content delivered to mobile devices usually benefits from being tailored to take into account a range of factors such as screen size, markup language support and image format support. Such information is stored in "Device Description Repositories" (DDRs). This document describes a simple API for access to DDRs, in order to ease and promote the development of Web content that adapts to its Delivery Context. """@en; ; cat:DocLicense; data:W3C; "Device Description Repository Simple API"; ; xhv:last ; xhv:previous ; rdfs:label "Device Description Repository Simple API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-22"^^xsd:date; """ This specification defines the ElementTraversal interface, which allows script navigation of the elements of a DOM tree, excluding all other nodes in the DOM, such as text nodes. It also provides an attribute to expose the number of child elements of an element. It is intended to provide a more convenient alternative to existing DOM navigation interfaces, with a low implementation footprint. """@en; ; cat:DocLicense; data:W3C; "Element Traversal Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Element Traversal Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-01"^^xsd:date; """ This document specifies the third version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL 3.0 has the following design goals: Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL, an author may describe the temporal behaviour of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen.Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL components are used for integrating timing into XHTML [XHTML10] and into SVG [SVG].Extend the functionalities contained in the SMIL 2.1 [SMIL21] into new or revised SMIL 3.0 modules.Define new SMIL 3.0 Profiles incorporating features useful within the industry. """@en; ; cat:DocLicense; data:W3C; "Synchronized Multimedia Integration Language (SMIL 3.0)"; ; xhv:last ; xhv:previous ; rdfs:label "Synchronized Multimedia Integration Language (SMIL 3.0)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-22"^^xsd:date; """This specification defines the features and syntax for Scalable Vector Graphics (SVG) Tiny, Version 1.2, a language for describing two-dimensional vector graphics in XML, combined with raster graphics and multimedia. Its goal is to provide the ability to create a whole range of graphical content, from static images to animations to interactive Web applications. SVG 1.2 Tiny is a profile of SVG intended for implementation on a range of devices, from cellphones and PDAs to laptop and desktop computers, and thus includes a subset of the features included in SVG 1.1 Full, along with new features to extend the capabilities of SVG. Further extensions are planned in the form of modules which will be compatible with SVG 1.2 Tiny, and which when combined with this specification, will match and exceed the capabilities of SVG 1.1 Full."""@en; ; cat:DocLicense; data:W3C; "Scalable Vector Graphics (SVG) Tiny 1.2 Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Scalable Vector Graphics (SVG) Tiny 1.2 Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-11"^^xsd:date; """ Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general. WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material. WCAG 2.0 succeeds Web Content Accessibility Guidelines 1.0 [WCAG10], which was published as a W3C Recommendation May 1999. Although it is possible to conform either to WCAG 1.0 or to WCAG 2.0 (or both), the W3C recommends that new and updated content use WCAG 2.0. The W3C also recommends that Web accessibility policies reference WCAG 2.0. """@en; ; cat:DocLicense; data:W3C; "Web Content Accessibility Guidelines (WCAG) 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Web Content Accessibility Guidelines (WCAG) 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-07-29"^^xsd:date; """ This document specifies Best Practices for delivering Web content to mobile devices. The principal objective is to improve the user experience of the Web when accessed from such devices. The recommendations refer to delivered content and not to the processes by which it is created, nor to the devices or user agents to which it is delivered. It is primarily directed at creators, maintainers and operators of Web sites. Readers of this document are expected to be familiar with the creation of Web sites, and to have a general familiarity with the technologies involved, such as Web servers and HTTP. Readers are not expected to have a background in mobile-specific technologies. """@en; ; cat:DocLicense; data:W3C; "Mobile Web Best Practices 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Mobile Web Best Practices 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-08"^^xsd:date; """ This document defines the tests that provide the basis for making a claim of W3C® mobileOKâ„¢ Basic conformance and are based on W3C Mobile Web Best Practices [Best Practices]. The details of how to claim mobileOK conformance will be described separately. Providers of content which passes the tests have taken some steps to provide a functional user experience for users of basic mobile devices whose capabilities at least match those of the Default Delivery Context (DDC). mobileOK Basic primarily assesses basic usability, efficiency and interoperability. It does not address the important goal of assessing whether users of more advanced devices enjoy a richer user experience than is possible using the DDC. """@en; ; cat:DocLicense; data:W3C; "W3C mobileOK Basic Tests 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "W3C mobileOK Basic Tests 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-10-14"^^xsd:date; """ This document defines the syntax for specifying pronunciation lexicons to be used by Automatic Speech Recognition and Speech Synthesis engines in voice browser applications. """@en; ; cat:DocLicense; data:W3C; "Pronunciation Lexicon Specification (PLS) Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Pronunciation Lexicon Specification (PLS) Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-01-15"^^xsd:date; """ RDF is a flexible, extensible way to represent information about World Wide Web resources. It is used to represent, among other things, personal information, social networks, metadata about digital artifacts like music and images, as well as provide a means of integration over disparate sources of information. 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. This document describes an XML format for the variable binding and boolean results formats provided by the SPARQL query language for RDF, developed by the W3C RDF Data Access Working Group (DAWG), part of the Semantic Web Activity as described in the activity statement . """@en; ; cat:DocLicense; data:W3C; "SPARQL Query Results XML Format"; ; xhv:last ; xhv:previous ; rdfs:label "SPARQL Query Results XML Format"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-01-15"^^xsd:date; """ The SPARQL Protocol and RDF Query Language (SPARQL) is a query language and protocol for RDF. This document specifies the SPARQL Protocol; it uses WSDL 2.0 to describe a means for conveying SPARQL queries to an SPARQL query processing service and returning the query results to the entity that requested them. This protocol was developed by the W3C RDF Data Access Working Group (DAWG), part of the Semantic Web Activity as described in the activity statement . """@en; ; cat:DocLicense; data:W3C; "SPARQL Protocol for RDF"; ; xhv:last ; xhv:previous ; rdfs:label "SPARQL Protocol for RDF"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-01-15"^^xsd:date; """ RDF is a directed, labeled graph data format for representing information in the Web. This specification defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. SPARQL contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. SPARQL also supports extensible value testing and constraining queries by source RDF graph. The results of SPARQL queries can be results sets or RDF graphs. """@en; ; cat:DocLicense; data:W3C; "SPARQL Query Language for RDF"; ; xhv:last ; xhv:previous ; rdfs:label "SPARQL Query Language for RDF"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-10-14"^^xsd:date; """The current Web is primarily made up of an enormous number of documents that have been created using HTML. These documents contain significant amounts of structured data, which is largely unavailable to tools and applications. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported into a user's desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo's creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing.RDFa is a specification for attributes to express structured data in any markup language. This document specifies how to use RDFa with XHTML. The rendered, hypertext data of XHTML is reused by the RDFa markup, so that publishers don't need to repeat significant data in the document content. The underlying abstract representation is RDF [RDF-PRIMER], which lets publishers build their own vocabulary, extend others, and evolve their vocabulary with maximal interoperability over time. The expressed structure is closely tied to the data, so that rendered data can be copied and pasted along with its relevant structure.The rules for interpreting the data are generic, so that there is no need for different rules for different formats; this allows authors and publishers of data to define their own formats without having to update software, register formats via a central authority, or worry that two formats may interfere with each other.RDFa shares some use cases with microformats [MICROFORMATS]. Whereas microformats specify both a syntax for embedding structured data into HTML documents and a vocabulary of specific terms for each microformat, RDFa specifies only a syntax and relies on independent specification of terms (often called vocabularies or taxonomies) by others. RDFa allows terms from multiple independently-developed vocabularies to be freely intermixed and is designed such that the language can be parsed without knowledge of the specific term vocabulary being used.This document is a detailed syntax specification for RDFa, aimed at:those looking to create an RDFa parser, and who therefore need a detailed description of the parsing rules;those looking to recommend the use of RDFa within their organisation, and who would like to create some guidelines for their users;anyone familiar with RDF, and who wants to understand more about what is happening 'under the hood', when an RDFa parser runs.For those looking for an introduction to the use of RDFa and some real-world examples, please consult the RDFa Primer.How to Read this DocumentIf you are already familiar with RDFa, and you want to examine the processing rules — perhaps to create a parser — then you'll find the Processing Model section of most interest. It contains an overview of each of the processing steps, followed by more detailed sections, one for each rule.If you are not familiar with RDFa, but you are familiar with RDF, then you might find reading the Syntax Overview useful, before looking at the Processing Model since it gives a range of examples of XHTML mark-up that use RDFa. Seeing some examples first should make reading the processing rules easier.If you are not familiar with RDF, then you might want to take a look at the section on RDF Terminology before trying to do too much with RDFa. Although RDFa is designed to be easy to author—and authors don't need to understand RDF to use it—anyone writing applications that consume RDFa will need to understand RDF. There is a lot of material about RDF on the web, and a growing range of tools that support RDFa, so all we try to do in this document is provide enough background on RDF to make the goals of RDFa clearer.And finally, if you are not familiar with either RDFa or RDF, and simply want to add RDFa to your documents, then you may find the RDFa Primer [RDFaPRIMER] to be a better introduction."""@en; ; cat:DocLicense; data:W3C; "RDFa in XHTML: Syntax and Processing"; ; xhv:last ; xhv:previous ; rdfs:label "RDFa in XHTML: Syntax and Processing"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-07-29"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XHTML™ Basic 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML™ Basic 1.1"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-11-26"^^xsd:date; """ 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. """@en; ; cat:DocLicense; data:W3C; "Extensible Markup Language (XML) 1.0 (Fifth Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Extensible Markup Language (XML) 1.0 (Fifth Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-05-02"^^xsd:date; """ Canonical XML Version 1.1 is a revision to Canonical XML Version 1.0 to address issues related to inheritance of attributes in the XML namespace when canonicalizing document subsets, including the requirement not to inherit xml:id, and to treat xml:base URI path processing properly. Any XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 [XML] and Namespaces in XML 1.0 [Names]. 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. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on application-specific equivalence rules for which no generalized XML specification could account. Canonical XML Version 1.1 is applicable to XML 1.0 and defined in terms of the XPath 1.0 data model. It is not defined for XML 1.1. """@en; ; cat:DocLicense; data:W3C; "Canonical XML Version 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "Canonical XML Version 1.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-06-10"^^xsd:date; """ This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere. """@en; ; cat:DocLicense; data:W3C; "XML Signature Syntax and Processing (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Signature Syntax and Processing (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-19"^^xsd:date; """ XForms for HTML provides a set of attributes and script methods that can be used by the tags or elements of an HTML or XHTML web page to simplify the integration of data-intensive interactive processing capabilities from XForms. The semantics of the attributes are mapped to the rich XForms model-view-controller-connector architecture, thereby allowing web application authors a smoother, selective migration path to the higher-order behaviors available from the full element markup available in modules of XForms. """@en; ; cat:DocLicense; data:W3C; "XForms for HTML"; ; xhv:last ; rdfs:label "XForms for HTML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-05"^^xsd:date; """ Content Adaptation on the Mobile Web can be simplified by creating groups for those devices that share common characteristics. This WG Note defines an XML format, a group definition syntax and an extension to the DDR Simple API that can be used in the development of adaptive Mobile Web sites that exploit grouping. """@en; ; cat:DocLicense; data:W3C; "Device Description Structures"; ; xhv:last ; rdfs:label "Device Description Structures"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-09-03"^^xsd:date; """ The Efficient XML Interchange (EXI) format defines a new representation for the Extensible Markup Language (XML) Information Set. The introduction of such a format may cause disruption in systems that have so far been able to assume XML as the only representation of XML Information Set data. This document reviews areas where the introduction of EXI may disrupt or otherwise have an impact on existing XML technologies, XML processors, and applications. It also describes EXI design features and steps that may be taken by implementors to reduce or eliminate disruption and impacts. """@en; ; cat:DocLicense; data:W3C; "Efficient XML Interchange (EXI) Impacts"; ; xhv:last ; rdfs:label "Efficient XML Interchange (EXI) Impacts"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-18"^^xsd:date; """ This document, developed by the Rule Interchange Format (RIF) Working Group, specifies use cases and requirements for the W3C Rule Interchange Format, a family of rule interchange dialects that allows rules to be translated between rule languages and thus transferred between rule systems. """@en; ; cat:DocLicense; data:W3C; "RIF Use Cases and Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Use Cases and Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-08-08"^^xsd:date; """ The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirement studies for voice browsers, and provides details of the requirements for marking up spoken dialogs. """@en; ; cat:DocLicense; data:W3C; "Voice Extensible Markup Language (VoiceXML) 3.0 Requirements"; ; xhv:last ; rdfs:label "Voice Extensible Markup Language (VoiceXML) 3.0 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-05-14"^^xsd:date; """ This document provides a review and analysis of guidelines and articles relating to the needs of older people with Web accessibility needs due to ageing, and compares these with the needs of people with disabilities as already addressed in WAI guidelines. The focus is particularly on Europe but applies internationally as well. This review is being undertaken in order to inform the development of educational materials which can better promote the needs of people who have accessibility needs due to ageing, and potential development of profiles and/or extensions on WAI guidelines. """@en; ; cat:DocLicense; data:W3C; "Web Accessibility for Older Users: A Literature Review"; ; xhv:last ; rdfs:label "Web Accessibility for Older Users: A Literature Review"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-02-04"^^xsd:date; """ The Roadmap for Accessible Rich Internet Applications addresses the accessibility of dynamic Web content for people with disabilities. The roadmap introduces the technologies to map controls, Ajax live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications. The roadmap also describes new navigation techniques to mark common Web structures as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview. """@en; ; cat:DocLicense; data:W3C; "Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)"; ; xhv:last ; xhv:previous ; rdfs:label "Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-04-14"^^xsd:date; """ This document surveys a group of market-leading widget user agents with the aim to inform the requirements of the Widgets 1.0: Requirements document. The survey exposes commonalities and fragmentation across widget user agents, and discusses how fragmentation currently affects, amongst other things, authoring, security, distribution and deployment, internationalisation and the device-independence of widgets. The document concludes by making a set of recommendations on what aspects of widgets require standardization to reduce fragmentation to ultimately standardize a cross-platform widget solution. """@en; ; cat:DocLicense; data:W3C; "Widgets 1.0: The Widget Landscape (Q1 2008)"; ; xhv:last ; rdfs:label "Widgets 1.0: The Widget Landscape (Q1 2008)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-12-03"^^xsd:date; """ This document specifies usage scenarios for the XQuery Scripting Extension. """@en; ; cat:DocLicense; data:W3C; "XQuery Scripting Extension 1.0 Use Cases"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery Scripting Extension 1.0 Use Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2008-03-26"^^xsd:date; """ The XSL 1.1 specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. This document enumerates the collected requirements for a 2.0 version of XSL. There are two parts to XSL: XSL Transformations (XSLT) for transformation of documents and XSL Formatting Objects (XSL-FO) for formatting of documents. This is the requirements document for XSL-FO and not for XSLT. """@en; ; cat:DocLicense; data:W3C; "Extensible Stylesheet Language (XSL) Requirements Version 2.0"; ; xhv:last ; rdfs:label "Extensible Stylesheet Language (XSL) Requirements Version 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-04-09"^^xsd:date; """ This document describes an activity of integrating personalization with device context for the delivery of content materials and interface components that are customized to meet both individual personal needs and preferences and delivery context. It brings together the work of separate standards and specifications organizations and working groups, notably W3C Ubiquitous Web Applications working group, IMS Global Learning Consortium Accessibility Special Interest group, ISO/IEC JTC1 SC36 Information Technology for Learning, Education and Training: Human Diversity and Access For All working group and associated working groups in SC36. The document should be viewed as a roadmap for the work to be undertaken and includes description of the basis for the work, the organizational context, the likely technologies and a partially complete description of how the technologies fit together. """@en; ; cat:DocLicense; data:W3C; "W3C Personalization Roadmap: Ubiquitous Web Integration of AccessForAll 1.0"; ; xhv:last ; rdfs:label "W3C Personalization Roadmap: Ubiquitous Web Integration of AccessForAll 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-09-15"^^xsd:date; """ This document describes requirements for some important aspects of the character model for W3C specifications. The two aspects discussed are string identity matching and string indexing. Both aspects are considered to be vital for the seamless interaction of many components of the current and future web architecture. """@en; ; cat:DocLicense; data:W3C; "Requirements for String Identity Matching and String Indexing"; ; xhv:last ; xhv:previous ; rdfs:label "Requirements for String Identity Matching and String Indexing"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ This document identifies the issues surrounding use of transforming proxies in the delivery of Web content. It does not comment on the techniques that cause these issues, it merely identifies them in order to inform the requirements of the Content Transformation Guidelines document. That document is to offer recommendations as to how components of the delivery context can cooperate to achieve, at a minimum, a functional user experience. In this revision the document is largely historical - the Content Transformation Guidelines document, published under the title "Guidelines for Web Content Transformation Proxies" was initially inspired by the set of requirements identified in this document, but has subsequently evolved based on available technologies and feedback. """@en; ; cat:DocLicense; data:W3C; "Content Transformation Landscape 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Content Transformation Landscape 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-15"^^xsd:date; """ These are the requirements intended to be met in the development of client-side APIs that enable the creation of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc."""@en; ; cat:DocLicense; data:W3C; "Device APIs Requirements"; ; xhv:last ; rdfs:label "Device APIs Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-05-12"^^xsd:date; """As support for Web technologies grows, it is important that tests writers develop test suites that will work as well as possible across devices. This document offers guidance in the form of simple guidelines to follow to create device-independent tests."""@en; ; cat:DocLicense; data:W3C; "Guidelines for writing device independent tests"; ; xhv:last ; rdfs:label "Guidelines for writing device independent tests"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-05-12"^^xsd:date; """Current Web technology allows governments to share with the public a variety of information in unlimited quantities on demand. Technology is also available to allow citizens to bring issues of concern to the attention of local, regional and national governments. However, exploiting these capabilities within government systems is a challenge that encompasses environmental, policy, legal, and cultural issues. Establishing effective eGovernment requires openness, transparency, collaboration and skill in taking advantage of the capabilities of the World Wide Web. The rich potential for two-way dialogue between citizens and government creates a need for global leadership. The W3C has an opportunity to provide guidance in support of eGovernment objectives by promoting existing open Web standards and noting the challenges external to the Web and technology. There is also role for the W3C to facilitate the development and vetting of new open Web standards needed by governments in context.This document is an attempt to describe, but not yet solve, the variety of issues and challenges faced by governments in their efforts to apply 21st century capabilities to eGovernment initiatives. Detail and useful examples of existing, applicable open Web standards are provided. Where government needs in the development of eGovernment services are not currently met by existing standards, those gaps are noted."""@en; ; cat:DocLicense; data:W3C; "Improving Access to Government through Better Use of the Web"; ; xhv:last ; xhv:previous ; rdfs:label "Improving Access to Government through Better Use of the Web"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-12-15"^^xsd:date; """ The EMMA: Extensible MultiModal Annotation specification defines an XML markup language for capturing and providing metadata on the interpretation of inputs to multimodal systems. Throughout the implementation report process and discussion since EMMA 1.0 became a W3C Recommendation, a number of new possible use cases for the EMMA language have emerged. These include the use of EMMA to represent multimodal output, biometrics, emotion, sensor data, multi-stage dialogs, and interactions with multiple users. In this document, we describe these use cases and illustrate how the EMMA language could be extended to support them. """@en; ; cat:DocLicense; data:W3C; "Use Cases for Possible Future EMMA Features"; ; xhv:last ; rdfs:label "Use Cases for Possible Future EMMA Features"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-20"^^xsd:date; """ As in several other scientific domains, the use of social software (such as blogs or wikis) and social networking applications is now commonly accepted in the Health Care and Life Science (HCLS) research community, with services such as the SWAN Alzheimer Knowledge Base, myExperiment, WikiProfessional Concept Web, Connotea and Nature Networks. In general, however, these applications suffer from a lack of interoperability, and this makes the reuse of information a complex task. The SIOC Ontology - Semantically-Interlinked Online Communities - aims to solve these issues and provides a comprehensive model to represent online communities and related user-generated content items thanks to Semantic Web technologies. This note describes the changes to the SIOC Core Ontology since its W3C Member Submission in June 2007, the SIOC Types Module, and their relevance in the Health Care and Life Sciences context. """@en; ; cat:DocLicense; data:W3C; "SIOC, SIOC Types and Health Care and Life Sciences"; ; xhv:last ; rdfs:label "SIOC, SIOC Types and Health Care and Life Sciences"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-20"^^xsd:date; """ Developing cures for highly complex diseases, such as neurodegenerative disorders, requires extensive interdisciplinary collaboration and exchange of biomedical information in context. Our ability to exchange such information across sub-specialties today is limited by the current scientific knowledge ecosystem’s inability to properly contextualize and integrate data and discourse in machine-interpretable form. This inherently limits the productivity of research and the progress toward cures for devastating diseases such as Alzheimer’s and Parkinson’s. The SWAN (Semantic Web Applications in Neuromedicine) ontology is an ontology for modeling scientific discourse and has been developed in the context of building a series of applications for biomedical researchers, as well as extensive discussions and collaborations with the larger bio-ontologies community. This document describes the SWAN ontology of scientific discourse. """@en; ; cat:DocLicense; data:W3C; "Semantic Web Applications in Neuromedicine (SWAN) Ontology"; ; xhv:last ; rdfs:label "Semantic Web Applications in Neuromedicine (SWAN) Ontology"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-20"^^xsd:date; """This notes describes the alignment between the SWAN - Semantic Web Applications in Neuromedicine - and SIOC - Semantically-Interlinked Online Communities - ontologies, providing a complete model to represent Scientific Discourse in online communities at different levels of granularity (discourse elements and content items). The goal of this alignment is to make the discourse structure and component relationships much more accessible to computation, so that information can be navigated, compared and understood in context far better that at present, across and within domains."""@en; ; cat:DocLicense; data:W3C; "SWAN/SIOC: Alignment Between the SWAN and SIOC Ontologies"; ; xhv:last ; rdfs:label "SWAN/SIOC: Alignment Between the SWAN and SIOC Ontologies"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-09-08"^^xsd:date; ; cat:DocLicense; data:W3C; "Authoring HTML: Handling Right-to-left Scripts"; ; xhv:last ; xhv:previous ; rdfs:label "Authoring HTML: Handling Right-to-left Scripts"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-08-25"^^xsd:date; """The mobileOK scheme allows content providers to promote their content as being suitable for use on very basic mobile devices. This document provides an overview of the scheme and references the documentation that composes it."""@en; ; cat:DocLicense; data:W3C; "W3C mobileOK Scheme 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "W3C mobileOK Scheme 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-12-08"^^xsd:date; """ This document is the heart of the MW4D IG work. Its purpose is to understand the current challenges of deploying development-oriented services on mobile phones, evaluate existing technologies, and identify the most promising directions to lower the barriers of developing, deploying and accessing services on mobile phones and thereby creating an enabling environment for more social-oriented services to appear. This document is divided into two major parts. The first part presents the major challenges today for both developing and accessing mobile services, potential ways to bridge them with existing tools, technologies and infrastructure, and potential research directions to follow to provide a more comprehensive resolution or solution. The second part focuses on presenting the major technologies and the major options existing today to deploy content and applications on mobile phones. For each of these technologies, the document presents a short analysis of the technology's potential and the requirements in terms of infrastructure, devices, targeted end-users, and costs associated with implementation and delivery. """@en; ; cat:DocLicense; data:W3C; "Mobile Web for Social Development Roadmap"; ; xhv:last ; xhv:previous ; rdfs:label "Mobile Web for Social Development Roadmap"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-20"^^xsd:date; """ This document supplements W3C Mobile Web Best Practices 1.0 [MWBP] by providing additional evaluations of conformance to Best Practice statements and by providing additional interpretations of Best Practice statements. """@en; ; cat:DocLicense; data:W3C; "Extended Guidelines for Mobile Web Best Practices 1.0"; ; xhv:last ; rdfs:label "Extended Guidelines for Mobile Web Best Practices 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-07-09"^^xsd:date; """This technical report describes the similarities and differences between the requirements in Web Content Accessibility Guidelines (WCAG) and Mobile Web Best Practices 1.0 (MWBP). Introductory information and links to related documents are in Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices."""@en; ; cat:DocLicense; data:W3C; "Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG)"; ; xhv:last ; xhv:previous ; rdfs:label "Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-09-01"^^xsd:date; """POWDER — the Protocol for Web Description Resources — provides a mechanism to describe and discover Web resources and helps the users to make a decision whether a given resource is of interest. There are a variety of use cases: from providing a better means to describing Web resources and creating trustmarks to aiding content discovery, child protection and Semantic Web searches.There are two varieties of POWDER: a complex, semantically rich variety, called POWDER-S, and a much simpler version, just called POWDER, which is intended as the primary transport mechanism for Description Resources. POWDER-S can be generated automatically from POWDER."""@en; ; cat:DocLicense; data:W3C; "Protocol for Web Description Resources (POWDER): Primer"; ; xhv:last ; xhv:previous ; rdfs:label "Protocol for Web Description Resources (POWDER): Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-09-10"^^xsd:date; """The document describes and presents test cases for the Protocol for Web Description Resources (POWDER). The test cases aim to indicate the correct formats of POWDER documents and illustrate various crucial aspects on the usage of POWDER documents, such as locating a document and infering information from it."""@en; ; cat:DocLicense; data:W3C; "Protocol for Web Description Resources (POWDER): Test Suite"; ; xhv:last ; xhv:previous ; rdfs:label "Protocol for Web Description Resources (POWDER): Test Suite"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-08-18"^^xsd:date; """ SKOS—Simple Knowledge Organization System—provides a model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, folksonomies, and other similar types of controlled vocabulary. As an application of the Resource Description Framework (RDF), SKOS allows concepts to be composed and published on the World Wide Web, linked with data on the Web and integrated into other concept schemes. This document is a user guide for those who would like to represent their concept scheme using SKOS. In basic SKOS, conceptual resources (concepts) are identified with URIs, labeled with strings in one or more natural languages, documented with various types of note, semantically related to each other in informal hierarchies and association networks, and aggregated into concept schemes. In advanced SKOS, conceptual resources can be mapped across concept schemes and grouped into labeled or ordered collections. Relationships can be specified between concept labels. Finally, the SKOS vocabulary itself can be extended to suit the needs of particular communities of practice or combined with other modeling vocabularies. This document is a companion to the SKOS Reference, which provides the normative reference on SKOS. """@en; ; cat:DocLicense; data:W3C; "SKOS Simple Knowledge Organization System Primer"; ; xhv:last ; xhv:previous ; rdfs:label "SKOS Simple Knowledge Organization System Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-08-18"^^xsd:date; """Knowledge organization systems, such as taxonomies, thesauri or subject heading lists, play a fundamental role in information structuring and access. The Semantic Web Deployment Working Group aims at providing a model for representing such vocabularies on the Semantic Web: SKOS (Simple Knowledge Organization System).This document presents the preparatory work for the 2009 version of SKOS [SKOS-REFERENCE]. It lists representative use cases, which were obtained after a dedicated questionnaire was sent to a wide audience. It also features a set of fundamental or secondary requirements derived from these use cases, that have been used to guide the design of SKOS.This document is a companion to the SKOS Reference and the SKOS Primer, which respectively provide the normative reference on SKOS and a user guide for those who would like to represent their concept scheme using SKOS."""@en; ; cat:DocLicense; data:W3C; "SKOS Use Cases and Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "SKOS Use Cases and Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-06-30"^^xsd:date; """ The Service Modeling Language [SML] specification extends the Extensible Mark-up Language [XML] and XML Schema [XML Schema] with a mechanism for incorporating into XML documents references to other documents or document fragments. This technical note addresses the construction of SML reference schemes for document or document fragment references that employ WS-Addressing [WS-A] endpoint references (EPRs). """@en; ; cat:DocLicense; data:W3C; "Framework for SML EPR-Based Reference Schemes"; ; xhv:last ; rdfs:label "Framework for SML EPR-Based Reference Schemes"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-23"^^xsd:date; """The Service Modeling Language [SML] specification extends the Extensible Mark-up Language [XML] and XML Schema [XML Schema] with a mechanism for incorporating into XML documents references to other documents or document fragments. This technical note addresses the construction of an SML reference scheme based on the XML Linking Language [XLink]."""@en; ; cat:DocLicense; data:W3C; "The SML XLink Reference Scheme"; ; xhv:last ; xhv:previous ; rdfs:label "The SML XLink Reference Scheme"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-01-16"^^xsd:date; ; cat:DocLicense; data:W3C; "XHTML Media Types - Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML Media Types - Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-05-05"^^xsd:date; """ This specification provides a set of basic [XML Schema 1.0] patterns known to be interoperable between state of the art databinding implementations. The patterns may be used to describe [XML 1.0] representations of commonly used data structures. The data structures described are intended to be independent of any particular programming language, database or modelling environment. """@en; ; cat:DocLicense; data:W3C; "Basic XML Schema Patterns for Databinding Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Basic XML Schema Patterns for Databinding Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-05-05"^^xsd:date; """ This specification provides a set of commonly used [XML Schema 1.0] patterns known to cause issues with some state of the art databinding implementations. The patterns in conjunction with the [Basic Patterns] may be used to describe XML representations of commonly used data structures. The data structures described are intended to be independent of any particular programming language, database or modelling environment. """@en; ; cat:DocLicense; data:W3C; "Advanced XML Schema Patterns for Databinding Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Advanced XML Schema Patterns for Databinding Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-07-30"^^xsd:date; """ Key derivation is a well-established mechanism for generating new cryptographic keys material from some existing, original ("master") key material and potentially other information. This document augments XML Signature and XML Encryption by defining XML types and elements necessary to enable use of derived keys in XML security applications. """@en; ; cat:DocLicense; data:W3C; "XML Security Derived Keys"; ; xhv:last ; xhv:previous ; rdfs:label "XML Security Derived Keys"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-04-21"^^xsd:date; """ This specification defines the syntax and semantics of XSLT 2.0, a language for transforming XML documents into other XML documents. XSLT 2.0 is a revised version of the XSLT 1.0 Recommendation [XSLT 1.0] published on 16 November 1999. XSLT 2.0 is designed to be used in conjunction with XPath 2.0, which is defined in [XPath 2.0]. XSLT shares the same data model as XPath 2.0, which is defined in [Data Model], and it uses the library of functions and operators defined in [Functions and Operators]. XSLT 2.0 also includes optional facilities to serialize the results of a transformation, by means of an interface to the serialization component described in [XSLT and XQuery Serialization]. This document contains hyperlinks to specific sections or definitions within other documents in this family of specifications. These links are indicated visually by a superscript identifying the target specification: for example XP for XPath, DM for the XDM data model, FO for Functions and Operators. """@en; ; cat:DocLicense; data:W3C; "XSL Transformations (XSLT) Version 2.0 (Second Edition)"; ; xhv:last ; rdfs:label "XSL Transformations (XSLT) Version 2.0 (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-11-24"^^xsd:date; """ The W3C Digital Signature Working Group ("DSig") proposes a standard format for making digitally-signed, machine-readable assertions about a particular information resource. PICS 1.1 labels are an example of such machine-readable assertions. This document describes a method of adding extensions to PICS 1.1 labels for purposes of signing them. More generally, it is the goal of the DSig project to provide a mechanism to make the statement: signer believes statement about information resource. In DSig 1.0 statement is any statement that can be expressed with PICS 1.1. """@en; ; cat:DocLicense; data:W3C; "PICS Signed Labels (DSig) 1.0 Specification"; ; xhv:last ; xhv:previous ; rdfs:label "PICS Signed Labels (DSig) 1.0 Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-11-24"^^xsd:date; """ This document has been prepared for the technical subcommittee of PICS (Platform for Internet Content Selection). It defines a general format for labels and three methods by which these labels may be transmitted: In an HTML document.With a document transported via a protocol that uses RFC-822 headers.Separately from the document. Table of Contents Overview General Format Example Detailed Syntax Semantics of PICS Labels and Label Lists Embedding Labels in HyperText Markup Language (HTML) Using HTTP to Request Labels With A Document Requesting Labels Separately MICs and Digital Signatures Glossary Acknowledgments Appendix A: An Algorithm for Locating a Label Bureau Appendix B: Sample Label Bureau Queries and Responses """@en; ; cat:DocLicense; data:W3C; "PICS 1.1 Label Distribution -- Label Syntax and Communication Protocols"; ; xhv:last ; xhv:previous ; rdfs:label "PICS 1.1 Label Distribution -- Label Syntax and Communication Protocols"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-11-24"^^xsd:date; """ This document, which has been prepared for the technical subcommittee of PICS (Platform for Internet Content Selection), defines a language for describing rating services. Software programs will read service descriptions written in this language, in order to interpret content labels and assist end-users in configuring selection software. Table of Contents Introduction What is a "rating service"? What is a "rating system"? What is a "content label"? The application/pics-service document type Explanation of Sample Rating Service Detailed syntax of application/pics-service Glossary References Acknowledgments Appendix A: The Ages Rating Service Appendix B: RSAC Rating Service Appendix C: The SafeSurf~~ Rating Service """@en; ; cat:DocLicense; data:W3C; "PICS 1.1 Rating Services and Rating Systems -- and Their Machine Readable Descriptions"; ; xhv:last ; xhv:previous ; rdfs:label "PICS 1.1 Rating Services and Rating Systems -- and Their Machine Readable Descriptions"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-11-24"^^xsd:date; """ This document defines a language for writing profiles, which are filtering rules that allow or block access to URLs based on PICS labels that describe those URLs. This language is intended as a transmission format; individual implementations must be able to read and write their specifications in this language, but need not use this format internally. """@en; ; cat:DocLicense; data:W3C; "PICSRules 1.1 Specification"; ; xhv:last ; xhv:previous ; rdfs:label "PICSRules 1.1 Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-02-10"^^xsd:date; """The W3C Multimodal Interaction Working Group aims to develop specifications to enable access to the Web using multimodal interaction. This document is part of a set of specifications for multimodal systems, and provides details of an XML markup language for containing and annotating the interpretation of user input. Examples of interpretation of user input are a transcription into words of a raw signal, for instance derived from speech, pen or keystroke input, a set of attribute/value pairs describing their meaning, or a set of attribute/value pairs describing a gesture. The interpretation of the user's input is expected to be generated by signal interpretation processes, such as speech and ink recognition, semantic interpreters, and other types of processors for use by components that act on the user's inputs such as interaction managers."""@en; ; cat:DocLicense; data:W3C; "EMMA: Extensible MultiModal Annotation markup language"; ; xhv:last ; xhv:previous ; rdfs:label "EMMA: Extensible MultiModal Annotation markup language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document describes the conditions that OWL 2 tools must satisfy in order to be conformant with the language specification. It also presents a common format for OWL 2 test cases that both illustrate the features of the language and can be used for testing conformance. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language Conformance"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language Conformance"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document provides the direct model-theoretic semantics for OWL 2, which is compatible with the description logic SROIQ. Furthermore, this document defines the most common inference problems for OWL 2. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language Direct Semantics"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language Direct Semantics"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document defines the mapping of OWL 2 ontologies into RDF graphs, and vice versa. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language Mapping to RDF Graphs"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language Mapping to RDF Graphs"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document is a simple introduction to the new features of the OWL 2 Web Ontology Language, including an explanation of the differences between the initial version of OWL and OWL 2. The document also presents the requirements that have motivated the design of the main new features, and their rationale from a theoretical and implementation perspective. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language New Features and Rationale"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language New Features and Rationale"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. This document serves as an introduction to OWL 2 and the various other OWL 2 documents. It describes the syntaxes for OWL 2, the different kinds of semantics, the available profiles (sub-languages), and the relationship between OWL 1 and OWL 2. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language Document Overview"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language Document Overview"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This primer provides an approachable introduction to OWL 2, including orientation for those coming from other disciplines, a running example showing how OWL 2 can be used to represent first simple information and then more complex information, how OWL 2 manages ontologies, and finally the distinctions between the various sublanguages of OWL 2. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language Primer"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document provides a specification of several profiles of OWL 2 which can be more simply and/or efficiently implemented. In logic, profiles are often called fragments. Most profiles are defined by placing restrictions on the structure of OWL 2 ontologies. These restrictions have been specified by modifying the productions of the functional-style syntax. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language Profiles"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language Profiles"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document provides a non-normative quick reference guide to the OWL 2 language. It also provides links to other documents, including the OWL 2 Primer for language introduction and examples, the OWL 2 Structural Specification and Functional Syntax document for more details of the functional syntax, and the OWL 2 New Features and Rationale document for new feature descriptions. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language Quick Reference Guide"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language Quick Reference Guide"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document defines the RDF-compatible model-theoretic semantics of OWL 2. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language RDF-Based Semantics"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language RDF-Based Semantics"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. The meaningful constructs provided by OWL 2 are defined in terms of their structure. As well, a functional-style syntax is defined for these constructs, with examples and informal descriptions. One can reason with OWL 2 ontologies under either the RDF-Based Semantics [OWL 2 RDF-Based Semantics] or the Direct Semantics [OWL 2 Direct Semantics]. If certain restrictions on OWL 2 ontologies are satisfied and the ontology is in OWL 2 DL, reasoning under the Direct Semantics can be implemented using techniques well known in the literature. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document specifies an XML serialization for OWL 2 that mirrors its structural specification. An XML schema defines this syntax and is available as a separate document, as well as being included here. """@en; ; cat:DocLicense; data:W3C; "OWL 2 Web Ontology Language XML Serialization"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 Web Ontology Language XML Serialization"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-09-01"^^xsd:date; """The purpose of the Protocol for Web Description Resources (POWDER) is to provide a means for individuals or organizations to describe a group of resources through the publication of machine-readable metadata, as motivated by the POWDER Use Cases [USECASES]. This document details the creation and lifecycle of Description Resources (DRs), which encapsulate such metadata. These are typically represented in a highly constrained XML dialect that is relatively human-readable. The meaning of such DRs are underpinned by formal semantics, accessible by performing a GRDDL Transform."""@en; ; cat:DocLicense; data:W3C; "Protocol for Web Description Resources (POWDER): Description Resources"; ; xhv:last ; xhv:previous ; rdfs:label "Protocol for Web Description Resources (POWDER): Description Resources"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-09-01"^^xsd:date; """This document underpins the Protocol for Web Description Resources (POWDER). It describes how the relatively simple operational format of a POWDER document can be transformed through two stages: first into a more tightly constrained XML format (POWDER-BASE), and then into an RDF/OWL encoding (POWDER-S) that may be processed by Semantic Web tools. Such processing is only possible, however, if tools implement the semantic extension defined within this document. The formal semantics of POWDER are best understood after the reader is acquainted with the Description Resources [DR] and Grouping of Resources [GROUP] documents."""@en; ; cat:DocLicense; data:W3C; "Protocol for Web Description Resources (POWDER): Formal Semantics"; ; xhv:last ; xhv:previous ; rdfs:label "Protocol for Web Description Resources (POWDER): Formal Semantics"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-09-01"^^xsd:date; """The Protocol for Web Description Resources (POWDER) facilitates the publication of descriptions of multiple resources such as all those available from a Web site. This document describes how sets of IRIs can be defined such that descriptions or other data can be applied to the resources obtained by dereferencing IRIs that are elements of the set. IRI sets are defined as XML elements with relatively loose operational semantics. This is underpinned by the formal semantics of POWDER which include a semantic extension, defined separately. A GRDDL transform is associated with the POWDER namespace that maps the operational to the formal semantics."""@en; ; cat:DocLicense; data:W3C; "Protocol for Web Description Resources (POWDER): Grouping of Resources"; ; xhv:last ; xhv:previous ; rdfs:label "Protocol for Web Description Resources (POWDER): Grouping of Resources"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-27"^^xsd:date; """ This document presents the specification of a primitive datatype for the plain literals of RDF. """@en; ; cat:DocLicense; data:W3C; "rdf:PlainLiteral: A Datatype for RDF Plain Literals"; ; xhv:last ; xhv:previous ; rdfs:label "rdf:PlainLiteral: A Datatype for RDF Plain Literals"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-08-18"^^xsd:date; """ This document defines the Simple Knowledge Organization System (SKOS), a common data model for sharing and linking knowledge organization systems via the Web. Many knowledge organization systems, such as thesauri, taxonomies, classification schemes and subject heading systems, share a similar structure, and are used in similar applications. SKOS captures much of this similarity and makes it explicit, to enable data and technology sharing across diverse applications. The SKOS data model provides a standard, low-cost migration path for porting existing knowledge organization systems to the Semantic Web. SKOS also provides a lightweight, intuitive language for developing and sharing new knowledge organization systems. It may be used on its own, or in combination with formal knowledge representation languages such as the Web Ontology language (OWL). This document is the normative specification of the Simple Knowledge Organization System. It is intended for readers who are involved in the design and implementation of information systems, and who already have a good understanding of Semantic Web technology, especially RDF and OWL. For an informative guide to using SKOS, see the [SKOS-PRIMER]. """@en; ; cat:DocLicense; data:W3C; "SKOS Simple Knowledge Organization System Reference"; ; xhv:last ; xhv:previous ; rdfs:label "SKOS Simple Knowledge Organization System Reference"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-05-12"^^xsd:date; """ This specification defines the Service Modeling Language, Version 1.1 (SML) used to model complex services and systems, including their structure, constraints, policies, and best practices. SML uses XML Schema and Schematron. """@en; ; cat:DocLicense; data:W3C; "Service Modeling Language, Version 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "Service Modeling Language, Version 1.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-05-12"^^xsd:date; """ This specification defines the interchange format for Service Modeling Language, Version 1.1 (SML) models. This format identifies the model being interchanged, distinguishes between model definition documents and model instance documents, and defines the binding of rule documents with other documents in the interchange model. """@en; ; cat:DocLicense; data:W3C; "Service Modeling Language Interchange Format Version 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "Service Modeling Language Interchange Format Version 1.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-20"^^xsd:date; """ XForms is an XML application that represents the next generation of forms for the Web. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML, ODF or SVG. An XForms-based web form gathers and processes XML data using an architecture that separates presentation, purpose and content. The underlying data of a form is organized into instances of data schema (though formal schema definitions are not required). An XForm allows processing of data to occur using three mechanisms: a declarative model composed of formulae for data calculations and constraints, data type and other property declarations, and data submission parameters a view layer composed of intent-based user interface controls an imperative controller for orchestrating data manipulations, interactions between the model and view layers, and data submissions. Thus, XForms accommodates form component reuse, fosters strong data type validation, eliminates unnecessary round-trips to the server, offers device independence and reduces the need for scripting. XForms 1.1 refines the XML processing platform introduced by [XForms 1.0] by adding several new submission capabilities, action handlers, utility functions, user interface improvements, and helpful datatypes as well as a more powerful action processing facility, including conditional, iterated and background execution, the ability to manipulate data arbitrarily and to access event context information. """@en; ; cat:DocLicense; data:W3C; "XForms 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "XForms 1.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-12-08"^^xsd:date; """ XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references. """@en; ; cat:DocLicense; data:W3C; "Namespaces in XML 1.0 (Third Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Namespaces in XML 1.0 (Third Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-01-28"^^xsd:date; """ This document describes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents. """@en; ; cat:DocLicense; data:W3C; "XML Base (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Base (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-29"^^xsd:date; """ This document describes the requirements for the scope, design, and features of the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, and that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes. The terms of EARL are defined by Evaluation and Report Language (EARL) 1.0 Schema, HTTP Vocabulary in RDF 1.0, Representing Content in RDF 1.0, and Pointer methods in RDF 1.0. A companion document, Evaluation and Report Language (EARL) 1.0 Guide, describes the motivations for EARL and provides an introduction to its uses. An Evaluation and Report Language (EARL) Overview is also available. """@en; ; cat:DocLicense; data:W3C; "Requirements for the Evaluation and Report Language (EARL) 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Requirements for the Evaluation and Report Language (EARL) 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-03-20"^^xsd:date; """This working draft defines features of the Scalable Vector Graphics (SVG) Language that are specifically for display environments.This document defines the markup used by SVG Transforms. SVG Transforms allows two-dimensional objects to be transformed using three-dimensional transformations.Although originally designed for use in SVG, some aspects of this specification are defined in XML and are accessed via presentation properties, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO.This document defines the markup used by SVG Transforms."""@en; ; cat:DocLicense; data:W3C; "SVG Transforms 1.0, Part 2: Language"; ; xhv:last ; rdfs:label "SVG Transforms 1.0, Part 2: Language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-01"^^xsd:date; """This Working Draft defines features of the Scalable Vector Graphics (SVG) Language that are specifically for color-managed environments."""@en; ; cat:DocLicense; data:W3C; "SVG Color 1.2, Part 2: Language"; ; xhv:last ; rdfs:label "SVG Color 1.2, Part 2: Language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-10-01"^^xsd:date; """This Working Draft is a primer for use of the Scalable Vector Graphics (SVG) Language for color managed workflows. It explains the technical background and gives guidelines on how to use the SVG Color specification with SVG 1.2 Tiny and SVG 1.2 Full modules. It is purely informative and has no conformance statements."""@en; ; cat:DocLicense; data:W3C; "SVG Color 1.2, Part 1: Primer"; ; xhv:last ; rdfs:label "SVG Color 1.2, Part 1: Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-06-16"^^xsd:date; """The SVG Parameters specification is an SVG 2.0 Module to provide a declarative way to incorporate parameter values into SVG content. Often, users may wish to create a single resource, and reuse it several times with specified variations, and this specification provides a means to do so without the use of script.Although originally designed for use in SVG, some aspects of this specification are defined in XML and are accessed via presentation properties, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO.This document defines the markup and interfaces used by SVG Parameters."""@en; ; cat:DocLicense; data:W3C; "SVG Parameters 1.0, Part 2: Language"; ; xhv:last ; xhv:previous ; rdfs:label "SVG Parameters 1.0, Part 2: Language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-06-16"^^xsd:date; """The SVG Parameters specification is an SVG 2.0 Module to provide a declarative way to incorporate parameter values into SVG content. Often, users may wish to create a single resource, and reuse it several times with specified variations, and this specification provides a means to do so without the use of script.Although originally designed for use in SVG, some aspects of this specification are defined in XML and are accessed via presentation properties, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO.This document introduces the features used by SVG Parameters, for the use of the average developer or author."""@en; ; cat:DocLicense; data:W3C; "SVG Parameters 1.0, Part 1: Primer"; ; xhv:last ; xhv:previous ; rdfs:label "SVG Parameters 1.0, Part 1: Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-03-20"^^xsd:date; """CSS 3D Transforms extends CSS Transforms to allow elements rendered by CSS to be transformed in three-dimensional space."""@en; ; cat:DocLicense; data:W3C; "CSS 3D Transforms Module Level 3"; ; xhv:last ; rdfs:label "CSS 3D Transforms Module Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-04-07"^^xsd:date; """ This Working Group Note is an evaluation of the Efficient XML Interchange (EXI) Format 1.0 with reference to the Properties identified by the XML Binary Characterization (XBC) Working Group, relative to XML, gzipped XML and ASN.1 PER. It is conducted using the XBC Measurement methodology. For the "compactness" and "processing efficiency" Properties, the performance is measured with EXI Measurement framework, over the test data collected for the EXI measurements, representing XBC Use Cases. """@en; ; cat:DocLicense; data:W3C; "Efficient XML Interchange Evaluation"; ; xhv:last ; xhv:previous ; rdfs:label "Efficient XML Interchange Evaluation"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-12-08"^^xsd:date; """ This is a non-normative document intended to provide an easily readable technical background on the Efficient XML Interchange (EXI) format. It is oriented towards quickly understanding how the EXI format can be used in practice and how options can be set to achieve specific needs. Section 2. Concepts describes the structure and content of an EXI document and introduces the notions of EXI header, EXI body, and EXI grammar which are fundamental to the understanding of the EXI format. Furthermore, additional details about data type representation, compression, and their interaction with other format features are presented. Finally, Section 3. Efficient XML Interchange by Example provides a detailed, bit-level description of both, a schema-less and a schema-informed example. """@en; ; cat:DocLicense; data:W3C; "Efficient XML Interchange (EXI) Primer"; ; xhv:last ; xhv:previous ; rdfs:label "Efficient XML Interchange (EXI) Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-09-08"^^xsd:date; """ Every day, governments and government agencies publish more data on the Internet. Sharing this data enables greater transparency; delivers more efficient public services; and encourages greater public and commercial use and re-use of government information. Some governments have even created catalogs or portals (such as data.gov) to make it easy for the public to find and use this data. Although the reasons may vary, the logistics and practicalities of opening government data are the same. To help governments open and share their data, the W3C eGov Interest Group has developed the following guidelines. These straightforward steps emphasize standards and methodologies to encourage publication of government data, allowing the public to use this data in new and innovative ways. """@en; ; cat:DocLicense; data:W3C; "Publishing Open Government Data"; ; xhv:last ; rdfs:label "Publishing Open Government Data"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-12-17"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Use cases and requirements for Media Fragments"; ; xhv:last ; xhv:previous ; rdfs:label "Use cases and requirements for Media Fragments"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-07-02"^^xsd:date; """SPARQL is a query language for RDF data on the Semantic Web with formally defined meaning. This document is a simple introduction to the new features of the language, including an explanation of its differences with respect to the previous SPARQL Query Language Recommendation [SPARQL/Query 1.0]. It also presents the requirements that have motivated the design of the main new features, and their rationale from a theoretical and implementation perspective."""@en; ; cat:DocLicense; data:W3C; "SPARQL New Features and Rationale"; ; xhv:last ; rdfs:label "SPARQL New Features and Rationale"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2009-02-26"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "Web Forms 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Web Forms 2.0"; :accessURL ; :status , ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-10-12"^^xsd:date; """Markup languages such as HTML [HTML401] and SVG [SVG11] provide a style attribute on most elements, to hold inline style information that applies to those elements. One of the possible style sheet languages is CSS. This draft describes the syntax and interpretation of the CSS fragment that can be used in such style attributes."""@en; ; cat:DocLicense; data:W3C; "CSS Style Attributes"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Style Attributes"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-01-19"^^xsd:date; """ XML Schema: Component Designators defines a scheme for identifying XML Schema components as specified by XML Schema Part 1: Structures and XML Schema Part 2: Datatypes. """@en; ; cat:DocLicense; data:W3C; "W3C XML Schema Definition Language (XSD): Component Designators"; ; xhv:last ; xhv:previous ; rdfs:label "W3C XML Schema Definition Language (XSD): Component Designators"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """This document describes CC/PP (Composite Capabilities/Preference Profiles) Structure and Vocabularies 2.0. A CC/PP profile is a description of device capabilities and user preferences. This is often referred to as a device's delivery context and can be used to guide the adaptation of content presented to that device.The Resource Description Framework (RDF) is used to create profiles that describe user agent capabilities and preferences. The structure of a profile is discussed. Topics include:structure of client capability and preference descriptions, ANDuse of RDF classes to distinguish different elements of a profile, so that a schema-aware RDF processor can handle CC/PP profiles embedded in other XML document types.Version 2.0 of CC/PP ensures its alignment with the latest version of RDF.CC/PP vocabulary uses identifiers (URIs) to refer to specific capabilities and preferences, and covers:the types of values to which CC/PP attributes may refer,an appendix describing how to introduce new vocabularies,an appendix giving an example small client vocabulary covering print and display capabilities, andan appendix providing a survey of existing work from which new vocabularies may be derived."""@en; ; cat:DocLicense; data:W3C; "Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-08-19"^^xsd:date; """ This document specifies the Compound Document by Reference Framework 1.0. When combining separate markup languages, specific problems have to be resolved that are not addressed by their individual language specifications, such as the propagation of events across namespaces, the combination of rendering or the user interaction model. Compound Document is the W3C term for a document that combines multiple formats. """@en; ; cat:DocLicense; data:W3C; "Compound Document by Reference Framework 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Compound Document by Reference Framework 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """ This document defines platform and language neutral programming interfaces that provide Web applications access to a hierarchy of dynamic properties representing device capabilities, configurations, user preferences and environmental conditions. """@en; ; cat:DocLicense; data:W3C; "Delivery Context: Client Interfaces (DCCI) 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Delivery Context: Client Interfaces (DCCI) 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-08-19"^^xsd:date; """ This document specifies WICD Core 1.0, a device independent Compound Document profile based on XHTML, CSS and SVG. Compound Document is the W3C term for a document that combines multiple formats. WICD stands for Web Integration Compound Document and is based on the idea of integrating existing markup language formats in preference to inventing new markup. """@en; ; cat:DocLicense; data:W3C; "WICD Core 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "WICD Core 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-08-19"^^xsd:date; """ Compound Document is the W3C term for a document that combines multiple formats. The CDF Working Group has defined CDRF 1.0 as a framework to describe such documents. This document specifies WICD Full 1.0, a Compound Document profile based on XHTML, CSS, SVG and DOM, which conforms to CDRF 1.0 and WICD Core 1.0. WICD Full 1.0 is targeted at desktop agents and is a superset of WICD Mobile 1.0. WICD stands for Web Integration Compound Document. """@en; ; cat:DocLicense; data:W3C; "WICD Full 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "WICD Full 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-08-19"^^xsd:date; """ Compound Document is the W3C term for a document that combines multiple formats. The CDF Working Group has defined CDRF 1.0 as a framework to describe such documents. This document specifies WICD Mobile 1.0, a Compound Document profile based on XHTML, CSS, SVG and DOM, which conforms to CDRF 1.0 and WICD Core 1.0. WICD Mobile 1.0 is targeted at mobile agents and is a subset of WICD Full 1.0. WICD stands for Web Integration Compound Document. """@en; ; cat:DocLicense; data:W3C; "WICD Mobile 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "WICD Mobile 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """ This document specifies a syntax and processing model for general purpose content selection or filtering. Selection involves conditional processing of various parts of an XML information set according to the results of the evaluation of expressions. Using this mechanism some parts of the information set can be selected for further processing and others can be suppressed. The specification of the parts of the infoset affected and the expressions that govern processing is by means of XML-friendly syntax. This includes elements, attributes and XPath expressions. This document specifies how these components work together to provide general purpose selection. There is a companion document which provides introductory information concerned with this specification DI Primer. """@en; ; cat:DocLicense; data:W3C; "Content Selection for Device Independence (DISelect) 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Content Selection for Device Independence (DISelect) 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """ Content Selection for Device Independence is a specification that allows authors to choose between different versions of content for use in different circumstances. This Primer is designed to provide the reader with the basic knowledge required to make effective use of this markup. It positions DISelect in relation to other methods of content selection. It also describes the features of DISelect and illustrates how they can be used in a variety of scenarios using a number of examples. """@en; ; cat:DocLicense; data:W3C; "Content Selection Primer 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Content Selection Primer 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """ 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. These functions have been designed to satisfy the requirements to adapt content based on the Delivery Context. While designed to work with Device Independent Content Selection it can be used in any XPath processor. There is a companion document which provides introductory information concerned with this specification, Content Selection for Device Independence Primer. """@en; ; cat:DocLicense; data:W3C; "Delivery Context: XPath Access Functions 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Delivery Context: XPath Access Functions 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-10-26"^^xsd:date; """ This document provides guidance to Content Transformation proxies as to whether and how to transform Web content. Content Transformation proxies alter requests sent by user agents to servers and responses returned by servers so that the appearance, structure or control flow of Web applications are modified. Content Transformation proxies are mostly used to convert Web sites designed for desktop computers to a form suitable for mobile devices. Based on current practice and standards, this document specifies mechanisms with which Content Transformation proxies should make their presence known to other parties, present the outcome of alterations performed on HTTP traffic, and react to indications set by clients or servers to constrain these alterations. The objective is to reduce undesirable effects on Web applications, especially mobile-ready ones, and to limit the diversity in the modes of operation of Content Transformation proxies, while at the same time allowing proxies to alter content that would otherwise not display successfully on mobile devices. Important considerations regarding the impact on security are highlighted. """@en; ; cat:DocLicense; data:W3C; "Guidelines for Web Content Transformation Proxies 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Guidelines for Web Content Transformation Proxies 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-16"^^xsd:date; """ This document defines a generic, abbreviated syntax for expressing URIs. This syntax is intended to be used as a common element by language designers. Target languages include, but are not limited to, XML languages. The intended audience for this document is Language designers, not the users of those Languages. """@en; ; cat:DocLicense; data:W3C; "CURIE Syntax 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "CURIE Syntax 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """ This document provides definitions, use cases, and requirements for making device APIs more privacy-friendly."""@en; ; cat:DocLicense; data:W3C; "Device API Privacy Requirements"; ; xhv:last ; rdfs:label "Device API Privacy Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """ The Delivery Context Ontology provides a formal model of the characteristics of the environment in which devices interact with the Web or other services. The Delivery Context includes the characteristics of the Device, the software used to access the service and the Network providing the connection among others. The Delivery Context is an important source of information that can be exploited to create context-aware applications, thus providing a compelling user experience. The ontology is formally specified in the Web Ontology Language. This document describes the ontology and gives details of each term that it contains. The normative definition of the ontology terms is generated automatically from the OWL file. """@en; ; cat:DocLicense; data:W3C; "Delivery Context Ontology"; ; xhv:last ; xhv:previous ; rdfs:label "Delivery Context Ontology"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """ The purpose of the Device Independent Authoring Language (DIAL) is to provide a markup language for the filtering and presentation of Web page content available across different delivery contexts. This will facilitate an optimal user experience following adaptation of the DIAL instance document. Please refer to the DIAL Primer for an introduction to the profile and its purpose. DIAL is a language profile based on existing W3C XML vocabularies and CSS modules. These provide standard mechanisms for representing Web page structure, presentation and form interaction. The DIAL also makes use of the DISelect metadata vocabulary for overcoming the authoring challenges inherent in authoring for multiple delivery contexts. DIAL is part of the Authoring for Device Independence work category of the DIWG. This encompasses a number of work items associated with authoring Web sites and applications that support access from a wide range of devices with a variety of delivery contexts. These include work on Authoring Challenges, Authoring Techniques, and Scenarios and Extension Markup. """@en; ; cat:DocLicense; data:W3C; "Device Independent Authoring Language (DIAL)"; ; xhv:last ; xhv:previous ; rdfs:label "Device Independent Authoring Language (DIAL)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-29"^^xsd:date; """ This document provides an introduction to, and the benefits of, DIAL (the Device Independent Authoring Language). It summarizes the concept of device independence, the scenarios in which it could be used, and the considerations in order to achieve that goal. It then describes the role of DIAL in ensuring the delivery of content suitable for the user, device and inherent circumstances in which it was requested. """@en; ; cat:DocLicense; data:W3C; "DIAL Part 0: Primer"; ; xhv:last ; xhv:previous ; rdfs:label "DIAL Part 0: Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-16"^^xsd:date; """The HLink module defined in this specification provides XHTML Family Members with the ability to specify which attributes of elements represent links, and how those links should be traversed, and extends XLink use to a wider class of languages than those restricted to the syntactic style allowed by XLink."""@en; ; cat:DocLicense; data:W3C; "HLink"; ; xhv:last ; xhv:previous ; rdfs:label "HLink"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document is an overview of the Rule Interchange Format (RIF). It provides a high-level explanation of RIF concepts and architecture as well as a general survey of RIF documents. """@en; ; cat:DocLicense; data:W3C; "RIF Overview"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Overview"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document shows how OWL 2 RL can be implemented using RIF. It provides an analysis of how to represent OWL 2 RL inference rules within RIF Core. The OWL 2 RL inference rules can be implemented both via a fixed RIF Core rule set (Appendix 7) and via a mapping algorithm which converts an OWL 2 RL ontology to a customized RIF Core rule set (Appendix 8). """@en; ; cat:DocLicense; data:W3C; "OWL 2 RL in RIF"; ; xhv:last ; xhv:previous ; rdfs:label "OWL 2 RL in RIF"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-01-28"^^xsd:date; """ In this document we present a method for writing, marking-up, and analyzing conformance requirements in technical specifications. """@en; ; cat:DocLicense; data:W3C; "A Method for Writing Testable Conformance Requirements"; ; xhv:last ; rdfs:label "A Method for Writing Testable Conformance Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-11-18"^^xsd:date; """This specification defines an API for storing data in databases that can be queried using a variant of SQL."""@en; ; cat:DocLicense; data:W3C; "Web SQL Database"; ; xhv:last ; xhv:previous ; rdfs:label "Web SQL Database"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-07-13"^^xsd:date; """ This specification defines extensions to WS-Transfer primarily to provide fragment-based access to resources. This document is in the state """@en; ; cat:DocLicense; data:W3C; "Web Services Resource Transfer (WS-RT)"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Resource Transfer (WS-RT)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-16"^^xsd:date; """XFrames is an XML application for composing documents together, replacing HTML Frames. By being a separate application from XHTML, it allows content negotiation to determine if the user agent accepts frames; by encoding the 'population' of frames in the URI, it allows framesets to be bookmarked."""@en; ; cat:DocLicense; data:W3C; "XFrames"; ; xhv:last ; xhv:previous ; rdfs:label "XFrames"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-16"^^xsd:date; """The XHTML Access module defines an element that, when used in conjunction with other XHTML modules in XHTML Family Markup Languages, enables a more robust accessibility model than is presently possible."""@en; ; cat:DocLicense; data:W3C; "XHTML Access Module"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML Access Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-16"^^xsd:date; """The XHTML Role Attribute defined in this specification allows the author to annotate XML Languages with machine-extractable semantic information about the purpose of an element. Use cases include accessibility, device adaptation, server-side processing, and complex data description. This attribute can be integrated into any markup language based upon XHTML Modularization [XHTMLMOD]."""@en; ; cat:DocLicense; data:W3C; "XHTML Role Attribute Module"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML Role Attribute Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-16"^^xsd:date; """XHTML 2 is a general-purpose markup language designed to represent documents for a wide range of purposes across the World Wide Web. To this end it does not attempt to be all things to all people, supplying every possible markup idiom, but to supply a generally useful set of elements."""@en; ; cat:DocLicense; data:W3C; "XHTML™ 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML™ 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-16"^^xsd:date; """This specification defines three modules: XML Events to define events and their characteristics; XML Handlers to define mappings between events and actions; and XML Scripting to assist in defining functions to support the handlers. These modules work together to provide XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 3 event interfaces [DOM3EVENTS]. The result is to provide an interoperable way of associating behaviors with document-level markup."""@en; ; cat:DocLicense; data:W3C; "XML Events 2"; ; xhv:last ; xhv:previous ; rdfs:label "XML Events 2"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-02-04"^^xsd:date; """ This document outlines a proposed simplification of the XML Signature Transform mechanism, intended to enhance security, performance, streamability and to ease adoption. """@en; ; cat:DocLicense; data:W3C; "XML Signature Transform Simplification: Requirements and Design"; ; xhv:last ; xhv:previous ; rdfs:label "XML Signature Transform Simplification: Requirements and Design"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-10-21"^^xsd:date; """ This specification defines the Mathematical Markup Language, or MathML. 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. This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document. MathML can be used to encode both mathematical notation and mathematical content. About thirty-eight of the MathML tags describe abstract notational structures, while another about one hundred and seventy provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of special characters used for mathematics, their handling in MathML, their presence in Unicode, and their relation to fonts. While MathML is human-readable, authors typically will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several versions of such MathML tools exist, both freely available software and commercial products, and more are under development. """@en; ; cat:DocLicense; data:W3C; "Mathematical Markup Language (MathML) Version 3.0"; ; xhv:last ; xhv:previous ; rdfs:label "Mathematical Markup Language (MathML) Version 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-14"^^xsd:date; """ The goal of this document is to aid the development of rich and dynamic mobile Web applications. It collects the most relevant engineering practices, promoting those that enable a better user experience and warning against those that are considered harmful. """@en; ; cat:DocLicense; data:W3C; "Mobile Web Application Best Practices"; ; xhv:last ; xhv:previous ; rdfs:label "Mobile Web Application Best Practices"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document, developed by the Rule Interchange Format (RIF) Working Group, specifies the Basic Logic Dialect, RIF-BLD, a format that allows logic rules to be exchanged between rule systems. The RIF-BLD presentation syntax and semantics are specified both directly and as specializations of the RIF Framework for Logic Dialects, or RIF-FLD. The XML serialization syntax of RIF-BLD is specified via a mapping from the presentation syntax. A normative XML schema is also provided. """@en; ; cat:DocLicense; data:W3C; "RIF Basic Logic Dialect"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Basic Logic Dialect"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document, developed by the Rule Interchange Format (RIF) Working Group, specifies RIF-Core, a common subset of RIF-BLD and RIF-PRD based on RIF-DTB 1.0. The RIF-Core presentation syntax and semantics are specified by restriction in two different ways. First, RIF-Core is specified by restricting the syntax and semantics of RIF-BLD, and second, by restricting RIF-PRD. The XML serialization syntax of RIF-Core is specified by a mapping from the presentation syntax. A normative XML schema is also provided. """@en; ; cat:DocLicense; data:W3C; "RIF Core Dialect"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Core Dialect"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document, developed by the Rule Interchange Format (RIF) Working Group, specifies a list of datatypes, built-in functions and built-in predicates expected to be supported by RIF dialects such as the RIF Core Dialect, the RIF Basic Logic Dialect, and the RIF Production Rules Dialect. Each dialect supporting a superset or subset of the datatypes, built-in functions and built-in predicates defined here shall specify these additions or restrictions. Some of the datatypes are adapted from [XML Schema Datatypes]. A large part of the definitions of the listed functions and operators are adapted from [XPath-Functions]. The rdf:PlainLiteral datatype as well as functions and operators associated with that datatype are adopted from [RDF-PLAINLITERAL]. """@en; ; cat:DocLicense; data:W3C; "RIF Datatypes and Built-Ins 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Datatypes and Built-Ins 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document, developed by the Rule Interchange Format (RIF) Working Group, defines a general RIF Framework for Logic Dialects (RIF-FLD). The framework describes mechanisms for specifying the syntax and semantics of logic RIF dialects through a number of generic concepts such as signatures, symbol spaces, semantic structures, and so on. The actual dialects should specialize this framework to produce their syntaxes and semantics. """@en; ; cat:DocLicense; data:W3C; "RIF Framework for Logic Dialects"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Framework for Logic Dialects"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document, developed by the Rule Interchange Format (RIF) Working Group, specifies the production rule dialect of the W3C rule interchange format (RIF-PRD), a standard XML serialization format for production rule languages. """@en; ; cat:DocLicense; data:W3C; "RIF Production Rule Dialect"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Production Rule Dialect"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ Rules interchanged using the Rule Interchange Format RIF may depend on or be used in combination with RDF data and RDF Schema or OWL ontologies. This document, developed by the Rule Interchange Format (RIF) Working Group, specifies the interoperation between RIF and the data and ontology languages RDF, RDF Schema, and OWL. """@en; ; cat:DocLicense; data:W3C; "RIF RDF and OWL Compatibility"; ; xhv:last ; xhv:previous ; rdfs:label "RIF RDF and OWL Compatibility"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-09-07"^^xsd:date; """ The Voice Browser Working Group has sought to develop standards to enable access to the Web using spoken interaction. The Speech Synthesis Markup Language Specification is one of these standards and is designed to provide a rich, XML-based markup language for assisting the generation of synthetic speech in Web and other applications. The essential role of the markup language is to provide authors of synthesizable content a standard way to control aspects of speech such as pronunciation, volume, pitch, rate, etc. across different synthesis-capable platforms. """@en; ; cat:DocLicense; data:W3C; "Speech Synthesis Markup Language (SSML) Version 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "Speech Synthesis Markup Language (SSML) Version 1.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-11-18"^^xsd:date; """ This document specifies the Timed Text Markup Language (TTML) in terms of a vocabulary and semantics thereof. The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information. It is intended to be used for the purpose of transcoding or exchanging timed text information among legacy distribution content formats presently in use for subtitling and captioning functions. In addition to being used for interchange among legacy distribution content formats, TTML content may be used directly as a distribution format, for example, providing a standard content format to reference from a or media object element in a [SMIL 2.1] document. """@en; ; cat:DocLicense; data:W3C; "Timed Text Markup Language (TTML) 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Timed Text Markup Language (TTML) 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-03-01"^^xsd:date; """ Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM, which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields. First published (1.0) in 1999, WebCGM unifies potentially diverse approaches to CGM utilization in Web document applications. It therefore represents a significant interoperability agreement amongst major users and implementers of the ISO CGM standard. The design criteria for WebCGM aim to balance graphical expressive power on the one hand, versus simplicity and implementability on the other. A small but powerful set of standardized metadata elements supports the functionalities of hyperlinking and document navigation, picture structuring and layering, and enabling search and query of WebCGM picture content. The present version, WebCGM 2.1, refines and completes the features of the major WebCGM 2.0 release. WebCGM 2.0 added a DOM (API) specification for programmatic access to WebCGM objects, a specification of an XML Companion File (XCF) architecture, and extended the graphical and intelligent content of WebCGM 1.0. """@en; ; cat:DocLicense; data:W3C; "WebCGM 2.1"; ; xhv:last ; xhv:previous ; rdfs:label "WebCGM 2.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-08-12"^^xsd:date; """ This specification defines guidelines and requirements for the presentation and communication of Web security context information to end-users."""@en; ; cat:DocLicense; data:W3C; "Web Security Context: User Interface Guidelines"; ; xhv:last ; xhv:previous ; rdfs:label "Web Security Context: User Interface Guidelines"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-11-23"^^xsd:date; ""@en; ; cat:DocLicense; data:W3C; "XHTML™ Basic 1.1 - Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML™ Basic 1.1 - Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-07-29"^^xsd:date; """ This document is the second edition of version 1.1 of XHTML Modularization, an abstract modularization of XHTML and implementations of the abstraction using XML Document Type Definitions (DTDs) and XML Schemas. This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms. This specification is intended for use by language designers as they construct new XHTML Family Markup Languages. This specification does not define the semantics of elements and attributes, only how those elements and attributes are assembled into modules, and from those modules into markup languages. This update includes several minor updates to provide clarifications and address errors found in version 1.1. """@en; ; cat:DocLicense; data:W3C; "XHTML™ Modularization 1.1 - Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML™ Modularization 1.1 - Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-11-23"^^xsd:date; """ XHTML-Print is a member of the family of XHTML languages defined by the Modularization of XHTML [XHTMLMOD]. It is designed to be appropriate for printing from mobile devices to low-cost printers that might not have a full-page buffer and that generally print from top-to-bottom and left-to-right with the paper in a portrait orientation. XHTML-Print is also targeted at printing in environments where it is not feasible or desirable to install a printer-specific driver and where some variability in the formatting of the output is acceptable. """@en; ; cat:DocLicense; data:W3C; "XHTML-Print - Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML-Print - Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-11-23"^^xsd:date; """ This specification defines an XHTML document type that is based upon the module framework and modules defined in XHTML Modularization [XHTMLMOD]. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 [HTML4] that was brought forward into the XHTML 1.0 [XHTML1] document types. This document type is most similar to XHTML 1.0 Strict, built using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in XHTML Modularization, and document authors are free to define document types based upon XHTML 1.1 that use these facilities (see [XHTMLMOD] for information on creating new document types). """@en; ; cat:DocLicense; data:W3C; "XHTML™ 1.1 - Module-based XHTML - Second Edition"; ; xhv:last ; xhv:previous ; rdfs:label "XHTML™ 1.1 - Module-based XHTML - Second Edition"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-05-06"^^xsd:date; """ This specification defines the XML Linking Language (XLink) Version 1.1, which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links. """@en; ; cat:DocLicense; data:W3C; "XML Linking Language (XLink) Version 1.1"; ; xhv:last ; xhv:previous ; rdfs:label "XML Linking Language (XLink) Version 1.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-04-01"^^xsd:date; """ This document defines several sets of names, so that to each name is assigned a Unicode character or sequence of characters. Each of these sets is expressed as a file of XML entity declarations. """@en; ; cat:DocLicense; data:W3C; "XML Entity Definitions for Characters"; ; xhv:last ; xhv:previous ; rdfs:label "XML Entity Definitions for Characters"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-10-28"^^xsd:date; """ This document allows style sheets to be associated with an XML document by including one or more processing instructions with a target of xml-stylesheet in the document's prolog. """@en; ; cat:DocLicense; data:W3C; "Associating Style Sheets with XML documents 1.0 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Associating Style Sheets with XML documents 1.0 (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-14"^^xsd:date; """ This document defines the W3C XQuery 1.0 and XPath 2.0 Data Model (XDM), which is the data model of [XML Path Language (XPath) 2.0 (Second Edition)], [XSLT 2.0 (Second Edition)], and [XQuery], and any other specifications that reference it. This data model is based on the [XPath 1.0] data model and earlier work on an [XML Query Data Model]. This document is the result of joint work by the [XSL Working Group] and the [XML Query Working Group]. """@en; ; cat:DocLicense; data:W3C; "XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-14"^^xsd:date; """ This document defines constructor functions, operators and functions on the datatypes defined in [XML Schema Part 2: Datatypes Second Edition] and the datatypes defined in [XQuery 1.0 and XPath 2.0 Data Model]. It also discusses functions and operators on nodes and node sequences as defined in the [XQuery 1.0 and XPath 2.0 Data Model]. These functions and operators are defined for use in [XML Path Language (XPath) 2.0], [XQuery 1.0: An XML Query Language] and [XSL Transformations (XSLT) Version 2.0] and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2005/xpath-functions/. """@en; ; cat:DocLicense; data:W3C; "XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-14"^^xsd:date; """ XPath 2.0 is an expression language that allows the processing of values conforming to the data model defined in [XQuery 1.0 and XPath 2.0 Data Model (Second Edition)]. The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values. The result of an XPath expression may be a selection of nodes from the input documents, or an atomic value, or more generally, any sequence allowed by the data model. The name of the language derives from its most distinctive feature, the path expression, which provides a means of hierarchic addressing of the nodes in an XML tree. XPath 2.0 is a superset of [XPath 1.0], with the added capability to support a richer set of data types, and to take advantage of the type information that becomes available when documents are validated using XML Schema. A backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 2.0; exceptions to this policy are noted in [I Backwards Compatibility with XPath 1.0]. """@en; ; cat:DocLicense; data:W3C; "XML Path Language (XPath) 2.0 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Path Language (XPath) 2.0 (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-05-11"^^xsd:date; """ This specification describes the syntax and semantics of XProc: An XML Pipeline Language, a language for describing operations to be performed on XML documents. An XML Pipeline specifies a sequence of operations to be performed on zero or more XML documents. Pipelines generally accept zero or more XML documents as input and produce zero or more XML documents as output. Pipelines are made up of simple steps which perform atomic operations on XML documents and constructs similar to conditionals, iteration, and exception handlers which control which steps are executed. """@en; ; cat:DocLicense; data:W3C; "XProc: An XML Pipeline Language"; ; xhv:last ; xhv:previous ; rdfs:label "XProc: An XML Pipeline Language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-14"^^xsd:date; """ XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources. """@en; ; cat:DocLicense; data:W3C; "XQuery 1.0: An XML Query Language (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 1.0: An XML Query Language (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-14"^^xsd:date; """ This document defines formally the semantics of XQuery 1.0 [XQuery 1.0: An XML Query Language (Second Edition)] and XPath 2.0 [XML Path Language (XPath) 2.0 (Second Edition)]. """@en; ; cat:DocLicense; data:W3C; "XQuery 1.0 and XPath 2.0 Formal Semantics (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 1.0 and XPath 2.0 Formal Semantics (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-14"^^xsd:date; """ This document defines an XML Syntax for [XQuery 1.0: An XML Query Language (Second Edition)]. """@en; ; cat:DocLicense; data:W3C; "XML Syntax for XQuery 1.0 (XQueryX) (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XML Syntax for XQuery 1.0 (XQueryX) (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-14"^^xsd:date; """ This document defines serialization of an instance of the data model as defined in [XQuery 1.0 and XPath 2.0 Data Model] into a sequence of octets. Serialization is designed to be a component that can be used by other specifications such as [XSL Transformations (XSLT) Version 2.0] or [XQuery 1.0: An XML Query Language]. """@en; ; cat:DocLicense; data:W3C; "XSLT 2.0 and XQuery 1.0 Serialization (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "XSLT 2.0 and XQuery 1.0 Serialization (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-01-26"^^xsd:date; """The Uniform Messaging Policy (UMP) enables cross-site messaging that avoids Cross-Site-Request-Forgery and similar attacks that abuse HTTP cookies and other credentials. For example, content from customer.example.org can safely specify requests to resources determined by service.example.com. Rather than restricting information retrieval to a single origin, as the Same Origin Policy almost does, the Uniform Messaging Policy supports origin independent messaging."""@en; ; cat:DocLicense; data:W3C; "Uniform Messaging Policy, Level One"; ; xhv:last ; rdfs:label "Uniform Messaging Policy, Level One"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-10-05"^^xsd:date; """ This document identifies the permissions that are needed to use specific client-side APIs which grant access to sensitive data and operations."""@en; ; cat:DocLicense; data:W3C; "Permissions for Device API Access"; ; xhv:last ; rdfs:label "Permissions for Device API Access"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-03-04"^^xsd:date; """ Authoring a web app that needs to support both right-to-left and left-to-right interfaces, or to take as input and display both left-to-right and right-to-left data, usually presents a number of challenges that make it an especially laborious and bug-prone task. Some of these are due to browser bugs, but some can be traced to a gap in the specification of the bidirectional aspects of a given HTML feature. And some of these challenges could be greatly simplified by adding a few strategically placed new HTML features. This document proposes fixes for some of the most repetitive pain points. """@en; ; cat:DocLicense; data:W3C; "Additional Requirements for Bidi in HTML"; ; xhv:last ; rdfs:label "Additional Requirements for Bidi in HTML"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-01-21"^^xsd:date; """ This document specifies use cases and requirements as an input for the development of the "Ontology for Media Resource 1.0" and the "API for Media Resource 1.0". The ontology will be a simple ontology to support cross-community data integration of information related to media resources on the Web. The API will provide read access and potentially write access to media resources, relying on the definitions from the ontology. The main scope of this document are videos. Metadata for other media resources like audio or images will be taken into account if it is applicable for videos as well. """@en; ; cat:DocLicense; data:W3C; "Use Cases and Requirements for Ontology and API for Media Resource 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Use Cases and Requirements for Ontology and API for Media Resource 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-08"^^xsd:date; """ The need to share data with collaborators motivates custodians and users of relational databases (RDB) to expose relational data on the Web of Data. This document examines a set of use cases from science and industry, taking relational data and exposing it in patterns conforming to shared RDF schemata. These use cases expose a set of functional requirements for exposing relational data as RDF in the RDB2RDF Mapping Language (R2RML). """@en; ; cat:DocLicense; data:W3C; "Use Cases and Requirements for Mapping Relational Databases to RDF"; ; xhv:last ; rdfs:label "Use Cases and Requirements for Mapping Relational Databases to RDF"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document describes the test cases developed by the Rule Interchange Format (RIF) Working Group in accordance with the Working Group's Charter. These test cases are intended to aid in the conformance evaluation of RIF implementations and thus promote interoperability. """@en; ; cat:DocLicense; data:W3C; "RIF Test Cases"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Test Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-22"^^xsd:date; """ This document, developed by the Rule Interchange Format (RIF) Working Group, specifies how a RIF document can be combined with XML data. """@en; ; cat:DocLicense; data:W3C; "RIF Combination with XML data"; ; xhv:last ; xhv:previous ; rdfs:label "RIF Combination with XML data"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-01-26"^^xsd:date; """ This document describes SPARQL Property Paths. Property Paths give a more succinct way to write parts of basic graph patterns and also extend matching of triple pattern to arbitrary length paths. Property paths do not invalidate or change any existing SPARQL query. Property paths are a time-permitting feature. """@en; ; cat:DocLicense; data:W3C; "SPARQL 1.1 Property Paths"; ; xhv:last ; rdfs:label "SPARQL 1.1 Property Paths"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-02-02"^^xsd:date; """ This specification defines an API to provide Web applications with access to various properties of the system which they are running on. Specifically, properties pertaining to the device hardware are addressed. Examples include battery status, current network bandwidth. Additionally, some of those properties offer access to the environment around the device, such as ambient brightness or atmospheric pressure. """@en; ; cat:DocLicense; data:W3C; "The System Information API"; ; xhv:last ; rdfs:label "The System Information API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-12-16"^^xsd:date; """ This document specifies VoiceXML 3.0, a modular XML language for creating interactive media dialogs that feature synthesized speech, recognition of spoken and DTMF key input, telephony, mixed initiative conversations, and recording and presentation of a variety of media formats including digitized audio, and digitized video. Its major goal is to bring the advantages of Web-based development and content delivery to interactive voice response applications. """@en; ; cat:DocLicense; data:W3C; "Voice Extensible Markup Language (VoiceXML) 3.0"; ; xhv:last ; xhv:previous ; rdfs:label "Voice Extensible Markup Language (VoiceXML) 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-09-16"^^xsd:date; """ This WAI-ARIA Authoring Practices Guide provides readers with an understanding of how to use WAI-ARIA [ARIA] to create accessible rich internet applications. It describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. This document is directed primarily to Web application developers, but the guidance is also useful for user agent and assistive technology developers. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview. """@en; ; cat:DocLicense; data:W3C; "WAI-ARIA 1.0 Authoring Practices"; ; xhv:last ; xhv:previous ; rdfs:label "WAI-ARIA 1.0 Authoring Practices"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-09-16"^^xsd:date; """ The WAI-WAI-ARIA Primer introduces developers to the use of WAI-ARIA [ARIA] for addressing the accessibility of dynamic Web content for people with disabilities. This primer explains the accessibility problems posed by hybrid technologies such as Dynamic Hypertext Markup Language (DHTML) and Asynchronous Java and XML (Ajax). It introduces the technologies to map controls, Ajax live regions, and events to accessibility application programming interfaces (APIs), including custom controls used for Rich Internet Applications. The primer also describes new navigation techniques to mark common Web elements with roles such as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview. """@en; ; cat:DocLicense; data:W3C; "WAI-ARIA 1.0 Primer"; ; xhv:last ; xhv:previous ; rdfs:label "WAI-ARIA 1.0 Primer"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-09-16"^^xsd:date; """ This document specifies goals and requirements for XML Query (XQuery) 3.0. """@en; ; cat:DocLicense; data:W3C; "XQuery 3.0 Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 3.0 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-04-08"^^xsd:date; """ This specification defines an extension to [XQuery 1.0] and [XQuery Update Facility]. Expressions can be evaluated in a specific order, with later expressions seeing the effects of the expressions that came before them. This specification introduces several new kinds of expression, including the apply, assignment, while, and exit expression, and a block expression with local variable declarations. """@en; ; cat:DocLicense; data:W3C; "XQuery Scripting Extension 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery Scripting Extension 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2010-06-10"^^xsd:date; """ This document is a characterization of requirements and use cases for [XSL Transformations (XSLT) Version 2.1]. The Requirements lists enhancements requested over time that may be addressed in XSLT 2.1. """@en; ; cat:DocLicense; data:W3C; "Requirements and Use Cases for XSLT 2.1"; ; xhv:last ; rdfs:label "Requirements and Use Cases for XSLT 2.1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-04-12"^^xsd:date; """This specification describes multi-column layouts in CSS, a style sheet language for the web. Using functionality described in the specification, content can be flowed into multiple columns with a gap and a rule between them."""@en; ; cat:DocLicense; data:W3C; "CSS Multi-column Layout Module"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Multi-column Layout Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-11-22"^^xsd:date; ; cat:DocLicense; data:W3C; "API for Media Resources 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "API for Media Resources 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-09-22"^^xsd:date; """The Progress Events specification defines an event interface that can be used for measuring progress; e.g. HTTP entity body transfers. This specification is primarily meant to be used by other specifications."""@en; ; cat:DocLicense; data:W3C; "Progress Events"; ; xhv:last ; xhv:previous ; rdfs:label "Progress Events"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-15"^^xsd:date; """ The Touch Events specification defines a set of low-level events that represent one or more points of contact with a touch-sensitive surface, and changes of those points with respect to the surface and any DOM elements displayed upon it (e.g. for touch screens) or associated with it (e.g. for drawing tablets without displays). """@en; ; cat:DocLicense; data:W3C; "Touch Events version 1"; ; xhv:last ; xhv:previous ; rdfs:label "Touch Events version 1"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-01-18"^^xsd:date; """ Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview. """@en; ; cat:DocLicense; data:W3C; "Accessible Rich Internet Applications (WAI-ARIA) 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Accessible Rich Internet Applications (WAI-ARIA) 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-08"^^xsd:date; """This specification defines an API for persistent data storage of key-value pair data in Web clients."""@en; ; cat:DocLicense; data:W3C; "Web Storage"; ; xhv:last ; xhv:previous ; rdfs:label "Web Storage"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-03"^^xsd:date; """ This document outlines proposed standard XML Signature Properties syntax and processing rules and an associated namespace for these properties. The intent is these can be composed with any version of XML Signature using the XML SignatureProperties element. These properties are intended to meet code signing requirements. """@en; ; cat:DocLicense; data:W3C; "XML Signature Properties"; ; xhv:last ; xhv:previous ; rdfs:label "XML Signature Properties"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-03"^^xsd:date; """ Generic hybrid ciphers allow for a consistent treatment of asymmetric ciphers when encrypting data and consist of a key encapsulation algorithm with associated parameters and a data encapsulation algorithm with associated parameters. Further, the key encapsulation algorithms introduced in this specification have attractive security properties. This document augments XML Encryption Version 1.1 [XMLENC-CORE1] by defining algorithms, XML types and elements necessary to enable use of generic hybrid ciphers in XML Security applications. """@en; ; cat:DocLicense; data:W3C; "XML Security Generic Hybrid Ciphers"; ; xhv:last ; xhv:previous ; rdfs:label "XML Security Generic Hybrid Ciphers"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-29"^^xsd:date; """ This document defines APIs for off-line serving of requests to HTTP resources using static and dynamic responses. It extends the function of application caches defined in HTML5. """@en; ; cat:DocLicense; data:W3C; "Programmable HTTP Caching and Serving"; ; xhv:last ; xhv:previous ; rdfs:label "Programmable HTTP Caching and Serving"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-12"^^xsd:date; """This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2010. The primary audience is CSS implementors, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate."""@en; ; cat:DocLicense; data:W3C; "Cascading Style Sheets (CSS) Snapshot 2010"; ; xhv:last ; xhv:previous ; rdfs:label "Cascading Style Sheets (CSS) Snapshot 2010"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-12"^^xsd:date; """This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2007. The primary audience is CSS implementors, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate."""@en; ; cat:DocLicense; data:W3C; "Cascading Style Sheets (CSS) Snapshot 2007"; ; xhv:last ; xhv:previous ; rdfs:label "Cascading Style Sheets (CSS) Snapshot 2007"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-17"^^xsd:date; """ With the emergence of numerous new APIs in Web browsers and runtime engines, the need to control which Web sites and applications can make use of these APIs increases. This document describes use cases and requirements for controlling access to these APIs."""@en; ; cat:DocLicense; data:W3C; "Device API Access Control Use Cases and Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "Device API Access Control Use Cases and Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-10-20"^^xsd:date; ; cat:DocLicense; data:W3C; "Ontology of Rhetorical Blocks (ORB)"; ; xhv:last ; rdfs:label "Ontology of Rhetorical Blocks (ORB)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-01"^^xsd:date; """ This document lists the design goals and requirements that potential W3C recommendations should support in order to enable access to services and content provided by home network devices on other devices, including the discovery and playback of content available to those devices, both from services such as traditional broadcast media and internet based services but also from the home network. """@en; ; cat:DocLicense; data:W3C; "Requirements for Home Networking Scenarios"; ; xhv:last ; rdfs:label "Requirements for Home Networking Scenarios"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-01"^^xsd:date; """ This document describes Modality Components in the MMI Architecture which are responsible for controlling the various input and output modalities on various devices by providing guidelines and suggestions for designing Modality Components. Also this document shows several possible examples of Modality Components, (1) face identification, (2) form-filling using handwriting recognition and (3) video display. """@en; ; cat:DocLicense; data:W3C; "Best practices for creating MMI Modality Components"; ; xhv:last ; rdfs:label "Best practices for creating MMI Modality Components"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-12"^^xsd:date; """ This document specifies a reversible mapping (or transformation) from Rule Interchange Format (RIF) XML documents to Resource Description Framework (RDF) graphs. This mapping allows the contents of RIF documents to be interoperably stored and processed as RDF triples, using existing serializations and tools for RDF. When used with the standard mapping from RDF triples to RIF frames, this also provides a "reflection" or "introspection" mechanism, an interoperable way for RIF rules to operate on RIF documents. """@en; ; cat:DocLicense; data:W3C; "RIF In RDF"; ; xhv:last ; xhv:previous ; rdfs:label "RIF In RDF"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-07-05"^^xsd:date; """ This document contains guidelines and best practices for working with time and time zones in applications and document formats. Use cases are provided to help choose an approach that ensures that geographically distributed applications work well with date and time values. This document also aims to provide a basic understanding and vocabulary for talking about time and time handling in software, a source of confusion for many developers and content authors on the Web. """@en; ; cat:DocLicense; data:W3C; "Working with Time Zones"; ; xhv:last ; xhv:previous ; rdfs:label "Working with Time Zones"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-03"^^xsd:date; """VoID is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document is a detailed guide to the VoID vocabulary. It describes how VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. It also provides deployment advice and discusses the discovery of VoID descriptions."""@en; ; cat:DocLicense; data:W3C; "Describing Linked Datasets with the VoID Vocabulary"; ; xhv:last ; rdfs:label "Describing Linked Datasets with the VoID Vocabulary"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-09-27"^^xsd:date; """ This document lists the design goals and requirements that specifications would need to address in order to standardize various aspects of widgets. A Widget is an interactive single purpose application for displaying and/or updating local data or data on the Web, packaged in a way to allow a single download and installation on a user's machine or mobile device. Typical examples of widgets include clocks, CPU gauges, sticky notes, battery-life indicators, games, and widgets that make use of Web services, like weather forecasters, news readers, e-mail checkers, photo albums, and currency converters. """@en; ; cat:DocLicense; data:W3C; "Requirement For Standardizing Widgets"; ; xhv:last ; xhv:previous ; rdfs:label "Requirement For Standardizing Widgets"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-01-25"^^xsd:date; """ The document specifies requirements for Full-Text Search for use in XQuery [XQuery 1.0: An XML Query Language] and XPath [XML Path Language (XPath) 2.0]. """@en; ; cat:DocLicense; data:W3C; "XQuery and XPath Full Text 1.0 Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery and XPath Full Text 1.0 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-01-25"^^xsd:date; """ This document specifies usage scenarios for full-text queries as part of XQuery [XQuery 1.0: An XML Query Language (Second Edition)] and XPath [XML Path Language (XPath) 2.0 (Second Edition)]. """@en; ; cat:DocLicense; data:W3C; "XQuery and XPath Full Text 1.0 Use Cases"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery and XPath Full Text 1.0 Use Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-01-25"^^xsd:date; """ This note describes two new XProc steps designed to make it easier to construct documents within an XProc pipeline using values computed by that pipeline. """@en; ; cat:DocLicense; data:W3C; "Document Templating Steps for XProc"; ; xhv:last ; rdfs:label "Document Templating Steps for XProc"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-01-25"^^xsd:date; """ This document specifies goals and requirements for the XQuery Update Facility. """@en; ; cat:DocLicense; data:W3C; "XQuery Update Facility 1.0 Requirements"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery Update Facility 1.0 Requirements"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-01-25"^^xsd:date; """ This document specifies usage scenarios for the XQuery Update Facility. """@en; ; cat:DocLicense; data:W3C; "XQuery Update Facility 1.0 Use Cases"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery Update Facility 1.0 Use Cases"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-06-09"^^xsd:date; """ This document defines a datatype designed for compatibility with IEEE 754 floating-point decimal data, which can be supported by XSD 1.1 processors as an implementation-defined datatype. """@en; ; cat:DocLicense; data:W3C; "An XSD datatype for IEEE floating-point decimal"; ; xhv:last ; rdfs:label "An XSD datatype for IEEE floating-point decimal"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-06-09"^^xsd:date; """ This document lists the names of character categories and character blocks defined by Unicode and used in the regular expression language defined by XSD 1.0 and XSD 1.1. """@en; ; cat:DocLicense; data:W3C; "Unicode block names for use in XSD regular expressions"; ; xhv:last ; rdfs:label "Unicode block names for use in XSD regular expressions"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-08-11"^^xsd:date; """ This document defines a profile of the XML Signature Syntax and Processing 1.1 specification to allow a widget package to be digitally signed. Authors and distributors can digitally sign a widget as a mechanism to ensure continuity of authorship and distributorship. A user agent, or other validation system, can use a digital signature to verify the data integrity of the files within a widget package and to confirm the signing key(s). """@en; ; cat:DocLicense; data:W3C; "XML Digital Signatures for Widgets"; ; xhv:last ; xhv:previous ; rdfs:label "XML Digital Signatures for Widgets"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-06-07"^^xsd:date; """This specification defines Cascading Style Sheets, level 2 revision 1 (CSS 2.1). CSS 2.1 is a style sheet language that allows authors and users to attach style (e.g., fonts and spacing) to structured documents (e.g., HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS 2.1 simplifies Web authoring and site maintenance.CSS 2.1 builds on CSS2 [CSS2] which builds on CSS1 [CSS1]. It supports media-specific style sheets so that authors may tailor the presentation of their documents to visual browsers, aural devices, printers, braille devices, handheld devices, etc. It also supports content positioning, table layout, features for internationalization and some properties related to user interface.CSS 2.1 corrects a few errors in CSS2 (the most important being a new definition of the height/width of absolutely positioned elements, more influence for HTML's "style" attribute and a new calculation of the 'clip' property), and adds a few highly requested features which have already been widely implemented. But most of all CSS 2.1 represents a "snapshot" of CSS usage: it consists of all CSS features that are implemented interoperably at the date of publication of the Recommendation.CSS 2.1 is derived from and is intended to replace CSS2. Some parts of CSS2 are unchanged in CSS 2.1, some parts have been altered, and some parts removed. The removed portions may be used in a future CSS3 specification. Future specs should refer to CSS 2.1 (unless they need features from CSS2 which have been dropped in CSS 2.1, and then they should only reference CSS2 for those features, or preferably reference such feature(s) in the respective CSS3 Module that includes those feature(s))."""@en; ; cat:DocLicense; data:W3C; "Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification"; ; xhv:last ; xhv:previous ; rdfs:label "Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-09-20"^^xsd:date; """ This document describes the syntax and semantics for the Ink Markup Language. The Ink Markup Language serves as the data format for representing ink entered with an electronic pen or stylus. The markup allows for the input and processing of handwriting, gestures, sketches, music and other notational languages in applications. It provides a common format for the exchange of ink data between components such as handwriting and gesture recognizers, signature verifiers, and other ink-aware modules. It may be used in the W3C Multimodal Interaction Framework as proposed by the W3C Multimodal Interaction Activity. """@en; ; cat:DocLicense; data:W3C; "Ink Markup Language (InkML)"; ; xhv:last ; xhv:previous ; rdfs:label "Ink Markup Language (InkML)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-08-16"^^xsd:date; """This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML."""@en; ; cat:DocLicense; data:W3C; "Scalable Vector Graphics (SVG) 1.1 (Second Edition)"; ; xhv:last ; xhv:previous ; rdfs:label "Scalable Vector Graphics (SVG) 1.1 (Second Edition)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-07-05"^^xsd:date; """ This document describes CCXML, or the Call Control eXtensible Markup Language. CCXML is designed to provide telephony call control support for dialog systems, such as VoiceXML [VOICEXML]. While CCXML can be used with any dialog systems capable of handling media, CCXML has been designed to complement and integrate with a VoiceXML interpreter. Because of this there are many references to VoiceXML's capabilities and limitations. There are also details on how VoiceXML and CCXML can be integrated. However, it should be noted that the two languages are separate and are not required in an implementation of either language. For example, CCXML could be integrated with a more traditional Interactive Voice Response (IVR) system or a 3GPP Media Resource Function (MRF), and VoiceXML or other dialog systems could be integrated with other call control systems. """@en; ; cat:DocLicense; data:W3C; "Voice Browser Call Control: CCXML Version 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Voice Browser Call Control: CCXML Version 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-06-07"^^xsd:date; """CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. It uses color-related properties and values to color the text, backgrounds, borders, and other parts of elements in a document. This specification describes color values and properties for foreground color and group opacity. These include properties and values from CSS level 2 and new values."""@en; ; cat:DocLicense; data:W3C; "CSS Color Module Level 3"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Color Module Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-09-29"^^xsd:date; """This CSS Namespaces module defines the syntax for using namespaces in CSS. It defines the @namespace rule for declaring the default namespace and binding namespaces to namespace prefixes, and it also defines a syntax that other specifications can adopt for using those prefixes in namespace-qualified names."""@en; ; cat:DocLicense; data:W3C; "CSS Namespaces Module"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Namespaces Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-09-29"^^xsd:date; """Selectors are patterns that match against elements in a tree, and as such form one of several technologies that can be used to select nodes in an XML document. Selectors have been optimized for use with HTML and XML, and are designed to be usable in performance-critical code.CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. CSS uses Selectors for binding style properties to elements in the document.This document describes the selectors that already exist in CSS1 [CSS1] and CSS2 [CSS21], and further introduces new selectors for CSS3 and other languages that may need them.Selectors define the following function: expression ∗ element → boolean That is, given an element and a selector, this specification defines whether that element matches the selector.These expressions can also be used, for instance, to select a set of elements, or a single element from a set of elements, by evaluating the expression across all the elements in a subtree. STTS (Simple Tree Transformation Sheets), a language for transforming XML trees, uses this mechanism. [STTS3]"""@en; ; cat:DocLicense; data:W3C; "Selectors Level 3"; ; xhv:last ; xhv:previous ; rdfs:label "Selectors Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-10"^^xsd:date; """ This document is the specification of the Efficient XML Interchange (EXI) format. EXI is a very compact representation for the Extensible Markup Language (XML) Information Set that is intended to simultaneously optimize performance and the utilization of computational resources. The EXI format uses a hybrid approach drawn from the information and formal language theories, plus practical techniques verified by measurements, for entropy encoding XML information. Using a relatively simple algorithm, which is amenable to fast and compact implementation, and a small set of datatype representations, it reliably produces efficient encodings of XML event streams. The grammar production system and format definition of EXI are presented. """@en; ; cat:DocLicense; data:W3C; "Efficient XML Interchange (EXI) Format 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Efficient XML Interchange (EXI) Format 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-06-07"^^xsd:date; """ This document describes a profile of MathML 3.0 that admits formatting with Cascading Style Sheets. """@en; ; cat:DocLicense; data:W3C; "A MathML for CSS Profile"; ; xhv:last ; xhv:previous ; rdfs:label "A MathML for CSS Profile"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-09-27"^^xsd:date; """ This specification standardizes a packaging format and metadata for a class of software known as widgets. Unlike traditional user interface widgets (e.g., buttons, input boxes, toolbars, etc.), widgets as specified in this document are full-fledged client-side applications that are authored using technologies such as HTML and then packaged for distribution. Examples range from simple clocks, stock tickers, news casters, games and weather forecasters, to complex applications that pull data from multiple sources to be "mashed-up" and presented to a user in some interesting and useful way. The specification relies on PKWare's Zip specification as the archive format, XML as a configuration document format, and a series of steps that runtimes follow when processing and verifying various aspects of a package. The packaging format acts as a container for files used by a widget. The configuration document is an XML vocabulary that declares metadata and configuration parameters for a widget. The steps for processing a widget package describe the expected behavior and means of error handling for runtimes while processing the packaging format, configuration document, and other relevant files. This specification is part of the Widgets family of specifications, which together standardize widgets as a whole. """@en; ; cat:DocLicense; data:W3C; "Widget Packaging and XML Configuration"; ; xhv:last ; xhv:previous ; rdfs:label "Widget Packaging and XML Configuration"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This specification describes a general SOAP-based protocol for enumerating a sequence of XML elements from a SOAP enabled information source. """@en; ; cat:DocLicense; data:W3C; "Web Services Enumeration (WS-Enumeration)"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Enumeration (WS-Enumeration)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This specification describes a mechanism by which an endpoint can advertise the structure and contents of the events it might generate. """@en; ; cat:DocLicense; data:W3C; "Web Services Event Descriptions (WS-EventDescriptions)"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Event Descriptions (WS-EventDescriptions)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This specification describes a protocol that allows Web services to subscribe to or accept subscriptions for notification messages. """@en; ; cat:DocLicense; data:W3C; "Web Services Eventing (WS-Eventing)"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Eventing (WS-Eventing)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This specification extends the WS-Transfer [WS-Transfer] specification to enable clients to retrieve and manipulate parts or fragments of a WS-Transfer enabled resource without needing to include the entire XML representation in a message exchange. """@en; ; cat:DocLicense; data:W3C; "Web Services Fragment (WS-Fragment)"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Fragment (WS-Fragment)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This specification defines how metadata associated with a Web service endpoint can be represented as [WS-Transfer] resources or HTTP resources, how metadata can be embedded in [WS-Addressing] endpoint references, how metadata could be retrieved from a metadata resource, and how metadata associated with implicit features can be advertised. """@en; ; cat:DocLicense; data:W3C; "Web Services Metadata Exchange (WS-MetadataExchange)"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Metadata Exchange (WS-MetadataExchange)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This specification defines two WS-Policy assertions that can be used to advertise the requirement to use a certain version of SOAP in message exchanges. """@en; ; cat:DocLicense; data:W3C; "Web Services SOAP Assertions (WS-SOAPAssertions)"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services SOAP Assertions (WS-SOAPAssertions)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This specification describes a general SOAP-based protocol for accessing XML representations of Web service-based resources. """@en; ; cat:DocLicense; data:W3C; "Web Services Transfer (WS-Transfer)"; ; xhv:last ; xhv:previous ; rdfs:label "Web Services Transfer (WS-Transfer)"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-17"^^xsd:date; """ This document defines the syntax and formal semantics of XQuery and XPath Full Text 1.0, which is a language that extends XQuery 1.0 [XQuery 1.0: An XML Query Language (Second Edition)] and XPath 2.0 [XML Path Language (XPath) 2.0 (Second Edition)] with full-text search capabilities. """@en; ; cat:DocLicense; data:W3C; "XQuery and XPath Full Text 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery and XPath Full Text 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-17"^^xsd:date; """ This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility provides expressions that can be used to make persistent changes to instances of the XQuery 1.0 and XPath 2.0 Data Model. """@en; ; cat:DocLicense; data:W3C; "XQuery Update Facility 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery Update Facility 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-10"^^xsd:date; """ This document is a specification for a vocabulary to represent content in the Resource Description Framework (RDF). This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by web quality assurance tools such as web accessibility evaluation tools to record a representation of the assessed web content, including text, images, or other types of formats. In many cases, it can be used together with HTTP Vocabulary in RDF 1.0, which allows quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. This is particularly useful for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). """@en; ; cat:DocLicense; data:W3C; "Representing Content in RDF 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Representing Content in RDF 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-10"^^xsd:date; """ This document provides guidance for developers on implementing Evaluation and Report Language (EARL) 1.0 in software tools and process. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes. While this document provides developer guidance for using and implmenting EARL, Evaluation and Report Language (EARL) 1.0 Schema defines the core terms of the vocabulary, and other specifications provide additional terms for representing HTTP exchanges between clients and servers, HTTP Vocabulary in RDF 1.0, for representing web content itself, Representing Content in RDF 1.0, or for specifying particular locations within or sections of content, Pointer methods in RDF 1.0. An Evaluation and Report Language (EARL) Overview is also available. """@en; ; cat:DocLicense; data:W3C; "Developer Guide for Evaluation and Report Language (EARL) 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Developer Guide for Evaluation and Report Language (EARL) 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-10"^^xsd:date; """ This document describes the formal schema of the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, and that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes. """@en; ; cat:DocLicense; data:W3C; "Evaluation and Report Language (EARL) 1.0 Schema"; ; xhv:last ; xhv:previous ; rdfs:label "Evaluation and Report Language (EARL) 1.0 Schema"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-10"^^xsd:date; """ The identification of resources on the Web by a Uniform Resource Identifier (URI) alone may not be sufficient, as other factors such as HTTP content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). This document provides a representation of the HTTP vocabulary in the Resource Description Framework (RDF), to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by RFC 2616, as well as additional HTTP headers registered by the Internet Assigned Numbers Authority (IANA). These terms can also be used to record HTTPS exchanges. """@en; ; cat:DocLicense; data:W3C; "HTTP Vocabulary in RDF 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "HTTP Vocabulary in RDF 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-10"^^xsd:date; """ This specification contains a framework for representing pointers - entities that permit identifying a portion or segment of a piece of content - making use of the Resource Description Framework (RDF). It also describes a number of specific types of pointers that permit portions of a document to be referred to in different ways. When referring to a specific part of, say, a piece of web content, it is useful to be able to have a consistent manner by which to refer to a particular segment of a web document, to have a variety of ways by which to refer to that same segment, and to make the reference robust in the face of changes to that document. This specification is part of the Evaluation And Report Language (EARL) but can be reused in other contexts too. """@en; ; cat:DocLicense; data:W3C; "Pointer Methods in RDF 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Pointer Methods in RDF 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-15"^^xsd:date; """SVG is a language for describing vector graphics, but it is typically rendered to a display or some form of print medium. The SVG Compositing module adds support for the full range of Porter and Duff operators [PorterDuff] and blending modes. The module allows for raster and vector objects to be combined to produce eye catching effects.This document defines the markup used by SVG Compositing for display and printing environments. It explains the technical background and gives guidelines on how to use the SVG Compositing specification with the SVG 1.1 Full and SVG 1.2 Tiny specifications and other SVG modules."""@en; ; cat:DocLicense; data:W3C; "SVG Compositing Specification"; ; xhv:last ; xhv:previous ; rdfs:label "SVG Compositing Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-08-16"^^xsd:date; """The XMLHttpRequest Level 2 specification enhances the XMLHttpRequest object with new features, such as cross-origin requests, progress events, and the handling of byte streams for both sending and receiving."""@en; ; cat:DocLicense; data:W3C; "XMLHttpRequest Level 2"; ; xhv:last ; xhv:previous ; rdfs:label "XMLHttpRequest Level 2"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-15"^^xsd:date; """ This specification introduces and compares two client-side APIs for processing and synthesizing real-time audio streams in the browser. """@en; ; cat:DocLicense; data:W3C; "Audio Processing API"; ; xhv:last ; rdfs:label "Audio Processing API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-04-19"^^xsd:date; """ The Calendar API defines the high-level interfaces required to obtain read access to a user's calendaring service. This API includes the following key interfaces: A Calendar interface, which provides the method needed to access to a user's unified calendar.A CalendarEvent interface, which provides the individual calendar information of type EVENT that may be returned following a successful read operation. """@en; ; cat:DocLicense; data:W3C; "Calendar API"; ; xhv:last ; rdfs:label "Calendar API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-09-15"^^xsd:date; """This specification provides a way for an author to specify, in CSS, the size, zoom factor, and orientation of the viewport that is used as the base for the initial containing block."""@en; ; cat:DocLicense; data:W3C; "CSS Device Adaptation"; ; xhv:last ; rdfs:label "CSS Device Adaptation"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-15"^^xsd:date; """CSS 2D Transforms allows elements rendered by CSS to be transformed in two-dimensional space."""@en; ; cat:DocLicense; data:W3C; "CSS 2D Transforms"; ; xhv:last ; xhv:previous ; rdfs:label "CSS 2D Transforms"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-11-29"^^xsd:date; """This module describes features often used in printed publications. Most of the specified functionality involves some sort of generated content where content from the document is adorned, replicated, or moved in the final presentation of the document. Along with two other CSS3 modules – multi-column layout and paged media – this module offers advanced functionality for presenting structured documents on paged media. Paged media can be printed, or presented on screens."""@en; ; cat:DocLicense; data:W3C; "CSS Generated Content for Paged Media Module"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Generated Content for Paged Media Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-11-29"^^xsd:date; ; cat:DocLicense; data:W3C; "CSS Template Layout Module"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Template Layout Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-24"^^xsd:date; """CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This draft contains the features of CSS level 3 relating to list styling. It includes and extends the functionality of CSS level 2 [CSS21] , which builds on CSS level 1 [CSS1]. The main extensions compared to level 2 are a pseudo-element representing the list marker, a new ‘hanging’ value for ‘list-style-position’, and a method for authors to define their own list-styles."""@en; ; cat:DocLicense; data:W3C; "CSS Lists and Counters Module Level 3"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Lists and Counters Module Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-06-30"^^xsd:date; """"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 document proposes a set of CSS properties associated with the 'Ruby' elements. They can be used in combination with the Ruby elements of HTML."""@en; ; cat:DocLicense; data:W3C; "CSS3 Ruby Module"; ; xhv:last ; xhv:previous ; rdfs:label "CSS3 Ruby Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-07-12"^^xsd:date; """CSSOM defines APIs (including generic parsing and serialization rules) for Media Queries, Selectors, and of course CSS itself."""@en; ; cat:DocLicense; data:W3C; "CSSOM"; ; xhv:last ; rdfs:label "CSSOM"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-08-04"^^xsd:date; """The APIs introduced by this specification provide authors with a way to inspect and manipulate the visual view of a document. This includes getting the position of element layout boxes, obtaining the width of the viewport through script, and also scrolling an element."""@en; ; cat:DocLicense; data:W3C; "CSSOM View Module"; ; xhv:last ; xhv:previous ; rdfs:label "CSSOM View Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-01"^^xsd:date; """This specification defines an API that provides scripted access to geographical location information associated with the hosting device."""@en; ; cat:DocLicense; data:W3C; "Geolocation API Specification Level 2"; ; xhv:last ; rdfs:label "Geolocation API Specification Level 2"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-01"^^xsd:date; """ This document complements the Media Fragments 1.0 specification. It described various recipes for processing media fragments URI when used over the HTTP protocol. """@en; ; cat:DocLicense; data:W3C; "Protocol for Media Fragments 1.0 Resolution in HTTP"; ; xhv:last ; rdfs:label "Protocol for Media Fragments 1.0 Resolution in HTTP"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-04-14"^^xsd:date; """ This specification defines an API that provides access to messaging functionality in the device, including SMS, MMS and e-mail. """@en; ; cat:DocLicense; data:W3C; "The Messaging API"; ; xhv:last ; xhv:previous ; rdfs:label "The Messaging API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-06-07"^^xsd:date; """ The Network Information API provides an interface for Web Applications to access the underlying network information (connection info) of the device."""@en; ; cat:DocLicense; data:W3C; "The Network Information API"; ; xhv:last ; rdfs:label "The Network Information API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-01"^^xsd:date; """This specification defines several new DOM events that provide information about the physical orientation and motion of a hosting device."""@en; ; cat:DocLicense; data:W3C; "DeviceOrientation Event Specification"; ; xhv:last ; xhv:previous ; rdfs:label "DeviceOrientation Event Specification"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-05-12"^^xsd:date; ; cat:DocLicense; data:W3C; "Points of Interest Core"; ; xhv:last ; rdfs:label "Points of Interest Core"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-03-03"^^xsd:date; """ This Note summarizes scenarios, design decisions, and requirements for the XML Signature and Canonical XML specifications, to guide ongoing W3C work to revise these specifications."""@en; ; cat:DocLicense; data:W3C; "XML Security 1.1 Requirements and Design Considerations"; ; xhv:last ; xhv:previous ; rdfs:label "XML Security 1.1 Requirements and Design Considerations"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-04-21"^^xsd:date; """ This document outlines use cases, requirements and design choices for XML Security 2.0, specifically Canonical XML 2.0 and XML Signature 2.0. It includes a proposed simplification of the XML Signature Transform mechanism, intended to enhance security, performance, streamability and to ease adoption."""@en; ; cat:DocLicense; data:W3C; "XML Security 2.0 Requirements and Design Considerations"; ; xhv:last ; xhv:previous ; rdfs:label "XML Security 2.0 Requirements and Design Considerations"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ XPath 3.0 is an expression language that allows the processing of values conforming to the data model defined in [XQuery and XPath Data Model (XDM) 3.0]. The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values. The result of an XPath expression may be a selection of nodes from the input documents, or an atomic value, or more generally, any sequence allowed by the data model. The name of the language derives from its most distinctive feature, the path expression, which provides a means of hierarchic addressing of the nodes in an XML tree. XPath 3.0 is a superset of [XML Path Language (XPath) Version 1.0], with the added capability to support a richer set of data types, and to take advantage of the type information that becomes available when documents are validated using XML Schema. A backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 3.0; exceptions to this policy are noted in [I Backwards Compatibility with XPath 1.0]. """@en; ; cat:DocLicense; data:W3C; "XML Path Language (XPath) 3.0"; ; xhv:last ; xhv:previous ; rdfs:label "XML Path Language (XPath) 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This document defines the XQuery and XPath Data Model 3.0, which is the data model of [XML Path Language (XPath) 3.0], [XSL Transformations (XSLT) Version 3.0], and [XQuery 3.0: An XML Query Language] , and any other specifications that reference it. This document is the result of joint work by the [XSL Working Group] and the [XML Query Working Group]. """@en; ; cat:DocLicense; data:W3C; "XQuery and XPath Data Model 3.0"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery and XPath Data Model 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This document defines the syntax and formal semantics of XQuery and XPath Full Text 3.0, which is a language that extends XQuery 3.0 [XQuery 3.0: An XML Query Language] and XPath 3.0 [XML Path Language (XPath) 3.0] with full-text search capabilities. """@en; ; cat:DocLicense; data:W3C; "XQuery and XPath Full Text 3.0"; ; xhv:last ; rdfs:label "XQuery and XPath Full Text 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ Change markings are relative to the Recommendation of 23 January 2007. This document defines constructor functions, operators, and functions on the datatypes defined in [XML Schema Part 2: Datatypes Second Edition] and the datatypes defined in [XQuery and XPath Data Model (XDM) 3.0]. It also defines functions and operators on nodes and node sequences as defined in the [XQuery and XPath Data Model (XDM) 3.0]. These functions and operators are defined for use in [XML Path Language (XPath) 3.0], [XQuery 3.0: An XML Query Language] and [XSL Transformations (XSLT) Version 3.0] and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2005/xpath-functions/. This is the third version of the specification of this function library. The first version was included as an intrinsic part of the [XML Path Language (XPath) Version 1.0] specification published on 16 November 1999. The second version was published under the title XQuery 1.0 and XPath 2.0 Functions and Operators on 23 January 2007, subsequently revised in a second edition published on 14 December 2010. This third version is the first to carry its own version number, which has been set at 3.0 to align with the version numbering for XPath, XQuery, and XSLT. """@en; ; cat:DocLicense; data:W3C; "XPath and XQuery Functions and Operators 3.0"; ; xhv:last ; xhv:previous ; rdfs:label "XPath and XQuery Functions and Operators 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources. XQuery 3.0 is an extended version of the XQuery 1.0 Recommendation published on 23 January 2007. A list of changes made since XQuery 1.0 can be found in J Change Log. Here are some of the new features in XQuery 3.0: group by clause in FLWOR Expressions (3.10.7 Group By Clause). tumbling window and sliding window in FLWOR Expressions (3.10.4 Window Clause). count clause in FLWOR Expressions (3.10.6 Count Clause). allowing empty in 3.10.2 For Clause, for functionality similar to outer joins in SQL. try/catch expressions (3.15 Try/Catch Expressions). Dynamic function call (3.2.2 Dynamic Function Call ). Inline function expressions (3.1.7 Inline Function Expressions). Private functions (4.18 Function Declaration). Switch expressions (3.13 Switch Expression). Computed namespace constructors (3.9.3.7 Computed Namespace Constructors). Output declarations (2.2.4 Serialization). Annotations (4.15 Annotations). Annotation assertions in function tests. """@en; ; cat:DocLicense; data:W3C; "XQuery 3.0: An XML Query Language"; ; xhv:last ; xhv:previous ; rdfs:label "XQuery 3.0: An XML Query Language"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility 3.0 provides expressions that can be used to make persistent changes to instances of the XQuery and XPath Data Model 3.0. """@en; ; cat:DocLicense; data:W3C; "XQuery Update Facility 3.0"; ; xhv:last ; rdfs:label "XQuery Update Facility 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This document defines an XML Syntax for [XQuery 3.0: An XML Query Language] . """@en; ; cat:DocLicense; data:W3C; "XQueryX 3.0"; ; xhv:last ; xhv:previous ; rdfs:label "XQueryX 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2011-12-13"^^xsd:date; """ This document defines serialization of an instance of the data model as defined in [XQuery and XPath Data Model (XDM) 3.0] into a sequence of octets. Serialization is designed to be a component that can be used by other specifications such as [XSL Transformations (XSLT) Version 3.0] or [XQuery 3.0: An XML Query Language]. """@en; ; cat:DocLicense; data:W3C; "XSLT and XQuery Serialization 3.0"; ; xhv:last ; xhv:previous ; rdfs:label "XSLT and XQuery Serialization 3.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-11-15"^^xsd:date; ; cat:DocLicense; data:W3C; "Content Security Policy 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Content Security Policy 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-04-19"^^xsd:date; ; cat:DocLicense; data:W3C; "Web IDL"; ; xhv:last ; xhv:previous ; rdfs:label "Web IDL"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-05-08"^^xsd:date; """ This specification defines an API that provides information about the battery status of the hosting device."""@en; ; cat:DocLicense; data:W3C; "Battery Status API"; ; xhv:last ; xhv:previous ; rdfs:label "Battery Status API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-07-24"^^xsd:date; """CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This draft contains the features of CSS level 3 relating to borders and backgrounds. It includes and extends the functionality of CSS level 2 [CSS21], which builds on CSS level 1 [CSS1]. The main extensions compared to level 2 are borders consisting of images, boxes with multiple backgrounds, boxes with rounded corners and boxes with shadows.This module replaces two earlier drafts: CSS3 Backgrounds and CSS3 Border."""@en; ; cat:DocLicense; data:W3C; "CSS Backgrounds and Borders Module Level 3"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Backgrounds and Borders Module Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-09-18"^^xsd:date; ; cat:DocLicense; data:W3C; "CSS Flexible Box Layout Module"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Flexible Box Layout Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-04-17"^^xsd:date; """CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This module contains the features of CSS level 3 relating to the type and replaced elements. It includes and extends the functionality of CSS level 2 [CSS21], which builds on CSS level 1 [CSS1] . The main extensions compared to level 2 are the generalization of the type to the type, several additions to the ‘’ type, a generic sizing algorithm for images and other replaced content in CSS, and several properties controlling the interaction of replaced elements and CSS's layout models."""@en; ; cat:DocLicense; data:W3C; "CSS Image Values and Replaced Content Module Level 3"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Image Values and Replaced Content Module Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-03-20"^^xsd:date; """CSS (Cascading Style Sheets) is a language that describes the rendering of markup documents (e.g. HTML, XML) on various supports, such as screen, paper, speech, etc. The Speech module defines aural CSS properties that enable authors to declaratively control the rendering of documents via speech synthesis, and using optional audio cues. Note that this standard was developed in cooperation with the Voice Browser Activity."""@en; ; cat:DocLicense; data:W3C; "CSS Speech Module"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Speech Module"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-08-28"^^xsd:date; ; cat:DocLicense; data:W3C; "CSS Values and Units Module Level 3"; ; xhv:last ; xhv:previous ; rdfs:label "CSS Values and Units Module Level 3"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-05-10"^^xsd:date; """As the web is becoming ubiquitous, interactive, and multimodal, technology needs to deal increasingly with human factors, including emotions. The specification of Emotion Markup Language 1.0 aims to strike a balance between practical applicability and scientific well-foundedness. The language is conceived as a "plug-in" language suitable for use in three different areas: (1) manual annotation of data; (2) automatic recognition of emotion-related states from user behavior; and (3) generation of emotion-related system behavior."""@en; ; cat:DocLicense; data:W3C; "Emotion Markup Language (EmotionML) 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Emotion Markup Language (EmotionML) 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-07-26"^^xsd:date; ; cat:DocLicense; data:W3C; "Page Visibility"; ; xhv:last ; xhv:previous ; rdfs:label "Page Visibility"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-07-26"^^xsd:date; ; cat:DocLicense; data:W3C; "Performance Timeline"; ; xhv:last ; xhv:previous ; rdfs:label "Performance Timeline"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-05-22"^^xsd:date; ; cat:DocLicense; data:W3C; "Resource Timing"; ; xhv:last ; xhv:previous ; rdfs:label "Resource Timing"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-07-12"^^xsd:date; """ The Role Attribute defined in this specification allows the author to annotate markup languages with machine-extractable semantic information about the purpose of an element. Use cases include accessibility, device adaptation, server-side processing, and complex data description. This attribute can be integrated into any markup language. In particular, schema implementations are provided to facilitate with languages based upon XHTML Modularization [XHTML-MODULARIZATION11-2e]. The role attribute is necessary to support Accessible Rich Internet Applications (WAI-ARIA) [WAI-ARIA] to define roles in XML-based languages, when the languages do not define their own role attribute. Although this is the reason the Role Attribute is published by the Protocols and Formats Working Group, the attribute has more general use cases as well. """@en; ; cat:DocLicense; data:W3C; "Role Attribute 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "Role Attribute 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-11-08"^^xsd:date; """ SPARQL is a query language and a protocol for data that is stored natively as RDF or viewed as RDF via middleware. The main mechanism for computing query results in SPARQL is subgraph matching: RDF triples in both the queried RDF data and the query pattern are interpreted as nodes and edges of directed graphs, and the resulting query graph is matched to the data graph using variables as wild cards. Various W3C standards, including RDF and OWL, provide semantic interpretations for RDF graphs that allow additional RDF statements to be inferred from explicitly given assertions. Many applications that rely on these semantics require a query language such as SPARQL, but in order to use SPARQL, basic graph pattern matching has to be defined using semantic entailment relations instead of explicitly given graph structures. There are different possible ways of defining a basic graph pattern matching extension for an entailment relation. This document specifies one such way for a range of standard semantic web entailment relations. Such extensions of the SPARQL semantics are called entailment regimes within this document. An entailment regime defines not only which entailment relation is used, but also which queries and graphs are well-formed for the regime, how the entailment is used (since there are potentially different meaningful ways to use the same entailment relation), and what kinds of errors can arise. The entailment relations used in this document are standard entailment relations in the semantic web: RDF entailment, RDFS entailment, D-entailment, OWL Direct and RDF-Based Semantics entailment, and RIF Core entailment. """@en; ; cat:DocLicense; data:W3C; "SPARQL 1.1 Entailment Regimes"; ; xhv:last ; xhv:previous ; rdfs:label "SPARQL 1.1 Entailment Regimes"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-11-08"^^xsd:date; """ This document describes the use of HTTP operations for the purpose of managing a collection of RDF graphs. This interface is an alternative to the SPARQL 1.1 Update protocol. Most of the operations defined here can be performed using that interface, but for some clients or servers, this interface may be easier to implement or work with. This specification may serve as a non-normative suggestion for HTTP operations on RDF graphs which are managed outside of a SPARQL 1.1 graph store. """@en; ; cat:DocLicense; data:W3C; "SPARQL 1.1 Graph Store HTTP Protocol"; ; xhv:last ; xhv:previous ; rdfs:label "SPARQL 1.1 Graph Store HTTP Protocol"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-11-08"^^xsd:date; """ The SPARQL Protocol and RDF Query Language (SPARQL) is a query language and protocol for RDF. This document specifies the SPARQL Protocol; it describes a means for conveying SPARQL queries and updates to a SPARQL processing service and returning the results via HTTP to the entity that requested them. This protocol was developed by the W3C SPARQL Working Group, part of the Semantic Web Activity as described in the activity statement . """@en; ; cat:DocLicense; data:W3C; "SPARQL 1.1 Protocol"; ; xhv:last ; xhv:previous ; rdfs:label "SPARQL 1.1 Protocol"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-07-26"^^xsd:date; ; cat:DocLicense; data:W3C; "User Timing"; ; xhv:last ; xhv:previous ; rdfs:label "User Timing"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-05-08"^^xsd:date; """ This specification defines an API that provides access to the vibration mechanism of the hosting device. Vibration is a form of tactile feedback. """@en; ; cat:DocLicense; data:W3C; "Vibration API"; ; xhv:last ; xhv:previous ; rdfs:label "Vibration API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-05-01"^^xsd:date; """This specification defines two mechanisms for communicating between browsing contexts in HTML documents."""@en; ; cat:DocLicense; data:W3C; "HTML5 Web Messaging"; ; xhv:last ; xhv:previous ; rdfs:label "HTML5 Web Messaging"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-09-20"^^xsd:date; """This specification defines an API that enables Web pages to use the WebSocket protocol (defined by the IETF) for two-way communication with a remote host."""@en; ; cat:DocLicense; data:W3C; "The WebSocket API"; ; xhv:last ; xhv:previous ; rdfs:label "The WebSocket API"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-05-01"^^xsd:date; """This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism."""@en; ; cat:DocLicense; data:W3C; "Web Workers"; ; xhv:last ; xhv:previous ; rdfs:label "Web Workers"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-01-24"^^xsd:date; """ Canonical XML Version 2.0 is a canonicalization algorithm for XML Signature 2.0. It addresses issues around performance, streaming, hardware implementation, robustness, minimizing attack surface, determining what is signed and more. 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 [XML10] and Namespaces in XML 1.0 [XML-NAMES]. 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. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on application-specific equivalence rules for which no generalized XML specification could account. Canonical XML Version 2.0 is applicable to XML 1.0. It is not defined for XML 1.1. """@en; ; cat:DocLicense; data:W3C; "Canonical XML Version 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Canonical XML Version 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-01-24"^^xsd:date; """ This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere. XML Signature 2.0 includes a new Reference processing model designed to address additional requirements including performance, simplicity and streamability. This "2.0 mode" model is significantly different than the XML Signature 1.x model in that it explicitly defines selection, canonicalization and verification steps for data processing and disallows generic transforms. XML Signature 2.0 is designed to be backward compatible through the inclusion of a "Compatibility Mode" which enables the XML Signature 1.x model to be used where necessary. """@en; ; cat:DocLicense; data:W3C; "XML Signature Syntax and Processing Version 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "XML Signature Syntax and Processing Version 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-01-24"^^xsd:date; """ This document defines a streamable profile of XPath 1.0 suitable for use with XML Signature 2.0. """@en; ; cat:DocLicense; data:W3C; "XML Signature Streaming Profile of XPath 1.0"; ; xhv:last ; xhv:previous ; rdfs:label "XML Signature Streaming Profile of XPath 1.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-03-13"^^xsd:date; """ This document specifies how the XML Signature 2.0 transform model may be used with XML Encryption 1.1 for CipherReference processing. """@en; ; cat:DocLicense; data:W3C; "XML Encryption 1.1 CipherReference Processing using 2.0 Transforms"; ; xhv:last ; xhv:previous ; rdfs:label "XML Encryption 1.1 CipherReference Processing using 2.0 Transforms"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-01-03"^^xsd:date; """ This document, "Understanding WCAG 2.0," is an essential guide to understanding and using Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. It is part of a series of documents that support WCAG 2.0. Please note that the contents of this document are informative (they provide guidance), and not normative (they do not set requirements for conforming to WCAG 2.0). See Web Content Accessibility Guidelines (WCAG) Overview for an introduction to WCAG, supporting technical documents, and educational material. WCAG 2.0 establishes a set of Success Criteria to define conformance to the WCAG 2.0 Guidelines. A Success Criterion is a testable statement that will be either true or false when applied to specific Web content. "Understanding WCAG 2.0" provides detailed information about each Success Criterion, including its intent, the key terms that are used in the Success Criterion, and how the Success Criteria in WCAG 2.0 help people with different types of disabilities. This document also provides examples of Web content that meet the success criterion using various Web technologies (for instance, HTML, CSS, XML), and common examples of Web content that does not meet the success criterion. This document indicates specific techniques to meet each Success Criterion. Details for how to implement each technique are available in Techniques for WCAG 2.0, but "Understanding WCAG 2.0" provides the information about the relationship of each technique to the Success Criteria. Techniques are categorized by the level of support they provide for the Success Criteria. "Sufficient techniques" are sufficient to meet a particular Success Criterion (either by themselves or in combination with other techniques), while other techniques are advisory and therefore optional. None of the techniques are required to meet WCAG 2.0, although some may be the only known method if a particular technology is used. "Advisory techniques" are not sufficient to meet the Success Criteria on their own (because they are not testable or provide incomplete support) but it is encouraged that authors follow them when possible to provide enhanced accessibility. Another support category is "Common Failures", which describe authoring practices known to cause Web content not to conform to WCAG 2.0. Although failures provide advisory information about certain authoring practices, authors must avoid those practices in order to meet the WCAG 2.0 Success Criteria. This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0. This document was published as a Working Group Note at the same time WCAG 2.0 was published as a W3C Recommendation. Unlike WCAG 2.0, is expected that the information in Understanding WCAG 2.0 will be updated from time to time. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction to WCAG, supporting technical documents, and educational material. """@en; ; cat:DocLicense; data:W3C; "Understanding WCAG 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Understanding WCAG 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-01-03"^^xsd:date; """ "Techniques for WCAG 2.0" provides information to Web content developers who wish to satisfy the success criteria of Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. Techniques are specific authoring practices that may be used in support of the WCAG 2.0 success criteria. This document provides "General Techniques" that describe basic practices that are applicable to any technology, and technology-specific techniques that provide information applicable to specific technologies. Technology-specific techniques do not supplant the general techniques: content developers should consider both general techniques and technology-specific techniques as they work toward conformance. Use of the techniques provided in this document makes it easier for Web content to demonstrate conformance to WCAG 2.0 success criteria than if these techniques are not used. Besides the techniques provided in this document, there may be other techniques that can be used to implement conformance to WCAG 2.0. The WCAG WG encourages submission of such techniques so they can be considered for inclusion in this document, in order to make the set of techniques maintained by the WCAG WG as comprehensive as possible. Please submit techniques for consideration using the "Techniques Submission Form." Some techniques contain User Agent and Assistive Technology Support Notes. As time passes, these versions of user agents or assistive technologies may no longer be current, and there is no commitment to update the notes as new versions are released. Authors should test techniques against the user agents and assistive technologies currently available to their users. See also Understanding Accessibility Support. This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0. This document was published as a Working Group Note at the same time WCAG 2.0 was published as a W3C Recommendation. Unlike WCAG 2.0, it is expected that the information in Understanding WCAG 2.0 will be updated from time to time. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction to WCAG, supporting technical documents, and educational material. """@en; ; cat:DocLicense; data:W3C; "Techniques for WCAG 2.0"; ; xhv:last ; xhv:previous ; rdfs:label "Techniques for WCAG 2.0"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-01-17"^^xsd:date; """The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server."""@en; ; cat:DocLicense; data:W3C; "XMLHttpRequest"; ; xhv:last ; xhv:previous ; rdfs:label "XMLHttpRequest"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-10-02"^^xsd:date; ; cat:DocLicense; data:W3C; "Web API Design Cookbook"; ; xhv:last ; rdfs:label "Web API Design Cookbook"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-07-03"^^xsd:date; """ This document describes privacy best practices for web applications, including those that might use device APIs. """@en; ; cat:DocLicense; data:W3C; "Web Application Privacy Best Practices"; ; xhv:last ; xhv:previous ; rdfs:label "Web Application Privacy Best Practices"; :accessURL ; :status ; radion:distribution . a :SemanticAsset, :SemanticAssetDistribution; "2012-05-10"^^xsd:date; """This document provides a list of emotion vocabularies that can be used with EmotionML to represent emotions and related states. EmotionML provides mechanisms to represent emotions in terms of scientifically valid descriptors: categories, dimensions, appraisals, and action tendencies. Given the lack of agreement in the community, EmotionML does not provide a single vocabulary of emotion terms, but gives users a choice to select the most suitable emotion vocabulary in their annotations. In order to promote interoperability, publicly defined vocabularies should be used where possible and reasonable from the point of view of the target application. The present document provides a number of emotion vocabularies that can be used for this purpose."""@en