picoformats: Difference between revisions

Latest revision as of 16:31, 18 July 2020

short URL: http://ufs.cc/w/pf

See the latest work being done on this in the IndieWebCamp community:

https://indiewebcamp.com/microsyntax

Introduction

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).

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.

Problem Statement

send messages to user mobiles - via SMS, or a small application, that contains information like appointment times, locations,

directions, and contact info. For example, when2where.com reminds users when they need to leave to get to their appointment, so the message may be like:

leave @ 4:35PM ~Dentist Office -> Detroit, MI

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 -> to pull up a Map/directions to the location

allow users to write messages to query an application - this is similar to what Mozes has started with notes:

when2where: ?today    --- what appointments to I have today
new @ 4PM ~Olive Garden -> Novi     --- add an appointment

In addition to the obvious mobile device arena, picoformats may be usable in any context where "markup" is too heavy. For example, an IRC bot, whereisbot, that announces user locations as they sign into a channel, or allows people to do:

.whereami, or .whereis <nick> to geolocate other people in a channel.

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:

ajturner: .whereami
whereisbot: ajturner is in Northville, MI, US  [42.4365 x -83.4884]

So then someone could write a Picoformat parser for X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide a Map url link.

Using arrows to denote time and place, familiar from video recorders and other devices. Some thoughts: <past >future ^now (the hat is also mnemonic for Here + At) or >5 (in five days time) >>5 (in 5 weeks time) >>>5 (5 months)

Meeting <Leeds went well. ^Home. See you >london
Sorry, saw them <<2 wanna go see film >3?

Syntaxes

Generic

@-replies (at start), @-mentions (everywhere in content)
#-hashtags
MicroTurtle

Service-Specific

References

Kiboze How it Works
Flagr: Creating mobile flags
Dodgeball Glossary
twttr lingo
Twitter (or Jaiku) twitter-nanoformats brainstorm A proposal for Twitter nanoformats
Skobee's email syntax
BillMonk syntax

concept

Thanks to Chris Messina for collecting a bunch of common work in this area, and exploring the area of short semi-structured text for potential "formats" of a sort that could be agreed upon, perhaps among multiple providers to make it easier for users to remember a common user interface.

