picoformats: Difference between revisions
Jump to navigation
Jump to search
(adding references to other services' vocabulae) |
m (typo) |
||
| Line 5: | Line 5: | ||
Using the Microformats process and principles of building block design, our goal is to openly develop a complete syntax for interacting with various mobile services using the characters available on most mobile devices. | Using the Microformats process and principles of building block design, our goal is to openly develop a complete syntax for interacting with various mobile services using the characters available on most mobile devices. | ||
== References == | |||
* Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags] | * Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags] | ||
* [http://www.dodgeball.com/glossary Dodgeball Glossary] | * [http://www.dodgeball.com/glossary Dodgeball Glossary] | ||
* [http://twttr.com/t/help/lingo twttr lingo] | * [http://twttr.com/t/help/lingo twttr lingo] | ||
Revision as of 17:17, 21 July 2006
Picoformats represent an effort being undertaken by Chris Messina and Andy Stack of Mozes to codify various standards and openly pursue a nomenclature and syntax for communicating and executing commands with mobile devices over SMS.
An example application is Dodgeball's use of the at symbol (@) to express checking in to a place.
Using the Microformats process and principles of building block design, our goal is to openly develop a complete syntax for interacting with various mobile services using the characters available on most mobile devices.