W3C home > Mailing lists > Public > public-bpwg-comments@w3.org > July to September 2008

RE: [CT-Guidelines LC] Fragment identifier in link alternate href (I)

From: JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>
Date: Mon, 04 Aug 2008 18:01:18 +0200
To: Julian Reschke <julian.reschke@gmx.de>
Cc: "public-bpwg-comments@w3.org" <public-bpwg-comments@w3.org>
Message-id: <93AA9E47B82F684A868C217766F48905374C6CCE3D@EXCLU2K7.hi.inet>

ok, perfect ! thanks for the clarification ...

If Francois can ammend my comment referencing RFC 3986 section 4.4 instead of RFC 1808 that would be great.

http://www.ietf.org/rfc/rfc3986.txt

Best Regards

-----Mensaje original-----
De: public-bpwg-comments-request@w3.org [mailto:public-bpwg-comments-request@w3.org] En nombre de Julian Reschke
Enviado el: lunes, 04 de agosto de 2008 17:51
Para: JOSE MANUEL CANTERA FONSECA
CC: public-bpwg-comments@w3.org
Asunto: Re: [CT-Guidelines LC] Fragment identifier in link alternate href (I)


JOSE MANUEL CANTERA FONSECA wrote:
> ...
> As per RFC 1808 an empty relative URI href="" resolves to complete base URL, so it is suggested to use this mechanism to point to the current resource
> ...

You really don't want to cite RFC 1808 anymore. It has been obsoleted by
RFC 3986 over three years ago.

BR, Julian
Received on Monday, 4 August 2008 16:02:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:50 UTC