Microformats Wiki - User contributions [en]

microblogging-nanoformats

2008-01-10T09:54:38Z

TekeTen: /* Open discussions */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

== Specification ==

; Editor : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
; Authors : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
: ...

=== Copyright ===
Per the public domain release on the authors' user pages ([[User:TekeTen|Gorka Julio]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

<div id="Some_apps_supporting_some_kind_of_nanoformat">

==Implementations==
Some apps supporting some kind of nanoformat:

* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foamee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event

</div>

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note -> this can be done using vote or rate nanoformats
** Example: @psd++ for updating this page, thanks also to @factoryjoe L:Berkhamsted,UK #microformats

* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** We gave more flexible description to #tag and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==

'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2008-01-10T09:53:53Z

TekeTen: /* Using more than one nanoformat in the same post */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

== Specification ==

; Editor : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
; Authors : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
: ...

=== Copyright ===
Per the public domain release on the authors' user pages ([[User:TekeTen|Gorka Julio]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

<div id="Some_apps_supporting_some_kind_of_nanoformat">

==Implementations==
Some apps supporting some kind of nanoformat:

* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foamee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event

</div>

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note -> this can be done using vote or rate nanoformats
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** We gave more flexible description to #tag and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==

'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2008-01-09T09:51:16Z

TekeTen: /* Some apps supporting some kind of nanoformat */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

== Specification ==

