Terence Eden. He has a beard and is smiling.
Theme Switcher:

It is spelled "URl"

· 15 comments · 150 words · Viewed ~1,165 times

There are many sectarian divides in computer.

  • "Little-Endians" and "Big-Endians" wage bitter war against each other over the order of bits.
  • Should line in text files end with \r\n or just \n?
  • And both vi and emacs users fight betwixt themselves while ignoring the superior foe - nano.

Perhaps the most contentious of these is the battle between URI and URL. Should we refer to links on the web as Uniform Resource Identifiers or Locators? Obviously there is a correct answer - and anyone who disagrees is a heretic.

So, I've come up with a compromise guaranteed to annoy satisfy everyone - URl.

That's upper-case U, upper-case R, lower case L.

Perfect!

Share this post on…

15 thoughts on “It is spelled "URl"”

  11. Frankly, the separator between records in a (text) file should be U+001E. Anything else is illogical.

    Reply

Trackbacks, Pingbacks, and Boosts

  1. We want your feedback on whether government should add Digital Object Identifiers (DOIs) to the data and documents it publishes. You can give feedback directly on our Open Standards GitHub page until the end of December 2020. We will use your feedback to decide whether to develop a formal proposal to take before the Open Standards Board for consideration.BackgroundThe DOI standard creates a persistent identifier for each document and dataset that we publish. We would assign a unique identifier to every publication, and maintain a metadata record. The metadata would contain the most recent URl (web address) of the publication, details about the author, publication date, and other information necessary for an academic to cite the work.Questions we are asking ourselves - and youThe UK Government publishes a lot of data and documents. But how do we know that they are being used by academic institutions? We don't add tracking to them, and most datasets don't require users to register before downloading.While GOV.UK endeavours to keep website addresses working, we can't always guarantee that's the case. Some content gets removed or withdrawn, and is usually backed up to The National Archive. And sometimes, things just break.Academics who work with government want to be able to put their names to data that they helped create. And we want to give credit to the brilliant people who help us write our publications.Using DOI would bring us into line with academic practice around the world. We would be able to do citation searches to see where our datasets have impact. Researchers would benefit from enhanced metadata and a persistent identifier.Things to considerAs part of our consultation, we need to understand the cost of running such a system. This includes not just the money required to run and maintain the infrastructure, but any cost associated with a potential delay in publishing, even if it’s not immediately financial.We will need to decide on an organisational structure if we adopt DOI. Should we have a single prefix for the whole of government? Or should each department have their own prefix and their own infrastructure? What makes the most sense for users?We also need to understand whether DOI meets our criteria for an open standard. Does it have an open organisational structure? Will the specification be published openly? Is it in widespread use outside of government?Finally, we need to understand the impact adopting DOIs would have on users who don't understand about them. Will this introduce confusion or any other unintended consequences?

    If you or your organisation have any thoughts on this work, you can give feedback directly on our Open Standards GitHub page up until 31st December 2020.

What are your reckons?

All comments are moderated and may not be published immediately. Your email address will not be published.

See allowed HTML elements: <a href="" title="">
<abbr title="">
<acronym title="">
<b>
<blockquote cite="">
<br>
<cite>
<code>
<del datetime="">
<em>
<i>
<img src="" alt="" title="" srcset="">
<p>
<pre>
<q cite="">
<s>
<strike>
<strong>

To respond on your own website, write a post which contains a link to this post - then enter the URl of your page here. Learn more about WebMentions.