- 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: Posterity
Amen, sister, re keeping data in closed-format form. And the Charles Stross quote struck me when I read it, too. I still have part of my email archive in a scarcely-accessible format from when one of my workplaces used Lotus Notes.
Of course (strokes beard - or rather, bald pate) this is one reason for the original unix philosophy of “all data files are text files”. And this keeps coming up - for example, this is a really interesting post about making your own pda/workflow-tool based on text files, allowing all sorts of anticipated and unanticipated analysis and processing. This relies, of course, on another part of the unix philosophy - building big special-purpose tools out of little general-purpose tools (using pipelining and scripting) - but I must be getting boring…
PS I really like, in the above quoted link the idea of analysing ones own degree of success in estimating task timing - and the quote “the ubiquitous relational database, while wonderful in some ways, does tend to get in the way of ad-hoc faffing with your data” - and the idea of emailing yourself the daily to-dos, rather than remembering to (or avoiding) reading a todo list.