- A "chunk" is an atomic piece of text; like an index card, a "to-do" item, a sticky note.
In this diagram, little foldy tabs in the upper left mean "local files." So these all live on my HD.
- These sets are like saved XML queries, dynamically updated, kept in a client on the local machine.
For GTD, each set represents a context: "@home" "@online," etc.
So they're tags, basically.
- In this diagram I chose to represent project sets as different from contexts, but they're probably the same thing.
You'd use them differently, but that's just a user choice, not an architecture choice.
- Note that the "contexts" could be characters, and "projects" could be plot threads, and this would be a story planning system instead of a productivity hack.
Additional metasoftware to manage that stuff better would rock.
- Chunks of your RSS feeds would be treated the same as chunks of text or pages in a wiki or whatever.
I should probably have a callout showing an automatic tag that holds the whole RSS feed together, huh?
- This is an associative diagram; it shows how the XML topic map[?] links the chunks of data together.
Probably Spotlight on Mac OS 10.4 will do much of this already. Can we tie into it?
- Like in del.icio.us or flickr, you'd get XML/Atom/RSS feeds of your personal data. But they'd have to be really secure, because this is your life, not your blog subscriptions.
A very real attention to security by pros from day 1 is called for IMO.
- A local web service on your machine does the mix and match of your "stuff."
My thought here was that you'd have this local web service for all your stuff, and then you'd "push" that to a web service where you can access it remotely, later. Or something?
- The reason for the web service.
In any text on your computer, if you input something like localhost:5555/project/projectname/ (auto-insertable via QS or service?), it's a hyperlink to that project.
- Getting vague, here; the idea was that we'd be defining an API, which then allows specific applications to be built around this schema.
- This all lives on the computer and synchs to your iPod, or something...
- Synching to a USB thumbdrive would be cool, also.
- A bluetooth link to my smartphone would be nifty.
Or, if you could host your secure XML feeds online, a client for the smartphone that could authenticate and read them would rock.
- This was supposed to indicate that projects link to the web service/create secure XML feeds, as well, but my own doodling got in the way.
- These are the same "context." Wanted to clarify that.