Microformats Wiki - User contributions [en]

microtron

2010-03-09T18:24:13Z

MarkNg: /* authors and contributors */ add christophe

{{stub}}

[http://github.com/amccollum/microtron Microtron] is a microformats [[parser]] and library for the Python
programming language.

http://github.com/amccollum/microtron

current version: 0.13

== authors and contributors ==
Microtron was originally written by Andrew McCollum and Christophe Benz at [[events/2009-07-25-dev-camp|microformatsDevCamp 2009]].

The following folks have contributed code to Microtron:
* Andrew McCollum
* Christophe Benz
* Mark Ng

== summary ==
Microtron is intended to be a general-purpose microformat parser/transformer.

It can operate on the definition file included in [[Optimus]], making it a close replacement for certain tasks, and can easily be extended with new formats without modifying the source. The primary advantages are speed (> 100x faster that [[Optimus]] for some operations), simplicity (single file) and small code size (currently < 150 lines).

* Requires [http://codespeak.net/lxml/ lxml] and [http://pypi.python.org/pypi/isodate/ isodate]

Right now it supports:

== supported microformats ==
* [[geo]]
* [[adr]]
* [[hcard]]
* [[hcalendar]]
* [[hatom]]
* [[hnews]]
* [[hreview]]
* [[hlisting]]
* [[haudio]]
* [[xfolk]]
* [[hresume]]
* [[xfn]]
* [[votelinks]]
* [[rel-tag]]
* [[rel-nofollow]]
* [[rel-license]]
* [[rel-principles]]

== installation ==

With setuptools' easy_install:
easy_install microtron

With pip:
pip install microtron

=== documentation ===
* ...

== feedback and issues ==
* ...

== future plans ==
* ...

== see also ==
* [[parsers]]
* [[open-source]]

microtron

2010-03-09T18:21:25Z

MarkNg: /* installation */ add some installation notes.

{{stub}}

[http://github.com/amccollum/microtron Microtron] is a microformats [[parser]] and library for the Python
programming language.

http://github.com/amccollum/microtron

current version: 0.13

== authors and contributors ==
Microtron was originally written by Andrew McCollum at [[events/2009-07-25-dev-camp|microformatsDevCamp 2009]].

The following folks have contributed code to Microtron:
* Andrew McCollum
* Christophe Benz
* Mark Ng

== summary ==
Microtron is intended to be a general-purpose microformat parser/transformer.

It can operate on the definition file included in [[Optimus]], making it a close replacement for certain tasks, and can easily be extended with new formats without modifying the source. The primary advantages are speed (> 100x faster that [[Optimus]] for some operations), simplicity (single file) and small code size (currently < 150 lines).

* Requires [http://codespeak.net/lxml/ lxml] and [http://pypi.python.org/pypi/isodate/ isodate]

Right now it supports:

== supported microformats ==
* [[geo]]
* [[adr]]
* [[hcard]]
* [[hcalendar]]
* [[hatom]]
* [[hnews]]
* [[hreview]]
* [[hlisting]]
* [[haudio]]
* [[xfolk]]
* [[hresume]]
* [[xfn]]
* [[votelinks]]
* [[rel-tag]]
* [[rel-nofollow]]
* [[rel-license]]
* [[rel-principles]]

== installation ==

With setuptools' easy_install:
easy_install microtron

With pip:
pip install microtron

=== documentation ===
* ...

== feedback and issues ==
* ...

== future plans ==
* ...

== see also ==
* [[parsers]]
* [[open-source]]

microtron

2010-03-09T18:19:46Z

MarkNg: Add microformats supported, Add Christophe Benz to contributors

{{stub}}

[http://github.com/amccollum/microtron Microtron] is a microformats [[parser]] and library for the Python
programming language.

http://github.com/amccollum/microtron

current version: 0.13

== authors and contributors ==
Microtron was originally written by Andrew McCollum at [[events/2009-07-25-dev-camp|microformatsDevCamp 2009]].

The following folks have contributed code to Microtron:
* Andrew McCollum
* Christophe Benz
* Mark Ng

== summary ==
Microtron is intended to be a general-purpose microformat parser/transformer.

It can operate on the definition file included in [[Optimus]], making it a close replacement for certain tasks, and can easily be extended with new formats without modifying the source. The primary advantages are speed (> 100x faster that [[Optimus]] for some operations), simplicity (single file) and small code size (currently < 150 lines).

* Requires [http://codespeak.net/lxml/ lxml] and [http://pypi.python.org/pypi/isodate/ isodate]

Right now it supports:

== supported microformats ==
* [[geo]]
* [[adr]]
* [[hcard]]
* [[hcalendar]]
* [[hatom]]
* [[hnews]]
* [[hreview]]
* [[hlisting]]
* [[haudio]]
* [[xfolk]]
* [[hresume]]
* [[xfn]]
* [[votelinks]]
* [[rel-tag]]
* [[rel-nofollow]]
* [[rel-license]]
* [[rel-principles]]

== installation ==
* ...

=== documentation ===
* ...

== feedback and issues ==
* ...

== future plans ==
* ...

== see also ==
* [[parsers]]
* [[open-source]]

hnews-fr

2010-01-22T01:32:04Z

MarkNg: change to rel-principles location (would be lovely if we can get a French translation of that too, at some point)

<entry-title>hNews 0.1</entry-title>
{{Template:DraftSpecification-fr}}

hNews est un microformat pour le contenu d'actualités. hNews prolonge [[hatom-fr|hAtom]], en introduisant un nombre de champs qui décrivent plus profondément un travail journalistique. hNews introduit aussi un autre format de donnée, [[rel-principles]], un format qui décrit les principes journalistiques maintenus par le journaliste ou le média qui a publié l'item d'actualité. hNews sera un des nombreux standards ouverts.
__TOC__
== Spécification Draft ==

;Editeur/Auteur
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])

;Contributeurs
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press])
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])

;Traduction en cours
:[[:User:ChristopheDucamp|Christophe Ducamp]]

=== Copyright ===
Du fait de la sortie dans le domaine public affichée sur les pages profils des auteurs, ([[:User:JonathanMalek|Jonathan Malek]]) cette spécification est versée dans le domaine public.

{{MicroFormatPublicDomainContributionStatement-fr}}

=== Brevets ===
{{MicroFormatPatentStatement-fr}}

== Introduction ==
hNews est un microformat pour identifier l'information sémantique dans les articles d'actualité. Il se construit sur [[hatom-fr|hAtom]], tout en ajoutant un certain nombre de champs qui définissent complètement un travail journalistique. hNews peut être pensé comme un format hérité de [[hatom-fr|hAtom]], du fait que les parseurs et outils qui ne comprennent pas les extensions hNews peuvent encore parser le contenu [[hatom-fr|hAtom]]. Néanmoins, ces parseurs et applications qui comprennent hNews peuvent permettre un ensemble plus riche d'actions sémantiques sur les articles d'actualités.

{{rfc-2119-intro-fr}}

== Principes de Design XHTML Sémantique ==
{{semantic-xhtml-design-principles-fr}}

== Format ==
=== En General ===
hNews prolonge hAtom. Tout comme le fait remarquer le format draft hAtom, "Atom fournit bien plus de fonctionnalités que ce dont nous avons besoin pour un microformat de billet de blog, aussi nous avons pris le nombre minimal d'éléments requis."
Les articles d'actualités introduisent typiquement plus de champs (par exemple, l'organisation qui publie) que le draft actuel hAtom 0.1,
et ces champs sont très importants pour lire ou évaluer un article d'actualité. Nous nous concentrons sur ces champs qui
permettent le développement d'actions sémantiques autour des actualités : licence, principes, dateline (geo) et organisation source.

=== Schéma ===
Le schéma hNews contient ce qui suit :

* hNews ('''<code>hnews</code>''') et '''<code>hentry</code>'''. requis. Utilisant [[hatom-fr|hAtom]].
** '''<code>source-org</code>'''. requis. En utilisant [[hcard-fr|hCard]].[*]
** '''<code>dateline</code>'''. optionnel. En utilisant du texte ou [[hcard-fr|hCard]].
** '''<code>geo</code>'''. optionnel. En utilisant [[geo-fr|geo]].[*]
** '''<code>item-license</code>'''. recommandé. En utilisant la [[licensing-brainstorming#item_as_container license|proposition en brainstorm]].
** '''<code>principles</code>'''. recommandé. En utilisant le microformat draft [[principles-brainstorming#rel-principles_specification|rel-principles]].

[*] Quelques éléments requis ont des valeurs par défaut s'ils viennent à manquer, voir ci-dessous.

=== Détails des Champs et Eléments ===

==== Champs hAtom ====

===== Entrée =====
* un article hNews DOIT être encodé sous une <code>hentry</code> [[hatom-fr|hAtom]].
* si un article hNews ne peut être parsé sous une <code>hentry</code> [[hatom-fr|hAtom]], c'est un hNews invalide.

==== Champs additionnels ====

===== Organisation Source =====
* Un élément "Source Organization" est identifié par le nom de classe <code>source-org</code>.
* "Source Organization" représente l'organisation source de l'article d'actualité.
* Une Organisation-Source DOIT être encodée dans une [[hcard-fr|hCard]]
* si l'Organisation-Source manque
** trouver le(s) éléments [[algorithm-nearest-in-parent|parents les plus proches]] avec le nom de classe <code>source-org</code> et qu'il y ait une [[hcard-fr|hCard]] valide.
** autrement l'entrée est une hNews invalide

===== Dateline =====
* un élément dateline est identifié par le nom de classe <code>dateline</code>.
* dateline represente le lieu où l'article d'actualité à été écrit ou fiché (voir [http://en.wikipedia.org/wiki/Dateline dateline] pour en savoir plus).
* un élément dateline PEUT être encodé dans une [[hcard-fr|hCard]].
* un article d'actualité DEVRAIT avoir un élément dateline.
* la dateline inclut parfois la date de publication de l'article. Dans de tels cas, utilisez le [[datetime-design-pattern-fr|modèle-de-design-datetime]] pour encoder la date.

===== Geo =====
* un élément géo est identifié par le nom de classe <code>geo</code>
* geo représente les coordonnées géographiques des lieux pertinents dans l'article d'actualité.
* un élément geo devreait être encodé dans un [[geo-fr|geo]].
* dans ces cas-là où la latitude et la longitude représentent la dateline, une variante de [[geo-fr|geo]] devrait être utilisée (voir [[geo-brainstorming#Geo_improvements|Améliorations Geo] pour un exemple).

===== Licence =====
* un élément licence est identifié par la valeur rel <code>item-license</code>.
* un élément licence DOIT être encodé dans cette [http://microformats.org/wiki/licensing-brainstorming#item_as_container proposition en brainstorming license].
* un article d'actualité DEVRAIT contenir un élément de licence.

===== Principes =====
* un élément principes est identifié by <code>rel-principles</code>.
* principles représente la déclaration des principes et éthique utilisés par l'organisation qui a produit l'article d'actualité.
* un élément "principles" DOIT être encodé en [[principles-brainstorming#rel-principles_specification|rel-principles]].
* un article d'actualité DEVRAIT inclure des principes.
* les principes DEVRAIENT être liés en utilisant les icônes http://labs.ap.org/principles-button-blue.png ou http://labs.ap.org/principles-book-blue.png.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>

<dt>hnews</dt>
<dd>
Used to describe semantic information associated with news stories.
</dd>

<dt>source-org</dt>
<dd>
The originating organization for the news story.
</dd>

<dt>dateline</dt>
<dd>
Represents the location where the news story was filed.
</dd>

<dt>geo</dt>
<dd>
Represents geographic coordinates of relevant locations in the story.
</dd>

<dt>rel</dt>
<dd>
<dl>
<dt>item-license</dt>
<dd>
Represents the license for the story.
</dd>
</dl>
</dd>

<dt>rel</dt>
<dd>
<dl>
<dt>principles</dt>
<dd>
Represents the statement of principles and ethics used by the news organization that produced the news story.
</dd>
</dl>
</dd>

</dl>
</dd>
</dl>
</pre>

== Exemples ==

Voir [[hnews-examples-fr|hNews-exemples]].

=== Exemples dans la jungle ===

voir [[hnews-examples-in-wild-fr|hNews-exemples-dans-la-jungle]].

== Implémentations ==

== Références ==

=== Références Normatives===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]
* [[hatom-fr|hAtom]]
* [[hcard-fr|hCard]]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag-fr|rel-tag]]
* [[geo-fr|geo]]
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)

=== Références Informatives ===
* Autres efforts pour l'actualité : voir [[news-formats]].

== Chantier en Cours ==
Cette spécification est un chantier en cours. Au fur et à mesure que des aspects supplémentaires seront discutés, compris et écrits, ils
seront ajoutés ici.

=== Version 0.1 ===

La version 0.1 a été ébauchée en août 2008.

== Autres lectures ==
* Voir les [http://www.technorati.com/cosmos/referer.html blogs discutant de cette page].

== Pages en rapport ==
* hnews
* [[news-brainstorming]] : idées d'amélioration de hNews.
* [[hnews-faq|hNews FAQ]] : si vous avez des questions à propos de hNews, regardez là, et si vous ne trouvez pas de réponses, ajoutez vos questions !
* [[hnews-issues]] : ajoutez SVP ici toute problématique avec la spécification
* [[news-formats]] : schémas existants
* [[news-examples]] : exemples de formats d'actualité sur le web.
** [[hnews-examples]] : exemples sur la manière d'implémenter hNews.

[[Category:Draft Specifications]]
[[Category:hNews]]

rel-principles

2010-01-22T00:54:17Z

MarkNg: whoops. Copy and pasted without changing to my name ;)

<entry-title>rel-principles 0.1</entry-title>
{{Template:DraftSpecification}}

rel-principles is a simple, open format for indicating statements of principles for the associated content, which is embeddable in HTML or XHTML, Atom, RSS, and arbitrary XML.

== Draft Specification 2010-01-21 ==

;Editor/Author
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])

;Contributors
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])
:Ben Campbell ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press])
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])

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

{{MicroFormatPublicDomainContributionStatement}}

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

== Introduction ==

rel-principles is a format for identifying principles statements for a piece of content. It builds on other microformats which define specific uses of the rel attribute for links, such as [[rel-tag]] and [[rel-license]].

Whilst its original intention is to be used for journalistic content in conjunction with [[hNews]], its use may extend to other entities or professions with principles or codes of conduct.

{{rfc-2119-intro}}

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

==Abstract==

By adding <code>rel=”principles”</code> to a hyperlink, a page indicates that the destination of that hyperlink is a description of the principles the content on the page was created under.

<a href="http://www.mediastandardstrust.org/code-of-practice" rel="principles">some statement
of principles name goes here</a>

==XMDP Profile==
See [[rel-principles-profile]]

[[Category:Draft Specifications]]

rel-principles

2010-01-22T00:27:08Z

MarkNg: Add category

<entry-title>rel-principles 0.1</entry-title>
{{Template:DraftSpecification}}

rel-principles is a simple, open format for indicating statements of principles for the associated content, which is embeddable in HTML or XHTML, Atom, RSS, and arbitrary XML.

== Draft Specification 2010-01-21 ==

;Editor/Author
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])

;Contributors
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])
:Ben Campbell ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press])
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])

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

{{MicroFormatPublicDomainContributionStatement}}

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

== Introduction ==

rel-principles is a format for identifying principles statements for a piece of content. It builds on other microformats which define specific uses of the rel attribute for links, such as [[rel-tag]] and [[rel-license]].

Whilst its original intention is to be used for journalistic content in conjunction with [[hNews]], its use may extend to other entities or professions with principles or codes of conduct.

{{rfc-2119-intro}}

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

==Abstract==

By adding <code>rel=”principles”</code> to a hyperlink, a page indicates that the destination of that hyperlink is a description of the principles the content on the page was created under.

<a href="http://www.mediastandardstrust.org/code-of-practice" rel="principles">some statement
of principles name goes here</a>

==XMDP Profile==
See [[rel-principles-profile]]

[[Category:Draft Specifications]]

hnews

2010-01-22T00:25:26Z

MarkNg: changed location for rel-principles specification

<entry-title>hNews 0.1</entry-title>
{{Template:DraftSpecification}}

hNews is a microformat for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [[rel-principles]], a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.
__TOC__
== Draft Specification ==

;Editor/Author
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])

;Contributors
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press])
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])

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

{{MicroFormatPublicDomainContributionStatement}}

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

== Introduction ==
hNews is a microformat for identifying semantic information in news stories. It builds on [[hAtom]], while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from [[hAtom]], since parsers and tools that do not understand the hNews extensions can still parse the [[hAtom]] content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.

{{rfc-2119-intro}}

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

== Format ==
=== In General ===
hNews extends hAtom. As the hAtom draft format notes, "Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed." News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.

=== Schema ===
The hNews schema consists of the following:

* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].
** '''<code>geo</code>'''. optional. Using [[geo]].[*]
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container|brainstorm proposal]].
** '''<code>principles</code>'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

==== hAtom Fields ====

===== Entry =====
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.

==== Additional Fields ====

===== Source Organization =====
* a Source Organization element is identified by the class name <code>source-org</code>.
* Source Organization represents the originating organization for the news story.
* a Source Organization {{must}} be encoded in an [[hCard]].
* if the Source Organization is missing
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]
** otherwise the entry is invalid hNews

===== Dateline =====
* a dateline element is identified by the class name <code>dateline</code>.
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).
* a dateline element {{may}} be encoded in an [[hCard]].
* a news story {{should}} have a dateline element.
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.

===== Geo =====
* a geo element is identified by the class name <code>geo</code>
* geo represents the geographic coordinates of relevant locations in the news story.
* a geo element should be encoded in a [[geo]].
* in those cases where the latitude and longitude represent the dateline, a variant of [[geo]] should be used (see [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).

===== License =====
* a license element is identified by the rel value of <code>item-license</code>.
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
* a news story {{should}} include a license element.

===== Principles =====
* a principles element is identified by <code>rel-principles</code>.
* principles represents the statement of principles and ethics used by the news organization that produced the news story.
* a principles element {{must}} be encoded in [[principles-brainstorming#rel-principles_specification|rel-principles]].
* a news story {{should}} include principles.
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>

<dt>hnews</dt>
<dd>
Used to describe semantic information associated with news stories.
</dd>

<dt>source-org</dt>
<dd>
The originating organization for the news story.
</dd>

<dt>dateline</dt>
<dd>
Represents the location where the news story was filed.
</dd>

<dt>geo</dt>
<dd>
Represents geographic coordinates of relevant locations in the story.
</dd>

<dt>rel</dt>
<dd>
<dl>
<dt>item-license</dt>
<dd>
Represents the license for the story.
</dd>
</dl>
</dd>

<dt>rel</dt>
<dd>
<dl>
<dt>principles</dt>
<dd>
Represents the statement of principles and ethics used by the news organization that produced the news story.
</dd>
</dl>
</dd>

</dl>
</dd>
</dl>
</pre>

== Examples ==

See [[hnews-examples]].

=== Examples in the wild ===

See [[hnews-examples-in-wild]].

== Implementations ==

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]
* [[hatom|hAtom]]
* [[hcard|hCard]]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag]]
* [[geo]]
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)

=== Informative References ===
* Other news efforts: see [[news-formats]].

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

=== Version 0.1 ===

Version 0.1 was drafted August 2008.

== Further Reading ==
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

== Related Pages ==
* hnews
* [[news-brainstorming]]: thoughts for improving hNews.
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!
* [[hnews-issues]]: please add any issues with the specification to the issues page.
* [[news-formats]]: existing news and news management schemas.
* [[news-examples]]: examples of news formats on the web.
** [[hnews-examples]]: examples of how to implement hNews.

[[Category:Draft Specifications]]
[[Category:hNews]]

principles-brainstorming

2010-01-22T00:23:58Z

MarkNg: moved principles spec to a draft spec

rel-principles

2010-01-22T00:22:19Z

MarkNg: initial add for rel-principles specification draft

<entry-title>rel-principles 0.1</entry-title>
{{Template:DraftSpecification}}

rel-principles is a simple, open format for indicating statements of principles for the associated content, which is embeddable in HTML or XHTML, Atom, RSS, and arbitrary XML.

== Draft Specification 2010-01-21 ==

;Editor/Author
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])

;Contributors
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])
:Ben Campbell ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press])
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])

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

{{MicroFormatPublicDomainContributionStatement}}

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

== Introduction ==

rel-principles is a format for identifying principles statements for a piece of content. It builds on other microformats which define specific uses of the rel attribute for links, such as [[rel-tag]] and [[rel-license]].

Whilst its original intention is to be used for journalistic content in conjunction with [[hNews]], its use may extend to other entities or professions with principles or codes of conduct.

{{rfc-2119-intro}}

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

==Abstract==

By adding <code>rel=”principles”</code> to a hyperlink, a page indicates that the destination of that hyperlink is a description of the principles the content on the page was created under.

<a href="http://www.mediastandardstrust.org/code-of-practice" rel="principles">some statement
of principles name goes here</a>

==XMDP Profile==
See [[rel-principles-profile]]

rel-principles-profile

2010-01-22T00:19:24Z

MarkNg: add title, summary

<entry-title>rel-tag Profile</entry-title>

The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[rel-tag]] specification.

<source lang=html4strict>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.
<dl>
<dt id="principles">statement of principles</dt>
<dd>Indicates that the referred resource is a statement of principles for the content on the referring page.</dd>
</dl>
</dd>
</dl>
</source>

rel-principles-profile

2010-01-22T00:13:49Z

MarkNg: Initial add for the XDMP profile

<pre>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.
<dl>
<dt id="principles">statement of principles</dt>
<dd>Indicates that the referred resource is a statement of principles for the content on the referring page.</dd>
</dl>
</dd>
</dl>
</pre>

hnews

2009-10-16T16:22:42Z

MarkNg: change link to internal for rel-principles

<entry-title>hNews 0.1</entry-title>
{{Template:DraftSpecification}}

hNews is a microformat for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [[principles-brainstorming#rel-principles_specification|rel-principles]], a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.
__TOC__
== Draft Specification ==

;Editor/Author
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])

;Contributors
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press])
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])

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

{{MicroFormatPublicDomainContributionStatement}}

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

== Introduction ==
hNews is a microformat for identifying semantic information in news stories. It builds on [[hAtom]], while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from [[hAtom]], since parsers and tools that do not understand the hNews extensions can still parse the [[hAtom]] content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.

{{rfc-2119-intro}}

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

== Format ==
=== In General ===
hNews extends hAtom. As the hAtom draft format notes, "Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed." News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.

=== Schema ===
The hNews schema consists of the following:

* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].
** '''<code>geo</code>'''. optional. Using [[geo]].[*]
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].
** '''<code>principles</code>'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

==== hAtom Fields ====

===== Entry =====
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.

==== Additional Fields ====

===== Source Organization =====
* a Source Organization element is identified by the class name <code>source-org</code>.
* Source Organization represents the originating organization for the news story.
* a Source Organization {{must}} be encoded in an [[hCard]].
* if the Source Organization is missing
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]
** otherwise the entry is invalid hNews

===== Dateline =====
* a dateline element is identified by the class name <code>dateline</code>.
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).
* a dateline element {{may}} be encoded in an [[hCard]].
* a news story {{should}} have a dateline element.
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.

===== Geo =====
* a geo element is identified by the class name <code>geo</code>
* geo represents the geographic coordinates of relevant locations in the news story.
* a geo element should be encoded in a [[geo]].
* in those cases where the latitude and longitude represent the dateline, a variant of [[geo]] should be used (see [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).

===== License =====
* a license element is identified by the class name <code>item-license</code>.
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
* a news story {{should}} include a license element.

===== Principles =====
* a principles element is identified by <code>rel-principles</code>.
* principles represents the statement of principles and ethics used by the news organization that produced the news story.
* a principles element {{must}} be encoded in [[principles-brainstorming#rel-principles_specification|rel-principles]].
* a news story {{should}} include principles.
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>

<dt>hnews</dt>
<dd>
Used to describe semantic information associated with news stories.
</dd>

<dt>source-org</dt>
<dd>
The originating organization for the news story.
</dd>

<dt>dateline</dt>
<dd>
Represents the location where the news story was filed.
</dd>

<dt>geo</dt>
<dd>
Represents geographic coordinates of relevant locations in the story.
</dd>

<dt>item-license</dt>
<dd>
Represents the license for the story.
</dd>

<dt>rel</dt>
<dd>
<dl>
<dt>principles</dt>
<dd>
Represents the statement of principles and ethics used by the news organization that produced the news story.
</dd>
</dl>
</dd>

</dl>
</dd>
</dl>
</pre>

== Examples ==

See [[hnews-examples]].

=== Examples in the wild ===

See [[hnews-examples-in-wild]].

== Implementations ==

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]
* [[hatom|hAtom]]
* [[hcard|hCard]]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag]]
* [[geo]]
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)

=== Informative References ===
* Other news efforts: see [[news-formats]].

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

=== Version 0.1 ===

Version 0.1 was drafted August 2008.

== Further Reading ==
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

== Related Pages ==
* hnews
* [[news-brainstorming]]: thoughts for improving hNews.
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!
* [[hnews-issues]]: please add any issues with the specification to the issues page.
* [[news-formats]]: existing news and news management schemas.
* [[news-examples]]: examples of news formats on the web.
** [[hnews-examples]]: examples of how to implement hNews.

[[Category:Draft Specifications]]
[[Category:hNews]]

hnews-issues

2009-10-15T00:51:39Z

MarkNg: /* Open Issues */ fix

<h1> hNews issues </h1>

These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft.

'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

See related [[hatom-issues]] and [[hcard-issues]].

== Template ==

{{issues-format}}

__TOC__

== Issues ==
=== Open Issues ===
<div class="hentry">
{{OpenIssue}} 2009-10-14 raised by [[User:MarkNg|MarkNg]]
<div class="entry-content discussion issues">
* adr for dateline. From [[http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter]] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]
</div>
</div>

=== Closed Issues ===
<div class="hentry">
{{ClosedIssue}} 2009-10-09 raised by Miles De Feyter
<div class="entry-content discussion issues">
* Implementation of item-license as it relates to hNews. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)
</div>
</div>
<div class="hentry">
{{ClosedIssue}} 2009-09-28 raised by [[User:MilesD|Miles De Feyter]]
<div class="entry-content discussion issues">
* Principles as a requirement. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCalendar instead of dateline? Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCard instead of geo? Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* What is item-license? Using [[rel-license]] presumably?
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)
</div>
</div>

hnews-issues

2009-10-15T00:50:38Z

MarkNg: /* Open Issues */ added adr in dateline issue

<h1> hNews issues </h1>

These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft.

'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

See related [[hatom-issues]] and [[hcard-issues]].

== Template ==

{{issues-format}}

__TOC__

== Issues ==
=== Open Issues ===
<div class="hentry">
{{OpenIssue}} 2009-10-14 raised by [[User:MarkNg|MarkNg]]
<div class="entry-content discussion issues">
* adr for dateline. From [[http://twitter.com/pigsonthewing/status/4831500605|Andy Mabbett on Twitter]] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]
</div>
</div>

=== Closed Issues ===
<div class="hentry">
{{ClosedIssue}} 2009-10-09 raised by Miles De Feyter
<div class="entry-content discussion issues">
* Implementation of item-license as it relates to hNews. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)
</div>
</div>
<div class="hentry">
{{ClosedIssue}} 2009-09-28 raised by [[User:MilesD|Miles De Feyter]]
<div class="entry-content discussion issues">
* Principles as a requirement. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCalendar instead of dateline? Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCard instead of geo? Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* What is item-license? Using [[rel-license]] presumably?
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)
</div>
</div>

User:MarkNg

2009-10-14T23:07:44Z

MarkNg: Adding public domain release.

http://www.markng.co.uk/

Any contributions I make to this wiki should be considered public domain, as mentioned below.

{{public-domain-release}}

news-brainstorming

2009-10-14T23:02:20Z

MarkNg: Moved issues to issues page

hnews-issues

2009-10-14T23:01:07Z

MarkNg: /* Issues */ move open/closed issues from brainstorming

<h1> hNews issues </h1>

These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft.

'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

See related [[hatom-issues]] and [[hcard-issues]].

== Template ==

{{issues-format}}

__TOC__

== Issues ==
=== Open Issues ===

=== Closed Issues ===
<div class="hentry">
{{ClosedIssue}} 2009-10-09 raised by Miles De Feyter
<div class="entry-content discussion issues">
* Implementation of item-license as it relates to hNews. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)
</div>
</div>
<div class="hentry">
{{ClosedIssue}} 2009-09-28 raised by [[User:MilesD|Miles De Feyter]]
<div class="entry-content discussion issues">
* Principles as a requirement. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCalendar instead of dateline? Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCard instead of geo? Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* What is item-license? Using [[rel-license]] presumably?
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)
</div>
</div>

principles-brainstorming

2009-10-13T23:57:02Z

MarkNg: fix up headings

A number of sites publish a "statement of principles" or a "code of ethics" that governs the behaviour of the author(s) of that site. This page is for discussion of a possible microformat for publishing links to those statements.

Below is an initial pass at a specification for these links.

=rel-principles specification=

rel-principles is a simple, open format for indicating statements of principles for the associated content, which is embeddable in HTML or XHTML, Atom, RSS, and arbitrary XML.

==Abstract==

By adding <code>rel=”principles”</code> to a hyperlink, a page indicates that the destination of that hyperlink is a description of the principles the content on the page was created under.

<a href="http://www.mediastandardstrust.org/code-of-practice" rel="principles">some statement
of principles name goes here</a>

==XMDP Profile==
<pre>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.
<dl>
<dt id="principles">statement of principles</dt>
<dd>Indicates that the referred resource is a statement of principles for the content on the referring page.</dd>
</dl>
</dd>
</dl>
</pre>

principles-brainstorming

2009-10-13T23:56:07Z

MarkNg: add previous spec

A number of sites publish a "statement of principles" or a "code of ethics" that governs the behaviour of the author(s) of that site. This page is for discussion of a possible microformat for publishing links to those statements.

Below is an initial pass at a specification for these links.

#rel-principles specification

rel-principles is a simple, open format for indicating statements of principles for the associated content, which is embeddable in HTML or XHTML, Atom, RSS, and arbitrary XML.

## Abstract

By adding <code>rel=”principles”</code> to a hyperlink, a page indicates that the destination of that hyperlink is a description of the principles the content on the page was created under.

<a href="http://www.mediastandardstrust.org/code-of-practice" rel="principles">some statement
of principles name goes here</a>

## XMDP Profile
<pre>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.
<dl>
<dt id="principles">statement of principles</dt>
<dd>Indicates that the referred resource is a statement of principles for the content on the referring page.</dd>
</dl>
</dd>
</dl>
</pre>

news-brainstorming

2009-10-08T19:24:22Z

MarkNg: /* Closed Issues */ Moved closed issues

= News Brainstorming =

There have been several efforts to define data formats for news content. Almost all have focused on the interchange of news content between systems and organizations, and so contain dozens (if not hundreds) of fields that are targeted at "news management"--a mix of content management, metadata management, versioning and other operations undertaken by news organizations.

This page serves to document the brainstorming and ideas resulting from analysis of news examples from real world sites and systems for the design of a simple news [[microformat]]. - [[User:JonathanMalek|Jonathan Malek]]

__TOC__

== Contributors ==

* Jonathan Malek
* Stuart Myles
* Martin Moore
* Mark Ng
* Todd Martin

== See Also ==

* [[news-examples]]
* [[news-formats]]

== The Problem ==

