microformat-aggregation: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<entry-title>Microformat Aggregation</entry-title>
{{DISPLAYTITLE:Microformat Aggregation}}


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.


Three Main Projects
Four Main Projects


* [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)
* [Parser] create new lxml-based parser in Python (Andrew)  


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 21: Line 22:
PROJECT URLS
PROJECT URLS


* http://github.com/amccollum/microtron
* http://github.com/peliom/mfgae/tree/master
* http://github.com/peliom/mfgae/tree/master
* http://mfgae1.appspot.com/
* http://mfgae1.appspot.com/
* http://semabox.com/mfcrawl


INFO
INFO

Latest revision as of 16:29, 18 July 2020


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.

Four 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)
  • [Parser] create new lxml-based parser in Python (Andrew)

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