Tom Coates: Native to a web of data
- Design and Web 2.0: it’s all about the rounded corners and gradients ;)
- Blogger may have started the trend
- Outline
- What is the web changing into?
- What can you / should you build on it?
- Architectural principles of Web 2.0
- Web 2.0?
- Buzzword, conference, new way of thinking
- Web 2.0 means so many things to so many people though
- Let’s concentrate on a “web of connected stuff”
- Web at the moment - data silos
- Now and in the future:
- A web of data sources, services for exploring and manipulating data, ways that users can act together
- Web of pages -> web of mashups - > a web of data
- Mashups
- two disparate data sources, made more useful by being combined with eachother
- A network effect of services
- Build on top of what’s already there
- What you build enhances what’s already there
- Consequences
- Massive creative possibilities
- Accel. innovation
- Competitive services++
- Componentised services++
- Money to be made
- Use APIs to drive people to your stuff
- Amazon is the prime example
- Better service with less centralised development
- Use syndicated content as a platform
- Turn API into a pay-for service
- It’s no good to be a web isolationist these days ;)
- Choosing what to build
- What can I build that will make the whole web better?
- Add value to the aggregate web
- Architectural principles
- Good URLs should:
- be permanent references to resources
- have a 1-to-1 correlation with concepts
- use directories to represent hierarchy
- not reflect the underlying technology
- reflect the structure of the data
- be predictable / guessable / hackable
- be as human-readable as possible
- be - or expose - identifiers
- Core types of page:
- Destination page
- A core first-order concept and its subordinate info.
- List view page (A slice of your data used to navigate between first-order concepts)
- Manipulation interface
- Interface for batch manipulation of first-order concepts
