picoformats: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(→‎Service-Specific: +GIFT http://docs.moodle.org/en/GIFT_format)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<entry-title>picoformats</entry-title>
{{DISPLAYTITLE:picoformats}}
;short URL
;short URL
:http://tr.im/picoformats
:http://ufs.cc/w/pf
 
<div style="background:#EFE;padding:1em">
See the latest work being done on this in the IndieWebCamp community:
* https://indiewebcamp.com/microsyntax
</div>
 
== Introduction ==
== 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 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).
Line 45: Line 51:


=== Generic ===
=== Generic ===
 
* @-replies (at start), @-mentions (everywhere in content)
* @-replies
* #-hashtags
* [http://hashtags.org/ hashtags]
* [http://buzzword.org.uk/2009/microturtle/spec MicroTurtle]
* [http://buzzword.org.uk/2009/microturtle/spec MicroTurtle]
* [http://microsyntax.org/ microsyntax.org]
* [http://twitterdata.org/ twitterdata.org]
* [http://civilities.net/Star_Priority_Notation Star Priority]


=== Service-Specific ===
=== Service-Specific ===
Line 81: Line 83:
* [http://www.kiboze.com/kiboze/CustWorks.aspx Kiboze How it Works]
* [http://www.kiboze.com/kiboze/CustWorks.aspx Kiboze How it Works]
* 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://web.archive.org/web/20090414182811/http://www.dodgeball.com/glossary Dodgeball Glossary]
* [http://twttr.com/t/help/lingo twttr lingo]
* [http://twttr.com/t/help/lingo twttr lingo]
* Twitter (or Jaiku) [[twitter-nanoformats]] brainstorm [http://twitternanoformats.wikispaces.com/ A proposal for Twitter nanoformats]
* Twitter (or Jaiku) [[twitter-nanoformats]] brainstorm [http://twitternanoformats.wikispaces.com/ A proposal for Twitter nanoformats]
Line 89: Line 91:
== concept ==
== 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.
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

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:

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?

References

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.

See Also