Home > Articles

Improving Web Linking Using XLink

The emerging XLink and XPointer standards could fundamentally change the way we use the Web, particularly how users interact with information. David Lowe and Dr. Erik Wilde take a look at some of the rich linking functionality these standards provide.
Like this article? We recommend

The linking model that underpins the Web is an integral part of HTML and has played a substantial role in supporting the incredible growth of the Web over the last decade. The original model (a simple link from one piece of information to another) was very simplistic, which led to much of its success. However, that simplicity is now restricting the functionality that can be achieved with the Web.

Much more sophisticated linking has been exhibited in a number of other (usually standalone) hypertext systems. Many of these systems (and their associated models) are indeed much older than the Web itself. The Web's linking model was already outdated (in a technical sense) when it was created. Some of the functionality can be enabled with the Web—but usually only with complex nonstandard coding.

The emergence of XML and, in particular, the linking model that accompanies it—XLink and XPointer—will enable a much more sophisticated linking model to be natively supported on the Web. In this article, we look at some of the emerging possibilities that are enabled by XLink and XPointer.

We begin by considering typical link functionalities that are not possible with the current Web. We then move on to look at how they might be supported using XLink and XPointer. We finish with a typical scenario that highlights some of these uses.

This article is not intended to be an introduction to XLink and XPointer. Indeed, we assume a least a passing knowledge of these standards (though the article should make sense even without this). Instead, the goal is to illustrate how these standards can support more effective usability of the Web by providing enhanced linking mechanisms.

Linking Functionality

The linking model that has underpinned the traditional Web model is very simplistic. Essentially, the standard <A HREF="..."> link is a simple static, directional, single-source, single-destination link that is embedded into the source document. It is static because the link never changes (at least, not once it has been coded into an HTML page). It is directional because the link has an explicit direction of association (and, hence, usually has an explicit direction of navigation). It is single-source because the link has only one point from which it can be triggered. It is single-destination because the link has only one resource to which the client traverses when the user activates the link. The link is embedded into the source document (indeed, it is embedded within the source anchor) because the description of the connection between the source and destination anchors exists within the source anchor.

Even this simple model highlights a number of different linking concepts—which, in turn, indicate aspects that, if changed, can lead to more complex and sophisticated linking. To start, we have resources—an addressable unit of information or service. In other words, this is basically anything that we are able to request, including Web pages, XML documents, images, audio clips, program outputs, and so on. A resource (in the URI sense of the word) is not necessarily a computer-related thing, but, at least conceptually, it could be anything you want to deal with, such as paper documents or even animals.

By utilizing standards for addressing fragments of these things, we can also treat fragments as resources. It is worth noting that Web standards—in particular, RFC 2396—distinguishes between addressing a whole resource (referred to as an identifier, and typically implemented using universal resource identifiers) and addressing a particular subresource (implemented using resource type-specific fragment identifiers).

A resource (or subresource) can be used in various ways, but in the context of this discussion, the most common use is related to linking. To do this, we need to define the relevant regions of the resources (or resources themselves) that are participating in a link. Within the context of a link, these regions are referred to as anchors—or, in XML linking, they are referred to as locators.

We also need to distinguish between links and arcs. This requires an understanding of a third concept: traversal. In an HTML A link, we have a single source anchor, a single destination anchor, and an implied connection between them. When we view an HTML document and activate the anchor (in most user interfaces, by simply clicking on it), the link is traversed to the link destination. Other forms of linking in HTML work differently. For example, the link between a document and an image (specified using the IMG element) is traversed automatically when the document is loaded, and the resultant image is embedded into the source. The link between a document and a style sheet (specified using a LINK element) is traversed automatically but does not result in any content being embedded. In each case, the various link characteristics (such as how the traversal of the link is initiated, the behavior upon traversal, and the specification of the link semantics) are typically implicit for that link type.

The situation is somewhat different—and much more flexible—with linking in XML. XLink allows the definition of links, but a link does not imply traversal! Instead, in XLink, a link is simply an association between a number of resources (specified using locators). There is no link "source," nor is there a link "destination." This is because XLink has separated the concept of associating resources (using a link) from the concept of traversal among these resources. This traversal is specified using arcs. A given link can contain a number of different arcs. Similarly, in many cases we might not need to provide traversal information—especially when the association is being defined for a reason other than to support navigational hyperlinking (for example, to define a collection of resources to be analyzed by computer rather than to be viewed by a human user). We'll return to this point again a little later in the article.

So, using the above concepts, we can identify a number of more sophisticated forms of linking. For example, consider a situation in which we have a link that has multiple participating resources, with an arc that starts from more than one resource and ends on more than one resource. In other words, the arc traversal can be activated from multiple different locations; when it is activated, it results in the presentation of multiple new resources instead of just a single resource. The result is a multisource, multidestination link—something that is not possible to easily implement using the simple linking model within HTML.

We can also have dynamic links, with the destinations resource(s) resolved only when traversal occurs. Specifically, a dynamic link has structure or behavior that changes over time, or with different users or circumstances. These changes can be with the link structure (such as changes in the link destinations) or with the link semantics (such as whether the activation results in the new resource replacing the existing content or being embedded in the existing content). In the most common example of dynamic links, the link destination is a service rather than a document, such as a CGI script. These types of links can be important for supporting adaptive systems. For example, we might want to change the destination of a link depending upon the pages a user has previously visited. Although HTML has no inherent support for dynamic links, it is possible to create them using server-side technologies such as CGI scripts or servlets, possibly in conjunction with other technologies such as HTTP cookies or URL rewriting.

A little more interestingly, generic links are links in which participating resources are defined not by a specific location, but by a particular pattern that can be matched to any relevant content. For example, we could have a link from any occurrence of the word XML within a document to a definition of the term XML.

This has several implications that are useful to look at briefly. The first is that because the source anchor is defined for a particular pattern rather than a particular location, it would be more accurate to refer to it as a generic anchor (or generic subresource) than a generic link. Again, implementing generic links with the conventional HTML linking model is very difficult (though possible, given some complex back-end processing).

The above example illustrates some of the limitations of the existing HTML linking model—and, hence, some of the potential areas that can be improved with XML linking. We will now look in more detail at the XML linking model and how it supports some of these concepts.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020