microformat-aggregation: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:
A project worked on at [[events/2009-07-25-dev-camp|microformatsDevCamp]]
A project worked on at [[events/2009-07-25-dev-camp|microformatsDevCamp]]


Jesse - jessehammons@peliom.net
* Jesse - jessehammons@peliom.net
Andrew - am2collum@gmail.com
* Andrew - am2collum@gmail.com
Dane - dane.hurtubise@gmail.com
* Dane - dane.hurtubise@gmail.com
Randy - randy@randykerber.com
* Randy - randy@randykerber.com
Yury - yurilifshits@gmail.com
* Yury - yury@yury.name


Extract microformats data from the web and provide access to it through JSON. Run at App Engine.
Extract microformats data from the web and provide access to it through JSON. Run at App Engine.
Line 15: Line 15:
* [In-Browser] Use xslt.js to extract microformats from HTML documents using Optimus's XSLT stylesheet (Dane,Andrew,works!)
* [In-Browser] Use xslt.js to extract microformats from HTML documents using Optimus's XSLT stylesheet (Dane,Andrew,works!)
* [GAE] upload AUMP and BeautifulSoup to google app engine to parse microformats (Jesse)
* [GAE] upload AUMP and BeautifulSoup to google app engine to parse microformats (Jesse)
* [Hosted] use lxml/python on personal server to parse microformats (Yury)
* [Hosted] use lxml/python on personal server to parse microformats (Yury, first version works at http://semabox.com/mfcrawl)


The primary output of this project was that there is little or no support for XSLT on Google App Engine.  Because the canonical programmatic description of microformats is in Optimus, this presents a problem.
The primary output of this project was that there is little or no support for XSLT on Google App Engine.  Because the canonical programmatic description of microformats is in Optimus, this presents a problem.
Line 25: Line 25:


INFO
INFO
* http://semabox.com/mfcrawl
* http://code.google.com/p/aump/downloads/list
* http://code.google.com/p/aump/downloads/list
* http://www.crummy.com/software/BeautifulSoup/
* http://www.crummy.com/software/BeautifulSoup/
* http://code.google.com/p/googleappengine/issues/detail?id=1255&q=xpath&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component
* http://code.google.com/p/googleappengine/issues/detail?id=1255&q=xpath&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component

Revision as of 04:27, 26 July 2009

<entry-title>Microformat Aggregation</entry-title>

A project worked on at microformatsDevCamp

  • Jesse - jessehammons@peliom.net
  • Andrew - am2collum@gmail.com
  • Dane - dane.hurtubise@gmail.com
  • Randy - randy@randykerber.com
  • Yury - yury@yury.name

Extract microformats data from the web and provide access to it through JSON. Run at App Engine.

Three Main Projects

  • [In-Browser] Use xslt.js to extract microformats from HTML documents using Optimus's XSLT stylesheet (Dane,Andrew,works!)
  • [GAE] upload AUMP and BeautifulSoup to google app engine to parse microformats (Jesse)
  • [Hosted] use lxml/python on personal server to parse microformats (Yury, first version works at http://semabox.com/mfcrawl)

The primary output of this project was that there is little or no support for XSLT on Google App Engine. Because the canonical programmatic description of microformats is in Optimus, this presents a problem.

PROJECT URLS

INFO