uri@w3.org from February 2004 by subject

":" in pchar twice in latest draft

"Relative URI" or "Relative URI Reference"?

#foo URI references

2396bis and the "/" char

ALPHA / DIGIT vs alphanum

Calculating relative URIs

Canonical Form of URIs "/" and IRIs

Comments on draft-fielding-uri-rfc2396bis-0x

Concern with URI normalization text; proposed change

defaults and equivalence, same-document references

definition of "character"

delimiters vs separators


draft-fielding-uri-rfc2396bis-03, section 1 and 2

draft-fielding-uri-rfc2396bis-03, section 3

draft-fielding-uri-rfc2396bis-03, section 6

draft-fielding-uri-rfc2396bis-03, section 7


Editorial comments on draft-fielding-uri-rfc2396bis-03

encoding related phrasing

feedback on draft-fielding-uri-rfc2396bis-03.txt

fragment prose proposal

FYI. Was: userinfo allowed in http URI or not?

Haskell URI handling; source code available

Host header

Host header (was uri handling of hosts is too restrictive)

Http and RFC-2396

I-D ACTION:draft-black-snmp-uri-02.txt

Just checking: pct-encoded in IPvFuture?


More test cases to be confirmed

non-hierarchical URIs and square brackets

Relative URI resolution test cases?

remove_dot_segment in draft-fielding-uri-rfc2396bis-03.txt

Removing null authority

Review of IETF netann Draft

RFC 2396bis draft 04 typo

RFC2396, parsing 'authority' and 'host'

RFC2396bis - implementation results using revised syntax

rfc2396bis, section 7.6, typo

Section 3.5. Passing fragment identifiers to other systems.

simplifying URI path production

SNMP URI and 2396bis

Status of draft-hoffman-rfc1738bis-01.txt

URI Generic Syntax doc (draft-fielding-uri-rfc2396bis-03)

uri handling of hosts is too restrictive

userinfo allowed in http URI or not?


Last message date: Sunday, 29 February 2004 16:41:30 UTC