Table of contents

[Home] [W3C Specs]

1.1 Origin and Goals

2 XLink Concepts

2.1 Links and Resources

2.2 Arcs, Traversal, and Behavior

2.3 Resources in Relation to the Physical Location of a Linking Element

3 XLink Processing and Conformance

3.1 Processing Dependencies

3.2 Markup Conformance

3.3 Application Conformance

4 XLink Markup Design

4.1 XLink Attribute Usage Patterns

4.2 XLink Element Type Relationships

4.3 Attribute Value Defaulting

4.4 Integrating XLink Usage with Other Markup

4.5 Using XLink with Legacy Markup

5 XLink Elements and Attributes

5.1 Extended Links (extended-Type Element)

5.1.1 Local Resources for an Extended Link (resource-Type Element)

5.1.2 Remote Resources for an Extended Link (locator-Type Element)

5.1.3 Traversal Rules for an Extended Link (arc-Type Element)

5.1.4 Titles for Extended Links, Locators, and Arcs (title-Type Element)

5.1.5 Locating Linkbases (Special Arc Role)

5.2 Simple Links (simple-Type Element)

5.3 XLink Element Type Attribute (type)

5.4 Locator Attribute (href)

5.5 Semantic Attributes (role, arcrole, and title)

5.6 Behavior Attributes (show and actuate)

5.6.1 show Attribute

5.6.2 actuate Attribute

5.7 Traversal Attributes (label, from, and to)

Appendices

A.1 Normative References

A.2 Non-Normative References

C Working Group Members and Acknowledgments

4.5 Using XLink with Legacy Markup

Using XLink with Legacy Markup

Because XLink's global attributes require the use of namespace prefixes, non-XLink-based links in legacy documents generally do not serve as conforming XLink constructs as they stand, even if attribute value defaulting is used. For example, XHTML 1.0 has an a element with an href attribute, but because the attribute is a local one attached to the a element in the XHTML namespace, it is not the same as an xlink:href global attribute in the XLink namespace.

[Next Chapter] [Home]