The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this specification are to be interpreted as described in .

Some special terms are defined here in order to clarify their relationship to similar terms used in the technologies on which the mapping is based. Refer to and for definitions of other technical terms used here.

The xlink: and rdf: prefixes are used throughout to stand for the declaration of the XLink and RDF namespaces, respectively, on elements in whose scope the so-marked element or attribute appears (on the same element or on some ancestor element), whether or not a namespace declaration is present in the example. The use of specific namespace prefixes is an editorial convienience; as dictated by the Names in XML Recommendation , any prefix may be used as long as the URI it maps to is the correct one.

RDF is based on the use of URIs for identifying resources. In XLink, the linking element itself (in the case of a simple link) or a subelement of the linking element (in the case of an extended link) often serves as one of the participating resources in the link. This requires that we be able to define URI references that identify those linking elements. Those URI references must follow the XPointer specification.

Any legal XPointer that identifies the proper element is allowed. However, in order that different implementations harvest equivalent RDF statements from an XLink, the procedure in this section should be used when synthesizing XPointers for such linking elements. The general approach recommended is for the synthesized XPointer to do element-wise navigation down the tree to reach the linking element. The navigation begins at the nearest identified point in the tree.

More formally, the base of the synthesized URI reference shall be specified as defined in .

The fragment identifier of the synthesized URI reference shall be delimited from the URI by the '#' character, as required by RFC 2396. The fragment identifier of the synthesized URI reference shall be an XPointer.

The XPointer should follow the production: Recommended Syntax for Synthesized XPointers XPointer ::= Name | ChildSeq ChildSeq ::= '/' [1-9] [0-9]* ('/' [1-9] [0-9]*)* | Name ('/' [1-9] [0-9]*)+

This is an edited version of the ChildSeq production, assuming that the production is updated in line with recent working group discussions. In the case of any differences between this document and the final XPointer specification, the XPointer specification's definition of ChildSeq should be followed.

The initial locator term of the XPointer should be an ID reference to the nearest ancestor of the linking element, including the linking element itself, that bears an attribute of type ID. If no such attribute exists on any ancestor of the linking element, the '/' character should be the first linking term, indicating that navigation proceeds from the document element.

As an example, consider a document that contains the following simple link:

The synthesized XPointer for this linking element is:

Unless stated otherwise, RDF statements are generated to represent the information for the arcs in a link. The value of the xlink:arcrole attribute, if one is given on an arc-type element or simple-type element, must be mapped to the predicate of the RDF statement. Note that the value of the xlink:arcrole attribute is already required, by the XLink specification, to be a URI reference.

If no xlink:arcrole attribute is specified, harvesting software should not generate an RDF statement. That is certainly the safest course. However, many XML files may not have arcrole attributes. Implementations that wish to attempt to harvest RDF statements from such files may map the element type of the linking element to the predicate of the RDF statement, as long as the element type is namespace qualified. This ensures that an an absolute URI reference can be constructed from the namespace URI and the local part. In this case the namespace name and the local part are concatenated to synthesize the absolute URI reference for the predicate. Implementations should examine the namespace URI to test if it ends in one of the URI characters '#', '?', or '/'. If it does then the namespace URI and the local part shall be concatenated using the simple approach documented in . If the namespace URI does not end in such a character, implementations may create a URI reference by inserting a '#' character. Note however that such URI references must not be exchanged with external parties, as they are not guaranteed to actually exist.

If a simple link's xlink:arcrole attribute has the value http://www.w3.org/1999/xlink/properties/linkbase, the link shall be harvested according to section . Otherwise the mapping defined in this section shall be used.

All simple links define zero or one traversal arcs. No traversal arc is specified if the xlink:href attribute is not specified. Therefore, harvesting software shall not generate an RDF statements if there is no xlink:href attribute in the link.

The starting resource of the simple link shall be mapped to the subject of the RDF statement. Note that the starting resource of a simple link is the linking element itself. Therefore, the harvesting software must create a URI reference that identifies the linking element, as defined in section .

The predicate of the RDF statement is obtained from the simple Link as defined in .

The ending resource of the simple link shall be mapped to the object of the RDF statement. Note that the ending resource of a simple link is always a URI reference, provided as the value of the xlink:href attribute.

If an xlink:role attribute is specified on the simple link, it shall result in an additional statement being added to the model. The subject of the statement is the ending resource of the simple link, its predicate is rdf:type, and its object is the resource identified by the role attribute.

If an implementation wishes to use facilities defined in the RDF Schema specification , it may add a second statement to the RDF model when an xlink:role attribute is specified. The subject of the second statement is the resource identified by the role attribute, its predicate is rdf:type, and its object is the resource rdfs:Class. The second statement should only be added to the model if an equivalent statement is not already part of the model.

An example of a simple linking element is:

Mapping that link according to this specification (and assuming it was the fourth child element within the third child element of the document) results in the RDF model shown below:

We first describe the rules for harvesting the components of an extended link (arcs, locators, and resources). Then we describe the rules for the extended link as a whole.

A linkbase is an XML document which functions like a database of links. A linkbase arc is an XLink element (simple- or arc-type) whose xlink:arcrole attribute takes the value of http://www.w3.org/1999/xlink/properties/linkbase. The ending resource of a linkbase arc is a linkbase.

When harvesting software encounters a linkbase arc, it shall not generate an RDF statement for the arc. It should traverse the arc to retrieve the linkbase, and harvest the links from the linkbase to add to the current model using the methods specified in this Note.