ToDo

last update: 02-MAY-2006

• write your suggestions and/or ideas to the priorart-mailinglist

• correct spelling-errors all over the wiki, especially in the HowTo search for Prior Art in the Internet and the HowTo search for Prior Art in the Internet

• pick one of the categories in Publication Categorization and add one software-category or one individual program that in your oppinion fits into that category (Example | Publication Categorization )

• summarize the Tagging Prototype (probably requires some programming knowledge in python)

• go through the mailinglist archive and update the FAQ . Maybe just download the full mbox and grep it for questionmarks '?' to find some questions 

• summarize important comments from Notice of Public Hearing and Request for Comments on Issues Related to the Identification of Prior Art During the Examination of a Patent Application (This is lots of text, but you don't need to do all yourself, just pick one single comment and summarize it)

• Use the HowTo search for Prior Art in the Internet on another patent, maybe one you really want to beeing voided. Add your progress as another Main-Section in our HowTo search for Prior Art in the Internet . Don't forget to update the HowTo as you find new/different ways of accomplishing some tasks.

• create list of interactive tagging tools
  • ccHost
  • Tasty
  • Leaftag
  • …
• evaluate tools, choosing one closest to our needs (or learning from one):
  • external information pointers
  • “author” tagging
  • “community” tagging
  • three-level tagging
  • tag export
  • tag inference engine
  • tagging API (for source crawlers)
• modify/implement tagging tool, getting it to a usable state
• create packagable version of the software
• install software on osapa.org
• attempt to tag a specific piece of software
  • choose “what” to tag
  • modify tagging tool based on input from community
  • choose export language (RDF, DOAP, others?)
  • choose basic solution to time-stamping metadata changes
• have tagging meeting to get people in physical proximity
• request input from USPTO on usefulness of prototype (but continue work)
• approach freshmeat, SF, kernel.org with working prototype
  • likely they'll want the DB schema or the export language
• popularize software tagging at the project-management level
• popularize software tagging at the community level
  • must be FLOSS
  • must be actually useful
  • must be easy to use
• attempt to search against exported tags from multiple repositories
  • work out any identified issues
• approach google, yahoo about carrying exported metadata
• get input from USPTO on search engine interfaces
  • improve search elements
• rinse, lather, repeat