- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 23 Jun 2014 18:16:25 -0400
- To: public-hydra@w3.org
- Message-ID: <53A8A739.2060306@openlinksw.com>
On 6/23/14 4:56 PM, Markus Lanthaler wrote: > It's certainly a fuzzy line but for me a Web specification is something that is exposed on the Web and used by different independent systems without central coordination. Not really. It's an application that leverages HTTP for interaction. "Exposure on the Web" is inaccurate. Taking that position leads people to assume that whenever you build so called "Web apps" they have to be publicly available over the World Wide Web. In fact, this is all about webby data and webby interactions. > This is not really the case here AFAICT. The description will be used by the processor (the server) internally. It uses it to know how to server the data it has. The client, AFAICT, doesn't see this description (and doesn't need to see it). A client and server can have their interactions driven by hypermedia based content, accessible from HTTP locations. The nature of the interactions can be progressively understood as interactions and data state transitions evolve. Ultimately, a client needs to understand what's contained in a payload. Likewise, so does a server. RDF enables machines (be them client, servers, or peers) to understand the hypermedia payloads that are encountered during message exchanges. No different to how we actually work in the real-world. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 23 June 2014 22:16:48 UTC