~ubuntu-branches/ubuntu/wily/phabricator/wily

This is a W3C Working Draft for review by W3C members and other interested parties. It is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". A list of current W3C working drafts can be found at <loc href="http://www.w3.org/TR">http://www.w3.org/TR</loc>.

<emph>Note:</emph> Since working drafts are subject to frequent change, you are advised to reference the above URI, rather than the URIs for working drafts themselves. Some of the work remaining is described in <specref ref="unfinished"/>.

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>.

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.

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.

</status>

This specification defines constructs that may be inserted into XML DTDs, schemas and document instances to describe links between objects. It uses XML syntax to create structures that can describe the simple unidirectional hyperlinks of today's HTML as well as more sophisticated links.

</abstract>

Burlington, Seekonk, et al.: World-Wide Web Consortium, XML Working Group, 1998.

</pubstmt>

Created in electronic form.

</sourcedesc>

<language id="en">English</language>

<language id="ebnf">Extended Backus-Naur Form (formal grammar)</language>

</langusage>

<slist>

<sitem>1997-01-15 : Skeleton draft by TB</sitem>

<sitem>1997-01-24 : Fleshed out by sjd</sitem>

<sitem>1997-04-08 : Substantive draft</sitem>

<sitem>1997-06-30 : Public draft</sitem>

<sitem>1997-08-01 : Public draft</sitem>

<sitem>1997-08-05 : Prose/organization work by sjd</sitem>

<sitem>1997-10-14: Conformance and design principles; a bit of cleanup by elm</sitem>

<sitem>1997-11-07: Update for editorial issues per issues doc, by sjd.</sitem>

<sitem>1997-12-01: Update for editorial issues per issues doc in preparation for F2F meeting, by sjd.</sitem>

<sitem>1998-01-13: Editorial cleanup, addition of new design principles, by elm.</sitem>

<sitem>1998-02-27: Splitting out of XLink and XPointer, by elm.</sitem>

<sitem>1998-03-03: Moved most of the XPointer locator stuff here. elm</sitem>

<sitem>1999-04-24: Editorial rewrites to represent new ideas on XLink, especially the inclusion of arcs. bent</sitem>

<sitem>1999-05-05: Prose/organization work by dorchard. Moved much of the semantics section around, from: locators, link semantics, remote resource semantics, local resource semantics; to: resource semantics, locators, behavior semantics, link semantics, arc semantics</sitem>

100

<sitem>1999-05-12: Prose/organization work. Re-organized some of the sections, removed XML constructs from the document, added descriptive prose, edited document text for clarity. Rewrote the link recognition section. bent</sitem>

101

<sitem>1999-05-17: Further prose work. Added non-normative examples. Clarified arcs. bent</sitem>

102

<sitem>1999-05-23: Edited for grammar and clarity. bent</sitem>

103

<sitem>1999-05-27: Final once-over before sending to group. Fixed sjd's email address. bent</sitem>

104

</slist>

105

</revisiondesc>

106

</header>

107

108

<body>

109

110

<head>Introduction</head>

111

This specification defines constructs that may be inserted into XML DTDs, schemas, and document instances to describe links between objects. A <termref def="dt-link">link</termref>, as the term is used here, is an explicit relationship between two or more data objects or portions of data objects. This specification is concerned with the syntax used to assert link existence and describe link characteristics. Implicit (unasserted) relationships, for example that of one word to the next or that of a word in a text to its entry in an on-line dictionary are obviously important, but outside its scope.

112

Links are asserted by <xtermref href="WD-xml-lang.html#dt-element">elements </xtermref> contained in <xtermref href="WD-xml-lang.html#dt-xml-doc">XML document instances</xtermref>. The simplest case is very like an HTML <code>A</code> link, and has these characteristics:

113

<ulist>

114

<item>The link is expressed at one of its ends (similar to the <code>A</code> element in some document)</item>

115

<item>Users can only initiate travel from that end to the other</item>

116

<item>The link's effect on windows, frames, go-back lists, stylesheets in use, and so on is mainly determined by browsers, not by the link itself. For example, traveral of <code>A</code> links normally replaces the current view, perhaps with a user option to open a new window.</item>

117

<item>The link goes to only one destination (although a server may have great freedom in finding or dynamically creating that destination).</item>

118

</ulist>

119

120

