FeatureImportanceComments
Centralized remote repository3
Can work offline (with syncing when back online)3
xml (rdf?) storage format3make our own (can't use vcal/ical unfortunately)
export to html and ....2trivial (use some xsl)
integration with a calendar app ...1difficult and in that case we might as well try building on sunbird
min info to store3 date entered, date due (if any), subject, details (allow html etc - specify markup type? different types (configurable of todo item): day schedule, todo, goals (long, short, medium). support for closure info (make this a separate item)
other possible info to store2 classification of entries (taxonomy) and allow for multiple classification. support linking between items

Architecture

Functionally can split into layers:
  1. Remote repository communication
  2. Read/write export data format
  3. GUI

Data Design and XML/RDF Format

Remarks

  1. Can make day schedule as compositions of todo items ??? (thing is they are kind of trivial .....). NO this is the way to do it. What to provide interface when it is like that .....?
  2. This is getting TOO complicated .....

Fields/Values

FeatureImportanceComments
standard attributes of dc: title, data created, date last modified, author (creator)3
details/fulltext3
classification with vocabularies2this should be the main site of extensibility
status (closed, open, urgent ....?)3trivial (use some xsl)
assigned1