Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Standard GTD File Format, Anyone?
dew | Oct 23 2006
I've been thinking that those of us developing GTD software ought to agree on some sort of common file format that our apps can export to and import from. I don?t expect that every (or even any) apps would natively read and write this format during day-to-day operations. The app I?m working on is based on the Mozilla platform, so I?m using RDF/XML to save GTD data. I don?t think I?m going to want to switch that out anytime soon, but I would love to provide an export/import mechanism so that folks won?t hesitate to experiment with my app, knowing they can easily get their data in and out of it. I imagine some sort of XML that?s not as ugly as RDF/XML would be a good idea, but another plain text format would work too. Ideally, it would be human and machine readable. Given the nature of the data, I don?t imagine this would be a problem. Also the format would need to lend itself well to various ?interpretations? of the data. Some programs out there deal with due dates, and others do not. Some programs deal with nested projects and others do not. It would be best if any given program could easily extract whatever data it needed and safely ignore the other bits. For example, the app I?m working on will not support due dates but it should still be able to import actions with due dates assigned to them by another program. Just wanted to plant a seed here. If anyone knows about a GTD file format that?s already being developed or used, please do tell. 6 Comments
POSTED IN:
 I was just about to...Submitted by amcewen on October 24, 2006 - 1:00am.
I was just about to suggest microformats. I haven't added any file export to tedium yet, but have been thinking of defining a new microformat when I do. I'd favour something modular, where actions can be separated from projects; but that's just because tedium has no explicit concept of projects, they'd just be one of the tags that you assign to the relevant actions. Taking your example above, wouldn't it be easier to pull the description into something wrapped in
<project>
<title>Preventing tooth decay</title>
<action>
<description>Call dentist re appt</description>
</action>
<action>
<description>Buy new toothbrush</description>
</action>
</project>
And I'd probably just ignore the <action> <description>Call dentist re appt</description> <tag>PreventingToothDecay</tag> <tag>Phoncalls</tag> </action> <action> <description>Buy new toothbrush</description> <tag>PreventingToothDecay</tag> <tag>StuffToGetInTown</tag> </action> » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
