A group named Web consortium XML linking is creating stipulations to facilitate more superior hypertext functionality on web. This description is about the goals and approaches of XML linking. It also describe the HTML linking limitations seeks to overcome the XML linking. Once the linking is done it does the survey of working groups main specifications.
A short description about background of xml linking is mentioned below:
You might know HTML tag set and element type such as A are most in use and famous as well. However, still there are
The design of XLink has been informed by knowledge of established hypermedia systems and standards. The following standards have been especially influential:
*
HTML [html]: Defines several element types that represent links.
*
HyTime [iso10744]: Defines inline and inbound and third-party link structures and some semantic features, including traversal control and presentation of objects.
*
Text Encoding Initiative Guidelines [tei]: Provides structures for creating links, aggregate objects, and link collections.
Many other linking systems
XLink Attribute Usage Patterns
While the XLink attributes are considered global by virtue of their use of the namespace mechanism, their allowed combinations on any one XLink element type depend greatly on the value of the special type attribute (see [XLink Element Type Attribute (] for more information) for the element on which they appear. The conformance constraint notes in this specification detail their allowed usage patterns. Following is a summary of the element types (columns) on which the global attributes (rows) are allowed, with an
Abstract
The Web Consortium's XML Linking working group is developing specifications to enable more advanced hypertext functionality on the Web: in particular fine-grained anchors, external annotation, and bi-directional links. This paper examines basic goals and approaches; describes HTML linking limitations XML Linking seeks to overcome; and surveys the Working Group's primary specifications: XPath, XPointer, and XLink. As of this writing, the last two, while well advanced, are not final recommendations, and so are subject to change. Consult the
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
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 [IETF RFC 2376]. This specification does not constrain the syntax or semantics of URI references to resources of other media types, although it provides extension facilities that may be used with other types.
XPointer supports addressing into
RSS/XML