Nations-States rely on constitutions. Common(er)s find common ground through a Charter. If you are part of the co-creation of a powerful Data Commons – through mapping, coding, data modelling or other activities – this is for you. It is an fundamental building-block for online and offline cooperation.
The following is version 0.6 of what has been called in previously: Charter for Building a Data Commons of Alternative Economies or Mapping for the Commons Manifesto. We, the participants of the Intermapping meeting (March 2017 in Florence), hope to hereby publish a version that provides orientation to the countless mapping processes for a free, fair and sustainable world.
We invite you to work together on the practical issues: how to implement the principles outlined in the Charter (see below)?
Let’s federate our efforts to make the Commons thrive!
Charter for Building a Data Commons for a Free, Fair and Sustainable Future (0.6)
This Charter/Carta provides practical guidance and political orientation for mapping, modeling, managing and sharing data as a Commons. If you follow these guidlines, you will contribute to a Global Data Commons. That is, you will govern your mapping community and manage data differently than people who centralize data control for profit.
The Charter does not describe the vision, scope or values of a specific mapping project, but Data Commons principles. It will help you reimagine how you protect the animating spirit of your mapping project and prevents your data from being co-opted or enclosed.
The Charter as a whole is the maximum „commons denominator“ of mapping projects that aspire to share data for the common good.
Help commonize maps and data! For the people, by the people.
1. **Reflect on your intentions together**
Discuss the core of your project again and again. Everybody involved should always feel in resonance with the direction in which it’s heading.
2. **Make your community thrive**
For the project to be successful, a reliable community is more important than anything else. Care for those who might support you when you need them most.
3. **Separate commons and commerce**
Mapping for the commons is different from producing services or products to compete on the map-market. Make sure you don’t feed power-imbalances or profit-driven agendas and learn how to systematically [separate commons from commerce](https://discourse.transformap.co/t/separate-commons-and-commerce-to-make-it-work-for-the-commons/625 separate commons from commerce).
4. **Design for interoperability**
Think of your map as a node in a network of many maps. Talk with other contributors to the Data Commons to find out if you can use the same data model, licence and approach to mapping.
5. **Care for a living vocabulary**
Vocabularies as entry points to complex social worlds are always incomplete. Learn from other mappers‘ vocabularies. Make sure your vocabulary can be adjusted. Make it explicit and publish it openly, so that others can learn from it too.
6. **Document transparently**
Sharing your working process, learnings and failures allow others to replicate, join and contribute. Don’t leave documentation for after. Do it often and make it understandable. Use technologies designed for open cooperation.
7. **Crowdsource what you can**
Sustain your project whenever possible with money, time, knowledge, storing space, hardware or monitoring from your community or public support. Stay independent!
8. **Use FLOSS tools**
It gives you the freedom to further develop your own project and software according to your needs. And it enables you to contribute to the development of these tools.
9. **Build upon the open web platform**
Open web standards ensure your map, its data and associated applications cannot be enclosed and are prepared for later remixing and integration with other sources.
10. **Own your data**
In the short run, it seems to be a nightmare to refrain from importing or copying what you are not legally entitled to. In the long run, it is the only way to prevent you from being sued or your data being enclosed. Ban Google.
11. **Protect your data**
To own your data is important, but not enough. Make sure nobody dumps your data back into the world of marketization and enclosures. Use appropriate licenses to protect your collective work!
12. **Archive your project**
When it doesn’t work anymore for you, others still might want to build on it in the future.
HOW TO?: first notes here. You can also use this Hackpad to add your comments and suggested changes. If so, please provide a reason. Other sites to provide your feedback:
- here on this blog
- on the transformap-discourse platform
PD: gosh, I think that the title is too long. Ideas for a smarter one are very welcome!