Difference between revisions of "microblogging-nanoformats"

From Microformats Wiki
Jump to navigation Jump to search
(more usual (and shorter) sub-head)
Line 13: Line 13:
 
; Editor : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
 
; 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.])
 
; Authors : [http://teketen.com Gorka Julio] ([http://www.elurnet.net Elurnet Informatika Zerbitzuak S.L.])
: [http:// Your name here!]
+
: ...
  
 
=== Copyright ===
 
=== Copyright ===
Line 23: Line 23:
 
{{MicroFormatPatentStatement}}
 
{{MicroFormatPatentStatement}}
  
==Some apps supporting some kind of nanoformat==
+
<div id="Some_apps_supporting_some_kind_of_nanoformat"><!-- uses former sub-heading as ID, to preserve existing links)
 +
 
 +
==Implementations==
 +
 
 
* [http://twitter.com Twitter]: @username for replies
 
* [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.tagzania.com Tagzania]: L: to share with you twitter friends the place where you are.
Line 31: Line 34:
 
* [http://foamee.com foamee] @ioubeer @twitterscreenname for being an amazing human being
 
* [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
 
* [http://hashtags.org Hashtags] #tag nanoformat is used as an easy way to track a specific topic or event
 +
 +
</div>
  
 
==Use examples==
 
==Use examples==
Line 136: Line 141:
  
 
==Using more than one nanoformat in the same post==
 
==Using more than one nanoformat in the same post==
 +
 
'''If you want to use more than one nanoformat in the same twit.'''
 
'''If you want to use more than one nanoformat in the same twit.'''
 
You have to use at the end of the twit.
 
You have to use at the end of the twit.
Line 145: Line 151:
 
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
 
* Example: @psd++ for updating this page, thanks also to @factoryjoe #microformats L:Berkhamsted,UK
 
* Generic example: @username <message> <nanoformats one each other>
 
* Generic example: @username <message> <nanoformats one each other>
 
  
 
'''Don't use more than one nanoformat of the same type in the same twit'''
 
'''Don't use more than one nanoformat of the same type in the same twit'''

Revision as of 10:03, 9 January 2008

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 
Gorka Julio (Elurnet Informatika Zerbitzuak S.L.)
Authors 
Gorka Julio (Elurnet Informatika Zerbitzuak S.L.)
...

Copyright

Per the public domain release on the authors' user pages (Gorka Julio) this specification is released into the public domain.

Public Domain Contribution Requirement. Since the author(s) released this work into the public domain, in order to maintain this work's public domain status, all contributors to this page agree to release their contributions to this page to the public domain as well. Contributors may indicate their agreement by adding the public domain release template to their user page per the Voluntary Public Domain Declarations instructions. Unreleased contributions may be reverted/removed.

Patents

This specification is subject to a royalty free patent policy, e.g. per the W3C Patent Policy, and IETF RFC3667 & RFC3668.