Re: Issue: fragment identifier for href attribute

[Murata Makoto <mura034@attglobal.net>]

Michael Fitzgerald wrote:

> This appears useful and appears to enhance modularity. With a fragment
> identifier, you could (apparently) retrieve only the part of the pattern you
> want, which would be nice especially if the pattern comes from a large file.

Certainly, your interpretation makes sense.  But it is different from 
what RFC 2396 says.  See below:

   When a URI reference is used to perform a retrieval action on the
   identified resource, the optional fragment identifier, separated from
   the URI by a crosshatch ("#") character, consists of additional
   reference information to be interpreted by the user agent after the
   retrieval action has been successfully completed.  As such, it is not
   part of a URI, but is often used in conjunction with a URI.

In my understanding, RELAX NG validators would handle fragment 
identifiers.

Michael Fitzgerald wrote:

> My question is, how would we identify fragments in RELAX NG patterns? With
> <xhtml:a>?

You only have to append "#" and then a fragment to an abstract URI.

> I would not be surprised to see XPointer support come along in due time
> (post-rec).

I would be surprised.

Cheers,

Makoto