While there are dozens of formats used on thousands of news sites, there is no single standardized format for presentation of news on the web. Having a standardized news format for web publishing would significantly benefit readers, aggregators, search engines and researchers alike. With no standard format for news, search engines are forced to parse unstructured data, and errors can be costly (see ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').

== Thoughts on a Microformat for News ==

We found significant overlap with [[hAtom]], and simplified an initial effort at a data format for news away from describing any fields already in [[hAtom]], or the superset [http://www.atomenabled.org/ Atom], with the expectation that future versions of that draft specification would approach feature parity. Instead, we focused on those news fields not in [[hAtom]].

In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.

The fields we've selected are a combination of the common fields from many of the news formats currently in use, and the introduction of one new field, '''principles'''.

=== Common News Fields ===

* [[hAtom]] fields: first and foremost, a news story is an [[hatom#Entry|hentry]]. If the news story cannot be parsed by an [[hAtom]] parser, it is not a valid news format.
* '''source-org''': the source organization for this particular news story--should be considered different from the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source atom:source element] because it does not represent the source feed, but rather the source organization (and so should use [[hCard]]). We're using ''source-org'' to avoid name conflict with [[hAtom]] should the draft decide to include the ''atom:source'' element.
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).
* '''geo''': using [[geo]], a simple way of providing the information necessary for services for readers around local news content. This field should be inherited from [[hAtom]], but since it is not part of the format yet, we're including it here. See the [[hatom-issues#Geo|hAtom and Geo]] discussion.
* '''item-license''': to express licensing around the item
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]

== Issues ==

Please add new issues to the bottom of the [[news-brainstorming#Open_Issues|Open Issues]] section by copy and pasting the [[news-brainstorming#Issues_Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

See also [[hatom-issues|hAtom Issues]]

=== Issues Template ===

{{issues-format}}

=== Open Issues ===

=== Closed Issues ===

<div class="hentry">
{{ClosedIssue}} 2009-09-28 raised by [[User:MilesD|Miles De Feyter]]
<div class="entry-content discussion issues">
* Principles as a requirement. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCalendar instead of dateline? Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCard instead of geo? Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* What is item-license? Using [[rel-license]] presumably?
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)
</div>
</div>

== Naming ==

Here are candidate names for a news microformat:

* hNews

= Proposal =
hNews is a data format (similar to a microformat) for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles], a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.

== Introduction ==
hNews is a format (similar to a [[microformat]]) for identifying semantic information in news stories. It builds on [[hAtom]], while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from [[hAtom]], since parsers and tools that do not understand the hNews extensions can still parse the [[hAtom]] content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.

{{rfc-2119-intro}}

== Format ==
=== In General ===
hNews extends hAtom. As the hAtom draft format notes, "Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed." News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.

=== Schema ===
The hNews schema consists of the following:

* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].
** '''<code>geo</code>'''. optional. Using [[geo]].[*]
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Source Organization =====
* a Source Organization element is identified by the class name <code>source-org</code>.
* Source Organization represents the originating organization for the news story.
* a Source Organization {{must}} be encoded in an [[hCard]].
* if the Source Organization is missing
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]
** otherwise the entry is invalid hNews

===== Dateline =====
* a dateline element is identified by the class name <code>dateline</code>.
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).
* a dateline element {{may}} be encoded in an [[hCard]].
* a news story {{should}} have a dateline element.
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.

===== Geo =====
* a geo element is identified by the class name <code>geo</code>
* geo represents the geographic coordinates of relevant locations in the news story.
* a geo element should be encoded in a [[geo]].
* in those cases where the latitude and longitude represent the dateline, a variant of [[geo]] should be used (see [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).

===== License =====
* a license element is identified by the class name <code>item-license</code>.
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].

===== Principles =====
* a principles element is identified by <code>rel-principles</code>.
* principles represents the statement of principles and ethics used by the news organization that produced the news story.
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].
* a news story {{should}} include principles.
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>

<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>

<dt>root</dt>
<dd>
Used to describe semantic information associated with news stories.
</dd>

<dt>source-org</dt>
<dd>
The originating organization for the news story.
</dd>

<dt>dateline</dt>
<dd>
Represents the location where the news story was filed.
</dd>

<dt>geo</dt>
<dd>
Represents geographic coordinates of relevant locations in the story.
</dd>

<dt>item-license</dt>
<dd>
Represents the license for the story.
</dd>

<dt>principles</dt>
<dd>
Represents the statement of principles and ethics used by the news organization that produced the news story.
</dd>

</dl>
</dd>
</dl>
</pre>

news-brainstorming

2009-10-08T19:23:49Z

MarkNg: /* Open Issues */ remove closed issues from open issues section

news-brainstorming

2009-10-08T19:22:44Z

MarkNg: /* Open Issues */ Closed Issue - principles

= News Brainstorming =

There have been several efforts to define data formats for news content. Almost all have focused on the interchange of news content between systems and organizations, and so contain dozens (if not hundreds) of fields that are targeted at "news management"--a mix of content management, metadata management, versioning and other operations undertaken by news organizations.

This page serves to document the brainstorming and ideas resulting from analysis of news examples from real world sites and systems for the design of a simple news [[microformat]]. - [[User:JonathanMalek|Jonathan Malek]]

__TOC__

== Contributors ==

* Jonathan Malek
* Stuart Myles
* Martin Moore
* Mark Ng
* Todd Martin

== See Also ==

* [[news-examples]]
* [[news-formats]]

== The Problem ==

While there are dozens of formats used on thousands of news sites, there is no single standardized format for presentation of news on the web. Having a standardized news format for web publishing would significantly benefit readers, aggregators, search engines and researchers alike. With no standard format for news, search engines are forced to parse unstructured data, and errors can be costly (see ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').

== Thoughts on a Microformat for News ==

We found significant overlap with [[hAtom]], and simplified an initial effort at a data format for news away from describing any fields already in [[hAtom]], or the superset [http://www.atomenabled.org/ Atom], with the expectation that future versions of that draft specification would approach feature parity. Instead, we focused on those news fields not in [[hAtom]].

In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.

The fields we've selected are a combination of the common fields from many of the news formats currently in use, and the introduction of one new field, '''principles'''.

=== Common News Fields ===

* [[hAtom]] fields: first and foremost, a news story is an [[hatom#Entry|hentry]]. If the news story cannot be parsed by an [[hAtom]] parser, it is not a valid news format.
* '''source-org''': the source organization for this particular news story--should be considered different from the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source atom:source element] because it does not represent the source feed, but rather the source organization (and so should use [[hCard]]). We're using ''source-org'' to avoid name conflict with [[hAtom]] should the draft decide to include the ''atom:source'' element.
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).
* '''geo''': using [[geo]], a simple way of providing the information necessary for services for readers around local news content. This field should be inherited from [[hAtom]], but since it is not part of the format yet, we're including it here. See the [[hatom-issues#Geo|hAtom and Geo]] discussion.
* '''item-license''': to express licensing around the item
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]

== Issues ==

Please add new issues to the bottom of the [[news-brainstorming#Open_Issues|Open Issues]] section by copy and pasting the [[news-brainstorming#Issues_Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

See also [[hatom-issues|hAtom Issues]]

=== Issues Template ===

{{issues-format}}

=== Open Issues ===

<div class="hentry">
{{ClosedIssue}} 2009-09-28 raised by [[User:MilesD|Miles De Feyter]]
<div class="entry-content discussion issues">
* Principles as a requirement. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCalendar instead of dateline? Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCard instead of geo? Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* What is item-license? Using [[rel-license]] presumably?
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)
</div>
</div>

=== Closed Issues ===

== Naming ==

Here are candidate names for a news microformat:

* hNews

= Proposal =
hNews is a data format (similar to a microformat) for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles], a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.

== Introduction ==
hNews is a format (similar to a [[microformat]]) for identifying semantic information in news stories. It builds on [[hAtom]], while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from [[hAtom]], since parsers and tools that do not understand the hNews extensions can still parse the [[hAtom]] content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.

{{rfc-2119-intro}}

== Format ==
=== In General ===
hNews extends hAtom. As the hAtom draft format notes, "Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed." News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.

=== Schema ===
The hNews schema consists of the following:

* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].
** '''<code>geo</code>'''. optional. Using [[geo]].[*]
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Source Organization =====
* a Source Organization element is identified by the class name <code>source-org</code>.
* Source Organization represents the originating organization for the news story.
* a Source Organization {{must}} be encoded in an [[hCard]].
* if the Source Organization is missing
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]
** otherwise the entry is invalid hNews

===== Dateline =====
* a dateline element is identified by the class name <code>dateline</code>.
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).
* a dateline element {{may}} be encoded in an [[hCard]].
* a news story {{should}} have a dateline element.
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.

===== Geo =====
* a geo element is identified by the class name <code>geo</code>
* geo represents the geographic coordinates of relevant locations in the news story.
* a geo element should be encoded in a [[geo]].
* in those cases where the latitude and longitude represent the dateline, a variant of [[geo]] should be used (see [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).

===== License =====
* a license element is identified by the class name <code>item-license</code>.
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].

===== Principles =====
* a principles element is identified by <code>rel-principles</code>.
* principles represents the statement of principles and ethics used by the news organization that produced the news story.
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].
* a news story {{should}} include principles.
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>

<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>

<dt>root</dt>
<dd>
Used to describe semantic information associated with news stories.
</dd>

<dt>source-org</dt>
<dd>
The originating organization for the news story.
</dd>

<dt>dateline</dt>
<dd>
Represents the location where the news story was filed.
</dd>

<dt>geo</dt>
<dd>
Represents geographic coordinates of relevant locations in the story.
</dd>

<dt>item-license</dt>
<dd>
Represents the license for the story.
</dd>

<dt>principles</dt>
<dd>
Represents the statement of principles and ethics used by the news organization that produced the news story.
</dd>

</dl>
</dd>
</dl>
</pre>

news-brainstorming

2009-10-08T19:14:35Z

MarkNg: /* Principles */ should

= News Brainstorming =

There have been several efforts to define data formats for news content. Almost all have focused on the interchange of news content between systems and organizations, and so contain dozens (if not hundreds) of fields that are targeted at "news management"--a mix of content management, metadata management, versioning and other operations undertaken by news organizations.

This page serves to document the brainstorming and ideas resulting from analysis of news examples from real world sites and systems for the design of a simple news [[microformat]]. - [[User:JonathanMalek|Jonathan Malek]]

__TOC__

== Contributors ==

* Jonathan Malek
* Stuart Myles
* Martin Moore
* Mark Ng
* Todd Martin

== See Also ==

* [[news-examples]]
* [[news-formats]]

== The Problem ==

While there are dozens of formats used on thousands of news sites, there is no single standardized format for presentation of news on the web. Having a standardized news format for web publishing would significantly benefit readers, aggregators, search engines and researchers alike. With no standard format for news, search engines are forced to parse unstructured data, and errors can be costly (see ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').

== Thoughts on a Microformat for News ==

We found significant overlap with [[hAtom]], and simplified an initial effort at a data format for news away from describing any fields already in [[hAtom]], or the superset [http://www.atomenabled.org/ Atom], with the expectation that future versions of that draft specification would approach feature parity. Instead, we focused on those news fields not in [[hAtom]].

In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.

The fields we've selected are a combination of the common fields from many of the news formats currently in use, and the introduction of one new field, '''principles'''.

=== Common News Fields ===

* [[hAtom]] fields: first and foremost, a news story is an [[hatom#Entry|hentry]]. If the news story cannot be parsed by an [[hAtom]] parser, it is not a valid news format.
* '''source-org''': the source organization for this particular news story--should be considered different from the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source atom:source element] because it does not represent the source feed, but rather the source organization (and so should use [[hCard]]). We're using ''source-org'' to avoid name conflict with [[hAtom]] should the draft decide to include the ''atom:source'' element.
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).
* '''geo''': using [[geo]], a simple way of providing the information necessary for services for readers around local news content. This field should be inherited from [[hAtom]], but since it is not part of the format yet, we're including it here. See the [[hatom-issues#Geo|hAtom and Geo]] discussion.
* '''item-license''': to express licensing around the item
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]

== Issues ==

Please add new issues to the bottom of the [[news-brainstorming#Open_Issues|Open Issues]] section by copy and pasting the [[news-brainstorming#Issues_Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

See also [[hatom-issues|hAtom Issues]]

=== Issues Template ===

{{issues-format}}

=== Open Issues ===

<div class="hentry">
{{OpenIssue}} 2009-09-28 raised by [[User:MilesD|Miles De Feyter]]
<div class="entry-content discussion issues">
* Principles as a requirement. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCalendar instead of dateline? Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCard instead of geo? Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* What is item-license? Using [[rel-license]] presumably?
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)
</div>
</div>

=== Closed Issues ===

== Naming ==

Here are candidate names for a news microformat:

* hNews

= Proposal =
hNews is a data format (similar to a microformat) for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles], a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.

== Introduction ==
hNews is a format (similar to a [[microformat]]) for identifying semantic information in news stories. It builds on [[hAtom]], while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from [[hAtom]], since parsers and tools that do not understand the hNews extensions can still parse the [[hAtom]] content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.

{{rfc-2119-intro}}

== Format ==
=== In General ===
hNews extends hAtom. As the hAtom draft format notes, "Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed." News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.

=== Schema ===
The hNews schema consists of the following:

* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].
** '''<code>geo</code>'''. optional. Using [[geo]].[*]
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Source Organization =====
* a Source Organization element is identified by the class name <code>source-org</code>.
* Source Organization represents the originating organization for the news story.
* a Source Organization {{must}} be encoded in an [[hCard]].
* if the Source Organization is missing
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]
** otherwise the entry is invalid hNews

===== Dateline =====
* a dateline element is identified by the class name <code>dateline</code>.
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).
* a dateline element {{may}} be encoded in an [[hCard]].
* a news story {{should}} have a dateline element.
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.

===== Geo =====
* a geo element is identified by the class name <code>geo</code>
* geo represents the geographic coordinates of relevant locations in the news story.
* a geo element should be encoded in a [[geo]].
* in those cases where the latitude and longitude represent the dateline, a variant of [[geo]] should be used (see [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).

===== License =====
* a license element is identified by the class name <code>item-license</code>.
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].

===== Principles =====
* a principles element is identified by <code>rel-principles</code>.
* principles represents the statement of principles and ethics used by the news organization that produced the news story.
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].
* a news story {{should}} include principles.
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>

<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>

<dt>root</dt>
<dd>
Used to describe semantic information associated with news stories.
</dd>

<dt>source-org</dt>
<dd>
The originating organization for the news story.
</dd>

<dt>dateline</dt>
<dd>
Represents the location where the news story was filed.
</dd>

<dt>geo</dt>
<dd>
Represents geographic coordinates of relevant locations in the story.
</dd>

<dt>item-license</dt>
<dd>
Represents the license for the story.
</dd>

<dt>principles</dt>
<dd>
Represents the statement of principles and ethics used by the news organization that produced the news story.
</dd>

</dl>
</dd>
</dl>
</pre>

news-brainstorming

2009-10-08T18:55:15Z

MarkNg: /* Schema */ change principles from "required" to "recommended"

= News Brainstorming =

There have been several efforts to define data formats for news content. Almost all have focused on the interchange of news content between systems and organizations, and so contain dozens (if not hundreds) of fields that are targeted at "news management"--a mix of content management, metadata management, versioning and other operations undertaken by news organizations.

This page serves to document the brainstorming and ideas resulting from analysis of news examples from real world sites and systems for the design of a simple news [[microformat]]. - [[User:JonathanMalek|Jonathan Malek]]

__TOC__

== Contributors ==

* Jonathan Malek
* Stuart Myles
* Martin Moore
* Mark Ng
* Todd Martin

== See Also ==

* [[news-examples]]
* [[news-formats]]

== The Problem ==

While there are dozens of formats used on thousands of news sites, there is no single standardized format for presentation of news on the web. Having a standardized news format for web publishing would significantly benefit readers, aggregators, search engines and researchers alike. With no standard format for news, search engines are forced to parse unstructured data, and errors can be costly (see ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').

== Thoughts on a Microformat for News ==

We found significant overlap with [[hAtom]], and simplified an initial effort at a data format for news away from describing any fields already in [[hAtom]], or the superset [http://www.atomenabled.org/ Atom], with the expectation that future versions of that draft specification would approach feature parity. Instead, we focused on those news fields not in [[hAtom]].

In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.

The fields we've selected are a combination of the common fields from many of the news formats currently in use, and the introduction of one new field, '''principles'''.

=== Common News Fields ===

* [[hAtom]] fields: first and foremost, a news story is an [[hatom#Entry|hentry]]. If the news story cannot be parsed by an [[hAtom]] parser, it is not a valid news format.
* '''source-org''': the source organization for this particular news story--should be considered different from the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source atom:source element] because it does not represent the source feed, but rather the source organization (and so should use [[hCard]]). We're using ''source-org'' to avoid name conflict with [[hAtom]] should the draft decide to include the ''atom:source'' element.
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).
* '''geo''': using [[geo]], a simple way of providing the information necessary for services for readers around local news content. This field should be inherited from [[hAtom]], but since it is not part of the format yet, we're including it here. See the [[hatom-issues#Geo|hAtom and Geo]] discussion.
* '''item-license''': to express licensing around the item
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]

== Issues ==

Please add new issues to the bottom of the [[news-brainstorming#Open_Issues|Open Issues]] section by copy and pasting the [[news-brainstorming#Issues_Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

See also [[hatom-issues|hAtom Issues]]

=== Issues Template ===

{{issues-format}}

=== Open Issues ===

<div class="hentry">
{{OpenIssue}} 2009-09-28 raised by [[User:MilesD|Miles De Feyter]]
<div class="entry-content discussion issues">
* Principles as a requirement. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCalendar instead of dateline? Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCard instead of geo? Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* What is item-license? Using [[rel-license]] presumably?
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)
</div>
</div>

=== Closed Issues ===

== Naming ==

Here are candidate names for a news microformat:

* hNews

= Proposal =
hNews is a data format (similar to a microformat) for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles], a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.

== Introduction ==
hNews is a format (similar to a [[microformat]]) for identifying semantic information in news stories. It builds on [[hAtom]], while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from [[hAtom]], since parsers and tools that do not understand the hNews extensions can still parse the [[hAtom]] content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.

{{rfc-2119-intro}}

== Format ==
=== In General ===
hNews extends hAtom. As the hAtom draft format notes, "Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed." News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.

=== Schema ===
The hNews schema consists of the following:

* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].
** '''<code>geo</code>'''. optional. Using [[geo]].[*]
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Source Organization =====
* a Source Organization element is identified by the class name <code>source-org</code>.
* Source Organization represents the originating organization for the news story.
* a Source Organization {{must}} be encoded in an [[hCard]].
* if the Source Organization is missing
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]
** otherwise the entry is invalid hNews

===== Dateline =====
* a dateline element is identified by the class name <code>dateline</code>.
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).
* a dateline element {{may}} be encoded in an [[hCard]].
* a news story {{should}} have a dateline element.
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.

===== Geo =====
* a geo element is identified by the class name <code>geo</code>
* geo represents the geographic coordinates of relevant locations in the news story.
* a geo element should be encoded in a [[geo]].
* in those cases where the latitude and longitude represent the dateline, a variant of [[geo]] should be used (see [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).

===== License =====
* a license element is identified by the class name <code>item-license</code>.
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].

===== Principles =====
* a principles element is identified by <code>rel-principles</code>.
* principles represents the statement of principles and ethics used by the news organization that produced the news story.
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>

<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>

<dt>root</dt>
<dd>
Used to describe semantic information associated with news stories.
</dd>

<dt>source-org</dt>
<dd>
The originating organization for the news story.
</dd>

<dt>dateline</dt>
<dd>
Represents the location where the news story was filed.
</dd>

<dt>geo</dt>
<dd>
Represents geographic coordinates of relevant locations in the story.
</dd>

<dt>item-license</dt>
<dd>
Represents the license for the story.
</dd>

<dt>principles</dt>
<dd>
Represents the statement of principles and ethics used by the news organization that produced the news story.
</dd>

</dl>
</dd>
</dl>
</pre>

news-brainstorming

2009-09-30T23:24:07Z

MarkNg: See also hatom

= News Brainstorming =

There have been several efforts to define data formats for news content. Almost all have focused on the interchange of news content between systems and organizations, and so contain dozens (if not hundreds) of fields that are targeted at "news management"--a mix of content management, metadata management, versioning and other operations undertaken by news organizations.

This page serves to document the brainstorming and ideas resulting from analysis of news examples from real world sites and systems for the design of a simple news [[microformat]]. - [[User:JonathanMalek|Jonathan Malek]]

__TOC__

== Contributors ==

* Jonathan Malek
* Stuart Myles
* Martin Moore
* Mark Ng
* Todd Martin

== See Also ==

* [[news-examples]]
* [[news-formats]]

== The Problem ==

While there are dozens of formats used on thousands of news sites, there is no single standardized format for presentation of news on the web. Having a standardized news format for web publishing would significantly benefit readers, aggregators, search engines and researchers alike. With no standard format for news, search engines are forced to parse unstructured data, and errors can be costly (see ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').

== Thoughts on a Microformat for News ==

We found significant overlap with [[hAtom]], and simplified an initial effort at a data format for news away from describing any fields already in [[hAtom]], or the superset [http://www.atomenabled.org/ Atom], with the expectation that future versions of that draft specification would approach feature parity. Instead, we focused on those news fields not in [[hAtom]].

In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.

The fields we've selected are a combination of the common fields from many of the news formats currently in use, and the introduction of one new field, '''principles'''.

=== Common News Fields ===

* [[hAtom]] fields: first and foremost, a news story is an [[hatom#Entry|hentry]]. If the news story cannot be parsed by an [[hAtom]] parser, it is not a valid news format.
* '''source-org''': the source organization for this particular news story--should be considered different from the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source atom:source element] because it does not represent the source feed, but rather the source organization (and so should use [[hCard]]). We're using ''source-org'' to avoid name conflict with [[hAtom]] should the draft decide to include the ''atom:source'' element.
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).
* '''geo''': using [[geo]], a simple way of providing the information necessary for services for readers around local news content. This field should be inherited from [[hAtom]], but since it is not part of the format yet, we're including it here. See the [[hatom-issues#Geo|hAtom and Geo]] discussion.
* '''item-license''': to express licensing around the item
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]

== Issues ==

Please add new issues to the bottom of the [[news-brainstorming#Open_Issues|Open Issues]] section by copy and pasting the [[news-brainstorming#Issues_Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

See also [[hatom-issues|hAtom Issues]]

=== Issues Template ===

{{issues-format}}

=== Open Issues ===

<div class="hentry">
{{OpenIssue}} 2009-09-28 raised by [[User:MilesD|Miles De Feyter]]
<div class="entry-content discussion issues">
* Principles as a requirement. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCalendar instead of dateline? Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* hCard instead of geo? Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ClosedIssue}} 18:32, 24 August 2009 (UTC) raised by [[User:Kevin Marks|Kevin Marks]]
<div class="entry-content discussion issues">
* What is item-license? Using [[rel-license]] presumably?
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)
</div>
</div>

=== Closed Issues ===

== Naming ==

Here are candidate names for a news microformat:

* hNews

= Proposal =
hNews is a data format (similar to a microformat) for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles], a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.

== Introduction ==
hNews is a format (similar to a [[microformat]]) for identifying semantic information in news stories. It builds on [[hAtom]], while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from [[hAtom]], since parsers and tools that do not understand the hNews extensions can still parse the [[hAtom]] content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.

{{rfc-2119-intro}}

== Format ==
=== In General ===
hNews extends hAtom. As the hAtom draft format notes, "Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed." News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.

=== Schema ===
The hNews schema consists of the following:

* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].
** '''<code>geo</code>'''. optional. Using [[geo]].[*]
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
** '''<code>principles</code>'''. required. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Source Organization =====
* a Source Organization element is identified by the class name <code>source-org</code>.
* Source Organization represents the originating organization for the news story.
* a Source Organization {{must}} be encoded in an [[hCard]].
* if the Source Organization is missing
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]
** otherwise the entry is invalid hNews

===== Dateline =====
* a dateline element is identified by the class name <code>dateline</code>.
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).
* a dateline element {{may}} be encoded in an [[hCard]].
* a news story {{should}} have a dateline element.
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.

===== Geo =====
* a geo element is identified by the class name <code>geo</code>
* geo represents the geographic coordinates of relevant locations in the news story.
* a geo element should be encoded in a [[geo]].
* in those cases where the latitude and longitude represent the dateline, a variant of [[geo]] should be used (see [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).

===== License =====
* a license element is identified by the class name <code>item-license</code>.
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].

===== Principles =====
* a principles element is identified by <code>rel-principles</code>.
* principles represents the statement of principles and ethics used by the news organization that produced the news story.
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>

<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>

<dt>root</dt>
<dd>
Used to describe semantic information associated with news stories.
</dd>

<dt>source-org</dt>
<dd>
The originating organization for the news story.
</dd>

<dt>dateline</dt>
<dd>
Represents the location where the news story was filed.
</dd>

<dt>geo</dt>
<dd>
Represents geographic coordinates of relevant locations in the story.
</dd>

<dt>item-license</dt>
<dd>
Represents the license for the story.
</dd>

<dt>principles</dt>
<dd>
Represents the statement of principles and ethics used by the news organization that produced the news story.
</dd>

</dl>
</dd>
</dl>
</pre>

principles-examples

2009-09-03T00:35:54Z

MarkNg: Add some more principles links

Per the microformats [[process]] this page documents examples of pages that link to a statement of principles or ethics that apply to the content within, towards the development of a [[principles-effort|principles microformat]].

* [http://www.opendemocracy.net/article/the-kennedys-the-democrats-and-obama Story] [http://www.opendemocracy.net/statement-of-principles Principles] - Opendemocracy
* [http://www.dailycal.org/article/27119/license_to_kill Story] [http://www.spj.org/ethicscode.asp SPJ ethics code] - The Daily Californian (see about -> ethics)
* [http://www.journalisted.com/article?id=1664755 story] [http://www.pcc.org.uk/cop/practice.html PCC code of practice] - Journalisted linking to the Independent
* [http://www.metro.co.uk/editorialpolicy internal editorial policy] which also links to [http://www.pcc.org.uk/cop/practice.html the PCC code of practice] - The London Metro
* [http://www.macclesfield-express.co.uk/contact_us/s/1015298_were_moving__but_its_business_as_usual contact page] links to [http://www.pcc.org.uk/cop/practice.html PCC code of practice] - The Macclesfield Express
* [http://manonplatform13.blogspot.com/2009/07/new-grid.html story] ([http://www.pcc.org.uk/cop/practice.html PCC] + [http://media.gn.apc.org/nujcode.html NUJ] codes) - Man on Platform 13 blog
* [http://www.whitehavennews.co.uk/home/contact_us contact page] links to [http://www.pcc.org.uk/cop/practice.html PCC code of practice] - whitehaven news
* [http://www.eadt.co.uk/content/eadt/contact-us/] East Anglian Daily Times (make a complaint)
* [http://group.bmj.com/group/about/legal] BMJ Group

<div class="discussion">
* '''Include links to actual issues pages as well.''' The obviousness/explicitness/descriptiveness of the examples could be improved by also listing the URL for the statement of principles for the page. — [[User:Tantek|Tantek]] 00:55, 29 August 2009 (UTC)
* '''Include snippet of markup used in examples to link to a statement of principles.'''. Similarly, documenting the sample markup (including link text) that is used to link to the statement of principles would help with the research. Even if in all cases it's a hyperlink, it helps to document that explicitly so that we can design accordingly (e.g. all uses being a hyperlink makes a good case to just use a single rel value). — [[User:Tantek|Tantek]] 00:55, 29 August 2009 (UTC)
</div>

== related ==
* [[principles]] of microformats
* [[principles-formats]] - research into previous attempts at formats for linking/referring/describing principles
* [[principles-brainstorming]] - per the microformats [[process]] proposals that take into account the research from the examples and the previous formats.
* [[news]] - a microformats effort that is likely to make use of a principles microformat.

principles-examples

2009-09-03T00:13:51Z

MarkNg: add linked principles

Per the microformats [[process]] this page documents examples of pages that link to a statement of principles or ethics that apply to the content within, towards the development of a [[principles-effort|principles microformat]].

* [http://www.opendemocracy.net/article/the-kennedys-the-democrats-and-obama Story] [http://www.opendemocracy.net/statement-of-principles Principles] - Opendemocracy
* [http://www.dailycal.org/article/27119/license_to_kill Story] [http://www.spj.org/ethicscode.asp SPJ ethics code] - The Daily Californian (see about -> ethics)
* [http://www.journalisted.com/article?id=1664755] - Journalisted linking to the Independent
* [http://www.metro.co.uk/editorialpolicy] - The London Metro
* [http://www.macclesfield-express.co.uk/contact_us/s/1015298_were_moving__but_its_business_as_usual] - The Macclesfield Express
* [http://manonplatform13.blogspot.com/2009/07/new-grid.html] - Man on Platform 13 blog (PCC + NUJ codes)
* [http://www.whitehavennews.co.uk/home/contact_us] - whitehaven news
* [http://www.eadt.co.uk/content/eadt/contact-us/] East Anglian Daily Times (make a complaint)
* [http://group.bmj.com/group/about/legal] BMJ Group

<div class="discussion">
* '''Include links to actual issues pages as well.''' The obviousness/explicitness/descriptiveness of the examples could be improved by also listing the URL for the statement of principles for the page. — [[User:Tantek|Tantek]] 00:55, 29 August 2009 (UTC)
* '''Include snippet of markup used in examples to link to a statement of principles.'''. Similarly, documenting the sample markup (including link text) that is used to link to the statement of principles would help with the research. Even if in all cases it's a hyperlink, it helps to document that explicitly so that we can design accordingly (e.g. all uses being a hyperlink makes a good case to just use a single rel value). — [[User:Tantek|Tantek]] 00:55, 29 August 2009 (UTC)
</div>

== related ==
* [[principles]] of microformats
* [[principles-formats]] - research into previous attempts at formats for linking/referring/describing principles
* [[principles-brainstorming]] - per the microformats [[process]] proposals that take into account the research from the examples and the previous formats.
* [[news]] - a microformats effort that is likely to make use of a principles microformat.

principles-formats

2009-09-02T18:23:31Z

MarkNg: add link to rel-principles

A number of sites publish a "statement of principles" or a "code of ethics" that governs the behaviour of the author(s) of that site. This page is to show research into previous attempts at codifying links to these principles in HTML.

[http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles] a format using the [[rel-design-pattern]] to describe links to a set of principles.

principles-formats

2009-09-02T18:19:19Z

MarkNg: New page: A number of sites publish a "statement of principles" or a "code of ethics" that governs the behaviour of the author(s) of that site. This page is to show research into previous attempts a...

principles-brainstorming

2009-09-02T18:18:07Z

MarkNg: New page: A number of sites publish a "statement of principles" or a "code of ethics" that governs the behaviour of the author(s) of that site. This page is for discussion of a possible microformat...

principles-examples

2009-08-28T21:53:39Z

MarkNg: some more

This page documents examples of pages that link to a statement of principles or ethics that apply to the content within.

* [http://www.opendemocracy.net/article/the-kennedys-the-democrats-and-obama] - Opendemocracy
* [http://www.dailycal.org/article/27119/license_to_kill] - The Daily Californian (see about -> ethics)
* [http://www.journalisted.com/article?id=1664755] - Journalisted linking to the Independent
* [http://www.metro.co.uk/editorialpolicy] - The London Metro
* [http://www.macclesfield-express.co.uk/contact_us/s/1015298_were_moving__but_its_business_as_usual] - The Macclesfield Express
* [http://manonplatform13.blogspot.com/2009/07/new-grid.html] - Man on Platform 13 blog (PCC + NUJ codes)
* [http://www.whitehavennews.co.uk/home/contact_us] - whitehaven news
* [http://www.eadt.co.uk/content/eadt/contact-us/] East Anglian Daily Times (make a complaint)
* [http://group.bmj.com/group/about/legal] BMJ Group

principles-examples

2009-08-28T21:47:31Z

MarkNg: some more

principles-examples

2009-08-28T21:38:15Z

MarkNg: add journalisted

principles-examples

2009-08-28T21:30:22Z

MarkNg: add a link

This page documents examples of pages that link to a statement of principles or ethics that apply to the content within.

[http://www.opendemocracy.net/article/the-kennedys-the-democrats-and-obama] - Opendemocracy
[http://www.dailycal.org/article/27119/license_to_kill] - The Daily Californian (see about -> ethics)

principles-examples

2009-08-28T21:18:04Z

MarkNg: New page: This page documents examples of pages that link to a statement of principles or ethics that apply to the content within. [http://www.opendemocracy.net/article/the-kennedys-the-democrats-a...

events/2009-07-25-dev-camp

2009-07-26T01:37:21Z

MarkNg: move that page

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt while supplies last). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]
** Coffee
** Snacks
** ______?

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
microformatsDevCamp, like any BarCamp, needs you - Sign up to volunteer, attend, design, code, and build with microformats!

=== volunteers ===
Like all [http://barcamp.org BarCamps], this event is what it is because of what everyone puts into it. Volunteer to help setup, check people in, get them setup with a name badge, clean up, and help people in general have a good time and get things done.
* Cindy Li - designer, helping with microformatsDevCamp logo design. done!
** full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
** on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
** designed and ordered buttons for event.Done!

* [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [[http://dentedreality.com.au/ Dented Reality]]. I know my way around the venue, so can help sort out power strips, projectors etc
* ...

=== participants ===

Please register with this [http://spreadsheets.google.com/viewform?formkey=dERvcnQ4SlFsX0ZLQi1KOE8wbk5obUE6MA.. online form].

Want to design interfaces or build stuff with microformats and want help doing it? Sign up! Add yourself. Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one.
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction)
# [http://yury.name Yury Lifshits]
# [http://www.markng.co.uk Mark Ng]
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer
# [http://www.jasonbolton.com Jason Bolton] - front-end designer
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday).
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher
# [http://feedblog.org Kevin Burton] - developer
# [http://jobspice.com Dane Hurtubise] - developer
# [http://developer.netflix.com JR Conlin] - developer, publisher
# Chirag Shah - developer
# [http://www.wezaggle.com Jesse Hammons] - developer [http://www.wezaggle.com Zaggle Social Calendar]
# [http://matthewlevine.com Matthew Levine] - developer
# [http://farukat.es/ Faruk Ateş] - UX Designer, developer
# [http://fourkitchens.com/ David Strauss] - Drupal, developer
# [http://huyhong.com/ Huy Hong] - Frontend Developer, UI/UX/UE, UGC nut
# [http://objectadjective.com Jeremy Anderson] - UX/UI/ID Designer, developer
# [http://objectadjective.com Lauren Scime] - front end designer / developer
# [http://blog.oofn.net Chad Weider] developer, designer, front-end, back-end, etc.
# (and about 35 more folks, according to [http://upcoming.yahoo.com/event/2888376/ Upcoming] as of noon Thursday 2009-7-23)
# ...

==schedule==
Outline of schedule for the weekend - more details at the DevCamp!
* Saturday July 25th
** 11:00am - planners+volunteers onsite for setup
** 12:00pm - registration, lunch
** intro session, what is a devcamp, introductions
** hack/project brainstorming and proposals
** day 1 building sessions
** dinner and group photo
** day 1 demos and social hour
** evening open hacking session (like DevHouse) / iteration on hacks/projects

* Sunday July 26th
** 10:00am - breakfast
** day 2 working sessions on hacks/projects
** 12:30pm lunch
** day 2 working sessions continued
** second day demos and wrap-up
** venue clean-up
** 5pm venue exit

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Cafe - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* '''(Sunday)''' '''CSS3, HTML5 and microformats "Zen Garden"''' - same premise as the CSS Zen Garden of yore, but with a strong emphasis on CSS3 advancements, microformats enrichment and done in HTML5. [[User:KuraFire|Faruk Ateş]]
* '''CheatSheet Translation''' [[User:Brian|Brian Suda]] This is a request to anyone who is speaks another language. I created the PDF cheatsheet awhile ago http://suda.co.uk/projects/microformats/cheatsheet/ if someone wants to translate it into Spanish, or another language, please let me know. I can send the source InDesign file, or if they send me the translations, I'd be happy to update it myself.
</div>

== projects ==
;short URL for this section
:http://tr.im/ufps
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
* [[hcard-input-interface]] for easy input of user data (creating hCards) by Chad. combined project/session with '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? by [[User:Tantek|Tantek]]
* [[self-updating-address-book]] - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
* [[hcard-contact-autocompletion]] by [[User:Rohit|Rohit Khare]]
* [[microformat-services]] by ________
* [[unified-rsvp]] by _________
* '''hCard to Google Address Book''' [[bookmarklet]]. [[User:Singpolyma|Singpolyma]]
* [[microformat-aggregation]] by [[User:jessehammons|Jesse Hammons]], [[User:yurylifshits|Yury Lifshits]], Andrew McCollum, Dane Hurtibuse, Randy Kerber
* [[twitter bus card exchange/display]] by [[User:perivision|Christopher]]

== photographs ==
* ...

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]
* ...

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, setup, welcome desk'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''

=== planner roles ===
Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

events/2009-07-25-dev-camp/self-updating-address-book

2009-07-26T01:36:49Z

MarkNg: events/2009-07-25-dev-camp/self-updating-address-book moved to self-updating-address-book

#REDIRECT [[self-updating-address-book]]

self-updating-address-book

2009-07-26T01:36:49Z

MarkNg: events/2009-07-25-dev-camp/self-updating-address-book moved to self-updating-address-book

== Self Updating Address Book ==

Basic Idea: an online address book/contact system, accessible via LDAP, which updates its records by periodically crawling/parsing URLs containing hCards.

=== Participants ===
* Beau Lebens
* Matt Wilkinson
* Mark Ng
* Tantek Celik
* Chad Weider

events/2009-07-25-dev-camp

2009-07-26T01:36:16Z

MarkNg: let's fix that

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt while supplies last). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]
** Coffee
** Snacks
** ______?

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
microformatsDevCamp, like any BarCamp, needs you - Sign up to volunteer, attend, design, code, and build with microformats!

=== volunteers ===
Like all [http://barcamp.org BarCamps], this event is what it is because of what everyone puts into it. Volunteer to help setup, check people in, get them setup with a name badge, clean up, and help people in general have a good time and get things done.
* Cindy Li - designer, helping with microformatsDevCamp logo design. done!
** full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
** on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
** designed and ordered buttons for event.Done!

* [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [[http://dentedreality.com.au/ Dented Reality]]. I know my way around the venue, so can help sort out power strips, projectors etc
* ...

=== participants ===

Please register with this [http://spreadsheets.google.com/viewform?formkey=dERvcnQ4SlFsX0ZLQi1KOE8wbk5obUE6MA.. online form].

Want to design interfaces or build stuff with microformats and want help doing it? Sign up! Add yourself. Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one.
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction)
# [http://yury.name Yury Lifshits]
# [http://www.markng.co.uk Mark Ng]
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer
# [http://www.jasonbolton.com Jason Bolton] - front-end designer
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday).
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher
# [http://feedblog.org Kevin Burton] - developer
# [http://jobspice.com Dane Hurtubise] - developer
# [http://developer.netflix.com JR Conlin] - developer, publisher
# Chirag Shah - developer
# [http://www.wezaggle.com Jesse Hammons] - developer [http://www.wezaggle.com Zaggle Social Calendar]
# [http://matthewlevine.com Matthew Levine] - developer
# [http://farukat.es/ Faruk Ateş] - UX Designer, developer
# [http://fourkitchens.com/ David Strauss] - Drupal, developer
# [http://huyhong.com/ Huy Hong] - Frontend Developer, UI/UX/UE, UGC nut
# [http://objectadjective.com Jeremy Anderson] - UX/UI/ID Designer, developer
# [http://objectadjective.com Lauren Scime] - front end designer / developer
# [http://blog.oofn.net Chad Weider] developer, designer, front-end, back-end, etc.
# (and about 35 more folks, according to [http://upcoming.yahoo.com/event/2888376/ Upcoming] as of noon Thursday 2009-7-23)
# ...

==schedule==
Outline of schedule for the weekend - more details at the DevCamp!
* Saturday July 25th
** 11:00am - planners+volunteers onsite for setup
** 12:00pm - registration, lunch
** intro session, what is a devcamp, introductions
** hack/project brainstorming and proposals
** day 1 building sessions
** dinner and group photo
** day 1 demos and social hour
** evening open hacking session (like DevHouse) / iteration on hacks/projects

* Sunday July 26th
** 10:00am - breakfast
** day 2 working sessions on hacks/projects
** 12:30pm lunch
** day 2 working sessions continued
** second day demos and wrap-up
** venue clean-up
** 5pm venue exit

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Cafe - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* '''(Sunday)''' '''CSS3, HTML5 and microformats "Zen Garden"''' - same premise as the CSS Zen Garden of yore, but with a strong emphasis on CSS3 advancements, microformats enrichment and done in HTML5. [[User:KuraFire|Faruk Ateş]]
* '''CheatSheet Translation''' [[User:Brian|Brian Suda]] This is a request to anyone who is speaks another language. I created the PDF cheatsheet awhile ago http://suda.co.uk/projects/microformats/cheatsheet/ if someone wants to translate it into Spanish, or another language, please let me know. I can send the source InDesign file, or if they send me the translations, I'd be happy to update it myself.
</div>

== projects ==
;short URL for this section
:http://tr.im/ufps
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
* [[hcard-input-interface]] for easy input of user data (creating hCards) by Chad. combined project/session with '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? by [[User:Tantek|Tantek]]
* [[events/2009-07-25-dev-camp/self-updating-address-book]] - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
* [[hcard-contact-autocompletion]] by [[User:Rohit|Rohit Khare]]
* [[microformat-services]] by ________
* [[unified-rsvp]] by _________
* '''hCard to Google Address Book''' [[bookmarklet]]. [[User:Singpolyma|Singpolyma]]
* [[microformat-aggregation]] by [[User:jessehammons|Jesse Hammons]], [[User:yurylifshits|Yury Lifshits]], Andrew McCollum, Dane Hurtibuse, Randy Kerber
* [[twitter bus card exchange/display]] by [[User:perivision|Christopher]]

== photographs ==
* ...

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]
* ...

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, setup, welcome desk'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''

=== planner roles ===
Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

events/2009-07-25-dev-camp

2009-07-26T01:28:49Z

MarkNg: Add a link to the project page

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt while supplies last). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]
** Coffee
** Snacks
** ______?

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
microformatsDevCamp, like any BarCamp, needs you - Sign up to volunteer, attend, design, code, and build with microformats!

=== volunteers ===
Like all [http://barcamp.org BarCamps], this event is what it is because of what everyone puts into it. Volunteer to help setup, check people in, get them setup with a name badge, clean up, and help people in general have a good time and get things done.
* Cindy Li - designer, helping with microformatsDevCamp logo design. done!
** full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
** on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
** designed and ordered buttons for event.Done!

* [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [[http://dentedreality.com.au/ Dented Reality]]. I know my way around the venue, so can help sort out power strips, projectors etc
* ...

=== participants ===

Please register with this [http://spreadsheets.google.com/viewform?formkey=dERvcnQ4SlFsX0ZLQi1KOE8wbk5obUE6MA.. online form].

Want to design interfaces or build stuff with microformats and want help doing it? Sign up! Add yourself. Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one.
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction)
# [http://yury.name Yury Lifshits]
# [http://www.markng.co.uk Mark Ng]
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer
# [http://www.jasonbolton.com Jason Bolton] - front-end designer
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday).
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher
# [http://feedblog.org Kevin Burton] - developer
# [http://jobspice.com Dane Hurtubise] - developer
# [http://developer.netflix.com JR Conlin] - developer, publisher
# Chirag Shah - developer
# [http://www.wezaggle.com Jesse Hammons] - developer [http://www.wezaggle.com Zaggle Social Calendar]
# [http://matthewlevine.com Matthew Levine] - developer
# [http://farukat.es/ Faruk Ateş] - UX Designer, developer
# [http://fourkitchens.com/ David Strauss] - Drupal, developer
# [http://huyhong.com/ Huy Hong] - Frontend Developer, UI/UX/UE, UGC nut
# [http://objectadjective.com Jeremy Anderson] - UX/UI/ID Designer, developer
# [http://objectadjective.com Lauren Scime] - front end designer / developer
# [http://blog.oofn.net Chad Weider] developer, designer, front-end, back-end, etc.
# (and about 35 more folks, according to [http://upcoming.yahoo.com/event/2888376/ Upcoming] as of noon Thursday 2009-7-23)
# ...

==schedule==
Outline of schedule for the weekend - more details at the DevCamp!
* Saturday July 25th
** 11:00am - planners+volunteers onsite for setup
** 12:00pm - registration, lunch
** intro session, what is a devcamp, introductions
** hack/project brainstorming and proposals
** day 1 building sessions
** dinner and group photo
** day 1 demos and social hour
** evening open hacking session (like DevHouse) / iteration on hacks/projects

* Sunday July 26th
** 10:00am - breakfast
** day 2 working sessions on hacks/projects
** 12:30pm lunch
** day 2 working sessions continued
** second day demos and wrap-up
** venue clean-up
** 5pm venue exit

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Cafe - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* '''(Sunday)''' '''CSS3, HTML5 and microformats "Zen Garden"''' - same premise as the CSS Zen Garden of yore, but with a strong emphasis on CSS3 advancements, microformats enrichment and done in HTML5. [[User:KuraFire|Faruk Ateş]]
* '''CheatSheet Translation''' [[User:Brian|Brian Suda]] This is a request to anyone who is speaks another language. I created the PDF cheatsheet awhile ago http://suda.co.uk/projects/microformats/cheatsheet/ if someone wants to translate it into Spanish, or another language, please let me know. I can send the source InDesign file, or if they send me the translations, I'd be happy to update it myself.
</div>

== projects ==
;short URL for this section
:http://tr.im/ufps
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
* [[hcard-input-interface]] for easy input of user data (creating hCards) by Chad. combined project/session with
** '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? by [[User:Tantek|Tantek]]
** see also [[hcard-user-interface]]
* [[hcard-input-interface]] - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
* [[hcard-contact-autocompletion]] by [[User:Rohit|Rohit Khare]]
* [[microformat-services]] by ________
* [[unified-rsvp]] by _________
* '''hCard to Google Address Book''' [[bookmarklet]]. [[User:Singpolyma|Singpolyma]]
* [[microformat-aggregation]] by [[User:jessehammons|Jesse Hammons]], [[User:yurylifshits|Yury Lifshits]], Andrew McCollum, Dane Hurtibuse, Randy Kerber

== photographs ==
* ...

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]
* ...

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, setup, welcome desk'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''

=== planner roles ===
Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

events/2009-07-25-dev-camp

2009-07-20T09:26:52Z

MarkNg: adding myself as an attendee

mobile

2008-09-12T12:56:22Z

MarkNg: /* Nokia */ I tested the N95 with vcal and vcard on recent projects..

<h1>mobile</h1>

'''This page is a stub and would benefit from your contributions!'''

{{TOC-right}}
Mobile and microformats make for a particularly powerful combination. Microformats help users complete more tasks with fewer steps, and requiring fewer steps is especially important in mobile applications. This page lists current known mobile support of microformats, and ideas/suggestions for mobile applications that could use microformats.

== mobile support ==
=== Treo ===
The Treo browser has good integration with the Treo address book and calendar.

* '''[[hCard]] support.''' Clicking on a "Add to Address Book" link (e.g. on [http://technorati.com/about/contact.html Technorati's contact page]) will prompt the user to add that [[hCard]] directly to their Treo address book.

* '''[[hCalendar]] support.''' Clicking on an "Add to Calendar" link (e.g. like on the [[events]] page) will prompt the user to add [[hCalendar]] events directly to their Treo calendar. (Note: the "Subscribe to" links that use <code>webcal:</code> do not appear to currently work on the Treo.)

=== BlackBerry ===
No support for hCard/vCard/hCalendar/iCalendar in BlackBerry 8700, 81xx, 88xx models. Anybody have experience either way with BlackBerry 9000?
* see [[mobile-advocacy]]

=== iPhone ===
No support for hCard/vCard/hCalendar/iCalendar in first generation iPhone / Safari / Webkit.
No support on iPhone 3G software v2.0.2(5C1), clicking the "add to address book" link as above results in a message saying "Safari can't download this file".

* see [[mobile-advocacy]]

=== Nokia ===

* The S60 3rd generation browser can handle vcards and icals (as those generated by X2V and technorati) extracted from hcards and vcards very well.

List of models: N80, N95, ''(please update)''.

=== Sony Ericsson ===

* The Sony Ericsson W810i can handle vCards generated by X2V (it also supports hCard to vCard to QR-Code (http://www.microform.at/hcard2qrcode/))

== mobile application thoughts ==
If this section gets too big, we can move it to a separate page like [[mobile-user-interface]].

=== browser address book integration ===
Every mobile browser should auto-detect [[hCards]] and provide the user a simple/unobtrusive user interface to add them to their mobile address book.

Example: you are browsing a business site, or business listings (e.g. on Google Maps) which list business name, telephone number, address, URL etc. With a simple click or two, it should be possible to save those listings in your address book for future reference or navigation (see below).

=== browser calendar integration ===
Every mobile browser should auto-detect [[hCalendar]] events and provide the user a simple/unobtrusive user interface to add (or subscribe to) them to their mobile address book.

Example: you are browsing an event site (e.g. Upcoming.org), or event listings on a business site, and see event names, start/end times, locations, etc. With a simple click or two, it should be possible to save those events in your calendar for future reference / alarms etc.

=== mapping and navigation ===
[[adr]] and [[geo]] microformats are useful for mobile mapping and navigation applications. (from tweet: [http://twitter.com/microformats/statuses/916437155]).

The most obvious thing to do is extending support for [[geo]] so you can get directions to places from browsers, so you could, for example, get off the train, go to Upcoming.org on your mobile, click the address and have the mobile mapping applications walk you there. (from tweets [http://twitter.com/markng/statuses/916433126], [http://twitter.com/markng/statuses/916436304]).

=== url dialing ===
Most phones have a way of invoking a call from the browser or from applications built in the native languages (JavaME, Python etc.) - it'd be useful if you could have a really simple way of putting in a URI, and it finding the relevant hCard on the page and auto-dials it. I can remember "companyname.com" but not some long phone number. I'm thinking of building something broadly on this line using JavaME, backed by a web service to get the numbers and return them to the device (favouring hCards, but regexing for things that look like phone numbers if it doesn't find any). This came to me a while back when I was walking around London trying to find a shop - I knew their URL but had no idea of their phone number. --[[User:TomMorris|TomMorris]] 05:07, 12 Sep 2008 (PDT)

=== effortlessly add a contact to the address book ===
By using a bit of URL voodoo we can provide a [http://en.wikipedia.org/wiki/QR_Code QR Code] (here's a [http://reader.kaywa.com/ reader])so that the user can point their phone at the image and following the URL, a popup appears prompting them to add the contact to their address book. '''Downside:''' It requires internet access.

Example: [http://chart.apis.google.com/chart?chs=500x500&cht=qr&chl=http://suda.co.uk/projects/microformats/hcard/get-contact.php?uri=http://id.andr3.net] (Thank Brian Suda for X2V!) --[[User:Andr3|Andr3]] 01:19PM, 12 Sep 2008 (WEST)

== thanks ==
* [http://twitter.com/bryanrieger @bryanrieger] for [http://twitter.com/bryanrieger/statuses/916416344 asking the question] on Twitter.
* [http://twitter.com/markng @markng] for providing some ideas with user scenarios.

== see also ==
* [[advocacy]]
* [[mobile-advocacy]]
* [[user-interface]]
* [[operator-phone-tests]]

user-interface

2008-09-10T13:51:32Z

MarkNg: make that a list.

<h1> User Interface </h1>
{{TOC-right}}
Recently there have been many really good user interface ideas and suggestions for working with microformats. This page serves to collect and document them so that we may be inspired by and iterate on each others' works.

== Design Guidelines ==
These are some suggested design guidelines for Web designers and developers by [http://blog.mozilla.com/faaborg/ Alex Faaborg], a user experience designer at Mozilla:
*Design based on actions, not data. A button that says "Send to Calendar" is considerably more useable than a green button that simply says "hCalendar"
*Use iconic images instead of acronyms. In addition to being more descriptive, they localize better. Here are some I've been showing in various talks: [http://people.mozilla.com/~faaborg/files/20061213-fundamentalTypes/fundamentalTypesStatic.jpg_large.jpg microformat icons]. These are still very preliminary. Mozilla will likely release all of the source artwork for our microformat icons under a creative commons license around the launch of Firefox 3. This will enable Web designers to integrate the icons into their sites, and other Web browsers can consider using a similar set of icons.

== Design Challenges ==
* Chris Messina: "What kind of solutions can we come up with that are single click only?"
* Alex Faaborg: Mozilla has had inquiries from reporters in the mainstream media (Wired and Business Week) who wanted to cover microformats in stories about the future of the Web browser, but they then later backed out because they felt the term "microformats" would only appeal to developers, and not the average reader. These types of mainstream stories need to focus on the user experience, and not the underlying technology, but what term should reporters use to describe the overall feature?
** I think we should stick with the term "microformats" until someone comes up with a better term that doens't "only appeal to developers". Note that we should avoid terms which are either overloaded, or dilute the concepts, or are just another form of made-up jargon. [[User:Tantek|Tantek]]

== Social Network Portability ==
See the separate [[social-network-portability]] page.

== Browser Integration ==
From visions to screenshot brainstorms to working plugins to shipping implementations, there is a lot going on with browser integration of microformats support.

=== Currently ===
* <del>The [[Flock]] browser ships with microformats support built-in.</del> - This has not been confirmed. -- Chris Messina.
* The [[Operator]] plug-in adds microformats detection and integration to [[Firefox]] version 1.5-2, [[Netscape Navigator]] versions 9 and [[Flock]] 1.0 [http://notizblog.org/2007/10/21/operator-unter-navigator-90/ http://notizblog.org/wp-content/uploads/2007/10/micro-netscape.png]
* A [[Safari|Safari microformats plugin]] has been implemented (requires OSX10.5 ) based on Jon Hicks's mockup: [http://microformats.org/wiki/safari http://farm3.static.flickr.com/2309/2036669631_6e99870645.jpg]

=== Soon ===
* [[Firefox]] version 3.0 has support similar to Operator built-in. See the [[Firefox]] page for details.

=== Vision ===
[http://blog.mozilla.com/faaborg/2006/12/13/microformats-part-2-the-fundamental-types/ http://people.mozilla.com/~faaborg/files/20061213-fundamentalTypes/informationBroker.jpg]Web Browser as Information Broker - part of a [http://blog.mozilla.com/faaborg/2006/12/13/microformats-part-2-the-fundamental-types/ blogpost by Alex Faaborg on Microformats - The Fundamental Types] 

=== In General ===
Browser support for microformats consists of three things in general:
# Automatically detect the presence of microformats on a page
# Parse them into a set of microformats for that page (preferably maintaining their relative relationships perhaps within a tree structure).
# Do something useful with them

=== Do something useful ===
Do something useful could be any or all of:
* '''User interface'''. Indicate the presence of microformats, and provide the user with an additional user interface for common actions to take with those microformats
* '''API'''. Provide an API (DOM extensions on "document" object?) to access those microformats for browser extension developers.
* '''Cache'''. cache that set/tree of parsed microformats along with the URL/Title/date-accessed of the page in the browser navigation "History" or even page cache, and then use that set of objects for various auto-complete/auto-fill uses and other enhancements to existing browser features.

=== Indicate presence of microformats ===
Browsers can indicate the presence of microformats on a page in several ways.
* one or more icons
** either a generic microformats icon, or
** an icon for each type of microformat present
** in the toolbar, in the footerbar, or perhaps on the margins of the page
* a special cursor when hovering over
** See [http://wiki.mozilla.org/ContentHandling:User_Interface/Preferences_Microformats mozilla wiki: ContentHandling:User Interface/Preferences Microformats]

Discussion and mockups / screenshots of indicating the presence of microformats:

* [http://blog.mozilla.com/faaborg/2007/02/04/microformats-part-4-the-user-interface-of-microformat-detection/ Conceptual Mockups of Microformat Detection in Firefox 3]
* [http://ben-ward.co.uk/journal/microformats-ui/ Ben Ward: Microformats in Web Browsers] [http://ben-ward.co.uk/journal/microformats-ui/ http://ben-ward.co.uk/res/posts/uf-web-browser/autodiscovery.png]
* [http://glazkov.com/blog/margin-marks/ Margin Marks UI Concept], [http://flickr.com/photos/dglazkov/sets/72157601860335196/ Margin Marks Comps on Flickr] [http://glazkov.com/blog/margin-marks/ http://farm2.static.flickr.com/1098/1323814472_819bdd6373_m.jpg]

=== Authoring Tools ===

Examples and ideas for tools to author microformats within CMS tools.

* [http://www.undergroundwebdesigns.com/tinyMCE-hcard-plugin.html tinyMCE hcard plugin]
* [http://www.undergroundwebdesigns.com/tinyMCE-hcalendar-plugin.html tinyMCE hcalendar plugin]
* [http://matthewlevine.com/projects/hcard-wizard hcard wizard]

It would be nice to have a bookmarklet that you can just hit on a selected bit of text in a textarea or WYSIWYG editor to turn into an hcard with just FN, and not have to fill out a form. Whilst this doesn't give us rich information, it's really easy and doesn't create much extra work burden.

=== Additional user interface ===
Some examples of additional user interface for common actions to take with microformats found in pages, grouped by specific microformat. Note that most of these use cases should be applicable to all instances of the microformat on the page at once (e.g. export all contacts), or for a selection of instances (e.g. export selected contacts), or one just one specific instance (e.g. export contact XYZ).

* [[hcard|hCard]] - see [[hcard-user-interface#Additional_user_interface|Additional hCard user interfaces]]
* [[hcalendar|hCalendar]]:
** "Add to Calendar" (convert the hCalendar events to iCalendar vEvents (.ics) and pass them onto the OS to automatically open/incorporate into the user's preferred local calendaring application).
** add to gCalendar, Yahoo Calendar, Upcoming, Eventful (etc.)
** "Subscribe to Calendar" - construct and pass on a conversion URL (e.g. using X2V, or prefixing the URL to the current page (or to the specific event within using a fragment identifier) with webcal://feeds.technorati.com/events/ ) and pass it onto the OS to get the OS to pass the URL onto the user's preferred local calendaring application for that app to subscribe to.
** export as text/ [[csv|comma-separated-variables]] (CSV) to allow editing, sorting and/ or import into spreadsheets/ databases, etc. (or concatenate to existing file).
*[[adr]]
** export a vCard, either prompting for a name, or using default place-holder text
** export as text/ CSV as above
** find on map of user's choosing
** find pictures, nearest hotel, nearest restaurant, etc., using site of user's choosing
** see also [[hcard-user-interface#Additional_user_interface|Additional hCard user interfaces]]
*[[geo|Geo]]
** find on map of user's choosing
** find pictures, nearest hotel, nearest restaurant, etc., using site of user's choosing
** export as [[KML]]/ [[GPX]] file; or concatenate to existing file
** export as text/ CSV as above
** send (in suitable format) via bluetooth to GPS device.
* [[hreview|hReview]]
**If the item is a book, look up on library site(s) of user's choosing
**If the item is a book, generate COinS or other standard citation mark-up
**If the item is a book, film/ DVD, CD, etc., look up on shopping site(s) of user's choosing
* [[hatom|hAtom]]
** let the user subscribe to the page as a series of hAtom hentrys
*** challenges to keep in mind:
**** what if user goes to permalink of a blog post and that has just one static hentry - does subscribe make sense? wouldn't it be better if the default subscribe verb in that context subscribed to the blog home page?
**** or if user goes to an archive page which just has a set of static hentry items - again, how does subscribe help? wouldn't it be better if the default subscribe verb in that context subscribed to the blog home page?
**** possible solution: using a combination of [[rel-home]] and [[rel-archive]] (one of several already widely deployed [[existing-rel-values]] in WordPress and other [[blogging-tools]]), it may be possible to identify the home page of a blog from a post permalink or archive page, or vice versa, and thus enable a smarter "subscribe to this blog" functionality.
* [[hresume|hResume]]
** ???

Discussion and mockups / screenshots of additional user interface for microformats (some screenshots are only available at the destination links, please click through).

* [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ Microformats in Flock]
* NetNewsWire [http://flickr.com/photos/factoryjoe/454706107/in/photostream/ detects] and then [http://flickr.com/photos/factoryjoe/454705203/ converts hcard and hcalendar data] in feed entries: [http://flickr.com/photos/factoryjoe/454705203/ http://farm1.static.flickr.com/183/454705203_33f9b8d7c6_o.png]
* [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin Jon Hicks: Proposal for a Safari Microformats plugin]

== Implementations ==
See [[implementations]], and document examples of good UI from there, here.

=== Plugins ===
* [[Operator]] Firefox extension
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) by Robert de Bruin can display and export some microformats.

=== Greasemonkey user scripts ===
* http://greasemonkey.makedatamakesense.com/callto_tel/ by Scott Reynen
* Some [[Greasemonkey]] scripts use a separate iFrame for microformat content
* Other [[Greasemonkey]] scripts insert an icon inline into the page

=== Browser buttons ===
* [[Miffy]] inserts a green square into the document to represent the presence of microformat

=== CSS user stylesheets ===
* Jon Hicks has written [http://www.hicksdesign.co.uk/journal/highlight-microformats-with-css a user stylesheet for Mac browsers] that highlights hCard and hCalendar data.

=== Planning and Discussion ===
*[http://wiki.mozilla.org/Microformats Discussion of microformat detection in Firefox 3]
*[http://wiki.mozilla.org/Microformats/UE/ideas UI brainstorming on the Mozilla Wiki]
* The [http://wiki.caminobrowser.org/Development:Planning:Microformats Camino Wiki has a page] where future microformats support is being discussed and organized

== Simpler Markup Languages ==
There are plenty of [[wiki-formats]] that attempt to make it easier for more people author semantic markup, often with textually decorative punctuation.

As these simpler markup languages are something that *users* are expected to type, they are user interface.

=== Markdown extension for hCalendar ===
See [http://article.gmane.org/gmane.text.markdown.general/2027 Markdown and the hCal microformat] which proposes an extension to the Markdown text markup language to capture and represent hCalendar event semantics in a human editable form.

== See Also ==
* [[browsers]]
* [[hcard-user-interface]]
* [[data-portability]]
* [[social-network-portability]]

user-interface

2008-09-10T13:50:16Z

MarkNg: Add authoring tools.

<h1> User Interface </h1>
{{TOC-right}}
Recently there have been many really good user interface ideas and suggestions for working with microformats. This page serves to collect and document them so that we may be inspired by and iterate on each others' works.

== Design Guidelines ==
These are some suggested design guidelines for Web designers and developers by [http://blog.mozilla.com/faaborg/ Alex Faaborg], a user experience designer at Mozilla:
*Design based on actions, not data. A button that says "Send to Calendar" is considerably more useable than a green button that simply says "hCalendar"
*Use iconic images instead of acronyms. In addition to being more descriptive, they localize better. Here are some I've been showing in various talks: [http://people.mozilla.com/~faaborg/files/20061213-fundamentalTypes/fundamentalTypesStatic.jpg_large.jpg microformat icons]. These are still very preliminary. Mozilla will likely release all of the source artwork for our microformat icons under a creative commons license around the launch of Firefox 3. This will enable Web designers to integrate the icons into their sites, and other Web browsers can consider using a similar set of icons.

== Design Challenges ==
* Chris Messina: "What kind of solutions can we come up with that are single click only?"
* Alex Faaborg: Mozilla has had inquiries from reporters in the mainstream media (Wired and Business Week) who wanted to cover microformats in stories about the future of the Web browser, but they then later backed out because they felt the term "microformats" would only appeal to developers, and not the average reader. These types of mainstream stories need to focus on the user experience, and not the underlying technology, but what term should reporters use to describe the overall feature?
** I think we should stick with the term "microformats" until someone comes up with a better term that doens't "only appeal to developers". Note that we should avoid terms which are either overloaded, or dilute the concepts, or are just another form of made-up jargon. [[User:Tantek|Tantek]]

== Social Network Portability ==
See the separate [[social-network-portability]] page.

== Browser Integration ==
From visions to screenshot brainstorms to working plugins to shipping implementations, there is a lot going on with browser integration of microformats support.

=== Currently ===
* <del>The [[Flock]] browser ships with microformats support built-in.</del> - This has not been confirmed. -- Chris Messina.
* The [[Operator]] plug-in adds microformats detection and integration to [[Firefox]] version 1.5-2, [[Netscape Navigator]] versions 9 and [[Flock]] 1.0 [http://notizblog.org/2007/10/21/operator-unter-navigator-90/ http://notizblog.org/wp-content/uploads/2007/10/micro-netscape.png]
* A [[Safari|Safari microformats plugin]] has been implemented (requires OSX10.5 ) based on Jon Hicks's mockup: [http://microformats.org/wiki/safari http://farm3.static.flickr.com/2309/2036669631_6e99870645.jpg]

=== Soon ===
* [[Firefox]] version 3.0 has support similar to Operator built-in. See the [[Firefox]] page for details.

=== Vision ===
[http://blog.mozilla.com/faaborg/2006/12/13/microformats-part-2-the-fundamental-types/ http://people.mozilla.com/~faaborg/files/20061213-fundamentalTypes/informationBroker.jpg]Web Browser as Information Broker - part of a [http://blog.mozilla.com/faaborg/2006/12/13/microformats-part-2-the-fundamental-types/ blogpost by Alex Faaborg on Microformats - The Fundamental Types] 

=== In General ===
Browser support for microformats consists of three things in general:
# Automatically detect the presence of microformats on a page
# Parse them into a set of microformats for that page (preferably maintaining their relative relationships perhaps within a tree structure).
# Do something useful with them

=== Do something useful ===
Do something useful could be any or all of:
* '''User interface'''. Indicate the presence of microformats, and provide the user with an additional user interface for common actions to take with those microformats
* '''API'''. Provide an API (DOM extensions on "document" object?) to access those microformats for browser extension developers.
* '''Cache'''. cache that set/tree of parsed microformats along with the URL/Title/date-accessed of the page in the browser navigation "History" or even page cache, and then use that set of objects for various auto-complete/auto-fill uses and other enhancements to existing browser features.

=== Indicate presence of microformats ===
Browsers can indicate the presence of microformats on a page in several ways.
* one or more icons
** either a generic microformats icon, or
** an icon for each type of microformat present
** in the toolbar, in the footerbar, or perhaps on the margins of the page
* a special cursor when hovering over
** See [http://wiki.mozilla.org/ContentHandling:User_Interface/Preferences_Microformats mozilla wiki: ContentHandling:User Interface/Preferences Microformats]

Discussion and mockups / screenshots of indicating the presence of microformats:

* [http://blog.mozilla.com/faaborg/2007/02/04/microformats-part-4-the-user-interface-of-microformat-detection/ Conceptual Mockups of Microformat Detection in Firefox 3]
* [http://ben-ward.co.uk/journal/microformats-ui/ Ben Ward: Microformats in Web Browsers] [http://ben-ward.co.uk/journal/microformats-ui/ http://ben-ward.co.uk/res/posts/uf-web-browser/autodiscovery.png]
* [http://glazkov.com/blog/margin-marks/ Margin Marks UI Concept], [http://flickr.com/photos/dglazkov/sets/72157601860335196/ Margin Marks Comps on Flickr] [http://glazkov.com/blog/margin-marks/ http://farm2.static.flickr.com/1098/1323814472_819bdd6373_m.jpg]

=== Authoring Tools ===

Examples and ideas for tools to author microformats within CMS tools.

[http://www.undergroundwebdesigns.com/tinyMCE-hcard-plugin.html tinyMCE hcard plugin]
[http://www.undergroundwebdesigns.com/tinyMCE-hcalendar-plugin.html tinyMCE hcalendar plugin]
[http://matthewlevine.com/projects/hcard-wizard hcard wizard]

It would be nice to have a bookmarklet that you can just hit on a selected bit of text in a textarea or WYSIWYG editor to turn into an hcard with just FN, and not have to fill out a form. Whilst this doesn't give us rich information, it's really easy and doesn't create much extra work burden.

=== Additional user interface ===
Some examples of additional user interface for common actions to take with microformats found in pages, grouped by specific microformat. Note that most of these use cases should be applicable to all instances of the microformat on the page at once (e.g. export all contacts), or for a selection of instances (e.g. export selected contacts), or one just one specific instance (e.g. export contact XYZ).

* [[hcard|hCard]] - see [[hcard-user-interface#Additional_user_interface|Additional hCard user interfaces]]
* [[hcalendar|hCalendar]]:
** "Add to Calendar" (convert the hCalendar events to iCalendar vEvents (.ics) and pass them onto the OS to automatically open/incorporate into the user's preferred local calendaring application).
** add to gCalendar, Yahoo Calendar, Upcoming, Eventful (etc.)
** "Subscribe to Calendar" - construct and pass on a conversion URL (e.g. using X2V, or prefixing the URL to the current page (or to the specific event within using a fragment identifier) with webcal://feeds.technorati.com/events/ ) and pass it onto the OS to get the OS to pass the URL onto the user's preferred local calendaring application for that app to subscribe to.
** export as text/ [[csv|comma-separated-variables]] (CSV) to allow editing, sorting and/ or import into spreadsheets/ databases, etc. (or concatenate to existing file).
*[[adr]]
** export a vCard, either prompting for a name, or using default place-holder text
** export as text/ CSV as above
** find on map of user's choosing
** find pictures, nearest hotel, nearest restaurant, etc., using site of user's choosing
** see also [[hcard-user-interface#Additional_user_interface|Additional hCard user interfaces]]
*[[geo|Geo]]
** find on map of user's choosing
** find pictures, nearest hotel, nearest restaurant, etc., using site of user's choosing
** export as [[KML]]/ [[GPX]] file; or concatenate to existing file
** export as text/ CSV as above
** send (in suitable format) via bluetooth to GPS device.
* [[hreview|hReview]]
**If the item is a book, look up on library site(s) of user's choosing
**If the item is a book, generate COinS or other standard citation mark-up
**If the item is a book, film/ DVD, CD, etc., look up on shopping site(s) of user's choosing
* [[hatom|hAtom]]
** let the user subscribe to the page as a series of hAtom hentrys
*** challenges to keep in mind:
**** what if user goes to permalink of a blog post and that has just one static hentry - does subscribe make sense? wouldn't it be better if the default subscribe verb in that context subscribed to the blog home page?
**** or if user goes to an archive page which just has a set of static hentry items - again, how does subscribe help? wouldn't it be better if the default subscribe verb in that context subscribed to the blog home page?
**** possible solution: using a combination of [[rel-home]] and [[rel-archive]] (one of several already widely deployed [[existing-rel-values]] in WordPress and other [[blogging-tools]]), it may be possible to identify the home page of a blog from a post permalink or archive page, or vice versa, and thus enable a smarter "subscribe to this blog" functionality.
* [[hresume|hResume]]
** ???

Discussion and mockups / screenshots of additional user interface for microformats (some screenshots are only available at the destination links, please click through).

* [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ Microformats in Flock]
* NetNewsWire [http://flickr.com/photos/factoryjoe/454706107/in/photostream/ detects] and then [http://flickr.com/photos/factoryjoe/454705203/ converts hcard and hcalendar data] in feed entries: [http://flickr.com/photos/factoryjoe/454705203/ http://farm1.static.flickr.com/183/454705203_33f9b8d7c6_o.png]
* [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin Jon Hicks: Proposal for a Safari Microformats plugin]

== Implementations ==
See [[implementations]], and document examples of good UI from there, here.

=== Plugins ===
* [[Operator]] Firefox extension
* [https://addons.mozilla.org/firefox/2240/ Tails Export] (Firefox extension) by Robert de Bruin can display and export some microformats.

=== Greasemonkey user scripts ===
* http://greasemonkey.makedatamakesense.com/callto_tel/ by Scott Reynen
* Some [[Greasemonkey]] scripts use a separate iFrame for microformat content
* Other [[Greasemonkey]] scripts insert an icon inline into the page

=== Browser buttons ===
* [[Miffy]] inserts a green square into the document to represent the presence of microformat

=== CSS user stylesheets ===
* Jon Hicks has written [http://www.hicksdesign.co.uk/journal/highlight-microformats-with-css a user stylesheet for Mac browsers] that highlights hCard and hCalendar data.

=== Planning and Discussion ===
*[http://wiki.mozilla.org/Microformats Discussion of microformat detection in Firefox 3]
*[http://wiki.mozilla.org/Microformats/UE/ideas UI brainstorming on the Mozilla Wiki]
* The [http://wiki.caminobrowser.org/Development:Planning:Microformats Camino Wiki has a page] where future microformats support is being discussed and organized

== Simpler Markup Languages ==
There are plenty of [[wiki-formats]] that attempt to make it easier for more people author semantic markup, often with textually decorative punctuation.

As these simpler markup languages are something that *users* are expected to type, they are user interface.

=== Markdown extension for hCalendar ===
See [http://article.gmane.org/gmane.text.markdown.general/2027 Markdown and the hCal microformat] which proposes an extension to the Markdown text markup language to capture and represent hCalendar event semantics in a human editable form.

== See Also ==
* [[browsers]]
* [[hcard-user-interface]]
* [[data-portability]]
* [[social-network-portability]]

hresume-examples-in-wild

2008-04-15T18:56:13Z

MarkNg: /* New Examples */

<h1>hResume examples in the wild</h1>

This page is '''informative'''.

The following sites have published '''hResumes''', and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing, etc.

__TOC__

== New Examples ==
If you have an hResume on your own page, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hresume|hResume]] markup. Examples added without a URL to a page with hResume markup may be removed.

* [[User:MarkNg|Mark Ng]] has marked up his [http://www.markng.co.uk/cv CV] with hResume.
* [[User:SidRoberts|Sid Roberts]] has marked up his [http://www.sidroberts.co.uk/cv/ CV] with hResume.
* [http://bergantinedesign.us/about/resume Joseph Bergantine] has marked up his resume with hResume
* [[User:NathanChase|Nathan Chase]] has marked up [http://www.nathanchase.com/resume.html his resume] with hResume.
* [[User:WikiObert|Alberto Ramacciotti]] has marked up an italian and an english version of his h[http://obertfsp.com/cv.html Resume].
* [[User:JaredEssig|Jared Essig]] has styled and marked up his h[http://prochor.us/resume Resume].
* [[User:Dreamisle|David Millar]] has *hopefully successfully* marked up [http://thegriddle.net/pages/resume his Resume] with hResume.
* [[User:Bczerniak|Brad Czerniak]] has created [http://brad.hawidu.com his Resume] with hResume.
* [[User:BenDodson|Ben Dodson]] has marked up [http://bendodson.com/cv/ his CV] with hResume.
* [[User:Twoplayer|Stephen Kelly]] has marked up his [http://www.twoplayer.net/stephen-kelly/cv.php CV] with hResume.
* [[User:MattWilliams|Matt Williams]] has marked up his [http://mattwilliamsnyc.com/resume/ resume] with hResume.
* [[User:Niall Kennedy|Niall Kennedy]] has marked up his [http://www.niallkennedy.com/about/resume.html résumé] with hResume.
* [[User:ManasTungare|Manas Tungare]] has marked up his [http://manas.tungare.name/resume/ Résumé] with hResume.
* [[User:Eferraiuolo|Eric Ferraiuolo]] has marked up his [http://eric.ferraiuolo.name/resume/ Resume] with hReesume
* [[User:ChristopheDucamp|Christophe Ducamp]] has marked up his [http://www.elanceur.org/CV_ChristopheDucampFr.html C.V.] with hResume
* [[User:RichardDavies|Richard Davies]] has marked up his [http://www.richarddavies.us/resume/ resume] as an hResume.
* [[User:JeffMcNeill|jeffmcneill]] has marked up [http://jeffmcneill.com/microformats/hresume-jeffmcneill.html his resume] with hResume
* Actor [[User:DavidSwain|David Swain]] has marked up his [http://davidswain.co.uk/cv cv] as an hResume.
* [[User:CiaranMc|Ciaran McNulty]] has marked up his [http://ciaranmcnulty.com/assets/files/Ciaran_McNulty_CV.html resume] as an hResume.
* [[User:RobCrowther|Rob Crowther]] has marked up his [http://www.dotrob.com/cv.html resume] as an hResume.
* [[User:Ajaswa|Andrew Jaswa]] has marked up his [http://www.gotkicked.net/hresume resume] as an hResume.
* [[User:ScottWallick|Scott Allan Wallick]] has [http://scottwallick.com/about/resume/ his resume] as an hResume.
* Ed Lau has [http://www.edlabs.net/ his resume] marked up with hResume.
* [[User:AndySmith|Andy Smith]] has marked up [http://ymkm.com/AndySmith.html his CV] with hResume.
* [[User:BruceDailey|Bruce Dailey]] has marked up his [http://www.jciti.com/cv/cv.php resume] as an hResume.
* [[User:JesseNewland|Jesse Newland]] has marked up his [http://resume.jnewland.com resume] as an hResume.
* [[User:Harriyott|Simon Harriyott]] has his [http://harriyott.com/cv.aspx curriculum vitae] as an hResume.
* [[User:BradT|Brad Touesnard]] has scraped together [http://brad.touesnard.com/documents/resume/ his resume] with the [http://brad.touesnard.com/projects/wordpress/linkedin-hresume/ LinkedIn hResume for Wordpress] plugin.
* [[User:ChadL|Chad Lindstrom]] has extended his [http://chadlindstrom.ca/resume/ resume] with hResume.
* Dawn Waswick has marked up [http://www.miniminx.com/portfolio/resume.cfm her CV] with hResume.
* [[User:Rolandinsh|Rolands Umbrovskis]] has [http://www.rolandinsh.lv/?ro=hResume marked up his CV] with hResume.
* [http://linkedin.com/ LinkedIn] has ~9 million Public Profiles marked up in hResume, e.g. [http://www.linkedin.com/in/steveganz Steve Ganz's Public Profile].
* [http://steinhardt.nyu.edu/ NYU Steinhardt] has [http://steinhardt.nyu.edu/faculty_bios/list/Faculty 240+ faculty bios marked up], e.g. [http://steinhardt.nyu.edu/faculty_bios/view/Susan_Murray]. ([[User:WizardIsHungry|Jon Williams]])
* [[User:ClintAndrewHall|Clint Hall]] has marked up his [http://www.clintandrewhall.com/resume.html resume] as an hResume.
* [[User:Csarven|Sarven Capadisli]] has marked up his [http://www.csarven.ca/cv Curriculum Vitae] as an hResume.
* [[User:Jax|Xavier Roy]] has marked his [http://xavierroy.com/resume/ resume] with hResume
* [[User:SanchTheFat|Robert O'Rourke]] has marked up his [http://robert.o-rourke.org/ CV] with hResume.
* [[User:Keri Henare|Keri Henare]] has marked up [http://www.kerihenare.com/cv/ his Curriculum Vitae] using hResume.
* [[User:Kwilson|Kenn Wilson]] has marked up [http://www.six23.net/resume/kenn-wilson.html his resume] using hResume, following [[User:Ralph Brandi|Ralph Brandi]]'s method of using object.include.
* [[User:Ralph Brandi|Ralph Brandi]] has [http://www.brandi.org/ralph/resume/ marked up his resume] with hResume, additionally using the object.include method to associate one description with three hCalendar experiences.
* [[User:Pat Ramsey|Pat Ramsey]] has his [http://www.patramsey.net/resume.html resume] marked up as an hResume.
* [[User:Wim Le Page|Wim Le Page]] has also marked up [http://adrem.ua.ac.be/~wlepage/curriculum-vitae/ his curriculum vitae] as an hResume.
* [[user:Jonathan Arkell|Jonathan Arkell]] has posted an [http://portfolio.jonnay.net/cv/ hResume] on his portfolio website.
* [http://steve.ganz.name/hresume/ Steve Ganz - hResume 0.1]
* [[User:Dave Cardwell|Dave Cardwell]] has marked up [http://davecardwell.co.uk/cv/ his curriculum vitae] as an hResume.
* [[User:EdwardOConnor|Edward O'Connor]]'s [http://edward.oconnor.cx/resume/ resume] is in hResume, and has some experimental JavaScript in it to extract a skill summary from the resume.
* [[User:Lindsey Simon|Lindsey Simon]] has his [http://www.commoner.com/~lsimon/lindsey_simon_resume.html resume] marked up as an hResume - with lots of thanks to Pat Ramsey.
* [[User:Ben Ward|Ben Ward]] has published [http://ben-ward.co.uk/cv his CV] with hResume.
* [http://www.kelleychambers.com Kelley Chambers] has published her [http://www.kelleychambers.com/resume resume] via [http://www.ssdesigninteractive.com/ssdesign/?p=96 Sajid Saiyed's Microformat hResume Plugin for Wordpress].
* [[User:Fishy5|Brennan Falkner]] used hResume to markup his [http://my.usf.edu/bbcswebdav/users/bfalker/resume.html resume].
* [http://www.zachary.com/creemer/resume.html David Creemer's resume] uses hResume, with thanks to Pat Ramsey for the CSS.
* [[User:ChristophBurgdorfer|Christoph Burgdorfer]] has integrated his hResume into a [http://emcons.net/index.php mashup].

== Examples with some problems ==

If you find a problem with any example in any other section, please move it here, and note the precise problem and cite the section of the [[hresume|hResume spec]] that appears to be violated. If the example that was moved here is yours, and you want to improve it, see the [[hresume-faq|hResume FAQ]], or raise any queries on [[hresume-issues|hResume Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you. 

* Inga Scholes had <nowiki>http://inga-art.co.uk/cv</nowiki> her CV marked up with hResume.
** '''invalid''' - hResume version missing as of 2007-10-28.
* [[User:RudyDesjardins|Rudy Desjardins]] has marked up his [http://rudy.theendless.org/resume/index.html resume] as an hResume.
** '''Invalid''' : hCard seems invalid
* [[User:MattBosworth|Matt Bosworth]] has marked up his chronological [http://www.codetastic.com/resume-chrono.html resume] and his functional [http://www.codetastic.com/resume-functional.html resume] with hResume.
** '''Invalid''' -- hCalendar's summaries to be specified
* [[User:AndrewPendrick|Andrew Pendrick]] has marked up his [http://www.andrewpendrick.co.uk/cv.html resume] as an hResume.
**'''Invalid''' - hCalendars's summaries to be specified (per Operator).[[User:ChristopheDucamp|xtof]]
* [[User:WebOrganics|Martin McEvoy]] has cobbled together his [http://weborganics.co.uk/hResume/ resume] as a hResume.
**'''Invalid''' - Three hCalendars have empty summary; several tags are invalid (per Operator). [[User:AndyMabbett|Andy Mabbett]] 22:48, 1 Sep 2007 (PDT)
* [[User:DmytroShteflyuk|Dmytro Shteflyuk]] has marked up [http://kpumuk.info/curriculum-vitae/ his resume] as an hResume.
** Invalid; job titles contain hCards without a "fn" (either directly or via object). --[[User:Gazza|Gazza]] 04:27, 1 May 2007 (PDT)
* [[user:Izo|Mathieu Drouet]] has posted an [http://izo.aucuneid.com/hresume.html hResume].
** ''Incorrect root class name hResume? -- [[DavidJanes]]''
* [[User:Stauciuc|Sergiu Sebastian Tauciuc]] has his [http://www.sergiutauciuc.ro/en/cv.html curriculum vitae] as an hResume.
** '''Invalid''' - no contact vCard specified. [[User:AndyMabbett|Andy Mabbett]] 04:05, 10 Mar 2007 (PST)

== Reviewed Examples ==

If you have reviewed a New Example (and you are not the author of the example) and believe it to be valid, go ahead and move it here.
* ...

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

hcard-cheatsheet

2008-03-05T11:17:07Z

MarkNg: /* Profile */ fixing spelling mistake

<h1>hCard cheatsheet</h1>

[[hcard|hCard]] properties and how to use them.

==Profile==
<nowiki><head profile="http://www.w3.org/2006/03/hcard"></nowiki>

==Properties (Class Names)==

*'''vcard''' {1}
**''[[adr]]''*
***type [work|home|pref|postal|dom|intl]?
***post-office-box?
***''street-address''*
***extended-address?
***region?
***locality?
***postal-code?
***country-name?
**''agent''*
**[[hcard-singular-properties#bday|bday]]? ''([[datetime-design-pattern |ISO date]])''
**[[hcard-singular-properties#class|class]]? ''confidentiality/access classification of the ''entire'' hCard''
**''category''*
**''email''*
***type?
***value?
**'''[[hcard-singular-properties#fn|fn]]''' {1}
**[[geo]]?
***latitude?
***longitude?
**''key''*
**''label''*
**''logo''*
**''mailer''*
**[[hcard-singular-properties#n|n]]?
***''honorific-prefix''*
***''given-name''*
***''additional-name''*
***''family-name''*
***''honorific-suffix''*
**''nickname''*
**''note''*
**''org''*
***organization-name?
***''organization-unit''*
**''photo''*
**[[hcard-singular-properties#rev|rev]]? ''datetime of the revision of the ''entire'' hCard''
**''role''*
**[[hcard-singular-properties#sort-string|sort-string]]?
**''sound''*
**''title''*
**''tel''* ''(Note [http://en.wikipedia.org/wiki/E.123 E.123] for formatting info.)''
***type [home|work|pref|fax|cell|pager]?
***value?
**[[hcard-singular-properties#tz|tz]]? ''timezone of the person''
**[[hcard-singular-properties#uid|uid]]? ''applies to the ''entire'' hCard''
**''url''*

{{cheatsheet-key}}
{| border="1" cellpadding="2"
| pref || preferred
|-
| dom || domestic
|-
| intl || international
|-
| cell || mobile
|}

===Notes===
*{{rfc-2119-intro}}
* <code>URL</code> in vCard becomes <code><a class="url" href=...>...</a></code> inside the element with class <code>vcard</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>FN</code> is an abbreviation of "'''formatted name'''".
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src=... alt="Photo of ..." /></code> or <code><object class="photo" data=... type=...>Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.
* Compare <code>TITLE</code> of "Wing Commander" with <code>ROLE</code> of "pilot".

====Adr====
{{adr-note}}

====Geo====
{{geo-note}}

==Related pages==
{{hcard-related-pages}}
*{{cheatsheets}}

hcomment

2008-03-05T09:22:37Z

MarkNg: /* Human vs. Machine Readable */

{{DeprecatedHistoricalPage}}

'''This page needs a major rewrite/edit. It appears to mostly be content copied from [[hReview]] without removing the hReview-specific content such as the draft spec note, date, authors, etc. This can be fixed by:'''
* Analyze what aspects are "comment" specific (rather than just copied from hReview)
* Extract comment-specific ideas/thoughts etc., and place them by themselves into a [[comment-brainstorming]] page.
* Reference [[hAtom]] for possible additional comment brainstorming (i.e. how to markup blog comments (in addition to posts) with hAtom).
* Leave a redirect from this page to [[comment-brainstorming]]
[[User:Tantek|Tantek]] 15:18, 29 Jan 2008 (PST)

= hComment 0.1 =

hComment is a simple, open, distributed comment format suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hComment is one of several [[microformats]] open standards.

{{TOC-right}}

== Draft Specification 2005-06-22 ==

=== Editor ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Authors ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
* [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]
* [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]
* [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]
* [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]
* [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]
* [http://mokolabs.com/ Patrick Crowley], [http://evdb.com EVDB, Inc.]
* [http://edward.oconnor.cx/ Edward O'Connor], [http://evdb.com EVDB, Inc.]

== Introduction ==

In order to enable and encourage the sharing, distribution, syndication, and aggregation, of comments, the authors propose the hComment MicroFormat, an open standard for distributed comments.

A "comment" is a block of text which allows a user to express an opinion, thought, or other feedback about a particular content object (an article, blog entry, event, venue, product, etc.).

At present, every website has its own way of rendering comments into XHTML, making intra-site comment sharing, searching, and aggregation difficult. Trackbacks have shown the potential of intra-site discussion. Why not allow all comments to jump the chasm too?

Note: this standard is a reformulation of the hReview Microformat.

=== Relationship between hComment and hReview ===

A "review" is simply a comment with additional properties such as a rating or a specific object reference. Numerous web sites publish reviews using a broad variety of schema for all sorts of things from products (movies, music, books), to businesses (restaurants, hotels, stores), to events (concerts, theatre), to people (artists, leaders, celebrities), to places (landmarks, parks), to online resources (web pages, files), to reviews of reviews themselves.

Since reviews and comments overlap so substantially, they should share a common microformat standard. So, instead of two mutually exclusive standards which contain 98% of the same functionality, hReview will be expressed in terms of hComment.

==== Expressing hReview in terms of hComment ====

If hReview v0.3 is to be expressed in terms of hComment, here's what would need to be done:

* Remove tags, permalink, description, summary, item type, item info, as they're now in hComment
* Retain rating, as it's not in hComment
* Remove reviewer and dtreviewed in favor of hcomment's poster and dtposted
** transition can have dual-classing: <code>class="dtposted dtreviewed"</code> is fine
* Deal with version being present in both somehow

=== Working Name ===
The name "hComment" is a working name for this microformat. The name was suggested as it shares much with the hCard and hCalendar microformats, despite not having an IETF RFC to reference for a normative schema.

=== Copyright ===
{{MicroformatCopyrightStatement2005}}

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

=== Inspiration and Acknowledgments ===
Thanks to everyone who responded to the open call for implementor participation for hReview. The authors in particular wish to thank the following individuals for their constructive input and feedback: [http://www.richardault.com/ Richard Ault], [http://dannyayers.com Danny Ayers], [http://www.vertexdev.com/~jeff/ Jeffrey Barr],[http://adriancuthbert.blogspot.com/ Adrian Cuthbert],[http://jason.defillippo.com/ Jason DeFillippo], [http://www.hybernaut.com/bdv Brian Del Vecchio], Scott Derringer, [http://budgibson.com/home/ Bud Gibson], [http://joi.ito.com/ Joi Ito], [http://www.kanai.net/weblog/ Gen Kanai],[http://niallkennedy.com/ Niall Kennedy], [http://labs.commerce.net/wiki/index.php/Rohit_Khare Rohit Khare], [http://theryanking.com/ Ryan King], [http://www.jluster.org/ Jonas Luster], [http://epeus.blogspot.com/ Kevin Marks], [http://www.powazek.com/ Derek Powazek], [http://www.judysbook.com/ Jeff Rodenburg], [http://sifry.com/alerts/ David Sifry], [http://jystewart.net/ James Stewart], [http://kung-foo.tv/ Adriaan Tijsseling], [http://www.flashenabled.com/ Phillip Torrone], Thai Tran, [http://w6daily.winn.com/ Phillip Winn], [http://yohei-y.blogspot.com YAMAMOTO Yohei].

=== Scope ===
Comments consistently share several common fields. Where possible hComment has been based on this minimal common subset.

==== Out of scope ====
Fields that are type-specific have been omitted from hComment. It is important that hComment be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.

The concept of a "universal object identifier", that is, how to identify the same object/item/product across different shopping sites, though something very useful to have, is outside the scope of this format.

== Semantic XHTML Design Principles ==
{{SemanticXHTMLDesignPrinciples}}

== Format ==
=== In General ===
The hComment format is based on a set of comment fields common to numerous websites, blogs, and other content in use on the web today. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] standards.

=== Schema ===
The hComment schema consists of the following:

* hComment
** version. optional. text.
** summary. optional. text.
** item type. optional. product | business | event | person | place | website | url.
** item info. required. (fn || url || photo ) | [[hcard|hCard]] (for person or business).
** poster. required. [[hcard|hCard]] | fn | email | url.
** dtposted. required. ISO8601 absolute date time.
** description. optional. text with optional valid XHTML markup.
** tags. optional. keywords or phrases, using RelTag, each with optional rating.
** permalink. optional.

=== Field details ===
The fields of the hComment schema represent the following:

'''version''':: This optional field permits hComment publishers to specify a particular version of hComment that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hComments according to any version of the hComment specification v0.1 or later. In practice the authors of this specification are comitted to maintaining backward compatibility with content produced using earlier versions of the specification. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.1".

'''summary''':: This optional field serves as a title for the comment itself.

'''item type''':: This optional field "type" provides the type of the item being commented upon, one of the following: product, business, event, person, place, website, url.

'''item info''':: This optional field, when present, MUST have at a minimum the name ("fn" - the formatted text corresponding to the name) of the item, SHOULD provide at least one URI ("url") for the item, and MAY provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) SHOULD be encapsulated in an [[hcard|hCard]]. Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item. When an hComment lacks this field, the hComment is implicitly assumed to be a comment on the page on which it appears.

'''poster''':: The person who authored the comment. An hCard representing the poster SHOULD be provided with full name and URL. Alternatively, just a name, email address, or URL to the person MAY be provided. To specify more than one of those, encapsulate them in an hCard. For anonymous comments, use "anonymous" (without quotes) for the full name of the poster.

'''dtposted''':: This required field MUST provide an ISO8601 absolute date time of when the comment was written or otherwise authored. This field SHOULD use UTC, but MAY use the time zone offset syntax.

'''description''':: This optional field contains the full text representing the written opinion of the poster. The field MAY include valid XHTML markup (e.g. paragraphs). User agents SHOULD preserve any markup. Multiple descriptions or section descriptions (e.g. pros and cons, plusses and minusses) SHOULD be included in the description field.

'''tags''':: Tags are represented using a list of keywords or phrases (using the [[reltag|RelTag]] microformat for each individual keyword or phrase tag) that the poster associates with the item. Authors MAY enclose all tags for a comment inside an element with a specific classname, e.g. "categories" (from vCard RFC2426 and iCalendar RFC2445), but are not required to do so.

'''permalink''':: This optional field is a URL for the hComment. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> MUST be used to indicate that the hyperlink is a permalink for the comment itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a comment as a unique ID in order to identify and collate the same comment from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the comment. Authors MAY use the classname of "permalink" on the element representing the permalink, but are not required to do so.

The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, email, photo, description, categories</code>. In addition, items and posters described by hCards MAY contain any hCard field.

=== More Semantic Equivalents ===

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For any "url", use <code><a class="url" href="...">...</a></code> inside the element with class="hreview" in hComment.
* Similarly, any "email", use <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* And for "photo", use <code><img class="photo" src="..." alt="Photo of ..." /></code>

==== Language ====
* To explicitly convey the natural language that an hComment is written in, use the standard (X)HTML 'lang' attribute on the element with class="hcomment", e.g. <code><div class="hcomment" lang="en"> ... </div></code> If portions of an hComment (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.
* hComment processors which need to handle the language of comments MUST process the standard (X)HTML 'lang' attribute as specified.

=== Human vs. Machine Readable ===
If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

Similarly, if an <code><img /></code> element is used for one or more properties, it MUST be treated as follows:

# For the "photo" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img /></code> element's '<code>alt</code>' attribute is the value of the property.

=== Notes ===
This section is informative.

* By marking up a comment with the hComment microformat, the expectation is communicated that the comment MAY be indexed. This has no impact on the copyright of the comment itself.
* The enumerated list of item types is under development and may be extended.
* Each type may have custom hComment fields that follow the common set.
* Additional details about a particular item should be specified with the rest of the item's info at the URL provided for the item.

== Examples ==
Here are a few examples of comments from current web sites, and how they could be easily enhanced to support the hComment structured comment microformat.

=== Blog comments ===

Here is an example of a simple blog comment (based on a real blog comment from [http://www.microformats.org/blog/2005/06/20/microformats-workshop-at-supernova2005/#comments here]):

<code><pre><nowiki>
<div id="comment-9">
<cite><a href='http://http//9rules.com' rel='external nofollow'>Mike</a></cite>:
 
Microformats sound cool, thanks for the great site guys!

<a href="#comment-9" title="">June 22nd, 2005 at 9:28 am</a> 
</div>
</nowiki></pre></code>

Adding hComment to this comment is quite simple:

<code><pre><nowiki>
<div class="hcomment" id="comment-9">
<cite class="poster vcard"><a class="url fn" href='http://http//9rules.com' rel='external nofollow'>Mike</a></cite>:

Microformats sound cool, thanks for the great site guys!

<a class="dtposted url" href="#comment-9" title="20050622T0928Z">June 22nd, 2005 at 9:28 am</a>
</div>
</nowiki></pre></code>

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

The following sites have published hComments, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you publish hComments on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

[Coming soon!]

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

The following implementations have been developed which either generate or parse hComments. If you have an hComment 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.

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[reltag|RelTag]]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc3986.txt RFC3986]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.ietf.org/rfc/rfc3667.txt RFC3667]
* [http://www.ietf.org/rfc/rfc3668.txt RFC3668]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]

==== Similar Work ====
* [[xoxo]]

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

=== Changes from hReview v0.2 ===
The following changes have been made in hComment v0.1:
# removed '''rating''' field
# changed '''reviewer''' to '''poster'''
# changed '''dtreviewed''' to '''dtposted'''
# removed many examples :(

== Feedback ==
* Feedback is encouraged on the [[Talk:hcomment]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

events/2008-london-microformats-vevent

2007-12-12T11:29:05Z

MarkNg: /* London Microformats vEvent */

= London Microformats vEvent =

This is a social [[events|event]] planned for the first quarter of 2008 in London.

__TOC__

== Details ==

TBC

This page will be filled as details are decided.

== Summary ==
We hope to put on a small social event in London in the first quarter of 2008. It'll feature a couple of speakers on the topic of microformats and the semantic web and hopefully some drinks too.

== Organisers ==
*[[User:Phae|Frances Berriman]] - http://fberriman.com
*[[User:DrewMcLellan|Drew McLellan]] - http://allinthehead.com

== Attending ==
Please put yourself down if you're interested in attending an event in the first part of 2008. We're currently using this page to gauge interest right now.

* PJ Barry
* James Darling
* Jason Cale
* David Thompson
* Adam Liptrot
* Mark Ford
* Elliot Jay Stocks
* Mark Ng
* Add your name
* ..

== Blog Posts ==

== Photos ==

== Additional Links / Information ==

User:MarkNg

2007-09-20T17:40:35Z

MarkNg:

http://www.markng.co.uk/

irc-people

2007-09-20T17:38:05Z

MarkNg:

A list of [[irc|IRC]] regulars, sorted by nick, and their normal timezones (winter/summer).

* [[User:Adam Ballai|AdamBallai]] (-700/-700)
* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Ajaswa|Andrew Jaswa]] (-0500)
* [[User:Alexander Graf|AlexanderGraf]] (+0100)
* [[User:Tomasino|aloneone]] (-0500)
* [[User:AmanuelTewolde|Amanuel]] (-0500/-0400)
* [[User:Amette|amette]] (+1000)
* [[User:Amir Guindehi|AmirGuindehi]] (+1000)
* [[User:AnselHalliburton|anselxyz]] (-0800/-0700)
* [[User:Ashley|Ashley]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Tyler Roehmholdt|Baristo]] (-0800/-0700)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:HenriBergius|bergie]] (+0200/+0300)
* [[User:BenWest|bewest]] (-0800/-0700)
* [[User:BluesMoon|bluesmoon]] (+0530)
* [[User:BobChao|BobChao]] (+0800)
* [[User:Bob Jonkman|BobJonkman]] (-0500/-0400)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (+0000)
* [[User:Briski|Briski]] (+0000)
* [[User:BryanL|BryanL]] (-0500/-0400)
* [[User:BryanRieger|Bryan Rieger]] (+0000)
* [[User:Bug-E|Bug-E]] (+0200)
* [[User:CarlaHufstedler|carlamagpie]] (-0500/-0400)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:CharlesRoper|charles_r]] (0000/+0100)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:Cloud|Cloud]] (+0000)
* [[User:Colin_Barrett|cbarrett]] (-1000)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cruster|cruster]] (+0200)
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:ChrisBrentano|ctb]] (-0800/-0700)
* [[User:DanielBurka|DanielBurka]] (-0400)
* [[User:DavidMead|DavidMead]] (-0400)
* [[User:DerrickPallas|DerrickPallas]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:DanC|DanC]] (-0600/-0500)
* [[User:DannyAyers|danja]] (+0100/+0200)
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DenisDefreyne|ddfreyne]] (+0100/+0200)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DiegoBudny|DiegoBudny]]
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrErnie|DrErnie]] (-0800/-0700)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:DrewBell|droob]] (-0600/-0500)
* [[User:DimitriosZachariadis|dzach]] (+0200/+0300)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:Fil|Fil]] (+0200)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Griffin|Griffin]] (-0600/-0500)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Aubergine10|Guy Fraser]] (+0100/+0000)
* [[User:HenrichPoehls|HenrichP]] (+0100)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:JosephHolsten|josephholsten]] (-0600/-0500)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Ichigo|ichigo]] (+1000)
* [[USer:Alper|illustir]] (+0100)
* [[User:Inkbase|inkbase]] (-0800/-0700)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Izo|IZO]]
* [[User:JamieKnight|JamieKnight]] (+1000/0000)
* [[User:WizardIsHungry|jcw9]] (-0500/-0400)
* [[User:Adactio|Jeremy Keith]] (+0000)
* [[User:JasonK|jkridner]] (-0600/-0500)
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:JulianStahnke|Julian Stahnke]] (+0000)
* [[User:Kapowaz|kapowaz]] (+0000/+0100)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Lachlan Hunt|Lachy]] (+1000/+1100)
* [[User:Linmic|linmic]] (+0800-0700)
* [[User:MarkNg|madness]] (+0000/+0100)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:MattBowen|Matt Bowen]] (-0500/-0400)
* [[User:MattisManzel|Mattis Manzel]] (+0100/+0200)
* [[User:CiaranMc|McNulty]] (+0000/+0100)
* [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.
* [[User:Mike|Michael McCracken(mmc)]] (-0800/-0700)
* [[User:MikeKaply|mkaply]] (-0600/-0500)
* [[User:SteveIvy|monkinetic/redmonk]] (-0700)
* [[User:RobManson|nambor]] (+1000)
* [[User:neuro|neuro]]
* [[User:Niekie|niekie]] (+0100/+0200)
* [[User:NTollervey|ntoll]] (+0000/+0100)
* [[User:Andy Pemberton|pembertona]] (-0500/-0400)
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:PetarPopov|popov]] (-0800/-0700)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:RCanine|RCanine]] (-0500/-0400)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:Ronnos|Ron Kok]] (+0000)
* [[User:SarahWorsham|sazbean]] (-0500/-0400)
* [[User:ScottNelle|snelle]] (-0500/-0400)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Stii|Stii]] (+0200 GMT)
* [[User:SuperPhly|SuperPhly]] (-600/-500)
* sym[[User:LynX|lynX]] or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100)
* [[User:DavidLehn|taaz]] (-0500/-0400)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Vadania|vadania]] (-0600/-0700)
* [[User:Vant|vant]] (+0900)
* [[User:Victor|victor]] (+0100/+0200)
* [[User:V-I-P|V-I-P]] (+0100/+0200)
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)
* [[User:WebOrganics|weborganics]] (+0100)
* [[User:JacksonWilkinson|whafro]] (-0500/-0400)
* [[User:Richard Conyard|WhiskeyM]] (+0000)
* [[User:Veeliam|William Lawrence]] (-0800/-0700)
* [[User:Wojciech|wzajac]] (+0100/+0200)
* [[User:Ianloic|yakk]] (-0800/-0700)
* [[User:StevenWoods|woodss]] (+0000 GMT)