This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 786 - Canonicalize input URI References
Summary: Canonicalize input URI References
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.0
Hardware: Other other
: P2 minor
Target Milestone: 0.7.0
Assignee: Terje Bless
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-04 13:12 UTC by Bj
Modified: 2004-11-13 15:55 UTC (History)
0 users

See Also:

Attachments

Description Bj 2004-06-04 13:12:54 UTC 
Depending on whether the input URI is http://www.google.com or 
http://www.google.com/ one gets different graphs in the Notation3 output, namely

  earl:testSubject <http://www.google.com>

versus

  earl:testSubject <http://www.google.com/>

which is rather undesirable. URI->canonicalize(...) would prevent that.
Comment 1 Terje Bless 2004-09-01 10:32:19 UTC 
Uhm. AFAIK, the two URLs are entirely equivalent. Why would this be a problem
(in n3 or otherwise)? Canonic URLs is probably a good idea on general principle,
but you seem to be implying a specific bug here?
Comment 2 Bj 2004-09-06 21:22:29 UTC 
They are not equivalent when compared as strings which is how things work in 
RDF, as I wrote, you have two different graphs which is undesirable. This does 
not violate some protocol, but should be fixed nonetheless.
Comment 3 Ville Skyttä 2004-11-13 15:55:48 UTC 
Fixed in HEAD.