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:
 Yes, supporting very different kinds...Submitted by dew on October 24, 2006 - 9:37am.
Yes, supporting very different kinds of organization like this is exactly what I would like to see. Perhaps the id driven approach would be a good idea. So while you might have: <action id="uniqueid1"> <description>Call dentist re appt</description> <tag>PreventingToothDecay</tag> <tag>Phoncalls</tag> </action> <action id="uniqueid2"> <description>Buy new toothbrush</description> <tag>PreventingToothDecay</tag> <tag>StuffToGetInTown</tag> </action> I could safely add: <project id="uniqueid3"> <title>Prevent Tooth Decay</title> <action ref="uniqueid1"/> <action ref="uniqueid2"/> </project> And tedium would ignore that part. Any my app might ignore the You're right about the issue of descriptions?they probably would do better in their own node, as you suggest. The app I'm writing will support breaking up projects into different areas of your life, so you don't have to sit down and look at 50-100+ projects at one time. So I would do this: <area id="uniqueid4"> <title>Personal</title> <project ref="uniqueid3"/> </area> » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
