me2c
if you can rewrite http://yourserver/page so that it shows as
http://yourpage/resource when page was the result of a redirect that
would indeed finllay resolve the completely unacceptable situations
where users are force to understand (and see in their browser bars)
the distinction.
Thanks Michael.
Very helpful to bring in the SEO perspective, even on a Friday evening.
On 14 Oct 2011, at 21:28, Michael Smethurst wrote:
Have to say from a pragmatic point of view that using replaceState to switch
between IR and NIR (or whatever we're supposed to call them) URIs feels like
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
*
The 9th Extended Semantic Web Conference (ESWC 2012)
27-31 May 2012
Heraklion, Greece
http://2012.eswc-conferences.org/
*
*About ESWC2012*
The Extended
On 10/15/11 11:40 AM, David Wood wrote:
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
On 10/15/11 12:09 PM, Kingsley Idehen wrote:
To my mind, conneg was and is the best solution to this problem.
To my mind, I've never said or implied anything contrary.
HTTP's ability to let user agents and servers negotiate data
representation its most powerful features.
Typo fix re.
