= BluePrint for Message Parser =
[[TOC]]

== Current Status ==
See DeveloperGuidelines/Messaging/Parser

== Plans ==
See [wiki:BluePrint/Messaging/ExtendingParsing BluePrint/Messaging/ExtendingParsing] 

== Notes ==
[http://pyparsing.wikispaces.com Pyparsing] is included in the modules folder.

This can decode messages, especially from compressed formats such as Tweets or SMS but also free-from formats such as email.

We could add further text processing such as our implementation of [http://en.wikipedia.org/wiki/Levenshtein_distance Levenshtein], [http://en.wikipedia.org/wiki/Jaro%E2%80%93Winkler_distance Jaro-Winkler Distance], [http://code.google.com/p/seentags/wiki/Algorithm SeenTags] or [http://organic.elis.ugent.be/oger Oger].

Alternative:
 * [http://github.com/ushahidi/SiLCC RESTful semantic tag extraction application for SMS, Twitter and Text]

==== Micro-Syntax ====
 * [http://en.wikipedia.org/wiki/Geohash GeoHashes]
  * [http://pypi.python.org/pypi/Geohash/ Python lib]
 * Tweets
  * [http://dev.twitter.com/doc/get/geo/:id Geotagging] where hardware/software combination available: place_id from http://twitter.com/{username}/statuses/{tweet_id}.json -> http://api.twitter.com/1/geo/id/{place_id}.json
  * otherwise use WW place WW message:
   * http://www.weather.gov/stormreports/
   * http://www.srh.noaa.gov/media/epz/Twitter/TwitterStormReportProgram.wmv
  * EPIC's [http://epic.cs.colorado.edu/tweak-the-tweet/helping_haiti_tweak_the_twe.html Tweak the Tweet]
 * SMS
  * geo lat lon
  * [http://www.opengeospatial.org/pressroom/pressreleases/1251 OGC GeoSMS standard]
  * http://en.wikipedia.org/wiki/Geo_%28microformat%29
  * http://nyaruka.github.com/rapidsms-xforms-builder/#getting-started
  * http://groups.google.com/group/rapidsms/browse_thread/thread/5cbac8c80d91ccae
  * Codes looked up on a paper wheel:
   * http://mekongict.org/2010/06/user-oriented-design/ (slide 23 on)
   * http://ndt.instedd.org/2010/05/it-without-software.html