While this set of characteristics is already very powerful and obviously has proven itself highly useful and effective, each of these assumptions also limits the range of hypertext functionality. The linking model defined here provides ways to create links that go beyond each of these specific characteristics, thus providing features previously available mostly in dedicated hypermedia systems.

121

122

123

<div2>

124

<head>Origin and Goals</head>

125

Following is a summary of the design principles governing XLink:

126

<olist>

127

<item>XLink must be straightforwardly usable over the Internet. </item>

128

<item>XLink must be usable by a wide variety of link usage domains and classes of linking application software.</item>

129

<item>XLink must support HTML 4.0 linking constructs.</item>

130

<item>The XLink expression language must be XML.</item>

131

<item>The XLink design must be formal, concise, and illustrative.</item>

132

<item>XLinks must be human-readable and human-writable.</item>

133

<item>XLinks may reside within or outside the documents in which the

134

participating resources reside. </item>

135

<item>XLink must represent the abstract structure and significance of links.</item>

136

<item>XLink must be feasible to implement.</item>

137

<item>XLink must be informed by knowledge of established hypermedia systems and standards.</item>

138

</olist>

139

140

</div2>

141

<!--Changed the list of requirements to reflect current XLink requirements

142

document. bent-->

143

144

<div2>

145

<head>Relationship to Existing Standards</head>

146

Three standards have been especially influential:

147

<ulist>

148

<item><emph>HTML:</emph> Defines several SGML element types that represent links.</item>

149

<item><emph>HyTime:</emph> Defines inline and out-of-line link structures and some semantic features, including traversal control and presentation of objects.

150

</item>

151

<item><emph>Text Encoding Initiative Guidelines (TEI P3):</emph> Provides structures for creating links, aggregate objects, and link collections out of them.</item>

152

</ulist>

153

154

Many other linking systems have also informed this design, especially Dexter, FRESS, MicroCosm, and InterMedia.

155

</div2>

156

157

<div2>

158

<head>Terminology</head>

159

The following basic terms apply in this document. <!--<IMG

160

SRC="local://./linkdiag.gif">(figure to be inserted)-->

161

<glist>

162

<gitem>

163

164

<def>A symbolic representation of traversal behavior in links, especially the direction, context and timing of traversal.</def>

165

</gitem>

166

<gitem>

167

<label><termdef id="dt-eltree" term="Element Tree">element tree</termdef></label>

168

<def>A representation of the relevant structure specified by the tags and attributes in an XML document, based on "groves" as defined in the ISO DSSSL standard. </def>

169

</gitem>

170

<gitem>

171

<label><termdef id="dt-inline" term="In-Line Link">inline link</termdef></label>

172

<def>Abstractly, a <termref def="dt-link">link</termref> which serves as one of its own <termref def="dt-resource">resources</termref>. Concretely, a link where the content of the <termref def="dt-linkel">linking element</termref> serves as a <termref def="dt-particip-resource">participating resource</termref>.

173

HTML <code>A</code>, HyTime <code>clink</code>, and TEI <code>XREF</code>

174

are all inline links.</def>

175

</gitem>

176

<gitem>

177

178

<def>An explicit relationship between two or more data objects or portions of data objects.</def>

179

</gitem>

180

<gitem>

181

<label><termdef id="dt-linkel" term="Linking Element">linking element </termdef></label>

182

<def>An <xtermref href="WD-xml-lang.html#dt-element">element</xtermref> that asserts the existence and describes the characteristics of a <termref def="dt-link"> link</termref>.</def>

183

</gitem>

184

<gitem>

185

<label><termdef id="dt-local-resource" term="Local Resource">local resource</termdef></label>

186

<def>The content of an <termref def="dt-inline">inline</termref>linking element. Note that the content of the linking element could be explicitly pointed to by means of a regular <termref def="dt-locator">locator</termref> in the same linking element, in which case the resource is considered <termref def="dt-remote-resource"> remote</termref>, not local.</def>

187

</gitem>

188

<gitem>

189

<label><termdef id="dt-locator" term="Locator">locator</termdef> </label>

190

<def>Data, provided as part of a link, which identifies a

191

<termref def="dt-resource">resource</termref>.</def>

192

</gitem>

193

<gitem>

194

<label><termdef id="dt-multidir" term="Multi-Directional Link">multidirectional link</termdef></label>

