Make WordPress Core

Opened 14 years ago

Closed 14 years ago

#2666 closed defect (bug) (fixed)

WordPress shouldn't use URI instead of URL just because URI is geeky cool.

Reported by: SilverPaladin Owned by:
Milestone: 2.1 Priority: normal
Severity: minor Version: 2.1
Component: General Keywords: URL URI Documentation website bg|has-patch bg|2nd-opinion
Focuses: Cc:


I know this is a topic that comes up periodically, but the last time
I found it specifically addressed on the Wordpress Forum was 2004 and no one
directly addressed it even then. So please bear with me if you think you've
heard it all before, for I'm going to try to be to the point.

I should say, Yes, I do know the difference between the a URI and a URL and did
the obligatory URL vs URI blog entry to prove it. The link is here
http://www.TheCodeCave.com/?p=93, but if you know the difference between a
url and URI you don't need to visit. This isn't a "get visitors" stunt, but
I knew people might try to explain the details to me, and I wanted to
outline my thoughts on the subject and definitions before a Q&A session was

Now, to the meat of it all...
I am speaking against the use of URI specifically in the Options form, but
also in the documentation. WordPress is asking for a URI when it will not
accept all valid URI. Therefore it is asking for the wrong thing.

The simple fact that WordPress it specifies *address* in the prompts for the
"WordPress address (URI):" and "Blog address (URI):" is a clue that it only
wants an URL.

Beyond that blogs now can have URNs (which are valid URIs). My blog,
like many others, has an ASIN from Alexa. Therefore, a valid formated URI for
my blog would be:
ASIN:B000F1J35C. That fits the URN specification and it for now an for ever
more will uniquely identify my site even after my site has long disappeared
from the web. However, can I enter that into the URI field in Wordpress? No,
of course not. You CANNOT enter a URN into those fields, because Wordpress
does not want any old URI. Wordpress specificially wants an URL.

My main point here, is that it is foolish to use a fancy
term that new users don't know just so that your software looks technical
and geeky. This is the sort of slippery slope that you have with open source
projects. Bad habits are promoted when smaller projects use a bad term or
code segment that is picked up in larger projects.

WordPress should do the right thing and change the term back from URI to

I see four primary reasons to do this:

  • URL is the language used in most professional projects.
  • The term URI is not known to the general computing public.
  • URL is more accurate in all WordPress use cases.
  • Some valid URIs would produce errors if entered into the URI field.

Can anyone provide any reasonings for using the less specific URI term other
than "It's the current fad."? If not, I'd support a decision that the next major release include documentation and code changes required to replace URI with URL.

Attachments (1)

2666.diff (26.9 KB) - added by Nazgul 14 years ago.

Download all attachments as: .zip

Change History (5)

#1 @davidhouse
14 years ago

  • Keywords bg|needs-patch bg|2nd-opinion added


#2 @Nazgul
14 years ago

  • Keywords bg|has-patch added; bg|needs-patch removed

I created a patch which changes all user visible references from URI to URL.

I've also taken the oportunity to add the abbr tag to all changed references that didn't have them yet.

And also +1.

14 years ago

#3 @markjaquith
14 years ago

  • Milestone set to 2.1

URL is correct, and more widely known, to boot.


#4 @ryan
14 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [4133]) s/URI/URL/. Props Nazgul. fixes #2666

Note: See TracTickets for help on using tickets.