On 10 Nov 2004, at 4:12 am, Tim Bray wrote:
On Nov 9, 2004, at 7:37 PM, Antone Roundy wrote:
'The value of "rel" MUST be either a name, which is non-empty and does not contain any colon (":") characters, or a URI [RFC2396bis, section 3].'
Are we going to allow relative URIs? Or shall we change that to:
'The value of "rel" MUST be either a name, which is non-empty and does not contain any colon (":") characters, or an absolute URI [RFC2396bis, section 4.3].'
Er, Ray is using the terminology carefully, and saying URI not URI reference, but it would be better to underline this and say "No relative URIs." -Tim
Erm, I thought when a name was used it was really a relative URI to the IANA base? Meaning that the value of rel is always a URI reference and never just a name? Thus resolving that reference ("related","./related","http://iana.etc/related","http://example.com/ extension",etc), would always give you the absolute URI of the relation. That's exactly what the processing model described does. Why not say so?
Graham
smime.p7s
Description: S/MIME cryptographic signature
