what problem are we addressing?
microformats - compromise between unstructured web pages (semantically speaking) and fully-structured RDF
	- 80% of the value with 20% of the work
	- easy to implement, and standardized so web authors don't have to worry about ontologies
operator - extracts these microformats from web pages so that they can actually be used

in a future of many types of microformats all over, you might want to store them for later use.
a "structured history" of visits - "I know I saw his contact info somewhere.." search and browse to find the information.

actually, structured bookmarks - it's a way of saving all of the metadata that has been marked up on the page, instead of just the page.  an alternative is tagging - but with packrat you don't even have to specify tags.

since this will end up being a lot of data if used over time, we want to store in a SQL database.

database issues
informal mf schemas -> formal db
use of columns as foreign key

• What is PackRat for - bookmarking structured data
• What are Microformats - easy repr. structured data on web
• Operator - FF extension, slated for inclusion in 3.0 - parses mfs and allows extension
• PackRat implementation/ DB issues - needs to scale to large #s of mfs
	- sqlite table schema conversion issues - text columns
	- sub-mfs and sub-props - cross referenced
	- export to exhibit
	- bridge between 3 different data schemas - each optimized for different purposes
	- general - not schema specific
• Demo - hCard
	- if time, hCite