rfc: remove "revision specs"

[Nir Soffer]

On 31 Aug, 2005, at 1:36, Jan Hudec wrote:

> So *try* it if you don't believe. If you enter URL with fragment in 
> browser
> url-bar, the fragment will *not* become part of the request, so the web
> application does not have a chance to give it another meaning than 
> scrolling
> to an <a name="fragment"> tag. That's how fragments are defined in the 
> rfc
> and how they are meant to be.

Thats a good point, it is ignored :)

Strange that it is ignored when rfc talks about:

	The identified secondary resource may be some
       portion or subset of the primary resource, some view on 
representations of
       the primary resource, or some other resource defined or described 
by those
       representations.

Both last options are not possible when the fragment is not sent to the 
server.


Best Regards,

Nir Soffer