Lines Matching full:xlink
15 <title>XML Linking Language (XLink)</title>
17 <w3c-designation><!-- &doc-type;-&iso6.doc.date; --> WD-xlink-19990527</w3c-designation>
23 <publoc><loc href="http://www.w3.org/XML/Group/1999/05/WD-xlink-current">http://www.w3.org/XML/Group/1999/05/WD-xlink-current</loc></publoc>
26 <loc href="http://www.w3.org/XML/Group/1999/05/WD-xlink-19990527">http://www.w3.org/XML/Group/1999/05/WD-xlink-19990527</loc>
27 <loc href="http://www.w3.org/XML/Group/1999/05/WD-xlink-19990505">http://www.w3.org/XML/Group/1999/05/WD-xlink-19990505</loc>
28 <loc href="http://www.w3.org/TR/1998/WD-xlink-19980303">http://www.w3.org/TR/1998/WD-xlink-19980303</loc>
59 <p>This work is part of the W3C XML Activity (for current status, see <loc href="http://www.w3.org/MarkUp/SGML/Activity">http://www.w3.org/XML/Activity </loc>). For information about the XPointer language which is expected to be used with XLink, see <loc href="http://www.w3.org/MarkUp/SGML/Activity">http://www.w3.org/TR/WD-xptr</loc>.
61 <p>See <loc href="http://www.w3.org/TR/NOTE-xlink-principles">http://www.w3.org/TR/NOTE-xlink-principles </loc> for additional background on the design principles informing XLink.</p>
62 <p>Also see <loc href="http://www.w3.org/TR/NOTE-xlink-req/">http://www.w3.org/TR/NOTE-xlink-req/</loc> for the XLink requirements that this document attempts to satisfy.</p>
95 <sitem>1998-02-27: Splitting out of XLink and XPointer, by elm.</sitem>
97 <sitem>1999-04-24: Editorial rewrites to represent new ideas on XLink, especially the inclusion of arcs. bent</sitem>
124 <p>Following is a summary of the design principles governing XLink:
126 <item><p>XLink must be straightforwardly usable over the Internet. </p></item>
127 <item><p>XLink must be usable by a wide variety of link usage domains and classes of linking application software.</p></item>
128 <item><p>XLink must support HTML 4.0 linking constructs.</p></item>
129 <item><p>The XLink expression language must be XML.</p></item>
130 <item><p>The XLink design must be formal, concise, and illustrative.</p></item>
134 <item><p>XLink must represent the abstract structure and significance of links.</p></item>
135 <item><p>XLink must be feasible to implement.</p></item>
136 <item><p>XLink must be informed by knowledge of established hypermedia systems and standards.</p></item>
140 <!--Changed the list of requirements to reflect current XLink requirements
302 <p>The existence of a <termref def="dt-link">link</termref> is asserted by a <termref def="dt-linkel">linking element</termref>. Linking elements must be recognized reliably by application software in order to provide appropriate display and behavior. There are several ways link recognition could be accomplished: for example, reserving element type names, reserving attributes names, leaving the matter of recognition entirely up to stylesheets and application software, or using the XLink <xtermref href="http://www.w3.org/TR/REC-xml-names/">namespace</xtermref> to specify element names and attribute names that would be recognized by namespace and XLink-aware processors. Using element and attribute names within the XLink namespace provides a balance between giving users control of their own markup language design and keeping the identification of linking elements simple and unambiguous.</p>
303 <p>The two approaches to identifying linking elements are relatively simple to implement. For example, here's how the HTML <code>A</code> element would be declared using attributes within the XLink namespace, and then how an element within the XLink namespace might do the same:
304 <eg><A xlink:type="simple" xlink:href="http://www.w3.org/TR/wd-xlink/"
305 xlink:title="The Xlink Working Draft">The XLink Working Draft.</A></eg>
306 <eg><xlink:simple href="http://www.w3.org/TR/wd-xlink/"
307 title="The XLink Working Draft">The XLink Working Draft</xlink:simple></eg>
308 Any arbitrary element can be made into an XLink by using the <code>xlink:type</code> attribute. And, of course, the explicit XLink elements may be used, as well. This document will go on to describe the linking attributes that are associated with linking elements. It may be assumed by the reader that these attributes would require the <code>xlink</code> namespace prefix if they existed within an arbitrary element, or that they may be used directly if they exist within an explicit Xlink element.</p>
315 <p>XLink has several attributes associated with the variety of links it may represent. These attributes define four main concepts: locators, arcs, behaviors, and semantics. <emph>Locators</emph> define where the actual resource is located. <emph>Arcs</emph> define the traversal of links. Where does the link come from? Where does it go to? All this information can be stored in the arc attributes. <emph>Behaviors</emph> define how the link is activated, and what the application should do with the resource being linked to. <emph>Semantics</emph> define useful information that the application may use, and enables the link for such specalized targets as constricted devices and accessibility software.</p>
346 <p>There are several kinds of linking elements in XLink: <code>simple</code> links, <code>locators</code>, <code>arcs</code>, and <code>extended</code> links. These elements may be instantiated via element declarations from the XLink namespace, or they may be instantiated via attribute declarations from the XLink namespace. Both kinds of instantiation are described in the definition of each linking element.</p>
352 <p>The following are two examples of linking elements, each showing all the possible attributes that can be associated with a simple link. Here is the explicit XLink simple linking element.
353 <eg><!ELEMENT xlink:simple ANY>
354 <!ATTLIST xlink:slink
362 <eg><!ELEMENT xlink:simple ANY>
364 xlink:type (simple|extended|locator|arc) #FIXED "simple"
365 xlink:href CDATA #REQUIRED
366 xlink:role CDATA #IMPLIED
367 xlink:title CDATA #IMPLIED
368 xlink:show (new|parsed|replace) "replace"
369 xlink:actuate (user|auto) "user"
372 <eg><xlink:simple href="http://www.w3.org/TR/wd-xlink" role="working draft"
373 title="The XLink Working Draft" show="replace" actuate="user">
374 The XLink Working Draft.</xlink:simple></eg>
375 <eg><foo xlink:href="http://www.w3.org/TR/wd-xlink" xlink:role="working draft"
376 xlink:title="The XLink Working Draft" xlink:show="new" xlink:actuate="user">
377 The XLink Working Draft.</foo></eg>
379 <eg><foo xlink:href="#stanza1">The First Stanza.</foo></eg>
385 a valid document, every element that is significant to XLink must still conform
415 <p>The <code>xlink:type</code> attribute value for an extended link must be <code> extended</code>, if the link is being instantiated on an arbitrary element. Note that extended links introduce variants of the <code>show</code> and <code>actuate</code> behavior attributes. These attributes, the <code>showdefault</code> and <code>actuatedefault</code> define the same behavior as their counterparts. However, in this case, they are considered to define the default behavior for all the linking elements that they contain.</p>
417 <p>The extended linking element itself retains those attributes relevant to the link as a whole, and to its local resource if any. Following are two sample declaration for an extended link. The first is an example of the explicit XLink extended link:
419 <eg><!ELEMENT xlink:extended ((xlink:arc | xlink:locator)*)>
420 <!ATTLIST xlink:extended
428 <eg><!ELEMENT foo ((xlink:arc | xlink:locator)*)>
430 xlink:type (simple|extended|locator|arc) #FIXED "extended"
431 xlink:role CDATA #IMPLIED
432 xlink:title CDATA #IMPLIED
433 xlink:showdefault (new|parsed|replace) #IMPLIED
434 xlink:actuatedefault (user|auto) #IMPLIED ></eg>
436 The following two examples demonstrate how each of the above might appear within a document instance. Note that the content of these examples would be other elements. For brevity's sake, they've been left blank. The first example shows how the link might appear, using an explicit XLink extended link:
438 <eg><xlink:extended role="address book" title="Ben's Address Book" showdefault="replace" actuatedefault="user"> ... </xlink:extended></eg>
442 <eg><foo xlink:type="extended" xlink:role="address book" xlink:title="Ben's Address Book" xlink:showdefault="replace" xlink:actuatedefault="user"> ... </foo></eg>
447 <div2 id="xlink-arcs">
456 <p>An element conforms to XLink if: <olist>
465 rather than whole XML documents, because XLink and non-XLink linking mechanisms
467 <p>An application conforms to XLink if it interprets XLink-conforming elements
