Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
”What’s 43 Folders?”
43Folders.com is Merlin Mann’s website about finding the time and attention to do your best creative work.
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:
If you have a complete...Submitted by emory on October 24, 2006 - 6:46am.
If you have a complete XSLT/XML ontology, you can easily port that data into assorted microformats (hCal, for example) in a consistant way. I really like the direction this conversation is headed. There is no reason to sacrifice flexibility especially in something so critical as a way to Track Your Shit. I would favor having the data live in XML primarily because it is easy enough to implement and robust enough for a lot of data that an indvidual is likely to have in it. Look at the iTunes library files, for example. » POSTED IN:
|
|
EXPLORE 43Folders | THE GOOD STUFF |