Re: [web-annotation] Make Selectors available for the wide world?

Re (3) above. I have contacted Liam Quin and Carine Bournez (both in 
the XML Activity) to find out about the status and the usability of 
the XPointer Framework and pointer schemes (see [1],[2],[3] below). 
Here is the summary of their answers:

- The framework is formally defined for XML. Ie, if we defined a 
`#selector(…)` scheme for HTML5, that would be, strictly speaking, not
 conform to the standard. (Fragment id-s are bound to media types.) 
Any fragment ID for HTML5 should be cleared with the Web Platform WG 
and/or IANA.
- It is unclear whether browser would ever implement this as a whole. 
It may be possible, however, to write some sort of a Javascript 
library/polyfill to implement this; after all, the various bits and 
pieces in the selector mechanism are simply combination of existing 
selector mechanisms like CSS or XPATH. (The implementation that, e.g.,
 Hypothes.is may have could be reused accordingly.)

Nevertheless, this is not a very pretty picture… in other words, there
 is no really suitable story to add additional fragment id-s to HTML5.
 This may have to be taken up with the TAG or the Web Platform WG.


1. http://www.w3.org/TR/xptr-framework/
2. http://www.w3.org/2005/04/xpointer-schemes/
3. http://www.w3.org/TR/xptr-xpointer/


-- 
GitHub Notification of comment by iherman
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/110#issuecomment-158280414
 using your GitHub account

Received on Friday, 20 November 2015 05:01:48 UTC