Pointing Syd Bauman WARNING: XInclude processing failed — this file should not be copied or used (and is invalid) as a result.

Based on the Stanford version, but trimmed down a lot

 Put XInclude back in (taking it from uvic2006, I think) Trim down by removing inclusions and the details that really are about auto-generating text automatically converted from presentation.odd conforming to yaps.odd conforming using p2y.xslt and p2y.perl Added clarifying words Updated from xref only to pointing and XPointer
Pointing <castList> <castItem type="role"> <role xml:id="CK">Clark Kent</role> <roleDesc>Mild-mannered reporter for a great metropolitan newspaper</roleDesc> </castItem> </castList> <!-- ... --> <sp who="#CK"> <speaker>Clrk.</speaker> <p>I don't know Lois, I must have fainted.</p> </sp>

When one XML element formally refers to another XML element, we say the one element points to the other

This is done through an attribute: the value of a pointer attribute is a URI that resolves to an XML element or other resource.
In XHTML The a element's href attribute points to another a element via its name attribute. The img element's src attribute points to a graphics file, e.g. a JPEG or PNG. <a href="#duck"> <a href="http://www.quack.com/fowl.html#duck"> <img src="http://bauman.zapto.org/gallery/commencement2005/2005_05_29t133624" alt="Julia gets her PhD">

Note that the img tag is a start-tag, not an emtpy-element-tag. That is on purpose. In a slide like this I am only showing the start-tag, because the point of discussion in the attributes. I didn't show the content or end-tag of the a elements either.
In TEI Any element may be identified by its xml:id attribute. Many elements have a variety of attributes that point for a variety of reasons. E.g.:who of sp indicates which character is speakingsameAs of any element indicates it is the same as another <l xml:id="jj17.423">I love rock n' roll</l> <l>So put another dime in the jukebox, baby</l> <l sameAs="#jj17.423">I love rock n' roll</l> <l>So come an' take your time an' dance with me</l> target for cross-references, or to indicate where a note is attached
Relative or Absolute URI

Just as in XHTML: a complete URI, including protocol (e.g. http://www.wwp.brown.edu/texts/index.html)relative to the pointing element's base URI, which is often the current document (e.g. #appendix2)

Simple Pointing Elements

Two elements, ptr and ref are used for this task. The only difference is that ptr must be an empty element, whereas ref may have content.

provides both pointer and text (the style-sheet or other processor may ignore the text, of course); an example of referring to a web accessible XML file: For some context, see <ref target="http://www.example.com/extreme2004closing.xml">the introduction</ref>. provides only the pointer; the style-sheet or other processor has to generate text (or sound or whatever); an example of pointing to a local element (via its xml:id): See <ptr target="#chap08"/>.
Inclusion

Take the contents of one file (the target, source, or included file) and include them as part of another (the driver or including file).

Reasons file management dynamically generate driver file from various source files boilerplate text reproduce without actually copying & pasting (e.g., for web critic) stand-off markup
Mechanism P5 uses W3C's XInclude mechanism declare namespace on including element or ancestor: <TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:xi="http://www.w3.org/2001/XInclude"> use inclusion element: <xi:include href="http://www.here/it/is.xml"/> an xinclude processor reads in the driver file and replaces each xi:include with the element it points at
Consequences

The driver TEI file should be well-formed, but will not typically be valid before xinclude processing.

Many XML software products, including xmllint and oXygen, will perform xinclude processing immediately before validation The TEI schemas can be customized to permit xi:include in a particular places in the hierarchy