- From: Harry Halpin <hhalpin@w3.org>
- Date: Thu, 05 Feb 2015 13:12:01 +0100
- To: public-socialweb@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/05/2015 12:54 PM, ☮ elf Pavlik ☮ wrote: > On 02/04/2015 07:26 PM, Harry Halpin wrote: >> >> >> On 02/04/2015 04:40 PM, ☮ elf Pavlik ☮ wrote: >>> On 02/04/2015 03:37 PM, henry.story@bblfish.net wrote: >>>>> Maybe for our next telecon you could sketch out an >>>>> alternative vision, without a server-to-server protocol? >>>> >>>> yes, that is not difficult. When you say client you mean >>>> browser, when you mean server you mean a machine that is >>>> usually without a display, and that is constantly bound to >>>> the internet. In my world - the world of HTTP and APIs - >>>> clients and server are just roles that computers play. A >>>> computer program can be in server role in one moment and then >>>> client the next. One multiple core machines they can be both >>>> simultaneously. So there is no server/server api. There can >>>> only ever be client/server relations. >>> I just started wiki page for Social Web Glossary[1] I find it >>> very important to clarify terms like: >> >>> 1 App 2 Domestic Server 3 Foreign Server 4 Web Service >> >> I in general would not use the term Web Service due to its >> history with SOAP, which is a separate stack. You could say >> simply "website" (if you mean domain, ala www.example.org running >> separate apps in different iframes) or just say "platform" if you >> mean something more cross-domain, like Twitter or Google >> eco-systems. > website - for most people may not sound like something providing > REST API, most people may expect HTML and web browser based > interaction > > platform - could you drop some links showing how people use this > term? Rather than make up new terms, let's use terms in a way people already. Google, Facebook, Twitter call themselves 'platforms.' You can use a search engine yourself easily to figure this out. http://en.wikipedia.org/wiki/Facebook_Platform Web Services has a very specific meaning inside W3C: http://www.w3.org/TR/ws-arch/ > >> >> Ditto domestic and foreign server. Typically, one says "provider" >> for domestic server and "relying party" for foreign server. > do you think people won't get confused when my "provider" will act > for you as "relying party" and your "provider" will act for me as > "relying party"? i find terms *domestic* and *foreign* putting more > emphasis on a perspective from which we look at it and not that > much on the functionality... Provider and relying party are the most common terms in how the rest of the standards world (i.e. OAuth etc.) uses. Foreign/domestic usually has to do with state boundaries in modern parlance. > >> >> There's a good terminology section here: >> >> http://www.w3.org/2005/Incubator/socialweb/wiki/FinalReport#The_Terminology > >> thanks, will check this out! > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJU014QAAoJEPgwUoSfMzqcvSkQAK1JVIUKLgdCpQ3gYsZJAqyX fbqZhdWVVmwu/jNs9itTFsbg0LbedbfwkSjbHwPej3avSC6+G0pOQp223Epu2z/h DNZhQ8HKFhiwKzI+X6RZlpdnhIGJ1tDt6yXR8kZQ+lkLQAssn+kDlt84zw+aNwqm mC0GMysjUV7kOzoSg+sKn8WMiEIWTaR9JHcQ+kr9nPonBjo/QQxyMRQxj5uWfUBp 1fiICED+yOAmH+uDsebx4Hv2d+uqbUibc7pEMMYpq4QvmMI2V1pZYGgn9djGwN4c Sg5G/H4Di9OH5PudBTdowuiQ36C2s9E/fZ0lHGU8uIHqkst/hzLCJ5f/XIR2/4if VtKWrh1adETKtCvmsfuFnbcgDzovVYti/ic5GV/ipKqdxpNu+kp58g5r58wURErA ceOqph02l8vfffidUWAjOE6ZKtW/JBRxFy3LaVdeIJTQwRbmFJwamcW9Po4E1L7Y 7Mg9AYWpygjgt0sykeTlJUQ+IOU2mrEBQdQmyW/9f2j6TlL/IKAx43/dtYy/4PL0 dNIGVaBDKNIeFTXFARqVnGtZxOnmy498QLsLUaFYNrSapCc+LWm2kDpV6/w1ptG9 aCckMpNYoXfxCTlQOERtfS+v2T6DT9PSSjikdx7c40gkGXthDP9i9uGWdcMdZGsC +EHA8aHz+iMvZAP2lGyv =kto0 -----END PGP SIGNATURE-----
Received on Thursday, 5 February 2015 12:12:10 UTC