[A later version]
Proposed Table of Contents for TAG work on Web Architecture for Web Applications
- Declarative vs. procedural
- APIs - good practices, etc.
- Modules and dependencies
- Security
- Sandboxing
- Trust boundaries
- Cross site
- Privacy
- Client-side URIs
- XMPP/Comet/HTML Web Sockets
- API access to personal data
- API access to phone SMS, /dev/*
- Resource Management
- Installation
- Offline storage
Phones as running example
Turn each item into a sentence
[] = webarch volume 1
() = not really anywhere
Syntax.
[XML]
(Language versioning ...)
Names and binding.
[URIs]
Client-side URIs
Module binding & dependencies
Types.
Interfaces
(Ontologies ...)
Binding and scope (of information and effects).
Security, authentication, authorization, trust
Privacy
Delegation (credentialing)
Mashups
Policy & license respect
Durable resource access (e.g. installation)
Sandboxing
Computational model.
Agents (client e.g. phone / server / P2P).
Declarative expression (e.g. metadata formats?)
Effects on the world (phone, SMS, payment, ...)
Good practice (around APIs).
Imperative (e.g. javascript)
Communication.
[HTTP ... email, blogs, wikis, ...]
[Metadata access]
Persistence.
[REST ...]
File/DB access.
XMPP (IM / presence), COMA?T