PUBLIC MARKS with tag webarchitecture

So, in a nutshell, here is a tick-list for an architecture for participation:

* Open Source Implementations

* Test Suites

* Continuous Integration

* Wiki Driven Documentation

* Small, Lightweight Specifications

* Free and Open Licensing

I've published a manifesto for this approach in the form of a gnomic sampler on http://standeace.com, a contraction of "Standards" and "Peace":

Designing your Product as a Platform

WebAccessControl is a decentralized system for allowing different users and groups various forms of access to resources, where users and groups are identified by HTTP URIs.

Once freed from the awkward initial step of building their own base map, non-specialists rapidly colonized the online mapping space.

Addressing the problem of scalable access to web resources is not a simple one. There are a number of ways it can be approached at a number of different levels in the web architecture stack. The W3C Technical Architecture Group has agreed to investigate the issue. ¶ In the meantime, if you're writing GlassFish[L] servlets or other applications that are performing XML processing, you can take advantage of the XML Catalog resolver built into GlassFish to directly reduce the burden your applications are creating. (Never heard of a XML Catalogs? I wrote some background information a while back.) ¶