195

<def>A <termref def="dt-link">link</termref> whose <termref def="dt-traversal"> traversal</termref> can be initiated from more than one of its <termref def="dt-particip-resource"> participating resources</termref>. Note that being able to "go back" after following a one-directional link does not make the link multidirectional.</def>

196

</gitem>

197

<gitem>

198

199

<def>A <termref def="dt-link">link</termref> whose content does not serve as one of the link's <termref def="dt-particip-resource">participating resources </termref>. Such links presuppose a notion like <termref def="dt-xlg">extended link groups</termref>, which instruct application software where to look for links. Out-of-line links are generally required for supporting multidirectional <termref def="dt-traversal">traversal</termref> and for allowing read-only resources to have outgoing links.</def>

200

</gitem>

201

<gitem>

202

<label><termdef id="dt-parsedq" term="Parsed">parsed</termdef></label> <def>In the context of link behavior, a parsed link is any link whose content is transcluded into the document where the link originated. The use of the term "parsed" directly refers to the concept in XML of a

203

parsed entity.</def>

204

</gitem>

205

<gitem>

206

<label><termdef id="dt-particip-resource" term="Participating Resource"> participating resource</termdef></label>

207

<def>A <termref def="dt-resource">resource</termref> that belongs to a link. All resources are potential contributors to a link; participating resources are the actual contributors to a particular link.</def>

208

</gitem>

209

<gitem>

210

<label><termdef id="dt-remote-resource" term="Remote Resource">remote resource</termdef></label>

211

<def>Any participating resource of a link that is pointed to with a locator. </def>

212

</gitem>

213

<gitem>

214

<label><termdef id="dt-resource" term="Resource">resource</termdef></label>

215

<def>In the abstract sense, an addressable unit of information or service that is participating in a <termref def="dt-link">link</termref>. Examples include files, images, documents, programs, and query results. Concretely, anything reachable by the use of a <termref def="dt-locator">locator</termref> in some <termref def="dt-linkel">linking element</termref>. Note that this term and its definition are taken from the basic specifications governing the World Wide Web.

216

</def>

217

</gitem>

218

<gitem>

219

<label><termdef id="dt-subresource" term="sub-Resource">sub-resource</termdef></label>

220

<def>A portion of a resource, pointed to as the precise destination of a link. As one example, a link might specify that an entire document be retrieved and displayed, but that some specific part(s) of it is the specific linked data, to be treated in an application-appropriate manner such as indication by highlighting, scrolling, etc.</def>

221

</gitem>

222

<gitem>

223

<label><termdef id="dt-traversal" term="Traversal">traversal</termdef></label>

224

<def>The action of using a <termref def="dt-link">link</termref>; that is, of accessing a <termref def="dt-resource">resource</termref>. Traversal may be initiated by a user action (for example, clicking on the displayed content of a <termref def="dt-linkel">linking element</termref>) or occur under program control.</def>

225

</gitem>

226

</glist>

227

228

</div2>

229

230

<div2>

231

<head>Notation</head>

232

The formal grammar for <termref def="dt-locator">locators</termref> is given using a simple Extended Backus-Naur Form (EBNF) location, as described in <xspecref href="http://www.w3.org/TR/REC-xml#sec-notation">the XML specification</xspecref>.

233

234

</div2>

235

</div1>

236

237

238

<head>Locator Syntax</head>

239

The locator for a <termref def="dt-resource">resource</termref> is typically provided by means of a Uniform Resource Identifier, or URI. XPointers can be used in conjunction with the URI structure, as fragment identifiers, to specify a more precise sub-resource.

240

241

A locator generally contains a URI, as described in IETF RFCs <bibref ref="rfc1738"/> and <bibref ref="rfc1808"/>. As these RFCs state, the URI may include a trailing <emph>query</emph> (marked by a leading "<code>?</code>"), and be followed by a "<code>#</code>" and a <emph>fragment identifier</emph>, with the query interpreted by the host providing the indicated resource, and the interpretation of the fragment identifier dependent on the data type of the indicated resource.

242

243

In order to locate XML documents and portions of documents, a locator value may contain either a <xtermref href="http://www.w3.org/Addressing/rfc1738.txt"> URI</xtermref> or a fragment identifier, or both. Any fragment identifier for pointing into XML must be an <xtermref href="http://www.w3.org/TR/WD-xptr#dt-xpointer"> XPointer</xtermref>.

