Participants

scott, ian, whit

General Usecase

To cover most of our imaginable usecases, we have identified 2 major types of tagging: we'll call these exo-tagging and endo-tagging.

• exo-tagging (save for later)

  
  

  The tagging of items for sharing or personal organization irrespective to ownership or formal categorization.  the act of creating folksonomy for creating organization of external resources. ex: http://del.icio.us/  .  other forms of collaborative bookmarking.
  

• endo-tagging (now)
  
  The creation of taxonomy by the classification of content based on ownership or stewardship.  ex: wordpress categories, dc:subject, etc.

Implementing Endo-tagging

Though we are in the long run interested in exotagging, we want to concentrate on endotagging for starters.   This usecase contains a replicable pattern for our basic content "types" in zope: member data, projects, wiki pages, attachments, etc.

• storage
  
  We'll begin by storing and retrieving data from FlatAtomPub aka Flap (as atom and gdata).  Tags will be represented as atom categories, application use of a particular tag will be denoted as a category scheme.
• client
  
  Python clients for zope will be based on the current work in TaggerClient.  The client is responsible for interpretting the returned data from Flap
• sync
  
  Zope will emit events to update Flap when a content item is updated.  Flap doesn't need to emit events yet since nothing will be talking to flap or changing tags outside zope (though later this may change).

Concerns / Unknowns / Considered Expectations

1. Flap is brand new.  We expect some possible reworking
2. [dwm] not sure about the state of the client
3. Data schema (schemes for our usecases) still has to be thought out
4. Possible optimization concerns
5. No UI (though this may be simple and fields based for our endo cases)
   

6. we want to handle geocoding in a smart way


General Task list

Overview tasks. Technical items with go into trac.

References

Geocoding

Atom Resources