; This what an OS should be providing. ; As thin a layer above the OS as possible. ; As language-agnostic as possible. ; See App Engine.
; Works on server(s) and clients, auto-propagates changes.
; DVCS-style, manual conflict resolution where necessary.
; All user-facing metadata is in tags
; audio, photo.
; Can it be unified with something?
; Post to subscribers’ queues
; Services are REST, so usual conventions should apply
; linked to security credentials as needed
; external services, RSS feeds, etc
; Many apps may need them
; Built on top of common services.
; Exposes the tag-based “file system”
; a web interface on top of regular exim/dovecot or whatnot.
; if possible, on top of a regular calendar server.
; See hackpad and ginkgo-app
; Common language-neutral engine allows to add parts. ; Language-neutral late binding: HTTP, REST, JSON.
; Any piece may provide consumer views, intended not only for authors / owners.
; OK for viewing. With caution, possible for commenting.
; See the reverse tags document
; most specific part goes first: inbox/mail, “Moby Dick”/title
; All applications within the cloud use the same set of tags.
; color, a short text blurb, maybe an icon, set manually or ; auto-extracted form auto-tags, like userpic for contacrs.
; Probably “firsname lastname”/contact and nickname/contact
; Searches by any content can be saved. Possibly “sub-searches” with additional ; constraints can look like “sub-folders”.
; Searches purely by tags are drag targets: if any taggable item was dragged ; onto them, necessary tags are added, incompatible tags are removed. ; It’s a fast categorization tool.
Message bus / queues. Key-value blob store with byte-range access. Full-text indexing engine. Tag storage. Common internal REST-like interfaces. Language independence.