simpleopendata.com is a one-page website that gives advice on how to format, publish, and license open data. It’s meant to be concrete and straightforward.
Simple Open Data fills a void: concrete, straightforward information. Each element of open data is deep enough to fall into - all of the licenses you can choose, the formats to avoid or adopt, API design, and even linked data and semantic web concerns. Some resources discuss everything in depth, making it seem like even your little department needs to embrace 20 different buzzwords right off the bat. This saps enthusiasm and causes analysis paralysis. Having so many priorities leads to inaction, wasteful planning processes, and often a resort to expensive service contracts.
So simpleopendata.com is simple. Which means it has a few opinions.
APIs are optional. For large datasets that lend themselves to APIs and for organizations that have the resources, they can be beneficial. Elsewhere, hard rules like “APIs for everything” are harmful: they devalue vital incremental steps, like simple downloads. The mistake of ‘checking all the boxes’ leads too many local governments to buy a license to Socrata or spend a few weeks setting up CKAN when an FTP server would have done just fine, and would actually be superior for bulk downloading data.
The ODbL license and others with share-alike clauses are not recommended. I’ve seen firsthand the detrimental effect of untested and broad legal language on potential users.
Linked data and the semantic web aren’t mentioned. Both are great visions for the future, but the lack of actual implementations, documentation, and tools mean that recommending that datasets are ‘linked data’ is meaningless in terms of real actions. JSON-LD might change this once adopted - time will tell.
The site embraces the worse is better principle by favoring simple, common formats over shiny new things. It’s an open source, CC0 licensed project, so as open data practices and technologies change, it will too.