; Editor : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
; Authors : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
: [http:// Your name here!]

=== Copyright ===
Per the public domain release on the authors' user pages ([[User:TekeTen|Gorka Julio]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foamee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note -> this can be done using vote or rate nanoformats
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** We gave more flexible description to #tag and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2008-01-04T12:44:52Z

TekeTen: /* Open discussions */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

== Specification ==

; Editor : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
; Authors : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
: [http:// Your name here!]

=== Copyright ===
Per the public domain release on the authors' user pages ([[User:TekeTen|Gorka Julio]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note -> this can be done using vote or rate nanoformats
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** We gave more flexible description to #tag and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2008-01-04T12:43:22Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

== Specification ==

; Editor : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
; Authors : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
: [http:// Your name here!]

=== Copyright ===
Per the public domain release on the authors' user pages ([[User:TekeTen|Gorka Julio]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

User:TekeTen

2008-01-02T23:50:58Z

TekeTen:

<div class="vcard"><span class="fn">Gorka Julio</span> (<span class="url" href="http://www.teketen.com">http://www.teketen.com</span>)</div>
----
{{cc-public-domain-release}}

User:TekeTen

2008-01-02T23:50:35Z

TekeTen:

<div class="vcard"><span class="fn">Gorka Julio</span><span class="url" href="http://www.teketen.com">http://www.teketen.com</span></div>
----
{{cc-public-domain-release}}

User:TekeTen

2008-01-02T23:49:51Z

TekeTen:

<div class="vcard"><span class="fn">Gorka Julio</span><span class="url" href="http://www.teketen.com"></span></div>
----
{{cc-public-domain-release}}

User:TekeTen

2008-01-02T23:47:55Z

TekeTen:

<div class="vcard">
(<span class="url fn n" href="http://www.teketen.com">)
<span class="given-name">Gorka</span> <span class="family-name">Julio</span>
</span>
</div>

{{cc-public-domain-release}}

User:TekeTen

2008-01-02T23:35:46Z

TekeTen:

<div class="vcard">
<span class="url fn n" href="http://www.teketen.com">
<span class="given-name">Gorka</span> <span class="family-name">Julio</span>
</span>
</div>

{{cc-public-domain-release}}

User:TekeTen

2008-01-02T23:33:17Z

TekeTen:

<div class="vcard">
<img style="float: left; margin-right: 4px;" src="http://site.gravatar.com/images/files/thumbs/124267.jpg" class="photo">
<a class="url fn n" href="http://www.teketen.com">
<span class="given-name">Gorka</span> <span class="family-name">Julio</span>
</a>
</div>
{{cc-public-domain-release}}

microblogging-nanoformats

2008-01-02T23:30:08Z

TekeTen: /* Copyright */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

== Specification ==

; Editor : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
; Authors : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
: [http:// Your name here!]

=== Copyright ===
Per the public domain release on the authors' user pages ([[User:TekeTen|Gorka Julio]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2008-01-02T23:27:47Z

TekeTen: /* Twitter (or Jaiku) nanoformats proposal */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

== Specification ==

; Editor : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
; Authors : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
: [http:// Your name here!]

=== Copyright ===
Per the public domain release on the authors' user pages ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2008-01-02T15:37:20Z

TekeTen: /* Some apps supporting some kind of nanoformat */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:58:53Z

TekeTen: /* Open discussions */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* ['''approved'''] proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:55:59Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group use example)
o Syntax: #<tag>
o Tools: #tag filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:55:28Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group example use)
o Syntax: #<tag>
o Tools: #tag filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:55:06Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts ['''discussion''']
o Example: kauta concert at Doka #music
o Example: #rockclub kauta concert tonight (group example use)
o Syntax: #<tag>
o Tools: #tag filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:49:48Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #tag
o Used to tag posts ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:48:40Z

TekeTen:

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> use #tag

=== 1nanoformats (syntaxparam) ===
* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa #summer #night
* Generic Example: <message> <other nanoformats one each other> <#tag>*
[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:44:07Z

TekeTen: /* Deprecated */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:43:30Z

TekeTen: /* 2nanoformats (syntax:param) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===Deprecated===
* play:<object> -> use enclosure
* tag:<tag> -> user #tag

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:37:20Z

TekeTen: /* Open discussions */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description and deprecate''' tag''' nanoformat.

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:35:26Z

TekeTen: /* Open discussions */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can we propose the change?
** note: this can be done using vote or rate nanoformats
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/
** interesting my proposal is to give more flexible description.

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:25:21Z

TekeTen: /* Open discussions */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com.
** question: is more regular to use ++ and -- before the word. Can you change plusplus? or support in some way?
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-16T10:19:00Z

TekeTen: /* Some apps supporting some kind of nanoformat */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar, hListing, hCard)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats), however ++tag isn't supported by http://plusplusbot.com
* proposal to use #group not only for groups, but for tags based common usage observed on Twitter as supported by http://hashtags.org/

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-14T22:30:45Z

TekeTen: /* Open discussions */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed better way can be ++tag or --tag (the same as other 1nanoformats)
* #group not only for groups, why is proposed to use with tags? More info needed!

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-14T22:30:04Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed
* #group not only for groups, why is proposed to use with tags? More info needed!

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''']
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''')
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''')
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-14T22:28:47Z

TekeTen:

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

===Open discussions===
* tag++ and tag-- are been discussed
* #group not only for groups, why is proposed to use with tags? More info needed!

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) ['''discussion''' or a tag]
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe
* tag++ ('''discussion''', better way can be ++tag)
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''', better way can be --tag)
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-12-14T22:22:07Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)
* [http://plusplusbot.com plusplus bot] tag++, @username++ to vote for or tag-- to vote against a tag or user
* [http://foammee.com foamee] @ioubeer @twitterscreenname for being an amazing human being

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe, [http://foamee.com/ foamee]
* #group
o Used to mention a group (more than one user) or a tag
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group or tag>
o Tools: #group filter pipe
* tag++ ('''discussion''', better way can be ++tag)
o Used to 'plusplus' (vote for) a user or subject
o Example: microformats++ because they rock the disco!
o Syntax: <tag-name>++
o Tools: [http://plusplusbot.com plusplus bot]
* tag-- ('''discussion''', better way can be --tag)
o Used to 'minusminus' (vote against) a user or subject
o Example: drm-- for breaking my backups
o Syntax: <tag-name>--
o Tools: [http://plusplusbot.com plusplus bot]

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code> at the end of a tweet
+ info [http://api.twittervision.com/api.html Twittervision API], [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: [http://twittervision.com Twittervision], [http://api.twittervision.com/api.html Twittervision API], location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party time:2007-06-23 22:00 L:Ondarreta beach, Donostia
* Generic example: <message> <nanoformats one each other>

* Exception: @username commonly used at the start of the twit.
* Example: @teketen I disagree with you!
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: 1nanoformats. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-09-20T12:43:08Z

TekeTen: /* 2nanoformats (syntax:param) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe
* #group
o Used to mention a group (more than one user).
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* note:
o Used to write a simple note.
o Example: note:printer ink catridge numbers HP336 / HP342
o Syntax: note:<note subject>
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-09-15T08:48:04Z

TekeTen: /* 3nanoformats (syntax:param:param) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe
* #group
o Used to mention a group (more than one user).
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer:n50 pda or deal:wanted:http://www.nabaztag.com
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-09-15T08:35:05Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Used to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe
* #group
o Used to mention a group (more than one user).
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer n50 pda 1 year use
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-09-15T08:34:47Z

TekeTen: /* 2nanoformats (syntax:param) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe
* #group
o Use to mention a group (more than one user).
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe

===2nanoformats (syntax:param)===

* lang:
o Used to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Used for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Used to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Used to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Used to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer n50 pda 1 year use
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-09-15T08:33:58Z

TekeTen: /* 3nanoformats (syntax:param:param) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe
* #group
o Use to mention a group (more than one user).
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Used for rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Used for vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transaction info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer n50 pda 1 year use
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-09-15T08:30:10Z

TekeTen:

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe
* #group
o Use to mention a group (more than one user).
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe
* deal:
o Used for transactional info (sell, rent, trade, wanted, offer, announce).
o Example: deal:sell:acer n50 pda 1 year use
o Syntax: deal:<sell,rent,trade,wanted,offer,announce>:<transaction subject>

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-08-30T16:10:01Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe
* #group
o Use to mention a group (more than one user).
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-08-30T16:09:34Z

TekeTen: /* 1nanoformats (syntaxparam) */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

* #group
o Use to mention a group (more than one user).
o Example: #rockclub kauta concert tonight
o Syntax: #<twitter group>
o Tools: #group filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

geo

2007-08-11T09:33:25Z

TekeTen: /* Examples in the wild */

<h1> geo </h1>
*http://rbach.priv.at/2006/buttons/geo.png
'''geo''' (pronounced "gee-oh") is a simple format for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the "geo" property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

== Draft Specification ==

;Editor/Author
: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])

=== Copyright ===
Per the public domain release on [[User:Tantek|my user page]], this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to everyone who participated in the [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], and in particular to [http://radar.oreilly.com/nat/ Nat Torkington] and Vee McMillen of [http://oreilly.com O'Reilly] for [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 arranging and hosting the BOF]. Thanks to Chris Hibbbert for providing the [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f real world geo-caching example].

== Introduction and Background ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly and interoperably implemented (e.g. Apple's Address Book application). The [[hcard|hCard]] microformat has similarly received significant adoption, from numerous sites publishing the format, to hCard to vCard proxies, to clientside javascript parsers.

At the [http://conferences.oreillynet.com/where/ Where 2.0 conference] in June 2005, there was widespread recognition that the community needed a way to simply and easily publish visible, extractable, geographic location information on the Web, given how often bloggers, and numerous other sites publish such information. The [[geo-bof-2005-06-30|geo microformat BOF]] discussed this very topic, and concluded with a consensus decision to just try using ''geo'' from vCard/hCard.

This specification introduces the '''geo''' microformat, which is a 1:1 representation of the aforementioned ''geo'' property from the vCard standard, by simply reusing the ''geo'' property and sub-properties as-is from the [[hcard|hCard]] microformat.

Publishers can both embed '''geo''' addresses directly in their web pages and feeds, as well as markup existing latitude/longitude coordinates in the context of the rest of the information in their web pages and feeds.

If the publisher knows and is publishing the ''name'' of the location in addition to its geo lat/long, then the publisher MUST use [[hcard|hCard]] instead of just '''geo''' to publish the name and geo lat/long of the location.

If the publisher knows and is publishing the address of the location, OR if the address of the location was what was actually entered by a human, and the publisher simply turned that into lat/long using some sort of a service, then the publisher SHOULD use [[adr]] to publish the actual human entered address information since that communicates far more semantic information than a simple geo lat/long coordinate.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== Singular Properties ===

Note that all the properties in '''geo''' are singular properties, and thus the first descendant element with that class should take effect, any others being ignored.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the <code>title</code> attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. For this purpose, the special class name <code>value</code> is used to excerpt out the subset of the element that is the value of the property. See [[hcard|hCard]] for details on this.

=== Root Class Name ===

The root class name for an geo location is <code>geo</code>.

=== Property List ===

This is the list of properties in geo, taken from [[hcard|hCard]]:

* latitude
* longitude

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]], with the only difference being that "geo" is the root class name, rather than "vcard".

== Examples ==

This section is informative.

=== Example from RFC2426 ===

Section 3.4.2 of RFC2426 has a simple geo example:

<pre><nowiki>
GEO:37.386013;-122.082932
</nowiki></pre>

this vCard fragment as a geo, as [http://microformats.org/wiki/hcard-examples#3.4.2_GEO_Type_Definition first documented on the hCard examples page]:

<pre><nowiki>
<div class="geo">GEO:
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
</div>
</nowiki></pre>

this geo could be displayed as: 

<div class="geo">GEO: <span class="latitude">37.386013</span>, <span class="longitude">-122.082932</span></div>

Note that this is a '''live''' geo microformat, which will be found on this page by parsers.

=== Real world geo example ===

Here is a sample of published lat/long info (from [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f geocaching: Noble Steed]):

<pre><nowiki>
N 37° 24.491 W 122° 08.313
</nowiki></pre>

With geo markup:

<pre><nowiki>
<div class="geo">
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr>
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>
</nowiki></pre>

This geo might be displayed as: 

<div class="geo"><abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>

Again, this is a '''live''' example.

Note that since the real world example used a more human readable presentation of the geo coordinates, we use the [[abbr-design-pattern]] to keep that more human readable presentation, and in addition provide the respective absolute numerical values for the geo.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published geos, outside their normal context of hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc., in addition to those in many [[hcard-examples-in-wild|hCard examples in the wild]]. If you find geos outside of hCards anywhere else, feel free to add them to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

Pages with live Geo can use this button (see [[buttons#Geo]] for any recent additions): http://rbach.priv.at/2006/buttons/geo.png


* [http://www.navitraveler.com/places/629/ NaviTraveler], e. g. [http://www.navitraveler.com/places/629/Lincoln_Memorial.html Lincoln Memorial].
** Response in under 12 hours, to advocacy request - [[User:AndyMabbett|Andy Mabbett]]
*[http://caving.atspace.com/ Caving in the Settle Area] uses Geo to mark up the U.K. NGR for cave locations.
*[http://gc.kls2.com/ Great Circle Mapper] ("GCM"; e.g. [http://tinyurl.com/yugscj sample GCM trip], [http://gc.kls2.com/airport/BHX BHX on GCM])
* [http://www.creation.uk.com Creation design & marketing] has Geo microformat on the [http://www.creation.uk.com/contact/ contact information].
* Wikipedia now has a template, [http://en.wikipedia.org/wiki/Template:Hcard-geo hcard-geo], for in-line hCards with coordinates, using Geo, such as that on [http://en.wikipedia.org/wiki/Engine_Arm Engine Arm]
*[http://www.logon.ie/contact-us/ LogOn.ie] have added geotags (and hcard) to their contact page.
*[http://www.davidosbornephotography.co.uk/gallery2/main.php www.davidosbornephotography.co.uk] has implemented Geo on all location photography pages; eg. [http://www.davidosbornephotography.co.uk/gallery2/main.php?g2_itemId=1747 Callanish Stones]
*[http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia-EN templates_generating_Geo]
*Wikipedia-IT now has Geo on all [http://it.wikipedia.org/wiki/Speciale:PuntanoQui/Template:Coord pages using the ''coord'' template], e.g. [http://it.wikipedia.org/wiki/Messina Messina]. [[User:AndyMabbett|Andy Mabbett]] 07:05, 26 May 2007 (PDT)
*'Area' pages on Wholemap, summarizing the photos, videos, etc... for a specific area, now have Geo codes - [http://wholemap.com/map/area.php?area=NiagaraFalls Niagara Falls, for example] May 10, 2007
*The Italian Wikipedia, for example [http://it.wikipedia.org/wiki/Genova Genova (Genoa)]
*I've just added geo support to all of [http://socialight.com Socialight]'s Sticky Notes - here's an example - http://socialight.com/note/2007/4/14/11Aqk_a-great-way-to-spend-a-few-hours
*The [http://www.bayofislands.net/ Bay of Islands] site has geo on its main page, and all photo pages. Example: [http://www.bayofislands.net/photos/8/ photo of Edgewater Apartments]
*I've added geo to [http://commons.wikimedia.org/wiki/Special:Whatlinkshere/Template:Location_dec_US all images tagged in Wikimedia Commons] using decimal values. Example: [http://commons.wikimedia.org/wiki/Image:Montreal_City_Hall_Jan_2006.jpg Montreal City Hall, Jan 2006] [[User:AndyMabbett|Andy Mabbett]] 08:54, 12 Apr 2007 (PDT)
**Now on pages tagged in D-M-S also.
*Spotstor.com - e.g. [http://spotstor.com] uses Geo for all coordinates displayed on the site.
*Panoramio - e.g. [http://www.panoramio.com/photo/564690]
* Wikipedia-NL now has Geo on all its map-links pages, e.g. [http://www.nsesoftware.nl/wiki/maps.asp?params=52_28_47_N_1_53_51_W_type:city_region:GB&src=Birmingham_%28Engeland%29 maps for Wikipedia-NL article on Birmingham]
**Called from '''87,724''' article pages as of 2006-04-09; reportedly the sixth most popular website in the Netherlands [http://www.multiscope.nl/organisatie/nieuws/sberichten/nederlandse-wikipedia-groeit-als-kool.html].
* I recently added Geo to Wikipedia-DE's map link pages e.g. [http://tools.wikimedia.de/~magnus/geo/geohack.php?language=de&params=52_28_47_N_1_53_51_W_type:city_region:GB maps for Wikipedia-DE article on Birmingham]. [[User:AndyMabbett|Andy Mabbett]] 14:27, 9 Apr 2007 (PDT)
* I've just added "geo" to OpenStreetMap documentation pages - see [http://wiki.openstreetmap.org/index.php/Birmingham Birmingham page on OpenStreetMap] for example. [[User:AndyMabbett|Andy Mabbett]] 02:39, 6 Apr 2007 (PDT)
* I've [http://en.wikipedia.org/w/index.php?title=Template%3AGeoTemplate&diff=119003866&oldid=118216477 just added] Geo to Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has a Geo microformat. [[User:AndyMabbett|Andy Mabbett]] 03:38, 30 Mar 2007 (PDT)
** [http://tools.wikimedia.de/~kolossos/wp-world/imageworld-art.php Map showing global distribution of geo-tagged Wikipedia articles].
* [http://www.jillesvangurp.com/places jillesvangurp.com] provides an xsl stylesheet to transform Google Earth place-marks (kmz files) into html with nested lists of geo formatted places. Several examples are provided.
*[http://www.geograph.org.uk Geograph British Isles] has experimental support for geos on '''350,000+''' photo pages, for example http://www.geograph.org.uk/photo/1234
*[http://www.poi66.com/ POI66] has '''over 58,500''' waypoints geo-formatted, many describing [[geo-waypoint-examples|trails]] e.g [http://www.poi66.com/maps/show_album.php?album=santiago Mijn pelgrimstocht naar Santiago]
* [http://3amproductions.net 3AM Productions] has published coordinates of cities both in and outside the context of hCards under [http://3amproductions.net/jason.php Jason's] and [http://3amproductions.net/gilbert.php Gil's] pages.
* [http://www.w3.org/People/Connolly/events/ Dan Connoly's Index of Events] has a few geos
** Notes that two of the geos are considered invalid because they use commas instead of semicolons
*Wikitravel now has the facility to add co-ordinates for the subject of the article, and publishes them as a 'geo' microformat - e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]; see [http://wikitravel.org/shared/Tech:Add_SpecialMap_using_Mapstraction_link_for_geo-tagged_pages_and_for_single_listings The announcement].
* [http://flickr.com/ Flickr] now [http://blog.flickr.com/flickrblog/2006/08/great_shot_wher.html supports the geo microformat] on all [http://flickr.com/map/ geotagged photos]. Within 11 days of launch there are now over '''3,000,000+''' photos (as of 2006-09-07) marked up with the "geo" microformat.
* [http://ocono.com/ ocono.com] has marked each of it's "Upcoming Events" items with lat/long values.
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]
* [http://www.multimap.com Multimap.com] uses the geo microformat to mark up latitude and longitude values on map pages.
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.
* [http://07.pagesd.info/ 07.pagesd.info] uses the geo microformat to mark up latitude and longitude values for each commune of the Ardèche département in France.
* [http://www.openguides.org/ OpenGuides] has support for the geo microformat in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide]
* [http://www.txioka.net/ekitaldiak.php Txioka] has support for geo and hcalendar microformats, parses twitter messages with [[twitternanoformats]] and converts to geo and hcalendar.


===Examples with some problems===

Entries may be moved here if there's a problem with the way Geo is used on the page concerned. If the page is yours, and you want to improve it, see the [[hcard-faq|hCard & Geo FAQ]], or raise any queries on [[hcard-issues|hCard & Geo Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you.

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse geos outside the context of hCards. If you have an geo implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

*I've added Geo mark-up to the output of Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has Geo mark-up in the "[http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.686_N_2.193_W_region:GB_type:landmark#Mark-up Mark-up]" section. [[User:AndyMabbett|Andy Mabbett]] 03:10, 13 Jul 2007 (PDT)
*GIS-Wiki's "[http://www.giswiki.org/hjl_get_CoorE.htm hjl_getCoor]" now outputs Geo markup, from a Google Maps API.
*[http://www.addressfix.com/ AddressFix] takes any valid address in the listed countries (as at 2003-07) or map point (using GoogleMaps API) and outputs geo markup.
**Countries: Andorra, Australia, Austria, Belgium, Canada, France, Germany, Gibraltar, Italy, Japan (but only in Japanese), Liechtenstein, Luxembourg, Monaco, Netherlands, New Zealand, San Marino, Spain, Sweden, Switzerland, United States of America and the Vatican City.
**For countries other than the UK, the British Isles and China it provides geocoding for country names and city names (e.g. "Nairobi, Kenya").
**For UK, the British Isles and China, Google returns an error.
* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner]
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
* [http://blog.codeeg.com/ Calvin Yu] has written a [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].
* [http://georss.org/geopress GeoPress] is a WordPress (http://wordpress.org) plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and GeoRSS (http://georss.org) feeds. Written by [http://highearthorbit.com Andrew Turner]

== References ==
=== Normative References ===
* [[hcard|hCard]]

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

* Proposals for changes, additions and other thoughts about [[geo]] may be found in the [[hcard-brainstorming#geo_improvements|hCard brainstorming - geo improvements]] section.

== Related Work ==
* [[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)
* [[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)
* [[geo-extension-strawman]] - extends [[geo]] to include the above, and for representing coordinates on other planets, moons etc.
* [[thoughts-on-extending-the-geo-microformat|thoughts on addind time and reference system]] to the geo microformat, that could also be used for places on other celestial bodies

== Similar Work ==
* [[adr]]
* [[hcalendar|hCalendar]]
* [[XOXO]]

== See Also ==
* [http://en.wikipedia.org/wiki/Geo_%28microformat%29 Geo on Wikipedia]
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page]
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]

== Related Pages ==
{{geo-related-pages}}

geo

2007-08-11T09:32:56Z

TekeTen: /* Examples in the wild */

<h1> geo </h1>
*http://rbach.priv.at/2006/buttons/geo.png
'''geo''' (pronounced "gee-oh") is a simple format for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the "geo" property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

== Draft Specification ==

;Editor/Author
: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])

=== Copyright ===
Per the public domain release on [[User:Tantek|my user page]], this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to everyone who participated in the [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], and in particular to [http://radar.oreilly.com/nat/ Nat Torkington] and Vee McMillen of [http://oreilly.com O'Reilly] for [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 arranging and hosting the BOF]. Thanks to Chris Hibbbert for providing the [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f real world geo-caching example].

== Introduction and Background ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly and interoperably implemented (e.g. Apple's Address Book application). The [[hcard|hCard]] microformat has similarly received significant adoption, from numerous sites publishing the format, to hCard to vCard proxies, to clientside javascript parsers.

At the [http://conferences.oreillynet.com/where/ Where 2.0 conference] in June 2005, there was widespread recognition that the community needed a way to simply and easily publish visible, extractable, geographic location information on the Web, given how often bloggers, and numerous other sites publish such information. The [[geo-bof-2005-06-30|geo microformat BOF]] discussed this very topic, and concluded with a consensus decision to just try using ''geo'' from vCard/hCard.

This specification introduces the '''geo''' microformat, which is a 1:1 representation of the aforementioned ''geo'' property from the vCard standard, by simply reusing the ''geo'' property and sub-properties as-is from the [[hcard|hCard]] microformat.

Publishers can both embed '''geo''' addresses directly in their web pages and feeds, as well as markup existing latitude/longitude coordinates in the context of the rest of the information in their web pages and feeds.

If the publisher knows and is publishing the ''name'' of the location in addition to its geo lat/long, then the publisher MUST use [[hcard|hCard]] instead of just '''geo''' to publish the name and geo lat/long of the location.

If the publisher knows and is publishing the address of the location, OR if the address of the location was what was actually entered by a human, and the publisher simply turned that into lat/long using some sort of a service, then the publisher SHOULD use [[adr]] to publish the actual human entered address information since that communicates far more semantic information than a simple geo lat/long coordinate.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== Singular Properties ===

Note that all the properties in '''geo''' are singular properties, and thus the first descendant element with that class should take effect, any others being ignored.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the <code>title</code> attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. For this purpose, the special class name <code>value</code> is used to excerpt out the subset of the element that is the value of the property. See [[hcard|hCard]] for details on this.

=== Root Class Name ===

The root class name for an geo location is <code>geo</code>.

=== Property List ===

This is the list of properties in geo, taken from [[hcard|hCard]]:

* latitude
* longitude

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]], with the only difference being that "geo" is the root class name, rather than "vcard".

== Examples ==

This section is informative.

=== Example from RFC2426 ===

Section 3.4.2 of RFC2426 has a simple geo example:

<pre><nowiki>
GEO:37.386013;-122.082932
</nowiki></pre>

this vCard fragment as a geo, as [http://microformats.org/wiki/hcard-examples#3.4.2_GEO_Type_Definition first documented on the hCard examples page]:

<pre><nowiki>
<div class="geo">GEO:
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
</div>
</nowiki></pre>

this geo could be displayed as: 

<div class="geo">GEO: <span class="latitude">37.386013</span>, <span class="longitude">-122.082932</span></div>

Note that this is a '''live''' geo microformat, which will be found on this page by parsers.

=== Real world geo example ===

Here is a sample of published lat/long info (from [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f geocaching: Noble Steed]):

<pre><nowiki>
N 37° 24.491 W 122° 08.313
</nowiki></pre>

With geo markup:

<pre><nowiki>
<div class="geo">
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr>
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>
</nowiki></pre>

This geo might be displayed as: 

<div class="geo"><abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>

Again, this is a '''live''' example.

Note that since the real world example used a more human readable presentation of the geo coordinates, we use the [[abbr-design-pattern]] to keep that more human readable presentation, and in addition provide the respective absolute numerical values for the geo.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published geos, outside their normal context of hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc., in addition to those in many [[hcard-examples-in-wild|hCard examples in the wild]]. If you find geos outside of hCards anywhere else, feel free to add them to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

Pages with live Geo can use this button (see [[buttons#Geo]] for any recent additions): http://rbach.priv.at/2006/buttons/geo.png


* [http://www.navitraveler.com/places/629/ NaviTraveler], e. g. [http://www.navitraveler.com/places/629/Lincoln_Memorial.html Lincoln Memorial].
** Response in under 12 hours, to advocacy request - [[User:AndyMabbett|Andy Mabbett]]
*[http://caving.atspace.com/ Caving in the Settle Area] uses Geo to mark up the U.K. NGR for cave locations.
*[http://gc.kls2.com/ Great Circle Mapper] ("GCM"; e.g. [http://tinyurl.com/yugscj sample GCM trip], [http://gc.kls2.com/airport/BHX BHX on GCM])
* [http://www.creation.uk.com Creation design & marketing] has Geo microformat on the [http://www.creation.uk.com/contact/ contact information].
* Wikipedia now has a template, [http://en.wikipedia.org/wiki/Template:Hcard-geo hcard-geo], for in-line hCards with coordinates, using Geo, such as that on [http://en.wikipedia.org/wiki/Engine_Arm Engine Arm]
*[http://www.logon.ie/contact-us/ LogOn.ie] have added geotags (and hcard) to their contact page.
*[http://www.davidosbornephotography.co.uk/gallery2/main.php www.davidosbornephotography.co.uk] has implemented Geo on all location photography pages; eg. [http://www.davidosbornephotography.co.uk/gallery2/main.php?g2_itemId=1747 Callanish Stones]
*[http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia-EN templates_generating_Geo]
*Wikipedia-IT now has Geo on all [http://it.wikipedia.org/wiki/Speciale:PuntanoQui/Template:Coord pages using the ''coord'' template], e.g. [http://it.wikipedia.org/wiki/Messina Messina]. [[User:AndyMabbett|Andy Mabbett]] 07:05, 26 May 2007 (PDT)
*'Area' pages on Wholemap, summarizing the photos, videos, etc... for a specific area, now have Geo codes - [http://wholemap.com/map/area.php?area=NiagaraFalls Niagara Falls, for example] May 10, 2007
*The Italian Wikipedia, for example [http://it.wikipedia.org/wiki/Genova Genova (Genoa)]
*I've just added geo support to all of [http://socialight.com Socialight]'s Sticky Notes - here's an example - http://socialight.com/note/2007/4/14/11Aqk_a-great-way-to-spend-a-few-hours
*The [http://www.bayofislands.net/ Bay of Islands] site has geo on its main page, and all photo pages. Example: [http://www.bayofislands.net/photos/8/ photo of Edgewater Apartments]
*I've added geo to [http://commons.wikimedia.org/wiki/Special:Whatlinkshere/Template:Location_dec_US all images tagged in Wikimedia Commons] using decimal values. Example: [http://commons.wikimedia.org/wiki/Image:Montreal_City_Hall_Jan_2006.jpg Montreal City Hall, Jan 2006] [[User:AndyMabbett|Andy Mabbett]] 08:54, 12 Apr 2007 (PDT)
**Now on pages tagged in D-M-S also.
*Spotstor.com - e.g. [http://spotstor.com] uses Geo for all coordinates displayed on the site.
*Panoramio - e.g. [http://www.panoramio.com/photo/564690]
* Wikipedia-NL now has Geo on all its map-links pages, e.g. [http://www.nsesoftware.nl/wiki/maps.asp?params=52_28_47_N_1_53_51_W_type:city_region:GB&src=Birmingham_%28Engeland%29 maps for Wikipedia-NL article on Birmingham]
**Called from '''87,724''' article pages as of 2006-04-09; reportedly the sixth most popular website in the Netherlands [http://www.multiscope.nl/organisatie/nieuws/sberichten/nederlandse-wikipedia-groeit-als-kool.html].
* I recently added Geo to Wikipedia-DE's map link pages e.g. [http://tools.wikimedia.de/~magnus/geo/geohack.php?language=de&params=52_28_47_N_1_53_51_W_type:city_region:GB maps for Wikipedia-DE article on Birmingham]. [[User:AndyMabbett|Andy Mabbett]] 14:27, 9 Apr 2007 (PDT)
* I've just added "geo" to OpenStreetMap documentation pages - see [http://wiki.openstreetmap.org/index.php/Birmingham Birmingham page on OpenStreetMap] for example. [[User:AndyMabbett|Andy Mabbett]] 02:39, 6 Apr 2007 (PDT)
* I've [http://en.wikipedia.org/w/index.php?title=Template%3AGeoTemplate&diff=119003866&oldid=118216477 just added] Geo to Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has a Geo microformat. [[User:AndyMabbett|Andy Mabbett]] 03:38, 30 Mar 2007 (PDT)
** [http://tools.wikimedia.de/~kolossos/wp-world/imageworld-art.php Map showing global distribution of geo-tagged Wikipedia articles].
* [http://www.jillesvangurp.com/places jillesvangurp.com] provides an xsl stylesheet to transform Google Earth place-marks (kmz files) into html with nested lists of geo formatted places. Several examples are provided.
*[http://www.geograph.org.uk Geograph British Isles] has experimental support for geos on '''350,000+''' photo pages, for example http://www.geograph.org.uk/photo/1234
*[http://www.poi66.com/ POI66] has '''over 58,500''' waypoints geo-formatted, many describing [[geo-waypoint-examples|trails]] e.g [http://www.poi66.com/maps/show_album.php?album=santiago Mijn pelgrimstocht naar Santiago]
* [http://3amproductions.net 3AM Productions] has published coordinates of cities both in and outside the context of hCards under [http://3amproductions.net/jason.php Jason's] and [http://3amproductions.net/gilbert.php Gil's] pages.
* [http://www.w3.org/People/Connolly/events/ Dan Connoly's Index of Events] has a few geos
** Notes that two of the geos are considered invalid because they use commas instead of semicolons
*Wikitravel now has the facility to add co-ordinates for the subject of the article, and publishes them as a 'geo' microformat - e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]; see [http://wikitravel.org/shared/Tech:Add_SpecialMap_using_Mapstraction_link_for_geo-tagged_pages_and_for_single_listings The announcement].
* [http://flickr.com/ Flickr] now [http://blog.flickr.com/flickrblog/2006/08/great_shot_wher.html supports the geo microformat] on all [http://flickr.com/map/ geotagged photos]. Within 11 days of launch there are now over '''3,000,000+''' photos (as of 2006-09-07) marked up with the "geo" microformat.
* [http://ocono.com/ ocono.com] has marked each of it's "Upcoming Events" items with lat/long values.
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]
* [http://www.multimap.com Multimap.com] uses the geo microformat to mark up latitude and longitude values on map pages.
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.
* [http://07.pagesd.info/ 07.pagesd.info] uses the geo microformat to mark up latitude and longitude values for each commune of the Ardèche département in France.
* [http://www.openguides.org/ OpenGuides] has support for the geo microformat in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide]
* [http://www.txioka.net/ekitaldiak.php Txioka] has support for geo and hcalendar microformat support, parses twitter messages with [[twitternanoformats]] and converts to geo and hcalendar.


===Examples with some problems===

Entries may be moved here if there's a problem with the way Geo is used on the page concerned. If the page is yours, and you want to improve it, see the [[hcard-faq|hCard & Geo FAQ]], or raise any queries on [[hcard-issues|hCard & Geo Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you.

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse geos outside the context of hCards. If you have an geo implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

*I've added Geo mark-up to the output of Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has Geo mark-up in the "[http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.686_N_2.193_W_region:GB_type:landmark#Mark-up Mark-up]" section. [[User:AndyMabbett|Andy Mabbett]] 03:10, 13 Jul 2007 (PDT)
*GIS-Wiki's "[http://www.giswiki.org/hjl_get_CoorE.htm hjl_getCoor]" now outputs Geo markup, from a Google Maps API.
*[http://www.addressfix.com/ AddressFix] takes any valid address in the listed countries (as at 2003-07) or map point (using GoogleMaps API) and outputs geo markup.
**Countries: Andorra, Australia, Austria, Belgium, Canada, France, Germany, Gibraltar, Italy, Japan (but only in Japanese), Liechtenstein, Luxembourg, Monaco, Netherlands, New Zealand, San Marino, Spain, Sweden, Switzerland, United States of America and the Vatican City.
**For countries other than the UK, the British Isles and China it provides geocoding for country names and city names (e.g. "Nairobi, Kenya").
**For UK, the British Isles and China, Google returns an error.
* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner]
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
* [http://blog.codeeg.com/ Calvin Yu] has written a [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].
* [http://georss.org/geopress GeoPress] is a WordPress (http://wordpress.org) plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and GeoRSS (http://georss.org) feeds. Written by [http://highearthorbit.com Andrew Turner]

== References ==
=== Normative References ===
* [[hcard|hCard]]

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

* Proposals for changes, additions and other thoughts about [[geo]] may be found in the [[hcard-brainstorming#geo_improvements|hCard brainstorming - geo improvements]] section.

== Related Work ==
* [[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)
* [[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)
* [[geo-extension-strawman]] - extends [[geo]] to include the above, and for representing coordinates on other planets, moons etc.
* [[thoughts-on-extending-the-geo-microformat|thoughts on addind time and reference system]] to the geo microformat, that could also be used for places on other celestial bodies

== Similar Work ==
* [[adr]]
* [[hcalendar|hCalendar]]
* [[XOXO]]

== See Also ==
* [http://en.wikipedia.org/wiki/Geo_%28microformat%29 Geo on Wikipedia]
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page]
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]

== Related Pages ==
{{geo-related-pages}}

geo

2007-08-11T09:32:28Z

TekeTen: /* Examples in the wild */

<h1> geo </h1>
*http://rbach.priv.at/2006/buttons/geo.png
'''geo''' (pronounced "gee-oh") is a simple format for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the "geo" property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

== Draft Specification ==

;Editor/Author
: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])

=== Copyright ===
Per the public domain release on [[User:Tantek|my user page]], this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to everyone who participated in the [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], and in particular to [http://radar.oreilly.com/nat/ Nat Torkington] and Vee McMillen of [http://oreilly.com O'Reilly] for [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 arranging and hosting the BOF]. Thanks to Chris Hibbbert for providing the [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f real world geo-caching example].

== Introduction and Background ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly and interoperably implemented (e.g. Apple's Address Book application). The [[hcard|hCard]] microformat has similarly received significant adoption, from numerous sites publishing the format, to hCard to vCard proxies, to clientside javascript parsers.

At the [http://conferences.oreillynet.com/where/ Where 2.0 conference] in June 2005, there was widespread recognition that the community needed a way to simply and easily publish visible, extractable, geographic location information on the Web, given how often bloggers, and numerous other sites publish such information. The [[geo-bof-2005-06-30|geo microformat BOF]] discussed this very topic, and concluded with a consensus decision to just try using ''geo'' from vCard/hCard.

This specification introduces the '''geo''' microformat, which is a 1:1 representation of the aforementioned ''geo'' property from the vCard standard, by simply reusing the ''geo'' property and sub-properties as-is from the [[hcard|hCard]] microformat.

Publishers can both embed '''geo''' addresses directly in their web pages and feeds, as well as markup existing latitude/longitude coordinates in the context of the rest of the information in their web pages and feeds.

If the publisher knows and is publishing the ''name'' of the location in addition to its geo lat/long, then the publisher MUST use [[hcard|hCard]] instead of just '''geo''' to publish the name and geo lat/long of the location.

If the publisher knows and is publishing the address of the location, OR if the address of the location was what was actually entered by a human, and the publisher simply turned that into lat/long using some sort of a service, then the publisher SHOULD use [[adr]] to publish the actual human entered address information since that communicates far more semantic information than a simple geo lat/long coordinate.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== Singular Properties ===

Note that all the properties in '''geo''' are singular properties, and thus the first descendant element with that class should take effect, any others being ignored.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the <code>title</code> attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. For this purpose, the special class name <code>value</code> is used to excerpt out the subset of the element that is the value of the property. See [[hcard|hCard]] for details on this.

=== Root Class Name ===

The root class name for an geo location is <code>geo</code>.

=== Property List ===

This is the list of properties in geo, taken from [[hcard|hCard]]:

* latitude
* longitude

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]], with the only difference being that "geo" is the root class name, rather than "vcard".

== Examples ==

This section is informative.

=== Example from RFC2426 ===

Section 3.4.2 of RFC2426 has a simple geo example:

<pre><nowiki>
GEO:37.386013;-122.082932
</nowiki></pre>

this vCard fragment as a geo, as [http://microformats.org/wiki/hcard-examples#3.4.2_GEO_Type_Definition first documented on the hCard examples page]:

<pre><nowiki>
<div class="geo">GEO:
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
</div>
</nowiki></pre>

this geo could be displayed as: 

<div class="geo">GEO: <span class="latitude">37.386013</span>, <span class="longitude">-122.082932</span></div>

Note that this is a '''live''' geo microformat, which will be found on this page by parsers.

=== Real world geo example ===

Here is a sample of published lat/long info (from [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f geocaching: Noble Steed]):

<pre><nowiki>
N 37° 24.491 W 122° 08.313
</nowiki></pre>

With geo markup:

<pre><nowiki>
<div class="geo">
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr>
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>
</nowiki></pre>

This geo might be displayed as: 

<div class="geo"><abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>

Again, this is a '''live''' example.

Note that since the real world example used a more human readable presentation of the geo coordinates, we use the [[abbr-design-pattern]] to keep that more human readable presentation, and in addition provide the respective absolute numerical values for the geo.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published geos, outside their normal context of hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc., in addition to those in many [[hcard-examples-in-wild|hCard examples in the wild]]. If you find geos outside of hCards anywhere else, feel free to add them to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

Pages with live Geo can use this button (see [[buttons#Geo]] for any recent additions): http://rbach.priv.at/2006/buttons/geo.png


* [http://www.navitraveler.com/places/629/ NaviTraveler], e. g. [http://www.navitraveler.com/places/629/Lincoln_Memorial.html Lincoln Memorial].
** Response in under 12 hours, to advocacy request - [[User:AndyMabbett|Andy Mabbett]]
*[http://caving.atspace.com/ Caving in the Settle Area] uses Geo to mark up the U.K. NGR for cave locations.
*[http://gc.kls2.com/ Great Circle Mapper] ("GCM"; e.g. [http://tinyurl.com/yugscj sample GCM trip], [http://gc.kls2.com/airport/BHX BHX on GCM])
* [http://www.creation.uk.com Creation design & marketing] has Geo microformat on the [http://www.creation.uk.com/contact/ contact information].
* Wikipedia now has a template, [http://en.wikipedia.org/wiki/Template:Hcard-geo hcard-geo], for in-line hCards with coordinates, using Geo, such as that on [http://en.wikipedia.org/wiki/Engine_Arm Engine Arm]
*[http://www.logon.ie/contact-us/ LogOn.ie] have added geotags (and hcard) to their contact page.
*[http://www.davidosbornephotography.co.uk/gallery2/main.php www.davidosbornephotography.co.uk] has implemented Geo on all location photography pages; eg. [http://www.davidosbornephotography.co.uk/gallery2/main.php?g2_itemId=1747 Callanish Stones]
*[http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia-EN templates_generating_Geo]
*Wikipedia-IT now has Geo on all [http://it.wikipedia.org/wiki/Speciale:PuntanoQui/Template:Coord pages using the ''coord'' template], e.g. [http://it.wikipedia.org/wiki/Messina Messina]. [[User:AndyMabbett|Andy Mabbett]] 07:05, 26 May 2007 (PDT)
*'Area' pages on Wholemap, summarizing the photos, videos, etc... for a specific area, now have Geo codes - [http://wholemap.com/map/area.php?area=NiagaraFalls Niagara Falls, for example] May 10, 2007
*The Italian Wikipedia, for example [http://it.wikipedia.org/wiki/Genova Genova (Genoa)]
*I've just added geo support to all of [http://socialight.com Socialight]'s Sticky Notes - here's an example - http://socialight.com/note/2007/4/14/11Aqk_a-great-way-to-spend-a-few-hours
*The [http://www.bayofislands.net/ Bay of Islands] site has geo on its main page, and all photo pages. Example: [http://www.bayofislands.net/photos/8/ photo of Edgewater Apartments]
*I've added geo to [http://commons.wikimedia.org/wiki/Special:Whatlinkshere/Template:Location_dec_US all images tagged in Wikimedia Commons] using decimal values. Example: [http://commons.wikimedia.org/wiki/Image:Montreal_City_Hall_Jan_2006.jpg Montreal City Hall, Jan 2006] [[User:AndyMabbett|Andy Mabbett]] 08:54, 12 Apr 2007 (PDT)
**Now on pages tagged in D-M-S also.
*Spotstor.com - e.g. [http://spotstor.com] uses Geo for all coordinates displayed on the site.
*Panoramio - e.g. [http://www.panoramio.com/photo/564690]
* Wikipedia-NL now has Geo on all its map-links pages, e.g. [http://www.nsesoftware.nl/wiki/maps.asp?params=52_28_47_N_1_53_51_W_type:city_region:GB&src=Birmingham_%28Engeland%29 maps for Wikipedia-NL article on Birmingham]
**Called from '''87,724''' article pages as of 2006-04-09; reportedly the sixth most popular website in the Netherlands [http://www.multiscope.nl/organisatie/nieuws/sberichten/nederlandse-wikipedia-groeit-als-kool.html].
* I recently added Geo to Wikipedia-DE's map link pages e.g. [http://tools.wikimedia.de/~magnus/geo/geohack.php?language=de&params=52_28_47_N_1_53_51_W_type:city_region:GB maps for Wikipedia-DE article on Birmingham]. [[User:AndyMabbett|Andy Mabbett]] 14:27, 9 Apr 2007 (PDT)
* I've just added "geo" to OpenStreetMap documentation pages - see [http://wiki.openstreetmap.org/index.php/Birmingham Birmingham page on OpenStreetMap] for example. [[User:AndyMabbett|Andy Mabbett]] 02:39, 6 Apr 2007 (PDT)
* I've [http://en.wikipedia.org/w/index.php?title=Template%3AGeoTemplate&diff=119003866&oldid=118216477 just added] Geo to Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has a Geo microformat. [[User:AndyMabbett|Andy Mabbett]] 03:38, 30 Mar 2007 (PDT)
** [http://tools.wikimedia.de/~kolossos/wp-world/imageworld-art.php Map showing global distribution of geo-tagged Wikipedia articles].
* [http://www.jillesvangurp.com/places jillesvangurp.com] provides an xsl stylesheet to transform Google Earth place-marks (kmz files) into html with nested lists of geo formatted places. Several examples are provided.
*[http://www.geograph.org.uk Geograph British Isles] has experimental support for geos on '''350,000+''' photo pages, for example http://www.geograph.org.uk/photo/1234
*[http://www.poi66.com/ POI66] has '''over 58,500''' waypoints geo-formatted, many describing [[geo-waypoint-examples|trails]] e.g [http://www.poi66.com/maps/show_album.php?album=santiago Mijn pelgrimstocht naar Santiago]
* [http://3amproductions.net 3AM Productions] has published coordinates of cities both in and outside the context of hCards under [http://3amproductions.net/jason.php Jason's] and [http://3amproductions.net/gilbert.php Gil's] pages.
* [http://www.w3.org/People/Connolly/events/ Dan Connoly's Index of Events] has a few geos
** Notes that two of the geos are considered invalid because they use commas instead of semicolons
*Wikitravel now has the facility to add co-ordinates for the subject of the article, and publishes them as a 'geo' microformat - e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]; see [http://wikitravel.org/shared/Tech:Add_SpecialMap_using_Mapstraction_link_for_geo-tagged_pages_and_for_single_listings The announcement].
* [http://flickr.com/ Flickr] now [http://blog.flickr.com/flickrblog/2006/08/great_shot_wher.html supports the geo microformat] on all [http://flickr.com/map/ geotagged photos]. Within 11 days of launch there are now over '''3,000,000+''' photos (as of 2006-09-07) marked up with the "geo" microformat.
* [http://ocono.com/ ocono.com] has marked each of it's "Upcoming Events" items with lat/long values.
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]
* [http://www.multimap.com Multimap.com] uses the geo microformat to mark up latitude and longitude values on map pages.
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.
* [http://07.pagesd.info/ 07.pagesd.info] uses the geo microformat to mark up latitude and longitude values for each commune of the Ardèche département in France.
* [http://www.openguides.org/ OpenGuides] has support for the geo microformat in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide]
* [http://www.txioka.net/ekitaldiak.php] has support for geo and hcalendar microformat support, parses twitter messages with [[twitternanoformats]] and converts to geo and hcalendar.


===Examples with some problems===

Entries may be moved here if there's a problem with the way Geo is used on the page concerned. If the page is yours, and you want to improve it, see the [[hcard-faq|hCard & Geo FAQ]], or raise any queries on [[hcard-issues|hCard & Geo Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you.

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse geos outside the context of hCards. If you have an geo implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

*I've added Geo mark-up to the output of Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has Geo mark-up in the "[http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.686_N_2.193_W_region:GB_type:landmark#Mark-up Mark-up]" section. [[User:AndyMabbett|Andy Mabbett]] 03:10, 13 Jul 2007 (PDT)
*GIS-Wiki's "[http://www.giswiki.org/hjl_get_CoorE.htm hjl_getCoor]" now outputs Geo markup, from a Google Maps API.
*[http://www.addressfix.com/ AddressFix] takes any valid address in the listed countries (as at 2003-07) or map point (using GoogleMaps API) and outputs geo markup.
**Countries: Andorra, Australia, Austria, Belgium, Canada, France, Germany, Gibraltar, Italy, Japan (but only in Japanese), Liechtenstein, Luxembourg, Monaco, Netherlands, New Zealand, San Marino, Spain, Sweden, Switzerland, United States of America and the Vatican City.
**For countries other than the UK, the British Isles and China it provides geocoding for country names and city names (e.g. "Nairobi, Kenya").
**For UK, the British Isles and China, Google returns an error.
* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner]
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
* [http://blog.codeeg.com/ Calvin Yu] has written a [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].
* [http://georss.org/geopress GeoPress] is a WordPress (http://wordpress.org) plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and GeoRSS (http://georss.org) feeds. Written by [http://highearthorbit.com Andrew Turner]

== References ==
=== Normative References ===
* [[hcard|hCard]]

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

* Proposals for changes, additions and other thoughts about [[geo]] may be found in the [[hcard-brainstorming#geo_improvements|hCard brainstorming - geo improvements]] section.

== Related Work ==
* [[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)
* [[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)
* [[geo-extension-strawman]] - extends [[geo]] to include the above, and for representing coordinates on other planets, moons etc.
* [[thoughts-on-extending-the-geo-microformat|thoughts on addind time and reference system]] to the geo microformat, that could also be used for places on other celestial bodies

== Similar Work ==
* [[adr]]
* [[hcalendar|hCalendar]]
* [[XOXO]]

== See Also ==
* [http://en.wikipedia.org/wiki/Geo_%28microformat%29 Geo on Wikipedia]
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page]
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]

== Related Pages ==
{{geo-related-pages}}

microblogging-nanoformats

2007-07-31T09:40:24Z

TekeTen: /* Some apps supporting some kind of nanoformat */

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) nanoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)
* [http://www.txioka.net Txioka] event, time, L, adr ... and conversion from nanoformats->microformats (hCalendar)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-07-25T21:47:10Z

TekeTen: /* Twitter (or Jaiku) picoformats proposal */

microblogging-nanoformats

2007-07-25T11:30:41Z

TekeTen:

:'''The official twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) picoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-07-25T11:30:23Z

TekeTen:

:'''The oficial twitter lingo [[twitter-syntax]]'''

=Twitter (or Jaiku) picoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-07-24T23:43:26Z

TekeTen: /* 2nanoformats (syntax:param) */

=Twitter (or Jaiku) picoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-07-24T23:05:00Z

TekeTen: /* 2nanoformats (syntax:param) */

=Twitter (or Jaiku) picoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
+ info: [http://maps.google.com/support/bin/answer.py?answer=20637&query=busqueda&topic=&type= Google maps]
o Geo Syntax: L:<lat;long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-07-23T16:08:37Z

TekeTen: /* Use examples */

=Twitter (or Jaiku) picoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning this [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe] (JP->EN [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g yahoo pipe])

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-07-23T16:06:17Z

TekeTen: /* 3nanoformats (syntax:param:param) */

=Twitter (or Jaiku) picoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g this pipe]

* JP->EN pipe

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

===3nanoformats (syntax:param:param)===

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)

microblogging-nanoformats

2007-07-23T15:58:11Z

TekeTen: /* Twitter (or Jaiku) picoformats proposal */

=Twitter (or Jaiku) picoformats proposal=
(old name was twitter nanoformats)
* Nanoformats try to extend twitter capabilities to give more utility to the tool.
* Nanoformats try to give more semantic information to the twitter post for better filtering.
* Nanoformats try to use commonly used (or semi-standard) parameters like microformats
* Nanoformats are better if more people use it, spread the word.
* Nanoformats are even better if you combine.
* Nanoformats are extensible, customizable, mashable...

Start [http://twitternanoformats.wikispaces.com Wiki] of the project

==Some apps supporting some kind of nanoformat==
* [http://twitter.com Twitter]: @username for replies
* [http://www.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
* [http://www.twittermap.com Twittermap]: L: to show your location (not standarized way)

==Use examples==
* New! translate your twitter feed into different languages using lang: nanoformat. Personalize it cloning [http://pipes.yahoo.com/pipes/pipe.info?_id=yPqQ7Eoe3BG9fmF8zKky6g this pipe]

* JP->EN pipe

* [http://twitter.com/nanoformatsbot Twitter Nanoformats bot] (add to your friends and use nanoformats) for experiments!
* [http://www.bloginfluence.net/nanoformats Example web app] showing tag: and event: nanoformats

==Syntax==

=== 1nanoformats (syntaxparam) ===

* @username
o Use to mention a user.
o Example: @mike I agree with you
o Syntax: @<twitter username>
o Tools: @yourusername filter pipe

===2nanoformats (syntax:param)===

* lang:
o Use to define the language of the post.
o Example: this is a post in English lang:en
o Syntax: lang:<iso639-1 code>
+ info: code list iso639-1
o Tools: lang filter pipe
* tag:
o Use for tag post.
o Example: My cat is stupid tag:cat tag:stupid
o Syntax: tag:<tag>
o Tools: tag filter pipe
* L:
o Use to define a location
o Example: Good place to visit L: Place Georges Pompidou, Paris, France
o Example2: Good place to visit L: Place Georges Pompidou, Paris, 75004
o Example3: Good place to visit L:48.860500,2.352260
o Text Syntax: L:<Addres, city or town, region> or L:<Address, city or town, postal code>
o Geo Syntax: L:<lat,long>
+ info: (Section 3.4.2 of RFC2426)
o Tools: location filter pipe
* todo:
o Use to define something to do (or for someone combined with @username).
o Example: todo:go to buy chocolate
o Syntax: todo:<to do info>
o Tools: todo filter pipe
* event:
o Use to define an event (better combined with L:).
o Example: event:Conference or event:http://www.web2summit.com/pub/w/40/coverage.html/
o Syntax: event:<event name> or event:<http://eventurl... >
o Tools: event filter pipe
* enclosure: [play:(deprecated)]
o Used to mark a link to playable media.
o Example: enclosure: http://media.mfdz.com/track/7.mp3
o Syntax: enclosure:<http://mediaurl... >
* time:
o Used to define a time (usually with event).
o Example: time:2006-06-30 21:00:00
o Syntax: to define (can change)

==3nanoformats (syntax:param:param)==

* rate:
o Use to rate something between 1-5.
o Example: rate:1:Epic movie or rate:5:http://www.twitter.com/
o Syntax: rate:<1-5>:<rated subject>
o Tools: rate filter pipe
* vote:
o Use to vote (for, against, abstain).
o Example: vote:against:Irak war or vote:for:Peace
o Syntax: vote:<for,against,abstain>:<voted subject>
o Tools: vote filter pipe

==Using more than one nanoformat in the same post==
'''If you want to use more than one nanoformat in the same twit.'''
You have to use at the end of the twit.
* Example: great party event:beach party L:Ondarreta beach, Donostia time:2007-06-23 22:00.
* Generic example: <message> <nanoformats one each other>

* Exception: @username. You have to use at the start of the twit.
* Example: @teketen I disagree with you!
* Generic example: @username <message> <nanoformats one each other>

'''Don't use more than one nanoformat of the same type in the same twit'''

Is not a good idea use the same type nanoformat in the same twit. Twits can be a good unit to convert the information given in a twit into other formats for that reason only the things that have meaning together are interesting. If you want to explain more than one thing you should use an other twit to do that.
* Wrong example: we go there tonight event:party event:home party
* Example: great party event:beach party L:Ondarreta beach, Donostia

* Exception: tag: nanoformat. You can use more than one in the same twit.
* Example: Summer night in Andoain http://tinyurl.com/2l6j8z L:Andoain, Gipuzkoa tag:summer tag:night
* Generic Example: <message> <other nanoformats one each other> <tag:>*

[[User:TekeTen|TekeTen]] 08:54, 23 Jul 2007 (PDT)