- From: carmen <_@whats-your.name>
- Date: Wed, 29 Jan 2014 14:10:54 +0000
- To: public-webize@w3.org
"We do need a name we can stick to. ;)" Semantic-Web <- sounds too AI, unrealistic until machine-learning deployed widely at client-level? Linked-Data <- referring to serializations & data-model not entire platform Read-Write-Web <- is this not the current name? you can read+write to just about any website though, save for luddite geocities-freaks who are still serving files via Apache and writing to them only via FTP/Rsync/SCP, but you'll need to reverse-engineer large mounds of obfuscated&minized JS with FireBug/WebkitDevtools or mitmproxy+tshark, and emulate their usage of ad-hoc site-specific APIs, over and over .. thus, borrowing nomenclature from Complex Math, these solutions which while "on the web" are not "on the read-write web" since the "web" part of the name implies a shared/unified way of doing writes, and related offshoots like identity + auth(orize|enticate) IRWW . Imaginary Read-Write Web . just link your "app" to liboursitedata.jar and you can read+write. we swear it's a "website" (the URL is https://api.liboursite.com) even though only accessible w/ SPDY, not HTTP 0 and only outputs JSON, not HTML, and uses our homebrew auth system. this ensures the smoothest user-experience, as determined by highly-paid UI consultants RRWW . Real Read-Write Web . stample/ldphp/other-newcomers so it's no longer the triple-W, but the double-RW - WWW RW + POSIX+RW underneath in most cases, unless you're a hyper anti-luddite who exclusively use RAM-only blobstores having abolished the filesystem to antiquity
Received on Wednesday, 29 January 2014 14:11:31 UTC