244

Special syntax may be used to request the use of particular processing models in accessing the locator's resource. This is designed to reflect the realities of network operation, where it may or may not be desirable to exercise fine control over the distribution of work between local and remote processors.

245

246

<head>Locator</head>

247

248

<lhs>Locator</lhs>

249

250

<rhs>| <nt def="nt-connector">Connector</nt> (<xnt href="http://www.w3.org/TR/WD-xptr">XPointer</xnt> | <xnt href="WD-xml-lang.html#NT-Name">Name</xnt>)</rhs>

251

<rhs>| <nt def="nt-uri">URI</nt> <nt def="nt-connector">Connector</nt> (<xnt href="http://www.w3.org/TR/WD-xptr">XPointer</xnt> | <xnt href="WD-xml-lang.html#NT-Name">Name</xnt>)</rhs>

252

</prod>

253

254

<lhs>Connector</lhs><rhs>'#' | '|'</rhs>

255

</prod>

256

257

<lhs>URI</lhs><rhs><xnt href="WD-xml-lang.html#NT-URLchar">URIchar*</xnt></rhs>

258

</prod>

259

</scrap>

260

261

<termdef id="dt-designated" term="Designated Resource">In this discussion, the term <term>designated resource</term> refers to the resource which an entire locator serves to locate.</termdef> The following rules apply:

262

<ulist>

263

<item>

264

<termdef id="dt-containing-resource" term="Containing Resource"> The URI, if provided, locates a resource called the <term>containing resource</term>.</termdef>

265

</item>

266

<item>

267

If the URI is not provided, the containing resource is considered to be the document in which the linking element is contained.

268

</item>

269

<item>

270

<termdef id="dt-sub-resource" term="Sub-Resource">If an XPointer is provided, the designated resource is a <term>sub-resource</term>

271

of the containing resource; otherwise the designated resource is the

272

containing resource.</termdef>

273

</item>

274

<!--Is this now incorrect, given the nature of the switch from here() to origin()? -elm

275

Oy, yes, i think so. it will require some fun wording, though, so i haven't fixed it yet here -sjd-->

276

<item>

277

If the <nt def="nt-connector">Connector</nt> is followed directly by a <xnt href="http://www.w3.org/TR/REC-xml#NT-Name">Name</xnt>, the <xnt href="http://www.w3.org/TR/REC-xml#NT-Name">Name</xnt> is shorthand for the XPointer"<code>id(Name)</code>"; that is, the sub-resource is the element in the containing resource that has an XML <xtermref href="http://www.w3.org/TR/REC-xml#sec-attrtypes">ID attribute</xtermref> whose value <xtermref href="http://www.w3.org/TR/REC-xml#dt-match">matches</xtermref> the <xnt href="http://www.w3.org/TR/REC-xml#NT-Name">Name</xnt>. This shorthand is to encourage use of the robust <code>id</code> addressing mode.

278

</item>

279

280

<item>

281

If the connector is "<code>#</code>", this signals an intent that the containing resource is to be fetched as a whole from the host that provides it, and that the XPointer processing to extract the sub-resource

282

is to be performed on the client, that is to say on the same system where the linking element is recognized and processed.

283

</item>

284

<item>

285

If the connector is "<code>|</code>", no intent is signaled as to what processing model is to be used to go about accessing the designated resource.

286

</item>

287

</ulist>

288

289

Note that the definition of a URI includes an optional query component.

290

In the case where the URI contains a query (to be interpreted by the server), information providers and authors of server software are urged to use queries as follows:

291

292

<head>Query</head>

293

294

<lhs>Query</lhs><rhs>'XML-XPTR=' (<xnt href="http://www.w3.org/TR/WD-xptr"> XPointer</xnt> | <xnt href="http://www.w3.org/TR/REC-xml#NT-Name">Name</xnt>)</rhs>

295

</prod>

296

</scrap>

297

298

299

</div1>

300

301

302

<head>Link Recognition</head>

303

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.

304

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:

305

<eg><A xlink:type="simple" xlink:href="http://www.w3.org/TR/wd-xlink/"

306

xlink:title="The Xlink Working Draft">The XLink Working Draft.</A></eg>

307

<eg><xlink:simple href="http://www.w3.org/TR/wd-xlink/"

