You know, the whole thing reminds me of the SOAP documents listing SMTP
as an alternative transport.
And my prediction is that the whole discussion will be as fruitless.
Wake me up when the note tying Linked Data to RDF over HTTP becomes
anything other than best practice... sorry, scratch that, sole practice.
Barry
On 17/06/13 14:33, Karl Dubost wrote:
Luca,
Luca Matteis [2013-06-17T08:34]:
Come on! If you're building something that works like the Web but isn't using
HTTP, then it's *not* the Web. It's something else that has similar dynamics to
the Web (like, I dunno, a gazillion of other things?).
HTTP is an important feature of the Web, a very fundamental one. Nobody will
disagree with that. BUT it is the URI which creates the Web. See Architecture
of the World Wide Web.
On Tue, 14 Dec 2004 20:19:19 GMT
In Architecture of the World Wide Web, Volume One
At http://www.w3.org/TR/webarch/#interaction
3. Interaction
Communication between agents over a network about
resources involves URIs, messages, and data. The
Web's protocols (including HTTP, FTP, SOAP, NNTP,
and SMTP) are based on the exchange of messages. A
message may include data as well as metadata about
a resource (such as the "Alternates" and "Vary"
HTTP headers), the message data, and the message
itself (such as the "Transfer-encoding" HTTP
header). A message may even include metadata about
the message metadata (for message-integrity
checks, for instance).