@@ Line 1: / Line 1: @@
-= Picoformats =
+{{DISPLAYTITLE:picoformats}}
+;short URL
+:http://ufs.cc/w/pf
-== Contributors ==
+<div style="background:#EFE;padding:1em">
-* [http://highearthorbit.com Andrew Turner]
+See the latest work being done on this in the IndieWebCamp community:
-* [http://factoryjoe.com/blog Chris Messina]
+* https://indiewebcamp.com/microsyntax
-* Andy Stack, [http://mozes.com Mozes]
+</div>
 == Introduction ==
+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).
-Picoformats represent an effort being undertaken by [http://factoryjoe.com/blog Chris Messina] and Andy Stack of [http://mozes.com Mozes] 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).
 An example application is [http://dodgeball.com Dodgeball's] use of the at symbol (@) to express checking in to a place.
@@ Line 15: / Line 16: @@
 == Problem Statement ==
+* send messages to user mobiles - via SMS, or a small application, that contains information like appointment times, locations,
-# send messages to user mobiles - via SMS, or a small application,
+directions, and contact info. For example, when2where.com reminds users when they need to leave to get to their appointment, so the
-that contains information like appointment times, locations,
-directions, and contact info. For example, when2where.com reminds
-users when they need to leave to get to their appointment, so the
 message may be like:
   leave @ 4:35PM ~Dentist Office -> Detroit, MI
-where the text itself is simple and readable, but there *may* be an
+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 -> to pull up a Map/directions to the location
-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 -> to pull up a Map/directions to the location
-# allow users to write messages to query an application - this is
+* allow users to write messages to query an application - this is similar to what Mozes has started with notes:
-similar to what Mozes has started with notes:
-  when2where: ?today    --- what appointements to I have today
+  when2where: ?today    --- what appointments to I have today
   new @ 4PM ~Olive Garden -> Novi     --- add an appointment
-In addition to the obvious mobile device arena, I think picoformats
+In addition to the obvious mobile device arena, picoformats may be usable in any context where "markup" is too heavy. For example, an IRC bot, whereisbot, that announces user locations as they sign into a channel, or allows people to do:
-are usable in any context where "markup" is too heavy. For example, I
-also just put together an IRC bot, whereisbot, that announces user
-locations as they sign into a channel, or allows people to do:
   .whereami, or .whereis <nick> to geolocate other people in a channel.
-I want to 'markup' the information, but putting actual XHTML or XML is
+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:
-annoying, since IRC doesn't parse the information at all. So right now
-the response is:
   ajturner: .whereami
   whereisbot: ajturner is in Northville, MI, US  [42.4365 x -83.4884]
-So then someone could write a Picoformat parser for
+So then someone could write a Picoformat parser for X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide a Map url link.
-X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide
-a Map url link.
 Using arrows to denote time and place, familiar from video recorders and other devices.
@@ Line 59: / Line 46: @@
   Sorry, saw them <<2 wanna go see film >3?
-== Documented Syntaxes ==
+<div id="Documented_Syntaxes">
+== Syntaxes ==
+=== Generic ===
+* @-replies (at start), @-mentions (everywhere in content)
+* #-hashtags
+* [http://buzzword.org.uk/2009/microturtle/spec MicroTurtle]
+=== Service-Specific ===
 * [[actiontastic-syntax | Actiontastic]]
+* [[brightkite-syntax| BrightKite]]
+* [[dodgeball-syntax| Dodgeball]]
 * [[dopplr-syntax | Dopplr]]
 * [[facebook-syntax | Facebook Mobile]]
+* [[gift-syntax | GIFT]] quizes[http://docs.moodle.org/en/GIFT_format]
 * [[igtd-syntax | iGTD]]
 * [[kiboze-syntax|Kiboze]]
+* [[jaiku-syntax|Jaiku]]
 * [[mixd-syntax | Mixd]]
 * [[plazes-syntax | Plazes]]
+* [[poi66-syntax | POI66]] - [http://www.poi66.com/maps/step1.php]
 * [[quickpack-syntax | QuickPack]]
-* [[stikkit-syntax | Stikkit]] http://stikkit.com/
+* [[remember-the-milk | Remember the Milk for Twitter]]
+* [[stikkit-syntax | Stikkit]] [http://stikkit.com/]
+* [[swaggle-syntax | Swaggle]] [http://swaggle.mobi/]
 * [[textmarks-syntax|Textmarks]]
 * [[tfl-syntax | Transport for London]]
+* [[tripit-syntax | TripIt]]
 * [[twitter-syntax | Twitter]]
+</div>
 == References ==
 * [http://www.kiboze.com/kiboze/CustWorks.aspx Kiboze How it Works]
 * Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags]
-* [http://www.dodgeball.com/glossary Dodgeball Glossary]
+* [http://web.archive.org/web/20090414182811/http://www.dodgeball.com/glossary Dodgeball Glossary]
 * [http://twttr.com/t/help/lingo twttr lingo]
-* [http://twitternanoformats.wikispaces.com/ A proposal for Twttr nanoformats]
+* Twitter (or Jaiku) [[twitter-nanoformats]] brainstorm [http://twitternanoformats.wikispaces.com/ A proposal for Twitter nanoformats]
 * [http://skobee.com/email_howto Skobee's email syntax]
-* [http://www.meetmoi.com/1/meetmoi?wicket:bookmarkablePage=:com.mdate.web.GettingStarted#11 MeetMoi syntax]
 * [https://www.billmonk.com/about/sms BillMonk syntax]
+== concept ==
+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 "formats" of a sort that could be agreed upon, perhaps among multiple providers to make it easier for users to remember a common user interface.
+== See Also ==
+* http://www.dumbsto.re/apps - apps that operate purely via txt message commands and work with any phone that supports SMS.
+* https://indiewebcamp.com/microsyntax - latest thoughts on a lot of text-based picoformats/microsyntax

picoformats: Difference between revisions

Latest revision as of 16:31, 18 July 2020

Contents

Introduction

Problem Statement

Syntaxes

Generic

Service-Specific

References

concept

See Also

Navigation menu

picoformats: Difference between revisions

Latest revision as of 16:31, 18 July 2020

Introduction

Problem Statement

Syntaxes

Generic

Service-Specific

References

concept

See Also

Navigation menu

Search