308

title="The XLink Working Draft">The XLink Working Draft</xlink:simple></eg>

309

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.

310

311

</div1>

312

313

314

<div1>

315

<head>Linking Attributes</head>

316

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.

317

318

319

<head>Locator Attributes</head>

320

The only locator attribute at this time is <code>href</code>. This attribute must contain either a string in the form of a URI that defines the remote resource being linked to, a string containing a fragment identifier that links to a local resource, or a string containing a URI with a fragment identifier concacenated onto it.

321

</div2>

322

323

324

<head>Arc Attributes</head>

325

Arcs contain two attributes, <code>from</code> and <code>to</code>. The <code>from</code> attribute may contain a string containing the content of a <code>role</code> attribute from the resource being linked from. The purpose of the <code>from</code> attribute is to define where this link is being actuated from.

326

The <code>to</code> attribute may contain a string containing the content of a <code>role</code> attribute from the resource being linked to. The purpose of the <code>to</code> attribute is to define where this link traverses to.

327

The application may use this information in a number of ways, especially in a complex hypertext system, but it is mainly useful in providing context for application behavior.

328

329

</div2>

330

331

332

<head>Behavior Attributes</head>

333

There are two attributes associated with behavior: <code>show</code> and <code>actuate</code>. The <code>show</code> attribute defines how the remote resource is to be revealed to the user. It has three options: <code>new</code>, <code>parsed</code>, and <code>replace</code>. The <code>new</code> option indicates that the remote resource should be shown in a new window (or other device context) without replacing the previous content. The <code>parsed</code> option, relating directly to the XML concept of a parsed entity, indicates that the content should be integrated into the document from which the link was actuated. The <code>replace</code> option is the one most commonly seen on the World Wide Web, where the document being linked from is entirely replaced by the object being linked to.

334

The <code>actuate</code> attribute defines how the link is initiated. It has two options: <code>user</code> and <code>auto</code>. The <code>user</code> option indicates that the link must be initiated by some sort of human-initiated selection, such as clicking on an HTML anchor. The <code>auto</code> option indicates that the link is automatically initiated when the application deems that the user has reached the link. It then follows the behavior set out in the <code>show</code> option.

335

336

</div2>

337

338

339

<head>Semantic Attributes</head>

340

There are two attributes associated with semantics, <code>role</code> and <code>title</code>. The <code>role</code> attribute is a generic string used to describe the function of the link's content. For example, a poem might have a link with a <code>role="stanza"</code>. The <code>role</code> is also used as an identifier for the <code>from</code> and <code>to</code> attributes of arcs.

341

The <code>title</code> attribute is designed to provide human-readable text describing the link. It is very useful for those who have text-based applications, whether that be due to a constricted device that cannot display the link's content, or if it's being read by an application to a visually-impaired user, or if it's being used to create a table of links. The <code>title</code> attribute contains a simple, descriptive string.

342

</div2>

343

</div1>

344

345

346

<head>Linking Elements</head>

347

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.

348

The <code>simple</code> link is used to declare a link that approximates the functionality of the HTML <code>A</code> element. It has, however, a few added features to increase its value, including the potential declaration of semantics and behavior. The <code>locator</code> elements are used to define the resource being linked to. Some links may contain multiple locators, representing a choice of potential links to be traversed. The <code>arcs</code> are used to define the traversal semantics of the link. Finally, an <code>extended</code> linking element differs from a simple link in that it can connect any number of resources, not just one local resource (optionally) and one remote resource, and in that extended links are more often out-of-line than simple links.

349

350

351

<head>Simple Links</head>

352

<termdef id="dt-simpleline" term="Simple Link"><term>Simple links</term> can be used for purposes that approximate the functionality of a basic HTML <code>A</code> link, but they can also support a limited amount of additional functionality. Simple links have only one locator and thus, for convenience, combine the functions of a linking element and a locator into a single element.</termdef> As a result of this combination, the simple linking element offers both a locator attribute and all the behavior and semantic attributes.

353

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.

354

355

<!ATTLIST xlink:slink

356

href CDATA #REQUIRED

357

role CDATA #IMPLIED

358

title CDATA #IMPLIED

359

show (new|parsed|replace) "replace"

360

actuate (user|auto) "user"

361

></eg>

362

And here is how to make an arbitrary element into a simple link.

