Re: Address Bar URI

[Kingsley Idehen]

On 10/14/11 10:26 AM, Norman Gray wrote:

Hugh, greetings.

On 2011 Oct 14, at 13:08, Hugh Glaser wrote:

My colleague, Don Cruickshank asked me if it was good practice to rewrite the 
URI in the Address Bar to be the NIR, rather than the IR.
I was surprised, but he tells me that it is permitted in HTML5.

Can you expand on this a little?

Is this some HTML5 cleverness that lets one declare in the HTML what the 
address bar should display?  Or is it some Javascript kludge^Wgadget that does 
it, in which case what is the sense in which this is 'permitted' in HTML5 and 
wasn't before?

All the best,

Norman

As a result of encountering a link, say: http://www.myexperiment.org/workflows/158, in an HTML document. You click on it, and your browse's address bar displays: http://www.myexperiment.org/workflows/158, in its address bar instead of: http://www.myexperiment.org/workflows/158.html.

Mechanically:
curl -I http://www.myexperiment.org/workflows/158
HTTP/1.1 303 See Other
Date: Fri, 14 Oct 2011 14:28:26 GMT
Server: Apache/2.2.0 (Fedora)
*Location: http://www.myexperiment.org/workflows/158.html*
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=iso-8859-1

DBpedia scenario example that leads to Hugh's *indirection* induced typo problem where: http://dbpedia.org/page/Linked_Data, ends up in the browser's address bar:

curl -I http://dbpedia.org/resource/Linked_Data
HTTP/1.1 303 See Other
Date: Fri, 14 Oct 2011 15:10:18 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Server: Virtuoso/06.03.3131 (Linux) x86_64-generic-linux-glibc25-64  VDB
Accept-Ranges: bytes
*Location: http://dbpedia.org/page/Linked_Data*
Content-Length: 0


What I am saying is this:

1. Resource Location == Resource Address
2. Browser Address Bar captures Resource Addresses
3. Resource Address == a URL
4. URL isAKindOf URI.






I hope this is clearer :-)

--

Regards,

Kingsley Idehen 
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen

Thus, the browser pattern, which is still about one level of URI indirection isn't at fault. We only make everything confusing when we start the whole narrative from the results of indirection instead of the lead up to indirection. Now when Hugh simply states URI and quibbles about the effects of URI indirection. I quibble about the fact that terminology continues to mangle the essence of the matter. These posts shouldn't have to be riddles, they should be crystal clear etc..

smime.p7s
Description: S/MIME Cryptographic Signature