Search Results for "addressing"

Traditional URLs are simple and easy to use, but they’re also quite limited. For one thing, a URL only points at a single, complete document. More granularity than that, such as linking to the third sentence of the seventeenth paragraph in a document, requires the author of the targeted document to manually insert named anchors at the targeted location. The author of the document doing the linking can’t do this unless he or she also has write access to the document being linked to. Even if the author doing the linking can insert named anchors into

This section describes the terms and concepts that are essential to understanding XLink, without discussing the syntax used to create XLink constructs. A few additional terms are introduced in later parts of this specification. 2.1 Links and Resources [Definition: An XLink link is an explicit relationship between resources or portions of resources.] [Definition: It is made explicit by an XLink linking element, which is an XLink-conforming XML element that asserts the existence of a link.] There are six XLink elements; only two of them are considered

Description This work defines the XML Pointer Language (XPointer), the language to be used as a fragment identifier for any URI-reference that locates a resource of Internet media type text/xml or application/xml. XPointer has been split into a framework for specifying location schemes, and three schemes: element(), xmlns() and xpointer(). The framework and the first two schemes form the XPointer Recommendation, and provide a minimal inventory of mechanisms. The xpointer() scheme, which is based on the XML Path Language (XPath), is still under

XPointer is a system for addressing components of XML based internet media. At the present time (late 2002), XPointer is divided among four specifications: a "framework" which forms the basis for identifying XML fragments, a positional element addressing scheme, a scheme for namespaces, and a scheme for XPath-based addressing. The XPointer language is designed to address structural aspects of XML, including text content and other information objects created as a result of parsing the document. Thus, it could be used to point to a section of a

Abstract 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. Status of this Document This document has been superceded. The design described in previous versions of this document has been factored into a basic framework (http://www.w3.org/TR/xptr-framework/) which defines XPointer schemes

XPointer provides a more fine-grained addressing than XPath. * Instead of just nodes, XPointers address locations, which can be nodes, points, or ranges. * A point can represent the location preceding or following any individual character in e.g. chardata nodes. The special node test point() selects the set of points of a node. * A range consists of two points in the same document, and is specified using a special range-to location step construct. * XPointer provides some extra functions: here() get location of element