<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=CnacoAcele</id>
	<title>Microformats Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=CnacoAcele"/>
	<link rel="alternate" type="text/html" href="https://microformats.org/wiki/Special:Contributions/CnacoAcele"/>
	<updated>2026-05-13T19:44:11Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.38.4</generator>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=picoformats&amp;diff=37235</id>
		<title>picoformats</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=picoformats&amp;diff=37235"/>
		<updated>2009-01-05T06:21:19Z</updated>

		<summary type="html">&lt;p&gt;CnacoAcele: monlav&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;liboolo&lt;br /&gt;
&amp;lt;h1&amp;gt;picoformats&amp;lt;/h1&amp;gt;&lt;br /&gt;
{{TOC-right}}&lt;br /&gt;
== Introduction ==&lt;br /&gt;
Picoformats represent an effort being undertaken led by Chris Messina to codify various standards and openly pursue a nomenclature and syntax for communicating and executing commands with mobile devices over SMS or via command line interfaces (CLI).&lt;br /&gt;
&lt;br /&gt;
An example application is [http://dodgeball.com Dodgeball's] use of the at symbol (@) to express checking in to a place.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Problem Statement ==&lt;br /&gt;
* send messages to user mobiles - via SMS, or a small application, that contains information like appointment times, locations,&lt;br /&gt;
directions, and contact info. For example, when2where.com reminds users when they need to leave to get to their appointment, so the&lt;br /&gt;
message may be like:&lt;br /&gt;
&lt;br /&gt;
 leave @ 4:35PM ~Dentist Office -&amp;gt; Detroit, MI&lt;br /&gt;
&lt;br /&gt;
where the text itself is simple and readable, but there *may* be an small utility that would parse the @ symbol to add the event to the calendar, the ~ to allow the person to quickly call that contact, or the -&amp;gt; to pull up a Map/directions to the location&lt;br /&gt;
&lt;br /&gt;
* allow users to write messages to query an application - this is similar to what Mozes has started with notes:&lt;br /&gt;
&lt;br /&gt;
 when2where: ?today    --- what appointments to I have today&lt;br /&gt;
 new @ 4PM ~Olive Garden -&amp;gt; Novi     --- add an appointment&lt;br /&gt;
&lt;br /&gt;
In addition to the obvious mobile device arena, picoformats may be usable in any context where &amp;quot;markup&amp;quot; is too heavy. For example, an IRC bot, whereisbot, that announces user locations as they sign into a channel, or allows people to do:&lt;br /&gt;
&lt;br /&gt;
 .whereami, or .whereis &amp;lt;nick&amp;gt; to geolocate other people in a channel.&lt;br /&gt;
&lt;br /&gt;
The intention is to 'markup' the information, but putting actual XHTML or XML is annoying, since IRC doesn't parse the information at all. So right now the response is:&lt;br /&gt;
&lt;br /&gt;
 ajturner: .whereami&lt;br /&gt;
 whereisbot: ajturner is in Northville, MI, US  [42.4365 x -83.4884]&lt;br /&gt;
&lt;br /&gt;
So then someone could write a Picoformat parser for X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide a Map url link.&lt;br /&gt;
&lt;br /&gt;
Using arrows to denote time and place, familiar from video recorders and other devices.&lt;br /&gt;
Some thoughts: &amp;lt;past  &amp;gt;future  ^now (the hat is also mnemonic for Here + At)  or &amp;gt;5 (in five days time) &amp;gt;&amp;gt;5 (in 5 weeks time) &amp;gt;&amp;gt;&amp;gt;5 (5 months)&lt;br /&gt;
 &lt;br /&gt;
 Meeting &amp;lt;Leeds went well. ^Home. See you &amp;gt;london&lt;br /&gt;
 Sorry, saw them &amp;lt;&amp;lt;2 wanna go see film &amp;gt;3?&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;Documented_Syntaxes&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Syntaxes ==&lt;br /&gt;
&lt;br /&gt;
* [[actiontastic-syntax | Actiontastic]]&lt;br /&gt;
* [[brightkite-syntax| BrightKite]]&lt;br /&gt;
* [[dodgeball-syntax| Dodgeball]]&lt;br /&gt;
* [[dopplr-syntax | Dopplr]]&lt;br /&gt;
* [[facebook-syntax | Facebook Mobile]]&lt;br /&gt;
* [[igtd-syntax | iGTD]]&lt;br /&gt;
* [[kiboze-syntax|Kiboze]]&lt;br /&gt;
* [[jaiku-syntax|Jaiku]]&lt;br /&gt;
* [[mixd-syntax | Mixd]]&lt;br /&gt;
* [[plazes-syntax | Plazes]]&lt;br /&gt;
* [[poi66-syntax | POI66]] - [http://www.poi66.com/maps/step1.php]&lt;br /&gt;
* [[quickpack-syntax | QuickPack]]&lt;br /&gt;
* [[remember-the-milk | Remember the Milk for Twitter]]&lt;br /&gt;
* [[stikkit-syntax | Stikkit]] [http://stikkit.com/]&lt;br /&gt;
* [[swaggle-syntax | Swaggle]] [http://swaggle.mobi/]&lt;br /&gt;
* [[textmarks-syntax|Textmarks]]&lt;br /&gt;
* [[tfl-syntax | Transport for London]]&lt;br /&gt;
* [[tripit-syntax | TripIt]]&lt;br /&gt;
* [[twitter-syntax | Twitter]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* [http://www.kiboze.com/kiboze/CustWorks.aspx Kiboze How it Works]&lt;br /&gt;
* Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags]&lt;br /&gt;
* [http://www.dodgeball.com/glossary Dodgeball Glossary]&lt;br /&gt;
* [http://twttr.com/t/help/lingo twttr lingo]&lt;br /&gt;
* Twitter (or Jaiku) [[twitter-nanoformats]] brainstorm [http://twitternanoformats.wikispaces.com/ A proposal for Twitter nanoformats]&lt;br /&gt;
* [http://skobee.com/email_howto Skobee's email syntax]&lt;br /&gt;
* [https://www.billmonk.com/about/sms BillMonk syntax]&lt;br /&gt;
&lt;br /&gt;
== concept ==&lt;br /&gt;
Thanks to [http://factoryjoe.com/blog Chris Messina] for collecting a bunch of common work in this area, and exploring the area of short semi-structured text for potential &amp;quot;formats&amp;quot; of a sort that could be agreed upon, perhaps among multiple providers to make it easier for users to remember a common user interface.&lt;/div&gt;</summary>
		<author><name>CnacoAcele</name></author>
	</entry>
</feed>