Microformats Wiki - User contributions [en]

parsing-microformats

2006-11-26T21:45:40Z

AndrewTurner: /* JavaScript example */

= Microformat Parsing =

Microformat parsing mechanisms that depend on documents having even minimal xml properties like well-formedness may fail when consuming non-well-formed content. [http://tidy.sourceforge.net/ Tidy] or even better [http://people.apache.org/~andyc/neko/doc/html/ CyberNeko] may be a useful work around.
In particular [http://suda.co.uk/projects/X2V/ Brian Suda's frequently cited X2V hCard and hCalendar discovery and transformation prototypes] use XSLT, and "tidy" any non-well-formed input before processing it.

Most microformats tend to be agnostic about things like exact element type used.

Developers can use tools like XPATH that assume well-formedness on well-formed content (from the web or by using tidy). Mark Pilgrim's example [http://sourceforge.net/projects/feedparser/ universal feed parser] suggests that it may be possible to sanitize user html to an extent that it is suitable for later processing as xml.

== Parsing class values ==

When parsing class values care must be taken:
# Class attributes may contain multiple class names, e.g: <code>class="foo vcard bar"</code>
# Class attributes may contain class names which contain the class name used by a microformat, e.g: <code>class="foo<strong>vcard</strong>bar"</code> <code>class="foo<strong>vcard</strong>"</code>, <code>class="<strong>vcard</strong>bar"</code>.
# Multiple class names are seperated by one or more whitespace charchters.
# Class names are case sensitive.

See http://www.w3.org/TR/html401/struct/global.html#h-7.5.2.

=== JavaScript example ===
The [http://www.robertnyman.com/2005/11/07/the-ultimate-getelementsbyclassname/ Ultimate getElementsByClassName] JavaScript function may be useful. Then you can do:

<code>
var adrs = document.getElementsByClassName(document, "*", "adr");
</code>

or even:

<code>
var cities = document.getElementsByClassName(document, "*", "locality");
</code>

<code>
if (<em>elemenent</em>.className.match(/<strong>vcard</strong>/)) ...
</code>

=== XSLT example ===
<code>
<xsl:if test="contains(
concat (
' ',
concat(normalize-whitespace(@class),' ')
),
' <strong>vcard</strong> '
)" > ...
</code>

[http://balloon.hobix.com/xpath-generator xpath generator], to help you generate those long ugly xpath queries. [link broken as of 8 August 2006]

== Parsing rel/rev values ==

Parsing rel and rev values is similar to parsing class values except for the following differences:

# rel and rev values should be seperated by one space.
# rel and rev values are case insensetive.

See http://www.w3.org/TR/html401/types.html#type-links.

== See Also ==

* [[xmdp-brainstorming]]

parsing-microformats

2006-11-26T21:45:12Z

AndrewTurner: /* JavaScript example */

= Microformat Parsing =

Microformat parsing mechanisms that depend on documents having even minimal xml properties like well-formedness may fail when consuming non-well-formed content. [http://tidy.sourceforge.net/ Tidy] or even better [http://people.apache.org/~andyc/neko/doc/html/ CyberNeko] may be a useful work around.
In particular [http://suda.co.uk/projects/X2V/ Brian Suda's frequently cited X2V hCard and hCalendar discovery and transformation prototypes] use XSLT, and "tidy" any non-well-formed input before processing it.

Most microformats tend to be agnostic about things like exact element type used.

Developers can use tools like XPATH that assume well-formedness on well-formed content (from the web or by using tidy). Mark Pilgrim's example [http://sourceforge.net/projects/feedparser/ universal feed parser] suggests that it may be possible to sanitize user html to an extent that it is suitable for later processing as xml.

== Parsing class values ==

When parsing class values care must be taken:
# Class attributes may contain multiple class names, e.g: <code>class="foo vcard bar"</code>
# Class attributes may contain class names which contain the class name used by a microformat, e.g: <code>class="foo<strong>vcard</strong>bar"</code> <code>class="foo<strong>vcard</strong>"</code>, <code>class="<strong>vcard</strong>bar"</code>.
# Multiple class names are seperated by one or more whitespace charchters.
# Class names are case sensitive.

See http://www.w3.org/TR/html401/struct/global.html#h-7.5.2.

=== JavaScript example ===
The [http://www.robertnyman.com/2005/11/07/the-ultimate-getelementsbyclassname/ Ultimate getElementsByClassName] JavaScript function may be useful. Then you can do:

[[adr]]
<code>
var adrs = document.getElementsByClassName(document, "*", "adr");
</code>

or even:

<code>
var cities = document.getElementsByClassName(document, "*", "locality");
</code>

<code>
if (<em>elemenent</em>.className.match(/<strong>vcard</strong>/)) ...
</code>

=== XSLT example ===
<code>
<xsl:if test="contains(
concat (
' ',
concat(normalize-whitespace(@class),' ')
),
' <strong>vcard</strong> '
)" > ...
</code>

[http://balloon.hobix.com/xpath-generator xpath generator], to help you generate those long ugly xpath queries. [link broken as of 8 August 2006]

== Parsing rel/rev values ==

Parsing rel and rev values is similar to parsing class values except for the following differences:

# rel and rev values should be seperated by one space.
# rel and rev values are case insensetive.

See http://www.w3.org/TR/html401/types.html#type-links.

== See Also ==

* [[xmdp-brainstorming]]

parsing-microformats

2006-11-26T21:42:39Z

AndrewTurner: Added getElementsByClassName example

geo

2006-11-20T01:44:02Z

AndrewTurner: /* Implementations */

<h1> geo </h1>

'''geo''' (working name, pronounced "gee-oh") is a simple format for marking up geographic latitude longitude information, suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the "geo" property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

== Draft Specification ==

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

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}

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

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

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

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

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

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

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

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

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

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

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

=== Human vs. Machine readable ===

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

=== Value excerpting ===

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

=== Root Class Name ===

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

=== Property List ===

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

* latitude
* longitude

=== XMDP Profile ===

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

=== Parsing Details ===

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

== Examples ==

This section is informative.

=== Example from RFC2426 ===

Section 3.4.2 of RFC2426 has a simple geo example:

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

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

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

this geo could be displayed as:

37.386013, -122.082932

=== Real world geo example ===

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

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

With geo markup:

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

This geo might be displayed as:

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

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

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

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

* [http://flickr.com/ Flickr] now [http://blog.flickr.com/flickrblog/2006/08/great_shot_wher.html supports the geo microformat] on all [http://flickr.com/map/ geotagged photos]. Within 11 days of launch there are now over 3M+ photos (as of 20060907) marked up with the "geo" microformat.
* [http://ocono.com/ ocono.com] has marked each of it's "Upcoming Events" items with lat/long values.
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]
* [http://www.multimap.com Multimap.com] uses the geo microformat to mark up latitude and longitude values on map pages.
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.
* [http://07.pagesd.info/ 07.pagesd.info] uses the geo microformat to mark up latitude and longitude values for each commune of the Ardèche département in France.
* [http://www.openguides.org/ OpenGuides] has support for the geo microformat in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide]

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

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

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner]
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
* [http://blog.codeeg.com/ Calvin Yu] has written a [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].
* [http://georss.org/geopress GeoPress] is a WordPress (http://wordpress.org) plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and GeoRSS (http://georss.org) feeds. Written by [http://highearthorbit.com Andrew Turner]

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

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]

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

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

== Discussions ==

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

=== Q&A ===
* If you have any questions about hCard, check the [[hcard-faq|hCard FAQ]] first, and if you don't find answers, add your questions! (Odds are that any geo question will apply to hCard as well).

=== Issues ===
* Please add any issues with the specification to the separate [[hcard-issues|hCard issues]] document. Ditto.
* Proposals for changes, additions and other thoughts about [[geo]] may be found in the [[hcard-brainstorming|hCard brainstorming]] page.

===See also===
*[[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)
*[[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]

geo

2006-11-20T01:43:39Z

AndrewTurner: Added GeoPress

<h1> geo </h1>

'''geo''' (working name, pronounced "gee-oh") is a simple format for marking up geographic latitude longitude information, suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the "geo" property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

== Draft Specification ==

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

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}

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

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

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

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

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

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

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

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

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

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

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

=== Human vs. Machine readable ===

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

=== Value excerpting ===

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

=== Root Class Name ===

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

=== Property List ===

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

* latitude
* longitude

=== XMDP Profile ===

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

=== Parsing Details ===

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

== Examples ==

This section is informative.

=== Example from RFC2426 ===

Section 3.4.2 of RFC2426 has a simple geo example:

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

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

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

this geo could be displayed as:

37.386013, -122.082932

=== Real world geo example ===

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

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

With geo markup:

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

This geo might be displayed as:

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

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

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

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

* [http://flickr.com/ Flickr] now [http://blog.flickr.com/flickrblog/2006/08/great_shot_wher.html supports the geo microformat] on all [http://flickr.com/map/ geotagged photos]. Within 11 days of launch there are now over 3M+ photos (as of 20060907) marked up with the "geo" microformat.
* [http://ocono.com/ ocono.com] has marked each of it's "Upcoming Events" items with lat/long values.
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]
* [http://www.multimap.com Multimap.com] uses the geo microformat to mark up latitude and longitude values on map pages.
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.
* [http://07.pagesd.info/ 07.pagesd.info] uses the geo microformat to mark up latitude and longitude values for each commune of the Ardèche département in France.
* [http://www.openguides.org/ OpenGuides] has support for the geo microformat in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide]

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

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

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner]
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
* [http://blog.codeeg.com/ Calvin Yu] has written a [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].
* GeoPress (http://georss.org/geopress) is a WordPress (http://wordpress.org) plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and GeoRSS (http://georss.org) feeds. Written by [http://highearthorbit.com Andrew Turner]

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

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]

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

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

== Discussions ==

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

=== Q&A ===
* If you have any questions about hCard, check the [[hcard-faq|hCard FAQ]] first, and if you don't find answers, add your questions! (Odds are that any geo question will apply to hCard as well).

=== Issues ===
* Please add any issues with the specification to the separate [[hcard-issues|hCard issues]] document. Ditto.
* Proposals for changes, additions and other thoughts about [[geo]] may be found in the [[hcard-brainstorming|hCard brainstorming]] page.

===See also===
*[[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)
*[[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]

adr

2006-11-20T01:42:09Z

AndrewTurner: Added GeoPress

= adr =

'''adr''' (working name, pronounced "adder") is a simple format for marking up address information, suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''adr''' is a 1:1 representation of the ''adr'' property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

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

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}

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

=== Inspiration and Acknowledgments ===
Thanks to everyone who participated in the [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], and in particular to [http://radar.oreilly.com/nat/ Nat Torkington] and Vee McMillen of [http://oreilly.com O'Reilly] for [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 arranging and hosting the BOF].

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

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

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

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

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

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

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

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

=== Human vs. Machine readable ===

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

Similarly, if an <code><img></code> element is used for one or more properties, it must be treated as follows:
# For the <code>PHOTO</code> property and any other property that takes a <abbr title="Uniform Resource Locator">URL</abbr> 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.

=== Value excerpting ===

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

=== Root Class Name ===

The root class name for an '''adr''' address is <code>adr</code>.

=== Property List ===

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

* <code>post-office-box</code>
* <code>extended-address</code>
* <code>street-address</code>
* <code>locality</code>
* <code>region</code>
* <code>postal-code</code>
* <code>country-name</code>

The <code>type</code> sub-property is omitted because without the context of a type of address for ''whom'', it doesn't make much sense.

=== XMDP Profile ===

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

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

== Examples ==
This section is informative.

=== Sample adr ===

Here is a sample adr:

<pre><nowiki>
<div class="adr">
<div class="street-address">665 3rd St.</div>
<div class="extended-address">Suite 207</div>
<span class="locality">San Francisco</span>,
<span class="region">CA</span>
<span class="postal-code">94107</span>
<div class="country-name">U.S.A.</div>
</div>
</nowiki></pre>

This adr might be displayed as:

<pre>665 3rd St.
Suite 207
San Francisco, CA 94107
U.S.A.</pre>

=== More Examples ===

See [http://microformats.org/wiki/hcard-examples#3.2.1_ADR_Type_Definition hCard example ADR] for more examples.

See [http://microformats.org/wiki/adr-examples adr examples] for additional uses of ADR.

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

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

* ...
* ...

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

The following implementations have been developed which either generate or parse adrs outside the context of hCards. If you have an adr 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.

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the location, or route to, an [[adr]] using a MapQuest map. The route is displayed from the starting location based on the viewer's IP-Address as determined by the [http://hostip.info HostIP] geolocation service.

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRouteEmbed] is another GreaseMonkey user script that will actually embed a route image in the webpage when the user clicks the "route" link.

* [http://georss.org/geopress GeoPress] is a [http://wordpress.org WordPress] plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and [http://georss.org GeoRSS] feeds.

* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding adrs and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].

* The [http://tantek.com/microformats/hcard-creator.html hCard creator], though it creates complete hCards, can also be used simply to create adrs by filling out the address portion and simply copy and pasting the <div class="adr"> element and its contents.

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

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]

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

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

== Discussions ==

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

=== Q&A ===
* If you have any questions about hCard, check the [[hcard-faq|hCard FAQ]] first, and if you don't find answers, add your questions! (Odds are that any '''adr''' question will apply to [[hCard]] as well).
* See also [http://microformats.org/discuss/ for other methods of feedback].

=== Issues ===
* Please add any issues with the specification to the separate [[hcard-issues|hCard issues]] document. Ditto.

== See also ==
* [[adr-examples]]

User:AndrewTurner

2006-09-28T01:43:00Z

AndrewTurner:

Andrew Turner - [http://highearthorbit.com HighEarthOrbit]

Interested in location, [[adr]], [[geo]], [[luna]], [[mars]], and any formats dealing with "place" and "experience". Also trying to raise awareness of licensing of data, especially when it comes to aggregation.

aka: ajturner on IRC

== Projects ==
* [[picoformats]]
* [http://code.highearthorbit.com/greaseroute/ GreaseRoute] - embeds a MapQuest map with directions to an [[adr]] or [[geo]] location
* [http://georss.org/geopress GeoPress] - WordPress blog plugin for embedding location, dynamic maps (Y-G-M), GeoRSS, and Microformats [[geo]] or [[adr]].
* [http://mapufacture.com Mapufacture] - [http://georss.org GeoRSS], and Microformats [[geo]] feed aggregator and mapping

mars

2006-09-28T01:39:55Z

AndrewTurner: Added MRO reference and ideas

Imagine viewing a web page with a reference to a landing site on Mars - and being able to use an add-on to you browser to be taken directly to that site, in a 'Martian' mapping application of your choosing, or on a site like Google Mars. Or being able to search, easily, for web sites referring to the same site, without seeing places on Earth with co-incidentally similar coordinates.

This is especially true now that the [http://mars.jpl.nasa.gov/mro/ Mars Reconnaissance Orbiter] is getting some publicity. It would be nice to markup photographs, findings, reports, etc.

Those are just two of the things a "mars" microformat, based on the existing [[geo]] version, might do for you.

Here's some work-in-progress:

*[[mars-brainstorming]]
*[[mars-examples]]

==Contributors==
*[[User:AndyMabbett|Andy Mabbett]] (proponent)
*[[User:AndrewTurner|Andrew Turner]]

==See also==
*[[luna]] - the same sort of thing, for The Moon

luna-brainstorming

2006-09-28T01:36:18Z

AndrewTurner: Added thoughts behind a general "location" uf that can be used for various coordinate systems/spatial bodies.

=Luna Brainstorming=

==Andy Mabbett==
===Proposal===
I propose a "'''[[luna]]'''" microformat, for marking up co-ordinates on our Moon. This would be based on the "[[geo]]" microformat (and thus relatively easy to implement, since code for "geo" can be re-used).

Note, though, that [http://www.xs4all.nl/~carlkop/stenneck.html] and [http://www.lunarrepublic.com/history/apollo_sites.shtml] indicate that more than one system of
recording the co-ordinates, for any given point, is in use, and it may be necessary to include an attribute to indicate which system is to be used, though the most recent standards appears to be the IAU Mean Earth
Polar Axis co-ordinate system, as used by [http://www.spds.nasa.gov/planetary/lunar/lunar_sites.html NASA] and [http://en.wikipedia.org/wiki/Apollo_11 Wikipedia], and described in Davies and Colvin, J. Geophys. Res., v. 105, pp. 20,227 - 20,280, 2000.

==Kevin Marks==
Note multiple statements of Apollo landing co-ords here: [http://www.hq.nasa.gov/alsj/alsjcoords.html]

:"Currently, the lunar geoid is being redefined with Clementine data, so the location (latitude, longitude, and elevation) of everything will change again very soon".

I believe the reference geoids for other planets are also under revision
* True, but there are also other reference systems for Earth too

==Drew McLellan==
Perhaps geo could be extended to encompass multiple grids. The existing type/value system in [[hCard]] et al could be used. Available types would intially be 'Earth', 'Luna', 'Mars', with the default (if none is specified) being 'Earth'. These could be extended to add new grids when needed. The value is then the co-ordinate.

Obviously the name 'geo' applies to Earth, but we should seriously consider if we want to create a different microformat for every lump of rock someone wishes to map. It has to be advantageous to have a single format for this function that can be applied to any orbiting mass.

* How would an existing user agent parse the grid ref.s for somewhere on the moon, marked up this way? - Andy Mabbett
** Badly, I'd imagine. However, it's easier to modify user agents to account for developments than a bulk of existing published data - Drew.
*** What published data would need to be modified? (Either way, I like the idea of an hCard for 'Ed Straker, SHADO, Moonbase 1, the Moon'. Maybe we need to add a "solar system" attribute... ;-) ) - Andy Mabbett
* Perhaps, like Mabbett points out, there should be a more general class for marking that this is a "coordinate", or a "location". Then a specific reference frame or spatial body can be defined. However, this may only happen once per document and then the rest of the locations references should/could be assumed to be in the same reference frame - AndrewTurner

== AndrewTurner ==
I think we should keep it simple, and also follow the same format used for marking Home/Work for adr, etc. which uses the class="type"

<pre><nowiki>
<span class="geo">
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
<span class="type">moon</span>
</span>
</nowiki></pre>

This would also apply to Earth-centric coordinate representations such as WGS84, NAD, ED50, etc.
<pre><nowiki>
<span class="geo">
<span class="type" title="moon">The Apollo 11 mission landed at </span>
<abbr class="latitude" title="0.67408">the Sea of Tranquility</abbr>
<abbr class="longitude" title="23.47297"></abbr >
</span>
</nowiki></pre>

*The value must be "luna" not "moon". "Luna" is the scientifically-correct name for ''our'' moon; there are other moons in our solar system, such as Titan. I have two concerns about re-using "geo" (aside from the fact that it means "Earth"!) - how it will affect existing tools, and the likely need to also specify the coordinate schema. Can these be addressed satisfactorily? - Andy Mabbett

==See also==
*[[luna-examples]]
*[[geo]]
*[[mars]]

greasemonkey

2006-09-24T18:08:36Z

AndrewTurner: Added GreaseRoute script examples

= About GreaseMonkey =
Greasemonkey is a powerful tool for customizing Firefox.

[http://www.reifysoft.com/turnabout.php Turnabout] is a tool for IE for the same purpose. Its APIs are largely compatible with Greasemonkey, allowing for cross-browser user scripts.

Opera can also run Greasmonkey scipts using the built-in support for [http://www.opera.com/support/tutorials/userjs/ user javascripts].

While there is no way to extend Safari directly, [http://safariguide.net/ Safari Guide] will allow you to run JavaScripts (though not GreaseMonkey scripts) against the front page in Safari.

This page collects ways to use them with microformats.

= Getting Started =
== Get Greasemonkey ==
* [http://www.mozilla.org/products/firefox/ Download FireFox] (required)
* [http://greasemonkey.mozdev.org/ Download Greasemonkey]

== Developing with Greasemonkey ==
* [http://diveintogreasemonkey.org/ Dive Into Greasemonkey] -- start here

= Demo =

== Setup ==
* install microfomat-find-gm5: http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/. '''Note:''' This does work with FireFox 1.5+/GreaseMonkey 0.6.4+, now!

== Prebuilt hCard ==
* go to Neil Dunn's vCard: http://www.ndunn.com/2005/10/7/hCard
* look for the [hCard] icon and click on it
* click on "Add to Address Book"
** note the magic of the data: URI here ...

== Dynamic hCard ==
* go to http://we05.com/presenters.cfm
* select any presenter
* look for the [hCard] icon and click on it
* click on "Show as Text"

== hCard Mapping ==
* go to: http://www.blogmatrix.com/company_main/
* look for the [hCard] icon and click on it
* click on "Show on Google Maps"
* go "ooo and ahh" ...

== xFolk demo ==
* go to: http://thecommunityengine.com/home/archives/2005/10/xfolk_vegomatic.html
* look for the [xFolk] icon and click on it
* look up tags on other services

= Resources =

== Posts and Articles ==

* Bud Gibson on [http://thecommunityengine.com/home/archives/2005/07/followup_to_gre.html Follow-up to Greasemonkey & Microformats]
* Alf Eaton on [http://hublog.hubmed.org/archives/001187.html Extracting microcontent (XSLT, GRDDL, RDF)]
* http://microformats.org/discuss/mail/microformats-discuss/2005-October/001112.html
* Phil Windley on [http://www.windley.com/archives/2005/10/greasemonkey_an.shtml Greasemonkey and Microformats]
* 90% Crud on [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey and Microformats]
* David Janes on "microformat find": [http://blog.davidjanes.com/mtarchives/2005_08.html#003375 Introduction], [http://blog.davidjanes.com/mtarchives/2005_08.html#003377 xFolk], [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 hCard], [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 hCalendar]

== Scripts ==
Some sample scripts:
;tails:http://blog.codeeg.com/tails-firefox-extension/ (shows all, works with 1.5)
;SmartZilla: http://www.stripytshirt.co.uk/features/firefox/smartzilla (exports data)
;[[hcard|hCard]]:http://diveintomark.org/projects/greasemonkey/hcard/
:http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ (updated for FF 1.5/Greasemonkey 0.6.4)
;[[hcalendar|hCalendar]]:http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ (updated for FF 1.5/Greasemonkey 0.6.4)
;[[xfolk|xFolk]]:http://thecommunityengine.com/resources/xfolk-veg-o-matic.user.js
:http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ (updated for FF 1.5/Greasemonkey 0.6.4)
;[[rellicense|RelLicense]]:http://diveintomark.org/projects/greasemonkey/rellicense/
;XFN (Magic Line):http://diveintomark.org/projects/greasemonkey/magicline.user.js
;GRDDL/RDF:http://alf.hubmed.org/microcontentextractor.user.js
;[[adr]] | [[geo]] - GreaseRoute:http://code.highearthorbit.com/greaseroute/index.php
;[[adr]] | [[geo]] -GreaseRouteEmbed:http://code.highearthorbit.com/greaseroute/index.php

==See also==
*[[firefox-extensions]] - other tools for customizing Firefox.

luna-brainstorming

2006-09-23T03:00:59Z

AndrewTurner: /* AndrewTurner */

=Luna Brainstorming=

==Andy Mabbett==
===Proposal===
I propose a "luna" microformat, for marking up co-ordinates on our Moon. This would be based on the "[[geo]]" microformat (and thus relatively easy to implement, since code for "geo" can be re-used).

Note, though, that [http://www.xs4all.nl/~carlkop/stenneck.html] and [http://www.lunarrepublic.com/history/apollo_sites.shtml] indicate that more than one system of
recording the co-ordinates, for any given point, is in use, and it may be necessary to include an attribute to indicate which system is to be used, though the most recent standards appears to be the IAU Mean Earth
Polar Axis co-ordinate system, as used by [http://www.spds.nasa.gov/planetary/lunar/lunar_sites.html NASA] and [http://en.wikipedia.org/wiki/Apollo_11 Wikipedia], and described in Davies and Colvin, J. Geophys. Res., v. 105, pp. 20,227 - 20,280, 2000.

==Kevin Marks==
Note multiple statements of Apollo landing co-ords here: [http://www.hq.nasa.gov/alsj/alsjcoords.html]

:"Currently, the lunar geoid is being redefined with Clementine data, so the location (latitude, longitude, and elevation) of everything will change again very soon".

I believe the reference geoids for other planets are also under revision
* True, but there are also other reference systems for Earth too

==Drew McLellan==
Perhaps geo could be extended to encompass multiple grids. The existing type/value system in [[hCard]] et al could be used. Available types would intially be 'Earth', 'Luna', 'Mars', with the default (if none is specified) being 'Earth'. These could be extended to add new grids when needed. The value is then the co-ordinate.

Obviously the name 'geo' applies to Earth, but we should seriously consider if we want to create a different microformat for every lump of rock someone wishes to map. It has to be advantageous to have a single format for this function that can be applied to any orbiting mass.

* How would an existing user agent parse the grid ref.s for somewhere on the moon, marked up this way? - Andy Mabbett
** Badly, I'd imagine. However, it's easier to modify user agents to account for developments than a bulk of existing published data - Drew.
*** What published data would need to be modified? (Either way, I like the idea of an hCard for 'Ed Straker, SHADO, Moonbase 1, the Moon'. Maybe we need to add a "solar system" attribute... ;-) ) - Andy Mabbett

== AndrewTurner ==
I think we should keep it simple, and also follow the same format used for marking Home/Work for adr, etc. which uses the class="type"

<pre><nowiki>
<span class="geo">
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
<span class="type">moon</span>
</span>
</nowiki></pre>

This would also apply to Earth-centric coordinate representations such as WGS84, NAD, ED50, etc.
<pre><nowiki>
<span class="geo">
<span class="type" title="moon">The Apollo 11 mission landed at </span>
<abbr class="latitude" title="0.67408">the Sea of Tranquility</abbr>
<abbr class="longitude" title="23.47297"></abbr >
</span>
</nowiki></pre>

==See also==
*[[luna-examples]]
*[[geo]]
*[[mars]]

luna-brainstorming

2006-09-23T03:00:44Z

AndrewTurner:

=Luna Brainstorming=

==Andy Mabbett==
===Proposal===
I propose a "luna" microformat, for marking up co-ordinates on our Moon. This would be based on the "[[geo]]" microformat (and thus relatively easy to implement, since code for "geo" can be re-used).

Note, though, that [http://www.xs4all.nl/~carlkop/stenneck.html] and [http://www.lunarrepublic.com/history/apollo_sites.shtml] indicate that more than one system of
recording the co-ordinates, for any given point, is in use, and it may be necessary to include an attribute to indicate which system is to be used, though the most recent standards appears to be the IAU Mean Earth
Polar Axis co-ordinate system, as used by [http://www.spds.nasa.gov/planetary/lunar/lunar_sites.html NASA] and [http://en.wikipedia.org/wiki/Apollo_11 Wikipedia], and described in Davies and Colvin, J. Geophys. Res., v. 105, pp. 20,227 - 20,280, 2000.

==Kevin Marks==
Note multiple statements of Apollo landing co-ords here: [http://www.hq.nasa.gov/alsj/alsjcoords.html]

:"Currently, the lunar geoid is being redefined with Clementine data, so the location (latitude, longitude, and elevation) of everything will change again very soon".

I believe the reference geoids for other planets are also under revision
* True, but there are also other reference systems for Earth too

==Drew McLellan==
Perhaps geo could be extended to encompass multiple grids. The existing type/value system in [[hCard]] et al could be used. Available types would intially be 'Earth', 'Luna', 'Mars', with the default (if none is specified) being 'Earth'. These could be extended to add new grids when needed. The value is then the co-ordinate.

Obviously the name 'geo' applies to Earth, but we should seriously consider if we want to create a different microformat for every lump of rock someone wishes to map. It has to be advantageous to have a single format for this function that can be applied to any orbiting mass.

* How would an existing user agent parse the grid ref.s for somewhere on the moon, marked up this way? - Andy Mabbett
** Badly, I'd imagine. However, it's easier to modify user agents to account for developments than a bulk of existing published data - Drew.
*** What published data would need to be modified? (Either way, I like the idea of an hCard for 'Ed Straker, SHADO, Moonbase 1, the Moon'. Maybe we need to add a "solar system" attribute... ;-) ) - Andy Mabbett

== AndrewTurner ==
I think we should keep it simple, and also follow the same format used for marking Home/Work for adr, etc. which uses the class="type"

<pre><nowiki>
<span class="geo">
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
<span class="type">moon</span>
</span>
</nowiki></pre>

This would also apply to Earth-centric coordinate representations such as WGS84, NAD, ED50, etc.
<pre><nowiki>
<span class="geo">
<span class="type" title="moon">The Apollo 11 mission landed at </span>
<abbr class="latitude" title="0.67408">the Sea of Tranquility</abbr>
<abbr class="longitude" title="23.47297E></abbr >
</span>
</nowiki></pre>

==See also==
*[[luna-examples]]
*[[geo]]
*[[mars]]

picoformats

2006-08-09T13:43:54Z

AndrewTurner: Added MeetMoi syntax link

Picoformats represent an effort being undertaken by [http://factoryjoe.com/blog Chris Messina] and Andy Stack of [http://mozes.com Mozes] to codify various standards and openly pursue a nomenclature and syntax for communicating and executing commands with mobile devices over SMS.

An example application is [http://dodgeball.com Dodgeball's] use of the at symbol (@) to express checking in to a place.

Using the Microformats process and principles of building block design, our goal is to openly develop a complete syntax for interacting with various mobile services using the characters available on most mobile devices.
== Problem Statement ==
# send messages to user mobiles - via SMS, or a small application,
that contains information like appointment times, locations,
directions, and contact info. For example, when2where.com reminds
users when they need to leave to get to their appointment, so the
message may be like:

leave @ 4:35PM ~Dentist Office -> Detroit, MI

where the text itself is simple and readable, but there *may* be an
small utility that would parse the @ symbol to add the event to the
calendar, the ~ to allow the person to quickly call that contact, or
the -> to pull up a Map/directions to the location

# allow users to write messages to query an application - this is
similar to what Mozes has started with notes:

when2where: ?today --- what appointements to I have today
new @ 4PM ~Olive Garden -> Novi --- add an appointment

In addition to the obvious mobile device arena, I think picoformats
are usable in any context where "markup" is too heavy. For example, I
also just put together an IRC bot, whereisbot, that announces user
locations as they sign into a channel, or allows people to do:

.whereami, or .whereis <nick> to geolocate other people in a channel.

I want to 'markup' the information, but putting actual XHTML or XML is
annoying, since IRC doesn't parse the information at all. So right now
the response is:

ajturner: .whereami
whereisbot: ajturner is in Northville, MI, US [42.4365 x -83.4884]

So then someone could write a Picoformat parser for
X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide
a Map url link.

== References ==

* Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags]
* [http://www.dodgeball.com/glossary Dodgeball Glossary]
* [http://twttr.com/t/help/lingo twttr lingo]
* [http://skobee.com/email_howto Skobee's email syntax]
* [http://www.meetmoi.com/1/meetmoi?wicket:bookmarkablePage=:com.mdate.web.GettingStarted#11 MeetMoi syntax]

== Contributors ==
* [http://highearthorbit.com Andrew Turner]
* [http://factoryjoe.com/blog Chris Messina]
* Andy Stack of [http://mozes.com Mozes]

geo

2006-08-05T05:03:39Z

AndrewTurner: /* Implementations */

<h1> geo </h1>

'''geo''' (working name, pronounced "gee-oh") is a simple format for marking up geographic latitude longitude information, suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the "geo" property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.
__TOC__

== Draft Specification ==

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

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}

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

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

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

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

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

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

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

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

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

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

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

=== Human vs. Machine readable ===

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

=== Value excerpting ===

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

=== Root Class Name ===

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

=== Property List ===

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

* latitude
* longitude

=== XMDP Profile ===

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

=== Parsing Details ===

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

== Examples ==

This section is informative.

=== Example from RFC2426 ===

Section 3.4.2 of RFC2426 has a simple geo example:

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

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

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

this geo could be displayed as:

37.386013, -122.082932

=== Real world geo example ===

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

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

With geo markup:

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

This geo might be displayed as:

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

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

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

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

* [http://ocono.com/ ocono.com] has marked each of it's "Upcoming Events" items with lat/long values.
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]
* [http://www.multimap.com Multimap.com] uses the geo microformat to mark up latitude and longitude values on map pages.
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.
* [http://07.pagesd.info/ 07.pagesd.info] uses the geo microformat to mark up latitude and longitude values for each commune of the Ardèche département in France.
* [http://www.openguides.org/ OpenGuides] has support for the geo microformat in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide]

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

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

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner]
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
* [http://blog.codeeg.com/ Calvin Yu] has written a [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.

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

=== Informative References ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]

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

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

== Discussions ==

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

=== Q&A ===
* If you have any questions about hCard, check the [[hcard-faq|hCard FAQ]] first, and if you don't find answers, add your questions! (Odds are that any geo question will apply to hCard as well).

=== Issues ===
* Please add any issues with the specification to the separate [[hcard-issues|hCard issues]] document. Ditto.
* Proposals for changes, additions and other thoughts about [[geo]] may be found in the [[hcard-brainstorming|hCard brainstorming]] page.

== Additional Related Reading and Sites ==

* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]

picoformats

2006-07-30T03:28:31Z

AndrewTurner: Added contributors section

Picoformats represent an effort being undertaken by [http://factoryjoe.com/blog Chris Messina] and Andy Stack of [http://mozes.com Mozes] to codify various standards and openly pursue a nomenclature and syntax for communicating and executing commands with mobile devices over SMS.

An example application is [http://dodgeball.com Dodgeball's] use of the at symbol (@) to express checking in to a place.

Using the Microformats process and principles of building block design, our goal is to openly develop a complete syntax for interacting with various mobile services using the characters available on most mobile devices.
== Problem Statement ==
# send messages to user mobiles - via SMS, or a small application,
that contains information like appointment times, locations,
directions, and contact info. For example, when2where.com reminds
users when they need to leave to get to their appointment, so the
message may be like:

leave @ 4:35PM ~Dentist Office -> Detroit, MI

where the text itself is simple and readable, but there *may* be an
small utility that would parse the @ symbol to add the event to the
calendar, the ~ to allow the person to quickly call that contact, or
the -> to pull up a Map/directions to the location

# allow users to write messages to query an application - this is
similar to what Mozes has started with notes:

when2where: ?today --- what appointements to I have today
new @ 4PM ~Olive Garden -> Novi --- add an appointment

In addition to the obvious mobile device arena, I think picoformats
are usable in any context where "markup" is too heavy. For example, I
also just put together an IRC bot, whereisbot, that announces user
locations as they sign into a channel, or allows people to do:

.whereami, or .whereis <nick> to geolocate other people in a channel.

I want to 'markup' the information, but putting actual XHTML or XML is
annoying, since IRC doesn't parse the information at all. So right now
the response is:

ajturner: .whereami
whereisbot: ajturner is in Northville, MI, US [42.4365 x -83.4884]

So then someone could write a Picoformat parser for
X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide
a Map url link.

== References ==

* Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags]
* [http://www.dodgeball.com/glossary Dodgeball Glossary]
* [http://twttr.com/t/help/lingo twttr lingo]

== Contributors ==
* [http://highearthorbit.com Andrew Turner]
* [http://factoryjoe.com/blog Chris Messina]
* Andy Stack of [http://mozes.com Mozes

picoformats

2006-07-30T03:21:51Z

AndrewTurner: Add picoformats "Problem Statement" from Mailing list ideas

Picoformats represent an effort being undertaken by [http://factoryjoe.com/blog Chris Messina] and Andy Stack of [http://mozes.com Mozes] to codify various standards and openly pursue a nomenclature and syntax for communicating and executing commands with mobile devices over SMS.

An example application is [http://dodgeball.com Dodgeball's] use of the at symbol (@) to express checking in to a place.

Using the Microformats process and principles of building block design, our goal is to openly develop a complete syntax for interacting with various mobile services using the characters available on most mobile devices.

== Problem Statement ==
# send messages to user mobiles - via SMS, or a small application,
that contains information like appointment times, locations,
directions, and contact info. For example, when2where.com reminds
users when they need to leave to get to their appointment, so the
message may be like:

leave @ 4:35PM ~Dentist Office -> Detroit, MI

where the text itself is simple and readable, but there *may* be an
small utility that would parse the @ symbol to add the event to the
calendar, the ~ to allow the person to quickly call that contact, or
the -> to pull up a Map/directions to the location

# allow users to write messages to query an application - this is
similar to what Mozes has started with notes:

when2where: ?today --- what appointements to I have today
new @ 4PM ~Olive Garden -> Novi --- add an appointment

In addition to the obvious mobile device arena, I think picoformats
are usable in any context where "markup" is too heavy. For example, I
also just put together an IRC bot, whereisbot, that announces user
locations as they sign into a channel, or allows people to do:

.whereami, or .whereis <nick> to geolocate other people in a channel.

I want to 'markup' the information, but putting actual XHTML or XML is
annoying, since IRC doesn't parse the information at all. So right now
the response is:

ajturner: .whereami
whereisbot: ajturner is in Northville, MI, US [42.4365 x -83.4884]

So then someone could write a Picoformat parser for
X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide
a Map url link.

== References ==

* Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags]
* [http://www.dodgeball.com/glossary Dodgeball Glossary]
* [http://twttr.com/t/help/lingo twttr lingo]

User:AndrewTurner

2006-07-30T03:18:55Z

AndrewTurner:

Andrew Turner - [http://highearthorbit.com HighEarthOrbit]

aka: ajturner on IRC

== Projects ==
* [[picoformats]]
* [http://code.highearthorbit.com/greaseroute/ GreaseRoute] - embeds a MapQuest map with directions to an [[adr]] or [[geo]] location

User:AndrewTurner

2006-07-30T03:18:48Z

AndrewTurner:

User:AndrewTurner

2006-07-30T03:18:37Z

AndrewTurner:

Andrew Turner - [http://highearthorbit.com HighEarthOrbit]

aka: ajturner on IRC

== Projects ==
[[picoformats]]
[http://code.highearthorbit.com/greaseroute/ GreaseRoute] - embeds a MapQuest map with directions to an [[adr]] or [[geo]] location

User:AndrewTurner

2006-07-30T03:18:24Z

AndrewTurner:

Andrew Turner - [http://highearthorbit.com HighEarthOrbit]

aka: ajturner on IRC

== Projects ==
[http://code.highearthorbit.com/greaseroute/ GreaseRoute] - embeds a MapQuest map with directions to an [[adr]] or [[geo]] location

User:AndrewTurner

2006-06-16T18:45:47Z

AndrewTurner:

Andrew Turner - [http://highearthorbit.com HighEarthOrbit]

== Projects ==
[http://code.highearthorbit.com/greaseroute/ GreaseRoute] - embeds a MapQuest map with directions to an [[adr]] or [[geo]] location

User:AndrewTurner

2006-06-16T18:45:28Z

AndrewTurner:

Andrew Turner - [http://highearthorbit.com HighEarthOrbit]

!! Projects
[http://code.highearthorbit.com/greaseroute/ GreaseRoute] - embeds a MapQuest map with directions to an [[adr]] or [[geo]] location

User:AndrewTurner

2006-06-16T18:45:17Z

AndrewTurner:

Andrew Turner - [http://highearthorbit.com HighEarthOrbit]

[http://code.highearthorbit.com/greaseroute/ GreaseRoute] - embeds a MapQuest map with directions to an [[adr]] or [[geo]] location

events/2006-06-13-where-2-bof

2006-06-16T18:44:10Z

AndrewTurner: /* Attending */

= Where 2.0 Microformats BOF II =

== Details ==

;Date: Tuesday, June 13, 2006
;Time: 7:30pm - 8:30pm PDT '''Tantek and Kevin running late ETA 7.50pm'''
;Location: Paseo Room, Fairmont Hotel San Jose, California, USA
;URLs: [http://wiki.oreillynet.com/where20_2006/index.cgi?BOFs Where 2.0 BOFs wiki page], [http://conferences.oreillynet.com/pub/w/47/bof.html Where 2.0 BOFs overview] > [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9406 Geo Microformats BOF II: Developing a "directions" Microformat BOF page].
;Overview: Tim O'Reilly and Bill Gates [http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/ recently discussed microformats], and the [http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html need for a directions microformat became clear]. This sequel to [http://microformats.org/wiki/geo-bof-2005-06-30 last year's Microformats BOF] at Where 2.0 will discuss the [http://microformats.org/wiki/directions-examples work on the directions microformat to date], and [http://microformats.org/wiki/directions-brainstorming brainstorm on proposals] for a directions microformat.

== Attending ==

* [http://tantek.com/ Tantek Çelik], [http://technorati.com/ Technorati] (moderator)
* [http://epeus.blogspot.com Kevin Marks] [http://technorati.com/ Technorati]
* Jérémy Huylebroeck [http://www.francetelecom.com/en France Telecom R&D]
* [http://greg.abstrakt.ch Gregor J. Rothfuss], [http://www.endoxon.com Endoxon]
* [http://360.yahoo.com/shi_norman Norman Shi]
* [http://metaweb.com/ Jamie Taylor]
* Michael Leahy
* Gregor Rothfuss
* Josu Azpillaga [http://www.tagzania.com Tagzania.com]
* Luistxo Fernandez [http://www.tagzania.com Tagzania.com]
* Adrian Cuthbert [http://www.m-spatial.com m-spatial] [http://www.mylocalguru.com mylocalguru]
* [[User:AndrewTurner|Andrew Turner]] [http://highearthorbit.com HighEarthOrbit]

== Original Proposal ==

Original proposal as submitted to the Where 2.0 BOF proposal form:

=== Title ===

Geo Microformats BOF II: Developing a "directions" microformat

=== Describe the people who would be interested in attending this BOF ===

Anyone interested in *simple* standards for publishing and sharing geo related information on the Web, in particular directions information.

=== Which evenings(s) are you available to host your BOF? ===

I am available to host the BOF on June 13th only. My recommended time is from 6:30pm-7:30pm.

=== Full description of this BOF Maximum 250 words, about 35 lines.* ===

Last year at the inaugural "Where 2.0" conference, the Microformats BOF brought together key folks in the geo and microformats communities and together we were able to brainstorm and develop the "geo" and "adr" microformats.

http://flickr.com/photos/tantek/45109751/

http://microformats.org/wiki/adr

http://microformats.org/wiki/geo

During the opening keynote at the Mix06 conference this past March, Tim O'Reilly engaged Bill Gates in a discussion about microformats. During that conversation, Bill Gates specifically noted that we need microformats for contacts, events, and directions.

http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/

http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html

The first of those two have been well defined by hCard and hCalendar microformats. However, a directions microformat has yet to be defined. Research has begun towards the development of a directions microformat.

http://microformats.org/wiki/directions-examples

The goal of this BOF is to once again bring together key interested folks in the geo and microformats communities, discuss the work on the directions microformat to date, and brainstorm on proposals for a directions microformat.

=== Brief description of this BOF Maximum 50 words, about 7 lines.* ===

Tim O'Reilly and Bill Gates recently discussed microformats, and the need for a directions microformat became clear.

http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/

http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html

This sequel to last year's Microformats BOF at Where 2.0 will discuss the work on the directions microformat to date, and brainstorm on proposals for a directions microformat.

http://microformats.org/wiki/directions-examples

=== Anything else we should know about your proposal? ===

=== Confirmation Post Submission ===

Birds of a Feather

Thank you for filling out the BOF Request Form. If you have any questions, please contact Vee McMillen at vee at oreilly dot com.

== Directions Examples ==

Examples of how directions information is available on the net
* [http://mashpit.pbwiki.com/WalkaPedia Walkapedia]
* Direction By Landmark: leaving from Fairmont Hotel front door, making a left, next block take a right, cross the street and then enter Gordons Beer.
* ...

== See Also ==

* [[adr]]
* [[geo]]
* [[location-formats]]
* [[events]]

events/2006-06-13-where-2-bof

2006-06-16T18:42:32Z

AndrewTurner: /* Attending */

= Where 2.0 Microformats BOF II =

== Details ==

;Date: Tuesday, June 13, 2006
;Time: 7:30pm - 8:30pm PDT '''Tantek and Kevin running late ETA 7.50pm'''
;Location: Paseo Room, Fairmont Hotel San Jose, California, USA
;URLs: [http://wiki.oreillynet.com/where20_2006/index.cgi?BOFs Where 2.0 BOFs wiki page], [http://conferences.oreillynet.com/pub/w/47/bof.html Where 2.0 BOFs overview] > [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9406 Geo Microformats BOF II: Developing a "directions" Microformat BOF page].
;Overview: Tim O'Reilly and Bill Gates [http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/ recently discussed microformats], and the [http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html need for a directions microformat became clear]. This sequel to [http://microformats.org/wiki/geo-bof-2005-06-30 last year's Microformats BOF] at Where 2.0 will discuss the [http://microformats.org/wiki/directions-examples work on the directions microformat to date], and [http://microformats.org/wiki/directions-brainstorming brainstorm on proposals] for a directions microformat.

== Attending ==

* [http://tantek.com/ Tantek Çelik], [http://technorati.com/ Technorati] (moderator)
* [http://epeus.blogspot.com Kevin Marks] [http://technorati.com/ Technorati]
* Jérémy Huylebroeck [http://www.francetelecom.com/en France Telecom R&D]
* [http://greg.abstrakt.ch Gregor J. Rothfuss], [http://www.endoxon.com Endoxon]
* [http://360.yahoo.com/shi_norman Norman Shi]
* [http://metaweb.com/ Jamie Taylor]
* Michael Leahy
* Gregor Rothfuss
* Josu Azpillaga [http://www.tagzania.com Tagzania.com]
* Luistxo Fernandez [http://www.tagzania.com Tagzania.com]
* Adrian Cuthbert [http://www.m-spatial.com m-spatial] [http://www.mylocalguru.com mylocalguru]
* AndrewTurner [http://highearthorbit.com HighEarthOrbit]

== Original Proposal ==

Original proposal as submitted to the Where 2.0 BOF proposal form:

=== Title ===

Geo Microformats BOF II: Developing a "directions" microformat

=== Describe the people who would be interested in attending this BOF ===

Anyone interested in *simple* standards for publishing and sharing geo related information on the Web, in particular directions information.

=== Which evenings(s) are you available to host your BOF? ===

I am available to host the BOF on June 13th only. My recommended time is from 6:30pm-7:30pm.

=== Full description of this BOF Maximum 250 words, about 35 lines.* ===

Last year at the inaugural "Where 2.0" conference, the Microformats BOF brought together key folks in the geo and microformats communities and together we were able to brainstorm and develop the "geo" and "adr" microformats.

http://flickr.com/photos/tantek/45109751/

http://microformats.org/wiki/adr

http://microformats.org/wiki/geo

During the opening keynote at the Mix06 conference this past March, Tim O'Reilly engaged Bill Gates in a discussion about microformats. During that conversation, Bill Gates specifically noted that we need microformats for contacts, events, and directions.

http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/

http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html

The first of those two have been well defined by hCard and hCalendar microformats. However, a directions microformat has yet to be defined. Research has begun towards the development of a directions microformat.

http://microformats.org/wiki/directions-examples

The goal of this BOF is to once again bring together key interested folks in the geo and microformats communities, discuss the work on the directions microformat to date, and brainstorm on proposals for a directions microformat.

=== Brief description of this BOF Maximum 50 words, about 7 lines.* ===

Tim O'Reilly and Bill Gates recently discussed microformats, and the need for a directions microformat became clear.

http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/

http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html

This sequel to last year's Microformats BOF at Where 2.0 will discuss the work on the directions microformat to date, and brainstorm on proposals for a directions microformat.

http://microformats.org/wiki/directions-examples

=== Anything else we should know about your proposal? ===

=== Confirmation Post Submission ===

Birds of a Feather

Thank you for filling out the BOF Request Form. If you have any questions, please contact Vee McMillen at vee at oreilly dot com.

== Directions Examples ==

Examples of how directions information is available on the net
* [http://mashpit.pbwiki.com/WalkaPedia Walkapedia]
* Direction By Landmark: leaving from Fairmont Hotel front door, making a left, next block take a right, cross the street and then enter Gordons Beer.
* ...

== See Also ==

* [[adr]]
* [[geo]]
* [[location-formats]]
* [[events]]

events/2006-06-13-where-2-bof

2006-06-16T18:42:18Z

AndrewTurner: /* Attending */

= Where 2.0 Microformats BOF II =

== Details ==

;Date: Tuesday, June 13, 2006
;Time: 7:30pm - 8:30pm PDT '''Tantek and Kevin running late ETA 7.50pm'''
;Location: Paseo Room, Fairmont Hotel San Jose, California, USA
;URLs: [http://wiki.oreillynet.com/where20_2006/index.cgi?BOFs Where 2.0 BOFs wiki page], [http://conferences.oreillynet.com/pub/w/47/bof.html Where 2.0 BOFs overview] > [http://conferences.oreillynet.com/cs/where2006/view/e_sess/9406 Geo Microformats BOF II: Developing a "directions" Microformat BOF page].
;Overview: Tim O'Reilly and Bill Gates [http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/ recently discussed microformats], and the [http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html need for a directions microformat became clear]. This sequel to [http://microformats.org/wiki/geo-bof-2005-06-30 last year's Microformats BOF] at Where 2.0 will discuss the [http://microformats.org/wiki/directions-examples work on the directions microformat to date], and [http://microformats.org/wiki/directions-brainstorming brainstorm on proposals] for a directions microformat.

== Attending ==

* [http://tantek.com/ Tantek Çelik], [http://technorati.com/ Technorati] (moderator)
* [http://epeus.blogspot.com Kevin Marks] [http://technorati.com/ Technorati]
* Jérémy Huylebroeck [http://www.francetelecom.com/en France Telecom R&D]
* [http://greg.abstrakt.ch Gregor J. Rothfuss], [http://www.endoxon.com Endoxon]
* [http://360.yahoo.com/shi_norman Norman Shi]
* [http://metaweb.com/ Jamie Taylor]
* Michael Leahy
* Gregor Rothfuss
* Josu Azpillaga [http://www.tagzania.com Tagzania.com]
* Luistxo Fernandez [http://www.tagzania.com Tagzania.com]
* Adrian Cuthbert [http://www.m-spatial.com m-spatial] [http://www.mylocalguru.com mylocalguru]
* Andrew Turner [http://highearthorbit.com HighEarthOrbit]

== Original Proposal ==

Original proposal as submitted to the Where 2.0 BOF proposal form:

=== Title ===

Geo Microformats BOF II: Developing a "directions" microformat

=== Describe the people who would be interested in attending this BOF ===

Anyone interested in *simple* standards for publishing and sharing geo related information on the Web, in particular directions information.

=== Which evenings(s) are you available to host your BOF? ===

I am available to host the BOF on June 13th only. My recommended time is from 6:30pm-7:30pm.

=== Full description of this BOF Maximum 250 words, about 35 lines.* ===

Last year at the inaugural "Where 2.0" conference, the Microformats BOF brought together key folks in the geo and microformats communities and together we were able to brainstorm and develop the "geo" and "adr" microformats.

http://flickr.com/photos/tantek/45109751/

http://microformats.org/wiki/adr

http://microformats.org/wiki/geo

During the opening keynote at the Mix06 conference this past March, Tim O'Reilly engaged Bill Gates in a discussion about microformats. During that conversation, Bill Gates specifically noted that we need microformats for contacts, events, and directions.

http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/

http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html

The first of those two have been well defined by hCard and hCalendar microformats. However, a directions microformat has yet to be defined. Research has begun towards the development of a directions microformat.

http://microformats.org/wiki/directions-examples

The goal of this BOF is to once again bring together key interested folks in the geo and microformats communities, discuss the work on the directions microformat to date, and brainstorm on proposals for a directions microformat.

=== Brief description of this BOF Maximum 50 words, about 7 lines.* ===

Tim O'Reilly and Bill Gates recently discussed microformats, and the need for a directions microformat became clear.

http://microformats.org/blog/2006/03/20/bill-gates-at-mix06-we-need-microformats/

http://radar.oreilly.com/archives/2006/03/directions_microformat_leading.html

This sequel to last year's Microformats BOF at Where 2.0 will discuss the work on the directions microformat to date, and brainstorm on proposals for a directions microformat.

http://microformats.org/wiki/directions-examples

=== Anything else we should know about your proposal? ===

=== Confirmation Post Submission ===

Birds of a Feather

Thank you for filling out the BOF Request Form. If you have any questions, please contact Vee McMillen at vee at oreilly dot com.

== Directions Examples ==

Examples of how directions information is available on the net
* [http://mashpit.pbwiki.com/WalkaPedia Walkapedia]
* Direction By Landmark: leaving from Fairmont Hotel front door, making a left, next block take a right, cross the street and then enter Gordons Beer.
* ...

== See Also ==

* [[adr]]
* [[geo]]
* [[location-formats]]
* [[events]]