On Fri, Nov 5, 2010 at 4:55 PM, Nathan nat...@webr3.org wrote:
Mike Kelly wrote:
http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-12#page-14
snipped and fuller version inserted:
4. If the response has a Content-Location header field, and that URI
is not the same as the
On Fri, Nov 5, 2010 at 5:28 PM, Nathan nat...@webr3.org wrote:
URI resolution is essentially:
dereference( uri.toAbsolute() );
Which gives us the simplicity and semantic indirection which we need. Use
frags, forget HTTP, know that uri#frag is never going to be a document
(unless you
Ian Davis wrote:
On Fri, Nov 5, 2010 at 4:55 PM, Nathan nat...@webr3.org wrote:
Mike Kelly wrote:
http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-12#page-14
snipped and fuller version inserted:
4. If the response has a Content-Location header field, and that URI
is not
apologies for cross-posting
CALL FOR PAPERS
3rd International Workshop on Visual Interfaces to the Social and Semantic Web
(VISSW 2011)
In conjunction with the ACM Conference on Intelligent User Interfaces (IUI 2011)
Stanford University, Palo Alto, US
13th February 2011
On 11/6/10 8:11 AM, Ian Davis wrote:
On Fri, Nov 5, 2010 at 4:55 PM, Nathannat...@webr3.org wrote:
Mike Kelly wrote:
http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-12#page-14
snipped and fuller version inserted:
4. If the response has a Content-Location header field, and
On 11/6/10 9:05 AM, Nathan wrote:
Ian Davis wrote:
On Fri, Nov 5, 2010 at 4:55 PM, Nathan nat...@webr3.org wrote:
Mike Kelly wrote:
http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-12#page-14
snipped and fuller version inserted:
4. If the response has a Content-Location header
On 11/6/10 12:41 PM, Bill Roberts wrote:
On 6 Nov 2010, at 17:25, Kingsley Idehen wrote:
All,
So we have arrived at a destination that's mutually inclusive re. 303 indirection.
Basically, an additional technique that uses Content-Location as the switch. Nice,
simple, clean, and shouldn't
David, hello.
On 2010 Nov 6, at 20:42, David Booth wrote:
httpRange-14 requires that a URI with a 200 response MUST be an IR;
^^^
Not quite. The httpRange-14 decision says that the resource *is* an IR:
On 11/6/10 4:42 PM, David Booth wrote:
httpRange-14 requires that a URI with a 200 response MUST be an IR;
^^^
Not quite. The httpRange-14 decision says that the resource *is* an IR:
On 06/11/2010 16:25, Kingsley Idehen wrote:
[snip]
In addition, I think we've also triggered a POWDER fix that's been long
overlooked.
And I'm grateful that it's come to my attention (wish I'd recognised the
problem a lot earlier :-()
I've made a proposal internally (at W3C) that I want
On 11/5/10 1:41 PM, Phil Archer wrote:
The 303 debate has prompted me to re-look at the definition of
wdrs:describedby - and it's obvious that the POWDER WG (which I
chaired), made an error.
I've begun the process of seeking to change the spec so that the range
restriction on this property
On Sat, 6 Nov 2010 12:33:34 +
Ian Davis li...@iandavis.com wrote:
On a practical level using frags can be inefficient when your linked
data output is backed by a triple store. If you use a slash URI then
generating the data for html/xml/turtle output is just a simple
describe uri. For
Begin forwarded message...
Date: Thu, 4 Nov 2010 00:32:50 +
From: Toby Inkster t...@g5n.co.uk
To: foaf-dev foaf-...@lists.foaf-project.org
Subject: [foaf-dev] EON - event of note
Let's do a bit of collaborative work to flesh out a FOAF-like
lightweight vocabulary for describing events,
13 matches
Mail list logo
