W3C home > Mailing lists > Public > public-ldp@w3.org > June 2014

Re: best practices comments

From: Cody Burleson <cody.burleson@base22.com>
Date: Mon, 9 Jun 2014 07:42:57 -0500
Message-ID: <CAJM-Rdr-brw2Jqmbc0gs0ZMSTW-w3-a1pkbz0KH+5hJKgP4Etg@mail.gmail.com>
To: "henry.story@bblfish.net" <henry.story@bblfish.net>
Cc: public-ldp <public-ldp@w3.org>
Thanks, Henry.

I added the hexBinary as per your suggestion.

I agree about canonicalization - reference to definition would be helpful.

Now, the funny thing is, I cannot for the life of me find any original
definition of the term "canonical URL". From what I could find, it seems
that "canonicalizing" a URL is the process of "normalizing" the URL, which
is described here:


With a little verification that I am correct, perhaps we should say
something like:

URL canonicalization (URL normalization) is the process by which URLs
<http://en.wikipedia.org/wiki/Uniform_Resource_Locator> are modified and
standardized in a consistent manner; see section 6, Normalization and
comparison in [RFC3986].



On Fri, Jun 6, 2014 at 3:36 AM, henry.story@bblfish.net <
henry.story@bblfish.net> wrote:

> -Section 2.8 you seem to have forgotten the xsd:hexBinary which is a
> standard rdf datatype, used by the cert ontology
> which is used widely by WebID.
> http://www.w3.org/2005/Incubator/webid/spec/
> - Canonical urls may need to refer to the definition in the URL spec. ( I
> think that's where the term is found )
> It removes things like ../ in urls.
> Henry
> Social Web Architect
> http://bblfish.net/

Cody Burleson
Enterprise Web Architect, Base22
Mobile: +1 (214) 537-8782
Skype: codyburleson
Email: cody@base22.com
Blog: codyburleson.com

Please be advised that I check and respond to mail
on the following Central Standard Time schedule:
9:00 am, 1:00 pm, and 4:00 pm

*Check my free/busy time.
Received on Monday, 9 June 2014 12:43:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:16:37 UTC