I would like to call your attention to: http://ietf.org/internet-drafts/draft-borden-frag-00.txt This has the potential to define a simplified XPointer. Let me clarify a few points. The intention is to define a generic fragment identifier _syntax_: 1) bare names 2) numeric 3) scheme based Note the symmetry with XPointer :-) A feature of this standardization is that new syntaxes for fragment identifiers would use the scheme based extensibility mechanism. There remains a requirement to define the syntax -> semantic mapping on a media type by media type basis e.g. it is not the intention to define what: #foo or #/12345 is intended to identify within an arbitrary media type. Furthermore each media type registration might define _its own subset_ of the general syntax. That is to say: application/xml may define the entire XPointer syntax application/foo+xml may restrict fragments to bare names audio/foo may restrict fragments to numeric etc. JonathanReceived on Saturday, 23 February 2002 05:28:16 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:39:43 GMT