363

364

<!ATTLIST foo

365

xlink:type (simple|extended|locator|arc) #FIXED "simple"

366

xlink:href CDATA #REQUIRED

367

xlink:role CDATA #IMPLIED

368

xlink:title CDATA #IMPLIED

369

xlink:show (new|parsed|replace) "replace"

370

xlink:actuate (user|auto) "user"

371

></eg>

372

Here is how the first example might look in a document:

373

<eg><xlink:simple href="http://www.w3.org/TR/wd-xlink" role="working draft"

374

title="The XLink Working Draft" show="replace" actuate="user">

375

The XLink Working Draft.</xlink:simple></eg>

376

<eg><foo xlink:href="http://www.w3.org/TR/wd-xlink" xlink:role="working draft"

377

xlink:title="The XLink Working Draft" xlink:show="new" xlink:actuate="user">

378

The XLink Working Draft.</foo></eg>

379

Alternately, a simple link could be as terse as this:

380

<eg><foo xlink:href="#stanza1">The First Stanza.</foo></eg>

381

382

383

There are no constraints on the contents of a simple linking element. In

384

the sample declaration above, it is given a content model of <code>ANY</code>

385

to illustrate that any content model or declared content is acceptable. In

386

a valid document, every element that is significant to XLink must still conform

387

to the constraints expressed in its governing DTD.

388

Note that it is meaningful to have an out-of-line simple link, although

389

such links are uncommon. They are called "one-ended" and are typically used

390

to associate discrete semantic properties with locations. The properties might

391

be expressed by attributes on the link, the link's element type name, or in

392

some other way, and are not considered full-fledged resources of the link.

393

Most out-of-line links are extended links, as these have a far wider range

394

of uses.

395

</div2>

396

397

398

<head>Extended Links</head>

399

<termdef id="dt-extendedlink" term="Extended Link">An <term>extended link</term> differs from a simple link in that it can connect any number of resources, not just one local resource (optionally) and one remote resource, and in that extended links are more often out-of-line than simple links.</termdef>

400

These additional capabilities of extended links are required for:

401

<ulist>

402

<item>

403

Enabling outgoing links in documents that cannot be modified to add an inline link

404

</item>

405

<item>

406

Creating links to and from resources in formats with no native support for embedded links (such as most multimedia formats)

407

</item>

408

<item>

409

Applying and filtering sets of relevant links on demand

410

</item>

411

<item>Enabling other advanced hypermedia capabilities</item>

412

</ulist>

413

414

Application software might be expected to provide traversal among all of a link's participating resources (subject to semantic constraints outside the scope of this specification) and to signal the fact that a given resource or sub-resource participates in one or more links when it is displayed (even though there is no markup at exactly that point to signal it).

415

A linking element for an extended link contains a series of <xtermref href="http://www.w3.org/TR/REC-xml/#dt-parentchild">child elements</xtermref> that serve as locators and arcs. Because an extended link can have more than one remote resource, it separates out linking itself from the mechanisms used to locate each resource (whereas a simple link combines the two).

416

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.

417

However, when a linking element within an extended link has a <code>show</code> or <code>actuate</code> attribute of its own, that attribute overrides the defaults set on the extended linking element.

418

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

420

421

<!ATTLIST xlink:extended

422

role CDATA #IMPLIED

423

title CDATA #IMPLIED

424

showdefault (new|parsed|replace) #IMPLIED

425

actuatedefault (user|auto) #IMPLIED ></eg>

426

427

The second is an example of an arbitrary element being used an extended link:

428

429

430

<!ATTLIST foo

431

xlink:type (simple|extended|locator|arc) #FIXED "extended"

432

xlink:role CDATA #IMPLIED

433

xlink:title CDATA #IMPLIED

434

xlink:showdefault (new|parsed|replace) #IMPLIED

435

xlink:actuatedefault (user|auto) #IMPLIED ></eg>

436

437

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

439

440

441

And the second shows how the link might appear, using an arbitrary element:

442

443

444

445

446

</div2>

447

448

449

<head>Arc Elements</head>

450

<termdef id="dt-arc" term="Arc">An <term>arc</term> is contained within an extended link for the purpose of defining traversal behavior.</termdef> More than one arc may be associated with a link. Otherwise, arc elements function exactly as the arc attributes might lead on to expect.

