So – yesterday’s post on civic architecture was I have to confess a little text heavy – below is the diagram which I think encapsulates the different areas of the digital ecosystem which we need to consider the need to create civic architecture online:
The Machine layer refers to protocols and TCPIP or the convention of things like HTTP. The infrastructure layer refers to choices of operating system or web server (for example the choice of open source Apache vs a proprietary web server). The Application layer refers to things the specific service such as Facebook or Twitter and the Content layer is as it says – the content – and includes the semantic information needed to make this portable and accessible.
. Running through all of these layers are on the one side the rule of law and the organisations managing this and on the other the influences of culture and identity which effect choices in each of these layers.
I am proposing a civic communicative layer which fulfils a number of needs:
- To ensure information and cultural exchange between applications and operating systems which are currently controlled by market forces often in proprietary systems
- To ensure that the conditions of a healthy public sphere are met in terms of ensuring free exchange of information and views rather than a reliance on market managed media sources
- To ensure balance between social and financial outcomes
There are alternatives which might also deliver civically vibrant online space; for example the new economy might create collaborative and open norms or improved take-up of open source technologies by content creators might swing the balance in favour of a more civic digital ecosystem. However, while waiting for these outcomes to happen and while matters of identity and culture develop I am proposing we ensure the robust existence of a civic communicative layer.