W3C home > Mailing lists > Public > public-lod@w3.org > January 2011

Re: URI Comparisons: RFC 2616 vs. RDF

From: William Waites <ww@styx.org>
Date: Thu, 20 Jan 2011 15:55:42 +0100
To: Nathan <nathan@webr3.org>
Cc: Dave Reynolds <dave.e.reynolds@gmail.com>, "public-lod@w3.org" <public-lod@W3.ORG>, Alan Ruttenberg <alanruttenberg@gmail.com>
Message-ID: <20110120145542.GN19921@styx.org>
* [2011-01-20 14:29:35 +0000] Nathan <nathan@webr3.org> écrit:

]   RDF Publishers MUST perform Case Normalization and Percent-Encoding 
] Normalization on all URIs prior to publishing. When using relative URIs 
] publishers SHOULD include a well defined base using a serialization 
] specific mechanism. Publishers are advised to perform additional 
] normalization steps as specified by URI (RFC 3986) where possible.
] 
]   RDF Consumers MAY normalize URIs they encounter and SHOULD perform 
] Case Normalization and Percent-Encoding Normalization.
] 
]   Two RDF URIs are equal if and only if they compare as equal, 
] character by character, as Unicode strings.
] 
] For many reasons it would be good to solve this at the publishing phase, 
] allow normalization at the consuming phase (can't be precluded as 
] intermediary components may normalize), and keep simple case sensitive 
] string comparison throughout the stack and specs (so implementations 
] remain simple and fast.)
] 
] Does anybody find the above disagreeable?


Sounds about right to me, but what about port numbers,
http://example.org/ vs http://example.org:80/?

-w

-- 
William Waites                <mailto:ww@styx.org>
http://eris.okfn.org/ww/         <sip:ww@styx.org>
F4B3 39BF E775 CF42 0BAB  3DF0 BE40 A6DF B06F FD45
Received on Thursday, 20 January 2011 14:56:11 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:31 UTC