A generic fragment identifier syntax for URI references
draft-borden-frag-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jonathan Borden , Simon St.Laurent | ||
| Last updated | 2002-02-20 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
URI references with fragment identifiers uniquely identify parts of a document. Such identifiers have been specified as SGML/XML IDs e.g. in HTML [6]. The XPointer [2] specification is intended to serve as a fragment identifier syntax for XML documents. IDs conform to the XPointer 'raw name' form. Specifications constraining the behavior of user agents such as SMIL [8], XHTML [15], and SVG [10] have all supported this simple fragment naming convention though some extend it.
Authors
Jonathan Borden
Simon St.Laurent
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)