That would be Our Father, who art in heaven.
Which is to say, when you a URI that has #whatever on the end,
what #whatever means depends on what kind of thing it is. Up
till now, if it was just a chunk of text (text/plain in web-geek
lingo), it didn’t mean anything.
Now
it does. I have a special interest in this one.
The special interest isn’t that I actually particularly need to do this; in
fact, my first reaction to the draft was “Whatever for!?!?” but they had some
decent motivating use-cases.
Once I got past that I had a big problem with the draft I read. It had an
OK model of character/line addressing, as it still does. But it also had
addressing by regex match, and furthermore, you could combine all the different
selectors so as to point at a more or less arbitrary collection of
discontinuous chunks of text.
I wrote back “YAGNI.
Decent idea, but why not just slice it back to characters and lines and see if
that’ll do it?”
Some people who know me will be snickering at this point, because I am
notorious for advising everybody to slash their draft specs brutally.
It usually doesn’t work.
Well, for the first time ever in my entire career, after a couple of
back-and-forths with Erik and Martin, they said, basically, “OK”.
I owe them a beer next time I see them.
Hey there, browser guys, you might as well implement this one, how hard can
it be?