Microformats Wiki - User contributions [en]

User:JeffMcNeill

2011-11-09T15:24:16Z

JeffMcNeill:

* email [mailto:jeff@jeffmcneill.com jeff@jeffmcneill.com]
* web [http://jeffmcneill.com/ http://jeffmcneill.com]

{{cc-public-domain-release}}

mediawiki-mark-up-issues

2008-08-18T00:55:19Z

JeffMcNeill:

=MediaWiki mark-up issues=
{{TOC-right}}

Issues with adding microformat mark-up to sites using [http://www.mediawiki.org/ MediaWiki] (such as this wiki, and [http://wikipedia.org Wikipedia]).

If you know of a solution, or work-around, please post it!

==Author==
[[User:AndyMabbett|Andy Mabbett]]

==Contributor(s)==
[[User:JeffMcNeill|Jeff McNeill]]

==URLs==
*Wiki mark-up such as <code><nowiki>[http://example.com sample text]</nowiki></code> (which displays as [http://example.com sample text]) cannot have a class="url" added to the output "<code>A</code>" element.
**Workaround (if display of the URL is acceptable): use <code><nowiki>http://example.com</nowiki></code> (which displays as http://example.com)
**Workaround (if display of the URL is not acceptable): ???
***Why not just use <code><nowiki>[http://example.com sample text]</nowiki></code>? --[[User:TiszaGergo|Tgr]][[User talk:TiszaGergo|talk]] / [[wikipedia:User:Tgr|home]] 06:16, 9 Aug 2007 (PDT)
****Returns a value of "sample text" [[User:AndyMabbett|Andy Mabbett]] 02:12, 10 Aug 2007 (PDT)

* The [http://www.mediawiki.org/wiki/Extension:ExtendAnchorTags ExtendAnchorTags] extension provides a work around using <xa></xa> tags, e.g.
<xa class="fn org" href="http://microformats.org/">microformats</xa>
will produce
<a fn class="fn org" href="http://microformats.org/>microformats</a> --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)

==Rel==
*Similarly, MediaWiki does not appear to support the use of the <code>rel</code> attribute on internal or external links.
** See [http://www.mediawiki.org/wiki/Extension:ExtendAnchorTags ExtendAnchorTags] extension --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)

==Tables==
*In the following code snippet (from an "[http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Infoboxes infobox]" table with an included [[hCard]]):

<code>
<pre>
<nowiki>
{| class="infobox vcard"
| class="fn org" | '''{{{name}}}'''
|-
{{#if: {{{address|}}} |
! Address
{{!}} {{{address}}}}}
|-
{{#if:{{{city|}}} |
! City
{{!}} {{{city|}}}}}
|-
{{#if:{{{country|}}} |
! Country
{{!}} {{{country|}}}}}
|-
{{#if:{{{latitude|}}} |
!
{{!}} <{{Coord|{{{latitude}}}|{{{longitude}}}|display=title}} }}
|}
</nowiki>
</pre>
</code>

:there is nowhere to hang the required <code>class="adr"</code>, such that it wraps the three relevant table rows, and no others.

*you can give a row a class (or any other valid HTML attribute) with <code><nowiki>{{!}} class="adr" {{!}} <span...</nowiki></code> --[[User:TiszaGergo|Tgr]][[User talk:TiszaGergo|talk]] / [[wikipedia:User:Tgr|home]] 06:16, 9 Aug 2007 (PDT)
**The need is not to apply a class to a single row, but (as stated) to apply it to (in this example) "the three relevant table rows, and no others". [[User:AndyMabbett|Andy Mabbett]] 02:14, 10 Aug 2007 (PDT)
***It seems this is a challenge with HTML tables and not necessarily MediaWiki? Please advise --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)
****Partly; but in HTML you can hang an intermediate class on <nowiki><tbody></nowiki>. [[User:AndyMabbett|Andy Mabbett]] 15:42, 19 Jan 2008 (PST)

==Abbr==
*MediaWiki supports the use of the <code>abbr</code> element, but this is disabled by some implementations (e.g. Wikipedia)
**See [[title-trigger]] for a proposed alternative to the [[abbr-design-pattern]], which would work on Wikipedia.
*** A mediawiki extension [http://www.mediawiki.org/wiki/Extension:EnableAbbrTags EnableAbbrTags] can support abbr by using a new xabbr command

==Dtend==

*The work-around for date-time pattern on Wikipedia (for example, birthdays in hCard) has been to use templates to output something like:

<pre>
<nowiki>
24 February 1993 (1993-02-24)
</nowiki>
</pre>

which degrades gracefully if CSS is not available. It is not acceptable to do so, to show the date advanced by one day for end-dates in hCalendar.

**See this [http://microformats.org/discuss/mail/microformats-discuss/2007-August/010449.html proposal to resolve exclusive end-date issue], for a proposal which would allow ''inclusive'' end dates to be marked up.

==XMDP==
*As with many CMSs, there is no facility for an editor to add an [[XMDP]] URI to (or in any other way to alter) the <code>head</code> element.

** Extensions can do this, working on it... --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)

==Address==

Address elements cannot be added to page content.

:<pre><nowiki><address class="vcard">The Microformat community</address></nowiki></pre>

displays as:

:<address class="vcard">The Microformat community</address>

*Not sure how this is a problem, which microformat uses this format? Markup within divs such as <pre><nowiki><div class="adr"></div></nowiki></pre> work fine. --[[User:JeffMcNeill|jeffmcneill]] 01:14, 21 Oct 2007 (PDT)

** [[hatom|hAtom]] uses <nowiki><address></nowiki>. [[User:AndyMabbett|Andy Mabbett]] 15:42, 19 Jan 2008 (PST)

=Mediawiki extension development=
*Are there any generic xml parsers/other extensions under development to provide support for some (most?) of the microformat needs? Is [http://ontoworld.org/wiki/Semantic_MediaWiki semantic mediawiki] a possible candidate for microformat support?
** It appears that semantic mediawiki is trying to do something different, namely OWL compliance. Based on the mediawiki [http://meta.wikimedia.org/wiki/Semantic_MediaWiki description of the semantic mediawiki project], ''hacks'' are to some extent discouraged (which to my mind is the orientation of Microformats). --[[User:JeffMcNeill|jeffmcneill]] 13:41, 18 Oct 2007 (PDT)

* Am working out the extensions needed to address this. --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)

mediawiki-mark-up-issues

2008-08-18T00:54:42Z

JeffMcNeill:

{{TOC-right}}
=MediaWiki mark-up issues=

Issues with adding microformat mark-up to sites using [http://www.mediawiki.org/ MediaWiki] (such as this wiki, and [http://wikipedia.org Wikipedia]).

If you know of a solution, or work-around, please post it!

==Author==
[[User:AndyMabbett|Andy Mabbett]]

==Contributor(s)==
[[User:JeffMcNeill|Jeff McNeill]]

==URLs==
*Wiki mark-up such as <code><nowiki>[http://example.com sample text]</nowiki></code> (which displays as [http://example.com sample text]) cannot have a class="url" added to the output "<code>A</code>" element.
**Workaround (if display of the URL is acceptable): use <code><nowiki>http://example.com</nowiki></code> (which displays as http://example.com)
**Workaround (if display of the URL is not acceptable): ???
***Why not just use <code><nowiki>[http://example.com sample text]</nowiki></code>? --[[User:TiszaGergo|Tgr]][[User talk:TiszaGergo|talk]] / [[wikipedia:User:Tgr|home]] 06:16, 9 Aug 2007 (PDT)
****Returns a value of "sample text" [[User:AndyMabbett|Andy Mabbett]] 02:12, 10 Aug 2007 (PDT)

* The [http://www.mediawiki.org/wiki/Extension:ExtendAnchorTags ExtendAnchorTags] extension provides a work around using <xa></xa> tags, e.g.
<xa class="fn org" href="http://microformats.org/">microformats</xa>
will produce
<a fn class="fn org" href="http://microformats.org/>microformats</a> --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)

==Rel==
*Similarly, MediaWiki does not appear to support the use of the <code>rel</code> attribute on internal or external links.
** See [http://www.mediawiki.org/wiki/Extension:ExtendAnchorTags ExtendAnchorTags] extension --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)

==Tables==
*In the following code snippet (from an "[http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Infoboxes infobox]" table with an included [[hCard]]):

<code>
<pre>
<nowiki>
{| class="infobox vcard"
| class="fn org" | '''{{{name}}}'''
|-
{{#if: {{{address|}}} |
! Address
{{!}} {{{address}}}}}
|-
{{#if:{{{city|}}} |
! City
{{!}} {{{city|}}}}}
|-
{{#if:{{{country|}}} |
! Country
{{!}} {{{country|}}}}}
|-
{{#if:{{{latitude|}}} |
!
{{!}} <{{Coord|{{{latitude}}}|{{{longitude}}}|display=title}} }}
|}
</nowiki>
</pre>
</code>

:there is nowhere to hang the required <code>class="adr"</code>, such that it wraps the three relevant table rows, and no others.

*you can give a row a class (or any other valid HTML attribute) with <code><nowiki>{{!}} class="adr" {{!}} <span...</nowiki></code> --[[User:TiszaGergo|Tgr]][[User talk:TiszaGergo|talk]] / [[wikipedia:User:Tgr|home]] 06:16, 9 Aug 2007 (PDT)
**The need is not to apply a class to a single row, but (as stated) to apply it to (in this example) "the three relevant table rows, and no others". [[User:AndyMabbett|Andy Mabbett]] 02:14, 10 Aug 2007 (PDT)
***It seems this is a challenge with HTML tables and not necessarily MediaWiki? Please advise --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)
****Partly; but in HTML you can hang an intermediate class on <nowiki><tbody></nowiki>. [[User:AndyMabbett|Andy Mabbett]] 15:42, 19 Jan 2008 (PST)

==Abbr==
*MediaWiki supports the use of the <code>abbr</code> element, but this is disabled by some implementations (e.g. Wikipedia)
**See [[title-trigger]] for a proposed alternative to the [[abbr-design-pattern]], which would work on Wikipedia.
*** A mediawiki extension [http://www.mediawiki.org/wiki/Extension:EnableAbbrTags EnableAbbrTags] can support abbr by using a new xabbr command

==Dtend==

*The work-around for date-time pattern on Wikipedia (for example, birthdays in hCard) has been to use templates to output something like:

<pre>
<nowiki>
24 February 1993 (1993-02-24)
</nowiki>
</pre>

which degrades gracefully if CSS is not available. It is not acceptable to do so, to show the date advanced by one day for end-dates in hCalendar.

**See this [http://microformats.org/discuss/mail/microformats-discuss/2007-August/010449.html proposal to resolve exclusive end-date issue], for a proposal which would allow ''inclusive'' end dates to be marked up.

==XMDP==
*As with many CMSs, there is no facility for an editor to add an [[XMDP]] URI to (or in any other way to alter) the <code>head</code> element.

** Extensions can do this, working on it... --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)

==Address==

Address elements cannot be added to page content.

:<pre><nowiki><address class="vcard">The Microformat community</address></nowiki></pre>

displays as:

:<address class="vcard">The Microformat community</address>

*Not sure how this is a problem, which microformat uses this format? Markup within divs such as <pre><nowiki><div class="adr"></div></nowiki></pre> work fine. --[[User:JeffMcNeill|jeffmcneill]] 01:14, 21 Oct 2007 (PDT)

** [[hatom|hAtom]] uses <nowiki><address></nowiki>. [[User:AndyMabbett|Andy Mabbett]] 15:42, 19 Jan 2008 (PST)

=Mediawiki extension development=
*Are there any generic xml parsers/other extensions under development to provide support for some (most?) of the microformat needs? Is [http://ontoworld.org/wiki/Semantic_MediaWiki semantic mediawiki] a possible candidate for microformat support?
** It appears that semantic mediawiki is trying to do something different, namely OWL compliance. Based on the mediawiki [http://meta.wikimedia.org/wiki/Semantic_MediaWiki description of the semantic mediawiki project], ''hacks'' are to some extent discouraged (which to my mind is the orientation of Microformats). --[[User:JeffMcNeill|jeffmcneill]] 13:41, 18 Oct 2007 (PDT)

* Am working out the extensions needed to address this. --[[User:JeffMcNeill|jeffmcneill]] 17:22, 20 Oct 2007 (PDT)

mediawiki

2008-08-17T21:25:32Z

JeffMcNeill:

#REDIRECT[[mediawiki-mark-up-issues]]

cms

2008-08-17T21:15:57Z

JeffMcNeill:

<h1> content management systems </h1>

One general category of microformats [[implementations]].

There are numerous modern content management systems (CMS), often open source, that support of [[microformats]], both by default, and with the installation of themes, plugins, or extensions.

== adding microformats support to CMS ==
See the specific pages for each CMS for specific support and instructions to add more support.

* [[drupal]]
* [[movable-type]]
* [[wordpress]]
* [[mediawiki]]

== related ==
* [[education]]
* [[implementations]]

microblogging-nanoformats

2008-04-11T00:12:31Z

JeffMcNeill:

= Microblogging Nanoformats=
:'''The official twitter lingo [[twitter-syntax]]'''
__TOC__

=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 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! It's time:2007-06-24 21:00
* 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-04-11T00:11:52Z

JeffMcNeill:

= Microblogging Nanoformats=
:'''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 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! It's time:2007-06-24 21:00
* 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-04-11T00:11:29Z

JeffMcNeill:

:'''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 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! It's time:2007-06-24 21:00
* 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)

twitter-nanoformats

2008-04-11T00:11:11Z

JeffMcNeill: twitter-nanoformats moved to microblogging-nanoformats

#REDIRECT [[microblogging-nanoformats]]

governance-issues

2008-03-11T21:39:59Z

JeffMcNeill: /* Petition */

== Issue Summary 2007-02-28 ==
=== Editor ===
[http://www.opendarwin.org/~drernie/ Ernest Prabhakar]

=== Contributors ===
*[[User:AndyMabbett|Andy Mabbett]]
* Joe Andrieu
* Phae
* Ryan Cannon
* Colin Barrett
* ... Please add yourself.

== Preamble ==
Over the last year, a few people (AndyMabbett, JoeAndrieu, ErnestPrabhakar, JamesCraig, [[User:ManuSporny|ManuSporny]]) have raised issues about how the Microformats wiki, mailing list, and community are governed. This page is here to discuss ideas for documenting, formalizing, and/or improving our collective governance.

== Abstract ==
Governance has [http://www.phac-aspc.gc.ca/vs-sb/voluntarysector/glossary.html been defined] as "the traditions, institutions and processes that determine how power is exercised, how citizens are given a voice, and how decisions are made on issues of public concern." In the context of Microformats, it covers:
* Rules (both written and unwritten) expected of community members
* Formal process for change requests for known format problems (i.e. abbr-design-pattern) by voting, with leeway for admin vetoes.
* Who the various Admins are
* What powers Admins have
* Rules for how/when Admins can/should use those powers
* How to questioning/appealing a decision by an Admin
* How to become an Admin
* How to question/change any of these

While not all of these need to be explicitly spelled out, a healthy community our size requires a broad shared understanding of these facts -- as well as acceptance of them as "legitimate."

== Who Are Admins ==
* 2007-01-04 raised by [[User:DrErnie|DrErnie]] on [[microformats-issues]], before this page existed, and moved from there
*# ''As discussed in [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008011.html], there exist various concerns about the lack of clarity regarding governance of the list, wiki, and the specifications themselves. While agree that there does need to be some form of strong leadership to preserve the integrity of the community, I agree with [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008022.html Colin Barrett] when he said:''
:::"I think there should be bit more visible superstructure around just who is in this "cabal". It seems to me like the Editors/Authors of the various specs form the majority it of it, but perhaps that should be made a bit more apparent, and the "powers" of an editor (essentially, the ability to veto changes to the wiki, it seems) outlined a bit and some information about how to become an editor (AFIACT, make numerous, quality edits to the Wiki that the other editors approve of)."
:An entry has been added to the FAQ regarding [http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F Who controls microformats?].[[User:DrErnie|Dr. Ernie]] 08:48, 2 Feb 2007 (PST)

== Mailing List Unmoderation Discussion ==
Discussion from [[mailing-list-unmoderation]].

* I'm glad to see this issue getting traction. However, I'm curious why Ernie's standing in the community is relevant to the issue of unmoderating Andy. Tantek, could you explain why that has been presented as an integral part of this decision making process? Clearly, personal clout always shapes one's ability to influence the community; however, I doubt it should be officially incorporated in these "proceedings". Shouldn't every member of the community have an equal hearing under whatever governance procedures we use? [[User:JoeAndrieu|JoeAndrieu]] 09:38, 19 Mar 2007 (PDT)

:[http://microformats.org/discuss/mail/microformats-discuss/2007-March/009066.html Tantek also said]: "''Ernie, as someone who has made overwhelmingly positive contributions to the microformats community, IMHO the occasional OT post is reasonable'".
* I believe the statement was added to give context to the appealing member of the community. i.e. Ernie is a long standing, good contributor, as opposed to someone new who has no experience with this particular community or someone who has had little or no interaction with the community until now, and also negates it being a personal statement (rather he is interested in community as a whole, instead of being a friend of the Andy and having a personal goal, for example). Basically, he is a person with a certain amount of credibility and trustworthiness. [[User:Phae|Phae]] 10:25, 19 Mar 2007 (PDT)
* Agreed, Phae, Ernie is such a person and that is Tantek's point. But should one need to be a "friend of the court" to bring an action? That practice reinforces a culture of privilege that has historically proven antithetical to transparency and equality, both characteristics of good governance, IMO. It is great to see the powers-that-be responding to Ernie's request. It is also a bit frustrating that only those deemed meritorious by the peerage can call forth due process and that Andy's own efforts to speak on his behalf--referencing my previous request to do the same--were summarily dismissed by Tantek because they were "adversarial." Any robust governance should, IMO, work independent of privilege and be capable of addressing adversarial situations without arbitrary limits on the speech of those whose liberties are under challenge.--[[User:JoeAndrieu|JoeAndrieu]] 14:18, 19 Mar 2007 (PDT)
** Point taken and appreciated, but this is the first incident to come to this kind of a situation where someone else has felt the need to step in, and just happened to also involve someone that is felt to be a member of good standing. I'd like to hope that if another member of the community had felt a similar way and had chosen to bring it up, that it would also have been dealt with in this open manner (and I'm sure this incident will be brought up in the future). Hopefully this incident will be a good test case to better structure future interactions with administration. I can't personally comment on Andy's own appeals. [[User:Phae|Phae]] 14:45, 19 Mar 2007 (PDT)
**Agreed. The first efforts to work through a process like this are bound to be less than ideal. However, I'd like to get on the record two main points that appear problematic.
# [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008490.html my previous request to do the same] was not, in fact, dealt with in this open manner. Rather it decayed into a defensive debate about governance generally, leaving poor Andy stuck in moderated censure. Perhaps I'm not the most diplomatic sort, but the issue on the table is not about me. It is about Andy's continuing moderation.
# The [[mailing-list-unmoderation|unmoderation wiki page]] for Andy is effectively a public hearing on Andy's standing and privileges in the community, especially with [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009066.html Tantek's request] that no replies be sent to the email list on the topic. I find it particularly disturbing that Andy's efforts to contribute to that hearing have been [http://microformats.org/wiki?title=mailing-list-unmoderation&diff=14419&oldid=14416 repeatedly] [http://microformats.org/wiki?title=mailing-list-unmoderation&diff=14456&oldid=14454 dismissed] by Tantek (see the [http://microformats.org/wiki?title=mailing-list-unmoderation&action=history history] for a complete list). While It probably wasn't the best form for Andy to edit my comment directly, he should, IMO, have a way to voice his opinion on the matter. He's been threatened with a ban if he does so on the mailing list. Is there another venue that is more appropriate than the wiki page taking input and votes on his unmoderation?--[[User:JoeAndrieu|JoeAndrieu]] 20:19, 19 Mar 2007 (PDT)
* Shouldn't this point be moot? According to the terms of the moderation, it will be lifted "if he successfully sends only topical / positive / improving email to the lists for one week." Once the week passed, this moderation ought to have been lifted automatically, and should not require a vote, right? --[[User:RCanine|Ryan Cannon]]
** At least one message was rejected during that first week, thus moderation was left as is, with the attention of the admins etc. focused on other higher priority matters. Given the higher quality of messages *with* moderation (as compared to before), some have made the statement that moderation is "working" and thus should be kept. [[User:Tantek|Tantek]] 08:58, 22 Mar 2007 (PDT)
* I dislike moderation because I find it causes me to be hesitant with my own contributions in some cases. Since I don't often know how long a message has been queued its hard for me to judge if my reply would be helpful, or if the moderated poster has already moved along with the rest of the discussion so I err on the side of moving onto something else. doesn't hurt me, but I feel sometimes it might not help with the overall discussions depth or conclusion. . Thus, I think the burden should be heavy to continue moderation for any length of time without a decision to unmoderate or outright ban. [[User:ChrisCasciano|ChrisCasciano]] 11:40, 23 Mar 2007 (ET)

== Examples ==
''Note: This is not to take a position on whether or not any of these decisions were appropriate or inappropriate. Rather, the existence of these events demonstrates the need to document why and how such decisions were -- or should be -- made and/or appealed.''

* Labelling microformats schema discussions as [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003551.html off-topic]
** Already covered by the [[microformats]] principles.
* Issue rejection [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008864.html governance]
* Negative, PoV and derogatory edit summary content such as "[http://microformats.org/wiki?title=hcard-authoring&diff=13621&oldid=12276#Add_To_Address_Book_Links smelled of excessive political correctness worrying]" and "[http://microformats.org/wiki?title=to-do&curid=1110&diff=13989&oldid=13988&rcid=23801 removed non-productive comment]".
** Removal of negative content from the wiki is not a negative. The Admins use their best judgment.
*[[rejected-formats#Pavatar|listing of items as "rejected"]] when [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008271.html requests for evidence of said rejection] reveal none.
** Not every email can be answered, nor should anyone expect them to be. In this case the rejection is in the mailing list archives.
* Despite an assurance that "all of the admins will be apropriately (sic) listed on the wiki page [http://microformats.org/discuss/mail/microformats-discuss/2007-February/008526.html]", the [http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F list given in FAQ] is prefaced with the qualifier "including".
** Reference for assurance? No such assurance should ever have been given.
* Removal of disputed edits / removal of negative content from the wiki
**[http://microformats.org/wiki?title=mailing-list-unmoderation&diff=next&oldid=14416 mailing-list-unmoderation (16:12, 19 Mar 2007)]
**[http://microformats.org/wiki?title=governance&curid=3084&diff=0&oldid=14390&rcid=24255 governance (12:50, 19 Mar 2007)]
** [http://microformats.org/wiki?title=governance-issues&diff=14401&oldid=14396 governance-issues (14:55, 19 Mar 2007)]
**[http://microformats.org/wiki?title=mailing-lists&curid=1297&diff=14391&oldid=14389&rcid=24254 mailing-lists (12:42, 19 Mar 2007)]

== Proposal ==

# Create a publicly-visible ''microformats-admin'' mailing list, for easily identifying and contacting all admins
# Document a forum/mechanism/process where individuals concerned about admin actions can legitimately raise their concerns, to ensure substantive issues are addressed
# Maintain a [[governance]] page that captures and describes
## the identity of current Admins
## how to contact them
## the process for becoming an Admin
## the specific kinds of behavior warranting Admin intervention
## how/when suspended/moderated individuals can return to "good standing"
## how to appeal an Admin decision/action

== Petition ==

We acknowledge that the microformats list and wiki is not a democracy, and that one of the key goals of microformats is to have as little process and structure as possible. However, at the same time we believe that the "dictatorship" needs to not merely ''be'', but ''be seen as'' "benevolent." This includes some minimal level of transparency and due process to ensure that there are legitimate ways for ordinary members to speak out if they feel (rightly or wrongly) that a particular administrative action was unwise or unfair. Whether that is similar to the '''[[#Proposal]]''' above, or a counter-proposal by the ''admin'' team, we believe that something is necessary.
:''Please add your vote here''
*+1 Ernest Prabhakar
*+1 Joe Andrieu
*+1 James Craig
*+1 Steve Robillard
*+1 Chris Messina
*+1 [[User:ManuSporny|ManuSporny]] 08:59, 3 Aug 2007 (PDT)
*+1 Ben Buchanan
*+1 [[User:EatYourGreens|Jim O'Donnell]]
*+1 [[User:Csarven|Sarven Capadisli]]
*+1 [[User:TobyInk|TobyInk]]
*+1 [[User:JohnAllsopp|John Allsopp]]
*+1 [[User:TomMorris|Tom Morris]] - I do not think the current admins are doing a bad job, but would appreciate greater transparency by providing clear reasons for all administrative actions. I also think that unless group administration is transparent, Bad Things Can Happen.
*+1 [[User:JeffMcNeill|Jeff McNeill]]

== Resources ==

* [http://www.shirky.com/writings/group_enemy.html Clay Shirky] on a group as its own worst enemy
* [http://www.informationweek.com/news/showArticle.jhtml?articleID=199600005 Cory Doctorow] on Internet Jerks

history-examples

2008-03-02T06:28:46Z