- From: Kevin Marks via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Nov 2015 18:45:47 +0000
- To: public-annotation@w3.org
I'm not sure why arbitrary complexity is seen as a goal in itself. The point of fragmention is that it is a minimal extension of the fragment syntax to reference a multiword phrase. It solves a huge part of the 'referring to a subset of the page' problem. My fragmention plugin doesn't highlight anything with bengo's url as the text is not in the document, but my [fragmention to quote parser](http://www.unmung.com/?rawtext=https%3A%2F%2Fgithub.com%2Fw3c%2Fweb-annotation%2Fissues%2F110%23data%253Aapplication%2Fld%252Bjson%253B%257B%2522%2540context%2522%253A%2520%2522http%253A%2F%2Fwww.w3.org%2Fns%2Fanno.jsonld%2522%252C%2520%2522exact%2522%253A%2520%2522I%2520have%2520often%2520explained%2520the%2520purpose%2520of%2520the%2520selectors%2520as%2520a%2520mechanism%2520to%2520escape%2520the%2520need%2520to%2520define%2520a%2520fragment%2520syntax%252C%2520a%2520projection%2520to%2520a%2520single%2520string%252C%2520for%2520arbitrarily%2520complex%2520selections.%2522%252C%2520%2522%2540type%2522%253A%2520%2522TextQuoteSelector%2522%257D&maxurllength=0&embed=on#arbitrarily%20complex) makes sense of it -- GitHub Notification of comment by kevinmarks Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/110#issuecomment-159698499 using your GitHub account
Received on Wednesday, 25 November 2015 18:45:50 UTC