OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

relax-ng message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Issue: fragment identifier for href attribute

Message text written by Murata Makoto
James Clark wrote:

> Should we allow the value of the href attribute (on <include> and 
> <externalRef>) to contain a fragment identifier (ie a # character)?

I propose not to allow fragment identifiers.  RELAX Core does not.

If we use text/xml or application/xml, fragment identifiers are still 
unclear.  The RFC for XML media types, namely RFC 3023 (Propose Standard),
does not have any normative references.



What about an XPointer?   

I'm thinking of course that the parser may be actually hitting a JSP for
instance and
essentially passing it a parameter....


And what comes back to the parser is then determined by the remote


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC