Hello Stephen,
On 2012/06/12 20:08, Stephen Farrell wrote:
So would it work to add this:
"
Note that relative ni URIs can occur, for example as shown in
Figure 5. In such cases, user agents MUST construct the absolute URI
as they would in the case of an HTTP URL, that is, in the example
shown the absolute URI for "this third document" would be
"ni://example.com/sha-256-128;...".
This looks fine, except that it contains a MUST when it can just refer
to RFC 3986. So I would suggest the following text:
Note that relative ni URIs can occur. In such cases, the algorithm
in Section 5 of RFC 3986 applies. As an example, in Figure 5, the
absolute URI for "this third document" is
"ni://example.com/sha-256-128;...".
<html>
<head>
<title>ni: relative URI test</title>
<base href="ni://example.com">
</head>
<body>
<p>Please check<a href="sha-256;f4OxZX...">this document</a>.
And<a href="sha-256;UyaQV...">this other document</a>.
And<a href="sha-256-128;...">this third document</a>.
</p>
</body>
</html>
Figure 5: Example HTML with relative ni URI
"
Better suggestions welcome.
Ta,
I tried to look "Ta" up on the Web, but there were just too many
potential explanations. What are you using it for?
Regards, Martin.
S.