I've had this problem with a few bookmarks. You've read the RFC wrong, it explicitly states in the section you point to -
This kind of technique is only appropriate when equivalence is clearly indicated by both the result of accessing the resources and the common conventions of their scheme's dereference algorithm (in this case, use of redirection by HTTP origin servers to avoid problems with relative references).
Moreover, the section 6.2.3 also suggest that
In general, a URI that uses the generic syntax for authority with an empty path should be normalized to a path of "/".
And personally I would also prefer empty path URLs normalized with trailing slash.
if you're talking about the plain 'export magnolia bookmarks' link on magnolia, then it would leave me with no tags and privacy settings, so that's not an option.
On the positive side, though, I think magnolia import has just worked for me ;-)
Michael Krelin wrote: > Joel, you're right about tags, somehow I overlooked it. But no privacy... > > Joel Liu wrote: > > http://ma.gnolia.com/export > > It contains your tags which can be seen in the source file. > > > > You can import the file to diigo.
Joel, not anymore, but the " was in the title, I believe, not in the URL. And it was imported with " instead of ". So I'd guess any bookmark with " in title should do for reproducing.
Joel Liu wrote: > We will look into it. Could you tell me the bookmark which was failed to be imported? Thanks.
> Re: URI comparison, see
> http://tools.ietf.org/html/rfc3986#section-6.2.4
>
> http://www.diigo.com/profile/grahamperrin and
> http://www.diigo.com/profile/grahamperrin/ are equivalent, as far as I can tell.
>
> Do you have a problem with a particular bookmark?
I've had this problem with a few bookmarks. You've read the RFC wrong, it explicitly states in the section you point to -
This
kind of technique is only appropriate when equivalence is clearly
indicated by both the result of accessing the resources and the
common conventions of their scheme's dereference algorithm (in this
case, use of redirection by HTTP origin servers to avoid problems
with relative references).
Moreover, the section 6.2.3 also suggest that
In general, a URI that uses the generic syntax for authority with an
empty path should be normalized to a path of "/".
And personally I would also prefer empty path URLs normalized with trailing slash.