Re: Address Bar URI

On Oct 14, 2011, at 18:22, Kingsley Idehen wrote:
> ...
> I posted a while back (a year or so) that in retrospect, when introducing DBpedia the flow *should* have been:
> 
> 1. http://dbpedia.org/page/Linked_Data -- a bookmark friendly and familiar address (URL) of an HTML based resource that describes 'Linked Data' .
> 
> 2. #1 unveils: http://dbpedia.org/resource/Linked_Data -- basically a de-referencable resource (object) name endowed with self reflection that's discernible from the retrieved resource hence the     About: XYZ pattern in DBpedia's HTML pages.
> 
> 3. http://dbpedia.org/resource/Linked_Data -- then surfaces as an alternative data access mechanism courtesy of indirection (which now has functional/usage context) delivered by URI abstraction; basically, you have a generic and extremely powerful data source name added to the mix.

Hmm, no.  Please remember that the nasty use of multiple addresses needed to be present only because HTTP content negotiation wasn't (isn't?) reliable in many implementations.  To my mind, conneg was and is the best solution to this problem.

Regards,
Dave