451

452

</div2>

453

454

</div1>

455

<div1>

456

<head>Conformance</head>

457

An element conforms to XLink if: <olist>

458

<item>The element has an <code>xml:link</code> attribute whose value is

459

one of the attribute values prescribed by this specification, and</item>

460

<item>the element and all of its attributes and content adhere to the

461

syntactic

462

requirements imposed by the chosen <code>xml:link</code> attribute value,

463

as prescribed in this specification.</item>

464

</olist>

465

Note that conformance is assessed at the level of individual elements,

466

rather than whole XML documents, because XLink and non-XLink linking mechanisms

467

may be used side by side in any one document.

468

An application conforms to XLink if it interprets XLink-conforming elements

469

according to all required semantics prescribed by this specification and,

470

for any optional semantics it chooses to support, supports them in the way

471

prescribed. <!--If/when we split out the XLinkfunctionality

472

(e.g. inline links and out-of-line links), the

473

conformance language will have to address the different

474

levels of support. -elm-->

475

</div1>

476

</body><back>

477

478

<head>Unfinished Work</head>

479

<div2>

480

<head>Structured Titles</head>

481

The simple title mechanism described in this draft is insufficient to cope

482

with internationalization or the use of multimedia in link titles. A future

483

version will provide a mechanism for the use of structured link titles.

484

</div2>

485

</div1>

486

<div1>

487

<head>References</head>

488

<blist>

489

<bibl id="xptr" key="XPTR">Eve Maler and Steve DeRose, editors. <titleref>

490

XML Pointer Language (XPointer) V1.0</titleref>. ArborText, Inso, and Brown

491

University. Burlington, Seekonk, et al.: World Wide Web Consortium, 1998.

492

(See <loc href="http://www.w3.org/TR/WD-xptr">http://www.w3.org/TR/WD-xptr

493

</loc>.)</bibl>

494

<bibl id="iso10744" key="ISO/IEC 10744">ISO (International Organization for

495

Standardization). <titleref>ISO/IEC 10744-1992 (E). Information technology

496

- Hypermedia/Time-based Structuring Language (HyTime).</titleref> [Geneva]:

497

International Organization for Standardization, 1992. <titleref>Extended

498

Facilities

499

Annex.</titleref> [Geneva]: International Organization for Standardization,

500

1996. (See <loc

501

href="http://www.ornl.gov/sgml/wg8/hytime/html/is10744r.html">http://www.ornl.go

502

v/sgml/wg8/hytime/html/is10744r.html </loc> <!--p m-r says this link is

503

broken. elm --> ).</bibl>

504

<bibl id="rfc1738" key="IETF RFC 1738">IETF (Internet Engineering Task

505

Force). <titleref>

506

RFC 1738: Uniform Resource Locators</titleref>. 1991. (See <loc

507

href="http://www.w3.org/Addressing/rfc1738.txt">

508

http://www.w3.org/Addressing/rfc1738.txt</loc>).</bibl>

509

<bibl id="rfc1808" key="IETF RFC 1808">IETF (Internet Engineering Task

510

Force). <titleref>

511

RFC 1808: Relative Uniform Resource Locators</titleref>. 1995. (See <loc

512

href="http://www.w3.org/Addressing/rfc1808.txt">http://www.w3.org/Addressing/rfc

513

1808.txt </loc>).</bibl>

514

<bibl id="tei" key="TEI">C. M. Sperberg-McQueen and Lou Burnard, editors.

515

516

Guidelines for Electronic Text Encoding and Interchange</titleref>. Association

517

for Computers and the Humanities (ACH), Association for Computational

518

Linguistics

519

(ACL), and Association for Literary and Linguistic Computing (ALLC). Chicago,

520

Oxford: Text Encoding Initiative, 1994.  </bibl>

521

<bibl id="chum" key="CHUM">]Steven J. DeRose and David G. Durand. 1995. "The

522

TEI Hypertext Guidelines." In <titleref>Computing and the Humanities

523

</titleref>29(3).

524

Reprinted in <titleref>Text Encoding Initiative: Background and

525

Context</titleref>,

526

ed. Nancy Ide and Jean ronis , ISBN 0-7923-3704-2. </bibl>

527

</blist></div1>

528

</back></spec>

529

<?Pub *0000052575?>

530

~~~~~~~~~~