XPath, XLink, XPointer, and XML A Practical Guide to Web Hyperlinking and Transclusion Erik Wilde and David Lowe

Welcome to transcluding.com, the Web site of XPath, XLink, XPointer, and XML: A Practical Guide to Web Hyperlinking and Transclusion. On this Web site you can find information about the subjects discussed in the book, and you can find many pointers to other useful information on the Web. You can directly jump to the following sections:

• News, the latest news in standards development.
• Resources, links to pages that are relevant for the book's subject (ie, XML and linking).
• Links to book pages, links to pages that deal with the book (in contrast to the book's subject).
• Errata, a list of known errors in the book's text.

• 13-Nov-2002: W3C releases XPointer proposed recommendations

  On November 13th, W3C released a number of new XPointer proposed recommendations:

  • W3C Proposed Recommendation PR-xptr-framework-20021113: XPointer Framework
  • W3C Proposed Recommendation PR-xptr-element-20021113: XPointer element() Scheme
  • W3C Proposed Recommendation PR-xptr-xmlns-20021113: XPointer xmlns() Scheme

  This release of new XPointer documents leaves "W3C Working Draft WD-xptr-xpointer-20020710: XPointer xpointer() Scheme" (the core of XPointer) in draft status.

• 13-Sep-2002: W3C releases HLink Working Draft

  On September 13th, W3C released a document produced by the XHTML working group, the HLink working draft:

  • W3C Working Draft WD-hlink-20020913: HLink - Link recognition for the XHTML Family

  For general information about this new W3C draft, please read the Cover Story "W3C HLink Working Draft Defines Hyperlink Markup Facility for XHTML Family".

  Basically, HLink is the XHTML working group's attempt to avoid using XLink syntax while still keeping the basic XLink linking model. HLink provides a mapping facility in order to support certain XHTML linking methods which cannot be accomplished using XLink's syntax. In addition, HLink slightly extends XLink's predefined semantic attributes with link behaviors required for XHTML.

• 16-Aug-2002: W3C releases new XPath 2.0 drafts

  On August 16th, W3C released a number of new XQuery-related drafts, among them three drafts about XPath 2.0:

  • W3C Working Draft WD-query-datamodel-20020816: XQuery 1.0 and XPath 2.0 Data Model
  • W3C Working Draft WD-xquery-operators-20020816: XQuery 1.0 and XPath 2.0 Functions and Operators
  • W3C Working Draft WD-xpath20-20020816: XML Path Language (XPath) 2.0

  For general information about the new W3C drafts, please read the Cover Story "W3C Working Groups Update Specifications for XSLT, XML Query, and XPath".

  The XPath 2.0 drafts show that XPath 2.0 will be much more powerful that XPath 1.0, the current version of XPath. In particular, XPath 2.0 extends the data model to include XML Schema type information, and changes the fundamental behavior of XPaths to primarily work with sequences rather than the node sets of XPath 1.0. Even though backwards compatibility of XPath 2.0 was a design goal of XPath 2.0, a number of incompatibilities do exist.

• 15-Jul-2002: W3C releases new XPointer drafts

  On July 10th, W3C released a number of new XPointer drafts. Replacing the now obsolete W3C Candidate Recommendation CR-xptr-20010911, the new drafts are separated according to the XPointer schemes they are defining:

  • W3C Working Draft WD-xptr-framework-20020710: XPointer Framework
  • W3C Working Draft WD-xptr-xpointer-20020710: XPointer xpointer() Scheme
  • W3C Working Draft WD-xptr-element-20020710: XPointer element() Scheme
  • W3C Working Draft WD-xptr-xmlns-20020710: XPointer xmlns() Scheme

  These new documents send XPointer back to Working Draft status. For a description of the new documents and some comments, please read the Cover Story "W3C Publishes Four Working Drafts for the XML Pointer Language (XPointer)".

  From John Cowan's comments about the new documents: "Because this is primarily a refactoring effort without any new semantics (except XML-Schema-compliant IDs), and only trivial changes to syntax, these documents will probably go straight from Last Call to Proposed Recommendation; the review period is only three weeks."

• W3C's official XLink area, the official Web page for XLink, XPointer and related standards, but only updated very rarely and not the best source of information.
• XLink Cover Pages, as with all of Robin Cover's pages, well maintained and frequently updated.
• On-Line Glossary for Web Technologies, a good source of information for searching for a particular technology or acronym and its relations to other Web technologies.

• Addison-Wesley's page for the book
• Amazon.com's page for the book (and here is Amazon.de's page for the book)
• Barnes and Noble's page for the book

• Page 87: In Figure 4.1, the "example" processing instruction item should be a child of the document item (rather than being a child of the "People" element item)
• Page 103: In Figure 5.2, the "example" processing instruction node should be a child of the root node (rather than being a child of the "People" element node)

Last modification: Monday, 12-Dec-2005 10:36:11 CET