• 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.

    Curses!
  • These are the same "context." Wanted to clarify that.

Moleskine Concept Diagram 1

Newer Older

This is a diagram I doodled before bed to try to encapsulate what I was thinking in response to discussion with Merlin Mann about his "I'd Like A Pony" blueskying.

Edward Vielmetti, Terry Madeley, and 158 other people added this photo to their favorites.

View 2 more comments

  1. Robert Brook 112 months ago | reply

    (still trying the understand the diff. between 'chunk' and 'atom'...)

  2. paperbits 112 months ago | reply

    robert:

    In this case, "atom" means "something I can pick up." I.e., a notecard.

    Which is why I used "chunk" instead of "atom."

  3. jkoshi 110 months ago | reply

    great use of notes!

  4. Ross_B 103 months ago | reply

    The correct link for the discussion with Merlin Mann is www.43folders.com/2005/01/05/i-want-a-pony-snapshots-of-a...

  5. paperbits 103 months ago | reply

    Fixed. Thanks.

  6. Robert Brook 103 months ago | reply

    Hmm. Makes me feel all microformat-y.

  7. neonlike 101 months ago | reply

    interesting that only men have commented so far!

  8. Br3nda 101 months ago | reply

    thoughts: bluetooth is only one layer - put something already encrypted over bluetooth, as well as another authentication layer, and those concerns should go away.

    I've always seen bluetooth as a USB cable, except in broadcast mode.

  9. paperbits 101 months ago | reply

    You make a good point re bluetooth... my knowledge of how BT works is fairly vague, truth to tell.

    Hell, my knowledge of how most of this stuff work is faily vague. :)

  10. Br3nda 101 months ago | reply

    the bluetooth problems are really flawed implementations...

    there's lotsa PCs out there that you can get root access to over TCP/IP, but that's not TCP/IPs fault :-)

  11. dgray_xplane 96 months ago | reply

    Whoooooaaaahhhh

  12. paperbits 96 months ago | reply

    I thought you'd seen this, Dave... :)

  13. SerialCoder 81 months ago | reply

    This image has been added to the Flickr Museum for making explore's top 25. Kudos!You can check it out here...

  14. paperbits 81 months ago | reply

    .....urr? Um.

    Thanks!

  15. mstephens7 75 months ago | reply

    May I use this as a background for a slide in a presentation - with full citation to you?

  16. paperbits 75 months ago | reply

    @mstephens7: sure.

    I'd be interested to see the slides when you have them, just for curiosity's sake.

  17. mstephens7 75 months ago | reply

    Of course. It's for a background on a slide that reminds folks technology is just a tool..only a tool...

    Thanks! I've had a great few days updating this talk... Merlin's post about presentations really fired me up.

  18. paperbits 75 months ago | reply

    Sounds good. Looking forward to seeing it.

  19. captcreate 46 months ago | reply

    Hi, I'm an admin for a group called Open notebooks, and we'd love to have this added to the group!

keyboard shortcuts: previous photo next photo L view in light box F favorite < scroll film strip left > scroll film strip right ? show all shortcuts