[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3023 update (was Re: Agenda TAG Telcon: 8th Nov 2004)
On Fri, 19 Nov 2004 08:58:52 +0900
Martin Duerst <duerst@xxxxxx> wrote:
> Please publish a draft, so that everybody can look at it and comment.
http://www.ietf.org/internet-drafts/draft-murata-kohn-lilley-xml-00.txt
(published in July) already has a section for XPointer. It allows
a bare minimum.
Cheers,
Makoto
> 5. Fragment Identifiers
>
> Uniform Resource Identifiers (URIs) may contain fragement identifiers
> (see Section 3.5 of [RFC2396bis]). Likewise, Internationalized
> Resource Identifiers (IRIs) [IRI] may contain fragement identifiers.
>
> A family of specifications define fragment identifiers for XML media
> types. The fragment identifier syntax for application/xml is defined
> by two W3C Recommendations in this family, namely [XPointerFramework]
> and [XPointerElement]. Schemes other than the element scheme MUST
> NOT be specified as part of fragment identifiers for these media
> types. In particular, the xpointer scheme MUST NOT be specified
> since it is still at the W3C working draft stage.
>
> When an XML-based MIME media type follows the naming convention
> '+xml', the fragment identifier syntax for this media type SHALL
> include the fragment identifier syntax for application/xml and
> application/xml-external-parsed-entity. It MAY further allow other
> schemes such as the xmlns scheme and other schemes.
>
> If an XML-based media type requires a fragment identifier syntax
> other than XPointer, the media type SHOULD NOT follow the naming
> convention '+xml'.
>
> When a URI has a fragment identifier, it is encoded by a limited
> subset of the repertoire of US-ASCII [ASCII] characters, as defined
> in [RFC2396bis]. When a IRI contains a fragment identifier, it is
> encoded by a much wider repertoire of characters. The conversion
> between IRI fragment identifiers and URI fragment identifiers is
> presented in Section 7 of [IRI].
>
--
MURATA Makoto <murata@xxxxxxxxxxxxxxxxxxxx>