The XPointer content-type() Scheme
draft-stlaurent-content-type-frag-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Simon St.Laurent | ||
| Last updated | 2002-11-04 | ||
| 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
This document specifies a content-type() scheme for use in XPointer- based fragment identifiers. This scheme, like other XPointer Framework [12] schemes, is designed primarily for use with the XML Media Types defined in RFC 3023 [5], to identify locations within a given XML representation of a resource, though it may potentially be used to mix schemes for XML and non-XML representations. The content-type() scheme notifies an XPointer processor whether the creator of the XPointer intended for a particular pointer part to apply to a resource representation which uses a particular MIME content type identifier.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)