Plan
Still work in progress…
1. Define standards for data
- date format (yyyy-mm-dd)
- date and time format (yyyy-mm-dd hh:mm:ss)
- address format
- post code
- name
- currency (no prefix, always to 2 decimal places)
- boolean
- numbers (no separators)
- hyperlink (whole thing including http:, got to work)
2. Define formats from db
- JSON
- XML
- CSV
- RSS
- iCal
3. Define static file formats
- Shapefiles from geosoftware
- KML
- Others
- iCal
4. Data dictionary
- data set title
- data set filename (generated off the title)
- language
- audience (public, restricted)
- friendly description
- geographical extent
- author name (could be a group)
- update frequency
- data set types (csv no headers, csv with headers, RSS feed, Excel spreadsheet…)
- date range
- release date of that version
- metadata update
- license summary
- license details
- version
- tags
- themes? (overarching categorisation?)
4a. Theme types
- Art and Culture
- Business and Economy
- Crime and Community Safety
- Demographics
- Education
- Employment and Skills
- Environment
- Health
- Housing
- Planning
- Sport
- Transparency
- Transport
- Young People
5. Define feed formats
- GeoRSS (http://www.georss.org/)
- RSS
- KML
6. URL structure
- for example - http://data.london.gov.uk/datastore/package/abandoned-vehicles
- would include version
- http://sitename/data/v-1-1/name-of-package.format?par=val…
- .format = .html - that's the data dictionary description
- parameters?
- date_from - date_to
7. Define REST interface
- ideas - http://www.xml.com/pub/a/2004/12/01/restful-web.html
Storage
- MySQL (+memcache?)
- MongoDB
- CouchDB
Anti-RDBMS - a list of distributed key/value stores
http://www.metabrew.com/article/anti-rdbms-a-list-of-distributed-key-value-stores/
