- markup (76)
- xml (11)
- xslt (23)
- pipelines (8)
- atom (9)
- overlapping markup (6)
- schema (11)
- creole (5)
- dtll (1)
- xforms (1)
- xpath (1)
- xquery (2)
- coding (2)
- datagovuk (1)
- genealogy (4)
- hardware (1)
- linked data (16)
- modelling (1)
- named graphs (1)
- opendata (1)
- provenance (1)
- psi (3)
- skos (1)
- sparql (4)
- Talis (7)
- unicode (1)
- uri (4)
- versioning (1)
- visualisation (6)
- web (78)
- google (4)
- html5 (5)
- jQuery (2)
- rdf (46)
- ontologies (2)
- rdfa (8)
- rdfQuery (5)
- rest (6)
- wikis (1)
- work (3)
- legislation (2)
- xmlsummerschool09 (2)
- life (28)
- children (5)
- equality (6)
- gtd (1)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (11)
- ukgc09 (1)
- xtech (9)
- xtech2008 (3)
- blog (8)
- drupal (3)
Re: Creating Google Visualisations of Linked Data
I’ll admit upfront that I haven’t read the whole article - much of it is over my head, but I’m so appalled by the bar graph that I have to comment. I glanced down it and was astonished to see that in Greenwich, for example, men live less than half as long as women! The blue bar is less than half the length of the red. Then I got to the bottom of the graph and discovered that it only showed ages from 70 upwards. Graphs simply must show zero, or indicate in such a way that it is unmissable that the information displayed is selective and must be interpreted. We live in an increasingly visual world, and software, the people who write it, and the people who use it, must ensure we are not misled. </soapbox>