http://microformats.org/wiki/api.php?action=feedcontributions&user=DimitriosZachariadis&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-29T15:03:57ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=icons&diff=38146icons2009-03-13T13:36:21Z<p>DimitriosZachariadis: corrected link for openmap.gif</p>
<hr />
<div><h1> Icons </h1><br />
These icons can be used to depict various microformats in webpages or on the desktop.<br />
<br />
== Creators ==<br />
* [http://factoryjoe.com/blog Chris Messina]<br />
* [http://dmitry.baranovskiy.com Dmitry Baranovskiy]<br />
* [http://bartleme.at Wolfgang Bartelme]<br />
<br />
==Accessibility==<br />
Publishers are advised to ensure that these icons are used in an accessible fashion, by including suitable "alt" attributes.<br />
<br />
Icon designers are reminded that inability to distinguish between red and green is the commonest form of color-blindness .<br />
<br />
=== Copyright ===<br />
Unless otherwise noted, these icons are licensed under the [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Attribution-ShareAlike 2.5 license].<br />
<br />
== Icons ==<br />
<br />
=== Web ===<br />
<br />
A [http://factorycity.net/projects/microformats-icons/ first effort] has been completed by Wolfgang Bartelme and Chris Messina to create a series of web-friendly icons and buttons for microformats.<br />
<br />
==== General ====<br />
<br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hatom.png hAtom <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcalendar.png hCalendar <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcard-add.png hCard Add <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcard-download.png hCard Download <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hresume.png hResume (button) <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-rel-tag.png rel-tag (button) <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-xfn.png XFN (button) <br />
<br />
'''Based on the General Icon DevKit:'''<br />
* http://farm1.static.flickr.com/247/515868619_ed9cda470a_o.png hCalendar Download<br />
* http://farm1.static.flickr.com/217/515843744_57bd70fdf5_o.png hCalendar Add<br />
* http://farm1.static.flickr.com/235/515843768_98956242a7_o.png hCard<br />
* http://farm3.static.flickr.com/2178/2528693942_1a58d71d27_o.png [http://notizblog.org/projects/haudio-icons/ hAudio Icons]<br />
<br />
'''Comments:'''<br />
<br />
* Hober pointed out that bright green seems to be a common color for [eventful.com/images/skin/ical.gif ical chicklets]<br />
* Tantek wonders if the rel-tag button is useful<br />
* ChrisMessina suggest a need for a small 10x10 tag icon<br />
** http://archgfx.net/aspnet_client/tag-ltblue.gif square tag<br />
** [[User:SunBurntKamel|Adam]] suggests 10x10 is a little small, but square is nice<br />
*** [[User:PatHawks|PatHawks]] thinks smaller is better, if the icon is going to sit next to every tag<br />
** [[User:Pfefferle|Pfefferle]] suggests the [http://www.famfamfam.com/lab/icons/silk/ FamFamFam] tag-icon: http://notizblog.org/wp-content/uploads/2007/05/tag_blue.png<br />
* Tantek wonders whether we need an hCard Download icon -- since it focuses too much on the "pipes"<br />
* Ron thinks it's ok to use icons, cause it's a nice way of promoting the "Microformat idea". Maybe it's a good idea to use a downward aimed arrow to indicate the possibility to "download" something (like an hCard or hResume).<br />
* Adam wonders if a multiple-license, including GPL, might be helpful in increasing adoption among wordpress themes.<br />
* [[User:Pfefferle|Pfefferle]] suggests to change the color of the XFN-button into blue, because it uses the rel-attribute like "rel-tag" http://farm1.static.flickr.com/195/515824030_3c0dd42493_o.png.<br />
* [[User:SvenDowideit|SvenDowideit]] wonders what font is used above, and why there are no open source friendly source files - ie svg (Dmitry's site is offline so i don't know if those are what I'm looking for)<br />
<br />
==== XFN ====<br />
<br />
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-me.png rel-me <br />
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-friend.png rel-friend <br />
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-friend-met.png met <br />
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-sweetheart.png rel-sweetheart <br />
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-sweetheart-met.png met <br />
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-colleague.png rel-colleague <br />
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-colleague-met.png met <br />
<br />
'''Comments:'''<br />
<br />
* Tantek: wonders if a rel-me icon is necessary or appropriate; perhaps something indicating "facets"?<br />
* ChrisMesssina: rel-me is useful in blog posts where you link to other posts that you've written<br />
* [[User:WizardIsHungry|Jon Williams]] 13:40, 5 Jan 2007 (PST): I thought "Flickr buddy" when I first saw these due to the color. Also the pink/blue may annoy people with some gender issues. Maybe we should use green for the sweetheart?<br />
* [[User:PatHawks|Pat Hawks]] 12:58, 11 Apr 2008 (CST): Should "crush" and "sweetheart" use the same icon? Should "colleague" and "co-worker" use the same? Do we need one for "contact" or "acquaintance" as well?<br />
<br />
==== VoteLinks ====<br />
<br />
[http://microformats.org/wiki/vote-links VoteLinks]<br />
<br />
* http://deliciouslymeta.com/projects/vote-links/vote-for.gif vote-for<br />
* http://deliciouslymeta.com/projects/vote-links/vote-against.gif vote-against<br />
* http://factorycity.net/projects/microformats%2Dicons/images/vote-links.png (download the [http://factorycity.net/projects/microformats%2Dicons/files/vote-links.zip kit])<br />
<br />
'''Comments:'''<br />
* [[User:SteveIvy|Steve Ivy]]: I don't have a good icon for vote-abstain. Recommendations welcome. These are also a tad large to site next to links, perhaps?<br />
** [[User:AndyMabbett|Andy Mabbett]]: Is +1/-1 a common way of representing voting? Would ticks and crosses be better, or thumbs up/ down (or horizontal for abstain)?<br />
*** [[User:SteveIvy|Steve Ivy]]: I rather like the icons used by [http://digg.com digg] for voting on comments, but cannot use them for obvious reasons. I'm no iconographer to be honest, but if someone were to create thumbs-up/thumbs-down icons I'd use them instead of these.<br />
<br />
==== Geo ====<br />
<br />
Can be used in the ''background-image'' CSS property, next to a geo microformat. It could also indicate that a map opens in a new window:<br />
<br />
* http://users.hol.gr/~dzach/microformats/openmap.gif<br />
<br />
* http://www.geotagicons.com/img/geotag-16px.png (taken from [http://www.geotagicons.com/ Geotag Icon Project])<br />
<br />
----<br />
<br />
=== Mac ===<br />
[http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons-preview.png]<br />
<br />
These [http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip icons] can be used for folders or files on your Mac. You can use a tool like [http://iconfactory.com/software/pixadex Pixadex] for managing and applying them.<br />
<br />
Created by [http://factoryjoe.com/blog Chris Messina]<br />
<br />
<br />
----<br />
<br />
<br />
=== PDF & SVG ===<br />
<br />
[http://dmitry.baranovskiy.com/res/mf-logo.pdf http://dmitry.baranovskiy.com/i/pdffile.png] [http://dmitry.baranovskiy.com/res/mf-logo.svg http://dmitry.baranovskiy.com/i/svgfile.png]<br />
<br />
This logo looks pretty much as first icon of Chris’ set. You could open it in any bitmap or vector editing tools, such as Adobe Photoshop or Adobe Illustrator.<br />
<br />
Created by [http://dmitry.baranovskiy.com Dmitry Baranovskiy]<br />
<br />
==See also==<br />
{{branding-see-also}}<br />
<br />
== Examples in the Wild ==<br />
<br />
* [http://zeroseis.com.br ZeroSeis] uses hCard download icon.<br />
* [http://www.bayofislands.net/ Bay of Islands] uses hCard geo icon eg. in [http://www.bayofislands.net/accommodation/backpackers/mousetrap/ Moustrap Backpackers] page<br />
* [http://www.nextbbs.com nextBBS] uses vote-links icons.<br />
* [http://www.revolucao.etc.br Revolução Etc] uses hCard download icon and tag icon.<br />
* There are various microformat logos on [http://www.westmidlandbirdclub.com/site/ the West Midland Bird Club's "about this site" page] and on its [http://www.westmidlandbirdclub.com/club/executive.htm contacts] and [http://www.westmidlandbirdclub.com/diary/2007/10.htm events] pages</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=geo-examples-in-wild&diff=25496geo-examples-in-wild2008-01-09T19:34:43Z<p>DimitriosZachariadis: </p>
<hr />
<div>==Geo Examples In The Wild==<br />
<br />
This section is '''informative'''.<br />
<br />
The following sites have published [[geo|Geo]] microformats, outside their normal context of [[hcard|hCards]] or [[hcalendar|hCalendars]], 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 the in many [[hcard-examples-in-wild|hCard examples in the wild]] and [[hcalendar-examples-in-wild|hCalendar examples in the wild]]. If you find Geos outside of hCards / hCalendars anywhere else, feel free to add them to the '''top''' of this list.<br />
<br />
Pages with live Geo can use this button (see [[buttons#Geo]] for any recent additions): http://rbach.priv.at/2006/buttons/geo.png<br />
<!--<br />
Please add new items to the TOP of this list<br />
--><br />
* [http://tilaphos.blogspot.com tilaphos blog] uses geo microformats for pointing to burnt areas recorded with a GPS and shown on a Google map. In Greek language. Other pages using geo microformats: [http://tilaphos.googlepages.com/areas.html map] and [http://tilaphos.googlepages.com/fullareas.html full page map]<br />
* [http://www.mapmytracks.com Map My Tracks] uses Geo microformats for the starting points of individual tracks created by mobile phone GPS tracking. See: [http://www.mapmytracks.com/explore/track/112 Elsenham Golf course]<br />
* [http://www.warmoth.com/gallery/gallery.cfm Warmoth Guitar Products Customer Gallery] features Geo microformats on the individual guitar detail pages. Example: [http://www.warmoth.com/gallery/gallery.cfm?fuseaction=include_container&id=193 Patrick Abbot's Guitar]<br />
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] a social network mashup, uses Geo with hAtom entries. See [http://dharmafly.com/blog/bangladeshboat Dharmafly blog discussion].<br />
* [http://www.gpsies.com/ GPSies.com] uses Geo markup to show start and endpoint of a track.<br />
* Christian Hess uses Geo to indicate where pictures in his photo gallery where taken, such as [http://www.hess-cr.com/secciones/galeria/playahermosa.shtml here] and [http://www.hess-cr.com/secciones/galeria/playascr.shtml here].<br />
* [http://www.txioka.net/ekitaldiak.php Txioka] has support for Geo and [[hcalendar|hCalendar]] microformats, parses twitter messages with [[twitter-nanoformats|twitter nanoformats]] and converts to geo and hcalendar.<br />
* [http://www.navitraveler.com/places/629/ NaviTraveler], e. g. [http://www.navitraveler.com/places/629/Lincoln_Memorial.html Lincoln Memorial].<br />
** Response in under 12 hours, to advocacy request - [[User:AndyMabbett|Andy Mabbett]]<br />
*[http://caving.atspace.com/ Caving in the Settle Area] uses Geo to mark up the U.K. NGR for cave locations.<br />
*[http://gc.kls2.com/ Great Circle Mapper] ("GCM"; e.g. [http://tinyurl.com/yugscj sample GCM trip], [http://gc.kls2.com/airport/BHX BHX on GCM])<br />
* [http://www.creation.uk.com Creation design & marketing] has Geo microformat on the [http://www.creation.uk.com/contact/ contact information].<br />
* <s>Wikipedia now has a template, [http://en.wikipedia.org/wiki/Template:Hcard-geo hcard-geo], for in-line hCards with coordinates, using Geo, such as that on [http://en.wikipedia.org/wiki/Engine_Arm Engine Arm]</s><br />
*[http://www.logon.ie/contact-us/ LogOn.ie] have added Geo (and hCard) to their contact page.<br />
*[http://www.davidosbornephotography.co.uk/gallery2/main.php www.davidosbornephotography.co.uk] has implemented Geo on all location photography pages; eg. [http://www.davidosbornephotography.co.uk/gallery2/main.php?g2_itemId=1747 Callanish Stones]<br />
*Wikipedia-IT now has Geo on all [http://it.wikipedia.org/wiki/Speciale:PuntanoQui/Template:Coord pages using the ''coord'' template], e.g. [http://it.wikipedia.org/wiki/Messina Messina]. [[User:AndyMabbett|Andy Mabbett]] 07:05, 26 May 2007 (PDT)<br />
*'Area' pages on Wholemap, summarizing the photos, videos, etc... for a specific area, now have Geo codes - [http://wholemap.com/map/area.php?area=NiagaraFalls Niagara Falls, for example] May 10, 2007<br />
*The Italian Wikipedia, for example [http://it.wikipedia.org/wiki/Genova Genova (Genoa)]<br />
*Geo has been added to all of [http://socialight.com Socialight]'s Sticky Notes - here's an example: [http://socialight.com/note/2007/4/14/11Aqk_a-great-way-to-spend-a-few-hours] <br />
*The [http://www.bayofislands.net/ Bay of Islands] site has Geo on its main page, and all photo pages. Example: [http://www.bayofislands.net/photos/8/ photo of Edgewater Apartments]<br />
*I've added geo to [http://commons.wikimedia.org/wiki/Special:Whatlinkshere/Template:Location_dec_US all images tagged in Wikimedia Commons] using decimal values. Example: [http://commons.wikimedia.org/wiki/Image:Montreal_City_Hall_Jan_2006.jpg Montreal City Hall, Jan 2006] [[User:AndyMabbett|Andy Mabbett]] 08:54, 12 Apr 2007 (PDT)<br />
**Now on pages tagged in D-M-S also.<br />
*Spotstor.com - e.g. [http://spotstor.com] uses Geo for all coordinates displayed on the site.<br />
*Panoramio - e.g. [http://www.panoramio.com/photo/564690]<br />
* Wikipedia-NL now has Geo on all its map-links pages, e.g. [http://www.nsesoftware.nl/wiki/maps.asp?params=52_28_47_N_1_53_51_W_type:city_region:GB&src=Birmingham_%28Engeland%29 maps for Wikipedia-NL article on Birmingham]<br />
**Called from '''87,724''' article pages as of 2006-04-09; reportedly the sixth most popular website in the Netherlands [http://www.multiscope.nl/organisatie/nieuws/sberichten/nederlandse-wikipedia-groeit-als-kool.html].<br />
* I recently added Geo to Wikipedia-DE's map link pages e.g. [http://tools.wikimedia.de/~magnus/geo/geohack.php?language=de&params=52_28_47_N_1_53_51_W_type:city_region:GB maps for Wikipedia-DE article on Birmingham]. [[User:AndyMabbett|Andy Mabbett]] 14:27, 9 Apr 2007 (PDT)<br />
* I've just added Geo to OpenStreetMap documentation pages - see [http://wiki.openstreetmap.org/index.php/Birmingham Birmingham page on OpenStreetMap] for example. [[User:AndyMabbett|Andy Mabbett]] 02:39, 6 Apr 2007 (PDT)<br />
* I've [http://en.wikipedia.org/w/index.php?title=Template%3AGeoTemplate&diff=119003866&oldid=118216477 just added] Geo to Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has a Geo microformat. [[User:AndyMabbett|Andy Mabbett]] 03:38, 30 Mar 2007 (PDT)<br />
** [http://tools.wikimedia.de/~kolossos/wp-world/imageworld-art.php Map showing global distribution of Geo-tagged Wikipedia articles].<br />
* [http://www.jillesvangurp.com/places jillesvangurp.com] provides an xsl stylesheet to transform Google Earth place-marks (KMZ files) into html with nested lists of Geo formatted places. Several examples are provided.<br />
*[http://www.geograph.org.uk Geograph British Isles] has experimental support for geos on '''350,000+''' photo pages, for example http://www.geograph.org.uk/photo/1234<br />
*[http://www.poi66.com/ POI66] has '''over 58,500''' waypoints Geo-formatted, many describing [[geo-waypoint-examples|trails]] e.g [http://www.poi66.com/maps/show_album.php?album=santiago Mijn pelgrimstocht naar Santiago]<br />
* [http://3amproductions.net 3AM Productions] has published coordinates of cities both in and outside the context of hCards under [http://3amproductions.net/jason.php Jason's] and [http://3amproductions.net/gilbert.php Gil's] pages.<br />
*Wikitravel now has the facility to add co-ordinates for the subject of the article, and publishes them as a Geo microformat - e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]; see [http://wikitravel.org/shared/Tech:Add_SpecialMap_using_Mapstraction_link_for_geo-tagged_pages_and_for_single_listings The announcement].<br />
* [http://flickr.com/ Flickr] now [http://blog.flickr.com/flickrblog/2006/08/great_shot_wher.html supports the geo microformat] on all [http://flickr.com/map/ geotagged photos]. Within 11 days of launch there are now over '''3,000,000+''' photos (as of 2006-09-07) marked up with the "geo" microformat. <br />
* [http://ocono.com/ ocono.com] has marked each of it's "Upcoming Events" items with latitude/longitude values.<br />
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]<br />
* [http://www.multimap.com Multimap.com] uses Geo to mark up latitude and longitude values on map pages.<br />
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.<br />
* [http://07.pagesd.info/ 07.pagesd.info] uses Geo to mark up latitude and longitude values for each commune of the Ardèche département in France.<br />
* [http://www.openguides.org/ OpenGuides] has support for Geo in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide]<br />
<br />
<!--<br />
Please add new items to the TOP of this list<br />
--><br />
<br />
===Examples with some problems===<br />
<br />
Entries may be moved here if there's a problem with the way Geo is used on the page concerned. If the page is yours, and you want to improve it, see the [[hcard-faq|hCard & Geo FAQ]], or raise any queries on [[hcard-issues|hCard & Geo Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you.<br />
<br />
*[http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia-EN templates_generating_Geo]<br />
**'''hidden''' - for example [http://en.wikipedia.org/wiki/List_of_Minnesota_State_Parks List of Minnesota state parks]<br />
*[http://barcamp.org/BarCampBlock Bar Camp Block]<br />
**Geo uses integer values; displayed text also has minutes and seconds <br />
* [http://www.w3.org/People/Connolly/events/ Dan Connoly's Index of Events] has a few Geos<br />
** Two of the Geos are invalid because they use commas instead of semicolons<br />
<br />
== Related Pages ==<br />
{{geo-related-pages}}</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=irc-people&diff=12893irc-people2007-01-24T08:28:00Z<p>DimitriosZachariadis: </p>
<hr />
<div>A list of [[irc|IRC]] regulars sorted by nick and their normal timezones (winter/summer).<br />
<br />
* [[User:Adam Craven|AdamCraven]] (+0000)<br />
* [[User:Amette|amette]] (+1000)<br />
* [[User:Ashley|Ashley]] (+1000)<br />
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)<br />
* [[User:Tyler Roehmholdt|Baristo]] (-0800/-0700)<br />
* [[User:Ben Ward|BenWard]] (+0000)<br />
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)<br />
* [[User:HenriBergius|bergie]] (+0200/+0300)<br />
* [[User:BenWest|bewest]] (-0800/-0700)<br />
* [[User:BluesMoon|bluesmoon]] (+0530)<br />
* [[User:Bob Jonkman|BobJonkman]] (-0500/-0400)<br />
* [[User:Boneill|boneill]] (+0000)<br />
* [[User:Brian|briansuda]] (+0000)<br />
* [[User:Cgriego|cgriego]] (-0600/-0500)<br />
* [[User:CharlesRoper|charles_r]] (0000/+0100)<br />
* [[User:Charlvn|Charl]] (+0200/+0200)<br />
* [[User:ChristopherStJohn|cks]] (-0600/-0500)<br />
* [[User:Cloud|Cloud]] (+0000)<br />
* [[User:Colin_Barrett|cbarrett]] (-1000)<br />
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)<br />
* [[User:Csarven|csarven]] (-0500/-0400)<br />
* [[User:Dan Kubb|dkubb]] (-0800/-0700)<br />
* [[User:DanC|DanC]] (-0600/-0500)<br />
* [[User:DannyAyers|danja]] (+0100/+0200)<br />
* [[User:Dave Cardwell|davecardwell]] (+0000)<br />
* [[User:DeanEro|deanero]] (-0800/-0700)<br />
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)<br />
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)<br />
* [[User:DrewBell|droob]] (-0600/-0500)<br />
* [[User:DimitriosZachariadis|dzach]] (+0200/+0300)<br />
* [[User:Ed Summers|edsu]] (-0500/-0400)<br />
* [[User:Enric|enric]] (-0800/-0700)<br />
* [[User:Enric|Enric]] (-0800/-0700)<br />
* [[User:Evan|evanpro]] (-0500)<br />
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)<br />
* [[User:Fil|Fil]] (+0200)<br />
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)<br />
* [[User:Grantbow|Grantbow]] (-0800/-0700)<br />
* [[User:Hlb|hlb]] (+0800-0700)<br />
* [[User:IanHickson|Hixie]] (-0800/-0700)<br />
* [[User:EdwardOConnor|hober]] (-0800/-0700)<br />
* [[User:IwaiMasaharu|iwaim]] (+0900)<br />
* [[User:Izo|IZO]]<br />
* [[User:JamieKnight|jammie_]] (+1000/0000)<br />
* [[User:WizardIsHungry|jcw9]] (-0500/-0400)<br />
* [[User:Adactio|Jeremy Keith]] (+0000)<br />
* [[User:JasonK|jkridner]] (-0600/-0500)<br />
* [[User:JoeGregorio|jcgregorio]]<br />
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)<br />
* [[User:JulianStahnke|Julian Stahnke]] (+0000)<br />
* [[User:Kapowaz|kapowaz]] (+0000/+0100)<br />
* [[User:Keri Henare|kerihenare]] (+1200)<br />
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)<br />
* [[User:RyanKing|kingryan]] (-0800/-0700)<br />
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC<br />
* [[User:Lachlan Hunt|Lachy]] (+1000/+1100)<br />
* [[User:Mark Mansour|Mark Mansour]] (+1100)<br />
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)<br />
* [[User:CiaranMc|McNulty]] (+0000/+0100)<br />
* [[User:MikeKaply|mkaply]] (-0600/-0500)<br />
* [[User:SteveIvy|monkinetic/redmonk]] (-0700)<br />
* [[User:neuro|neuro`]]<br />
* [[User:NTollervey|ntoll]] (+0000/+0100)<br />
* [[User:Phae|Phae]] (+0000/+0100)<br />
* [[User:PriitLaes|plaes]] (+0200/+0300)<br />
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)<br />
* [[User:DavidOsolkowski|qid]] (-0500)<br />
* [[User:Remi|Remi]] (-0500/-0400)<br />
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)<br />
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)<br />
* [[User:Ronnos|Ron Kok]] (+0000)<br />
* [[User:Dana Benson|Snowden]] (-0800/-0700)<br />
* [[User:Smackman|Steve Farrell]] (-0800/-0700)<br />
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)<br />
* [[User:SuperPhly|SuperPhly]] (-600/-500)<br />
* [[User:Tantek|Tantek]] (-0800/-0700)<br />
* [[User:Trovster|trovster]] (-0800/-0700)<br />
* [[User:Vant|vant]] (+0900)<br />
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)<br />
* [[User:JacksonWilkinson|whafro]] (-0500/-0400)<br />
* [[User:Richard Conyard|WhiskeyM]] (+0000)<br />
* [[User:Veeliam|William Lawrence]] (-0800/-0700)<br />
* [[User:Ianloic|yakk]] (-0800/-0700)</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=25647thoughts-on-extending-the-geo-microformat2007-01-23T21:54:56Z<p>DimitriosZachariadis: </p>
<hr />
<div>'''This page and effort is failing to follow the microformats [[process]]. If you are the author of this page, please join the [http://microformats.org/discuss #microformats IRC channel and/or microformats-discuss mailing list] so that the community can help walk you through the process.''' - Tantek<br />
<br />
<span style="color:red;">This page is now abandoned due to non conformance. Some of this material may appear on new pages following the proper process.</span> - DimitriosZachariadis<br />
<br />
==4d: A geo microformat alternative proposal==<br />
<br />
<div style="width:800px;"><br />
<br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction</div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an alternative for the draft '''geo''' microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and used without problems. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues at hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in one single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the '''4d''' microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' and displayed on [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
==Specification==<br />
It is proposed that the '''4d''' microformat be formed as follows:<br />
<br />
===Root Class Name===<br />
The root class name for a '''4d''' location/event is ''4d''<br />
<br />
===Property List===<br />
The '''4d''' microformat has the following no properties.<br />
<br />
===Value===<br />
The value of a '''4d''' location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, optional<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If abiguities arrise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''<br />
<br />
===Default Reference System===<br />
The default reference system is WGS84 and the Gregorian calendar.<br />
<br />
The time dimension is expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="4d.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''u'': '''WGS84'''<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, defaults to '''0.0'''<br />
''t'': time, no default<br />
<br />
The default reference system for an (X)HTML page can be set by using meta data properties.<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping '''4d''' values compact. By adding the '''4d''' metadata element, a conversion from the '''geo''' microformat to the '''4d''' would only require the change of the root class, from ''geo'' to ''4d''.<br />
<br />
===Reference systems===<br />
Indicative reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
<br />
==Examples==<br />
The markup used in the discussion, transferred in the '''4d''' microformat:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="4d" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
====Example 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
<abbr class="4d" title="37.971508;23.72658;;1687"></abbr><br />
</nowiki></pre><br />
<br />
====Example 2====<br />
Hidden 4d coordinates, free text content<br />
<pre><nowiki><br />
<span class="4d" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="4d" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Example 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Example 4====<br />
Minimum HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="4d.reference" content="WGS86"/><br />
</head><br />
<body><br />
<div class="4d" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Example 5====<br />
A fictitious Mars reference system, using actual Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="4d" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="4d" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appering here and a small map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
==Further discussion==<br />
Pages for discussing this proposal:<br />
<br />
* [[4d brainstorming]]<br />
* [[4d implementation notes]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12792thoughts-on-extending-the-geo-microformat2007-01-23T21:52:12Z<p>DimitriosZachariadis: </p>
<hr />
<div>'''This page and effort is failing to follow the microformats [[process]]. If you are the author of this page, please join the [http://microformats.org/discuss #microformats IRC channel and/or microformats-discuss mailing list] so that the community can help walk you through the process.''' - Tantek<br />
<br />
<h5 style="color:red;font-weight:bold;">This page is now abandoned due to non conformance. Some of this material may appear on new pages following the proper process'''.</h5> [[User:DimitriosZachariadis|DimitriosZachariadis]]<br />
==4d: A geo microformat alternative proposal==<br />
<br />
<div style="width:800px;"><br />
<br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction</div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an alternative for the draft '''geo''' microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and used without problems. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues at hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in one single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the '''4d''' microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' and displayed on [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
==Specification==<br />
It is proposed that the '''4d''' microformat be formed as follows:<br />
<br />
===Root Class Name===<br />
The root class name for a '''4d''' location/event is ''4d''<br />
<br />
===Property List===<br />
The '''4d''' microformat has the following no properties.<br />
<br />
===Value===<br />
The value of a '''4d''' location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, optional<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If abiguities arrise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''<br />
<br />
===Default Reference System===<br />
The default reference system is WGS84 and the Gregorian calendar.<br />
<br />
The time dimension is expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="4d.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''u'': '''WGS84'''<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, defaults to '''0.0'''<br />
''t'': time, no default<br />
<br />
The default reference system for an (X)HTML page can be set by using meta data properties.<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping '''4d''' values compact. By adding the '''4d''' metadata element, a conversion from the '''geo''' microformat to the '''4d''' would only require the change of the root class, from ''geo'' to ''4d''.<br />
<br />
===Reference systems===<br />
Indicative reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
<br />
==Examples==<br />
The markup used in the discussion, transferred in the '''4d''' microformat:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="4d" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
====Example 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
<abbr class="4d" title="37.971508;23.72658;;1687"></abbr><br />
</nowiki></pre><br />
<br />
====Example 2====<br />
Hidden 4d coordinates, free text content<br />
<pre><nowiki><br />
<span class="4d" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="4d" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Example 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Example 4====<br />
Minimum HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="4d.reference" content="WGS86"/><br />
</head><br />
<body><br />
<div class="4d" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Example 5====<br />
A fictitious Mars reference system, using actual Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="4d" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="4d" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appering here and a small map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
==Further discussion==<br />
Pages for discussing this proposal:<br />
<br />
* [[4d brainstorming]]<br />
* [[4d implementation notes]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=geo&diff=12787geo2007-01-23T12:40:53Z<p>DimitriosZachariadis: </p>
<hr />
<div><h1> geo </h1><br />
<br />
'''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.<br />
__TOC__<br />
<br />
== Draft Specification ==<br />
<br />
=== Editor/Author ===<br />
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2005}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
=== Inspiration and Acknowledgments ===<br />
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].<br />
<br />
== Introduction and Background ==<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== Singular Properties ===<br />
<br />
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.<br />
<br />
=== Human vs. Machine readable ===<br />
<br />
If an <code>&lt;abbr&gt;</code> element is used for a property, then the <code>title</code> attribute of the <code>&lt;abbr&gt;</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.<br />
<br />
=== Value excerpting ===<br />
<br />
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.<br />
<br />
=== Root Class Name ===<br />
<br />
The root class name for an geo location is <code>geo</code>.<br />
<br />
=== Property List ===<br />
<br />
This is the list of properties in geo, taken from [[hcard|hCard]]:<br />
<br />
* latitude<br />
* longitude<br />
<br />
=== XMDP Profile ===<br />
<br />
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.<br />
<br />
=== Parsing Details ===<br />
<br />
See [[hcard-parsing|hCard parsing]], with the only difference being that "geo" is the root class name, rather than "vcard".<br />
<br />
== Examples ==<br />
<br />
This section is informative.<br />
<br />
=== Example from RFC2426 ===<br />
<br />
Section 3.4.2 of RFC2426 has a simple geo example:<br />
<br />
<pre><nowiki><br />
GEO:37.386013;-122.082932<br />
</nowiki></pre><br />
<br />
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]:<br />
<br />
<pre><nowiki><br />
<span class="geo"><br />
<span class="latitude">37.386013</span>, <br />
<span class="longitude">-122.082932</span><br />
</span><br />
</nowiki></pre><br />
<br />
this geo could be displayed as: <br />
<br />
37.386013, -122.082932<br />
<br />
<br />
=== Real world geo example ===<br />
<br />
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]):<br />
<br />
<pre><nowiki><br />
N 37° 24.491 W 122° 08.313<br />
</nowiki></pre><br />
<br />
With geo markup:<br />
<br />
<pre><nowiki><br />
<div class="geo"><br />
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <br />
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr><br />
</div><br />
</nowiki></pre><br />
<br />
This geo might be displayed as:<br />
<br />
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <br />
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr><br />
<br />
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.<br />
<br />
== Examples in the wild ==<br />
This section is '''informative'''.<br />
<br />
The following sites have published geos, outside their normal context of hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc., in addition to those in many [[hcard-examples-in-wild|hCard examples in the wild]]. If you find geos outside of hCards anywhere else, feel free to add them to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
*Wikitravel now has the facility to add co-ordinates for the subject of the article, and publishes them as a 'geo' microformat - e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]; see [http://wikitravel.org/shared/Tech:Add_SpecialMap_using_Mapstraction_link_for_geo-tagged_pages_and_for_single_listings The announcement].<br />
* [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. <br />
* [http://ocono.com/ ocono.com] has marked each of it's "Upcoming Events" items with lat/long values.<br />
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]<br />
* [http://www.multimap.com Multimap.com] uses the geo microformat to mark up latitude and longitude values on map pages.<br />
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.<br />
* [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.<br />
* [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]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
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.<br />
<br />
* [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] <br />
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)<br />
* [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]].<br />
* [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]<br />
* [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].<br />
* [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]].<br />
* 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.<br />
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].<br />
* [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]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [[hcard|hCard]]<br />
<br />
=== Informative References ===<br />
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]<br />
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]<br />
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.<br />
<br />
== Related Work ==<br />
* [[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)<br />
* [[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)<br />
* [[geo-extension-strawman]] - extends [[geo]] to include the above, and for representing coordinates on other planets, moons etc.<br />
* [[thoughts-on-extending-the-geo-microformat|thoughts on addind time and reference system]] to the geo microformat, that could also be used for places on other celestial bodies<br />
<br />
== Similar Work ==<br />
* [[adr]]<br />
* [[hcalendar|hCalendar]]<br />
* [[XOXO]]<br />
<br />
== See Also ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]<br />
<br />
== Related Pages ==<br />
<br />
{{geo-related-pages}}<br />
* Proposals for changes, additions and other thoughts about [[geo]] may be found in the [[hcard-brainstorming|hCard brainstorming]] page.<br />
* If you have any questions about [[geo]], 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.</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Main_Page&diff=29402Main Page2007-01-23T02:25:46Z<p>DimitriosZachariadis: </p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.<br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]] <br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* [[thoughts-on-extending-the-geo-microformat|thoughts on extending the geo microformat]], [http://microformats.telemetry.gr examples] {{NewMarker}}<br />
<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])<br />
* Does somebody want to see a Dutch translation???</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts_on_extending_the_geo_microformat&diff=32698thoughts on extending the geo microformat2007-01-23T02:24:21Z<p>DimitriosZachariadis: thoughts on extending the geo microformat moved to thoughts-on-extending-the-geo-microformat</p>
<hr />
<div>#REDIRECT [[thoughts-on-extending-the-geo-microformat]]<br />
</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Main_Page&diff=29401Main Page2007-01-23T00:32:22Z<p>DimitriosZachariadis: </p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.<br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]] <br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* [[thoughts_on_extending_the_geo_microformat|thoughts on extending the geo microformat]], [http://microformats.telemetry.gr examples] {{NewMarker}}<br />
<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])<br />
* Does somebody want to see a Dutch translation???</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Thoughts_on_extending_the_geo_microformat&diff=32695Thoughts on extending the geo microformat2007-01-23T00:31:37Z<p>DimitriosZachariadis: Thoughts on extending the geo microformat moved to thoughts on extending the geo microformat</p>
<hr />
<div>#REDIRECT [[thoughts on extending the geo microformat]]<br />
</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Main_Page&diff=29400Main Page2007-01-23T00:30:02Z<p>DimitriosZachariadis: </p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.<br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]] <br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* [[Thoughts_on_extending_the_geo_microformat|thoughts on extending the geo microformat]], [http://microformats.telemetry.gr examples] {{NewMarker}}<br />
<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])<br />
* Does somebody want to see a Dutch translation???</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Main_Page&diff=29399Main Page2007-01-23T00:28:26Z<p>DimitriosZachariadis: </p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.<br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]] <br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* [[Thoughts_on_extending_the_geo_microformat|Thoughts on extending the geo microformat]], [http://microformats.telemetry.gr examples]<br />
<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])<br />
* Does somebody want to see a Dutch translation???</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=icons&diff=15196icons2007-01-23T00:19:30Z<p>DimitriosZachariadis: </p>
<hr />
<div><h1> Icons </h1><br />
These icons can be used to depict various microformats in webpages or on the desktop.<br />
<br />
== Creators ==<br />
* [http://factoryjoe.com/blog Chris Messina]<br />
* [http://dmitry.baranovskiy.com Dmitry Baranovskiy]<br />
* [http://bartleme.at Wolfgang Bartelme]<br />
<br />
==Accessibility==<br />
Publishers are advised to ensure that these icons are used in an accessible fashion, by including suitable "alt" attributes.<br />
<br />
Icon designers are reminded that inability to distinguish between red and green is the commonest form of colour-blindness .<br />
<br />
=== Copyright ===<br />
Unless otherwise noted, these icons are licensed under the [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Attribution-ShareAlike 2.5 license].<br />
<br />
== Icons ==<br />
<br />
=== Web ===<br />
<br />
A [http://factorycity.net/projects/microformats-icons/ first effort] has been completed by Wolfgang Bartelme and Chris Messina to create a series of web-friendly icons and buttons for microformats.<br />
<br />
==== General ====<br />
<br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hatom.png hAtom <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcalendar.png hCalendar <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcard-add.png hCard Add <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hcard-download.png hCard Download <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-hresume.png hResume (button) <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-rel-tag.png rel-tag (button) <br />
* http://factorycity.net/projects/microformats%2Dicons/images/icon-xfn.png XFN (button) <br />
<br />
'''Comments:'''<br />
<br />
* Hober pointed out that bright green seems to be a common color for [eventful.com/images/skin/ical.gif ical chicklets]<br />
* Tantek wonders if the rel-tag button is useful<br />
* ChrisMessina suggest a need for a small 10x10 tag icon<br />
* Tantek wonders whether we need an hCard Download icon -- since it focuses too much on the "pipes"<br />
* Ron thinks it's ok to use icons, cause it's a nice way of promoting the "Microformat idea". Maybe it's a good idea to use a downward aimed arrow to indicate the possibility to "download" something (like an hCard or hResume).<br />
<br />
==== XFN ====<br />
<br />
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-me.png rel-me <br />
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-friend.png rel-friend <br />
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-friend-met.png met <br />
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-sweetheart.png rel-sweetheart <br />
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-sweetheart-met.png met <br />
* http://factorycity.net/projects/microformats%2Dicons/images/xfn-colleague.png rel-colleague <br />
** http://factorycity.net/projects/microformats%2Dicons/images/xfn-colleague-met.png met <br />
<br />
'''Comments:'''<br />
<br />
* Tantek: wonders if a rel-me icon is necessary or appropriate; perhaps something indicating "facets"?<br />
* ChrisMesssina: rel-me is useful in blog posts where you link to other posts that you've written<br />
* [[User:WizardIsHungry|Jon Williams]] 13:40, 5 Jan 2007 (PST): I thought "Flickr buddy" when I first saw these due to the color. Also the pink/blue may annoy people with some gender issues. Maybe we should use green for the sweetheart?<br />
<br />
==== VoteLinks ====<br />
<br />
[http://microformats.org/wiki/vote-links VoteLinks]<br />
<br />
* http://deliciouslymeta.com/projects/vote-links/vote-for.gif vote-for<br />
* http://deliciouslymeta.com/projects/vote-links/vote-against.gif vote-against<br />
<br />
'''Comments:'''<br />
* [[User:SteveIvy|Steve Ivy]]: I don't have a good icon for vote-abstain. Recommendations welcome. These are also a tad large to site next to links, perhaps?<br />
** [[User:AndyMabbett|Andy Mabbett]]: Is +1/-1 a common way of representing voting? Would ticks and crosses be better, or thumbs up/ down (or horizontal for abstain)?<br />
*** [[User:SteveIvy|Steve Ivy]]: I rather like the icons used by [http://digg.com digg] for voting on comments, but cannot use them for obvious reasons. I'm no iconographer to be honest, but if someone were to create thumbs-up/thumbs-down icons I'd use them instead of these.<br />
<br />
==== Geo ====<br />
<br />
Can be used in the ''background-image'' CSS property, next to a geo microformat. It could also indicate that a map opens in a new window:<br />
<br />
* http://microformats.telemetry.gr/openmap.gif<br />
<br />
----<br />
<br />
=== Mac ===<br />
[http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons-preview.png]<br />
<br />
These [http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip icons] can be used for folders or files on your Mac. You can use a tool like [http://iconfactory.com/software/pixadex Pixadex] for managing and applying them.<br />
<br />
Created by [http://factoryjoe.com/blog Chris Messina]<br />
<br />
<br />
----<br />
<br />
<br />
=== PDF & SVG ===<br />
<br />
[http://dmitry.baranovskiy.com/res/mf-logo.pdf http://dmitry.baranovskiy.com/i/pdffile.png] [http://dmitry.baranovskiy.com/res/mf-logo.svg http://dmitry.baranovskiy.com/i/svgfile.png]<br />
<br />
This logo looks pretty much as first icon of Chris’ set. You could open it in any bitmap or vector editing tools, such as Adobe Photoshop or Adobe Illustrator.<br />
<br />
Created by [http://dmitry.baranovskiy.com Dmitry Baranovskiy]<br />
<br />
<br />
== Examples in the Wild ==<br />
<br />
* [http://zeroseis.com.br ZeroSeis] uses hCard download icon.<br />
* [http://www.nextbbs.com nextBBS] uses vote-links icons.<br />
* [http://www.revolucao.etc.br Revolução Etc] uses hCard download icon and tag icon.</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=A_proposal_for_amendment_of_the_geo_microformat&diff=32693A proposal for amendment of the geo microformat2007-01-23T00:10:43Z<p>DimitriosZachariadis: A proposal for amendment of the geo microformat moved to Thoughts on extending the geo microformat</p>
<hr />
<div>#REDIRECT [[Thoughts on extending the geo microformat]]<br />
</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12775thoughts-on-extending-the-geo-microformat2007-01-23T00:08:20Z<p>DimitriosZachariadis: </p>
<hr />
<div>==Thoughts on extending the geo microformat==<br />
<br />
<div style="width:800px;"><br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 23 Jan 2007 (PST)<br />
<br />
__toc__<br />
<br />
===Introduction===<br />
The need for inclusion of altitude, time and reference system in the geo microformat is discussed. A five part value, semicolon separated, is argued to be sufficient for uniquely identifying a place or an event in a four dimensional universe.<br />
<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present a status of draft. With this in mind, a number of issues regarding the need for time and a reference system are presented for discussion.<br />
<br />
===Time===<br />
In a four dimensional space, a point represents an event; three dimensional geometry, cartography, and time, can all be thought of as subsets of spacetime; a location on a map is expressed in a 2D spacetime subset, a photograph in a 3D subset where time is the 3rd dimension.<br />
<br />
It can be argued, that most of the location related information, whether on Earth or on another celestial body, have a time related aspect attached; historical places and events, geographical features, are usually related to an act or an observation made at some point in time. Landmarks existing for centuries have an age, which means they have a birthday, and most probably a death. Photographs and videos can be thought as 3D snapshots (2D+time) in a 4D continuum. <br />
<br />
A large amount of location information used by people on a daily basis on the web, is in fact an aggregation of events; stories, news, photographs and videos, even items auctioned on ebay are nothing more than snapshots of spacetime. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known.<br />
<br />
It is obvious that the inclusion of a time dimension in the geo markup moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events; events are about stories, cartography is about navigation. People are interested in stories, news and events, which undoubtedly constitutes most of the information viewed with a web browser; few people can successfully navigate a car using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in texts are quite useless without a map. Humans use names to identify places, not numbers. The reason geographic coordinates exist in text, is merely to help humans manually identify places on maps. If things can be done electronically, then numbers don't seem to matter a lot any more.<br />
<br />
=====Real world examples=====<br />
Countless examples of 2D+time events exist:<br />
<br />
*[http://flickr.com/map/ flickr]: geotagged photos with a date of capture.<br />
*[http://www.youtube.com/categories_portal?c=19&e=1 youtube]: videos with a location and a date.<br />
*[http://en.wikipedia.org/wiki/Main_Page wikipedia, In the news]: front page news, "On this day..."<br />
*[http://www.bbc.co.uk/ BBC]: news<br />
*[http://www.nasa.gov/externalflash/Mars_as_art/index_noaccess.html Mars As Art]<br />
*[http://www.nasa.gov/mission_pages/mars/main/index.html NASA: Explore Mars]: space exploration vehicles, celestial body features, [http://www.nasa.gov/missions/past/index.html Missions]<br />
*[http://ciclops.org/index.php Cassini imaging]<br />
<br />
Examples of loose, or changing, attachment of time to location also exist:<br />
<br />
An example from [http://www.ebay.com/ ebay] is indicative:<br />
<pre><nowiki><br />
End time: Jan-29-07 06:18:15 PST (6 days 21 hours)<br />
Shipping costs: US $1.88<br />
US Postal Service First Class Mail®<br />
Service to United States<br />
(more services)<br />
Ships to: Worldwide<br />
Item location: Dinwiddie, Virginia, United States<br />
History: 0 bids<br />
</nowiki></pre><br />
<br />
===Different times===<br />
Dealing with time in multiple reference systems is not quite the same as dealing with local time. It might not be necessary for humans to do it in their daily life, but it is important when when information on a global, or universal basis is involved. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar],[http://en.wikipedia.org/wiki/Hebrew_calendar Hebrew calendar], [http://en.wikipedia.org/wiki/Egyptian_calendar Egyptian calendar].<br />
<br />
In a similar manner, trying to understand Martian time, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a human cannot get a "7 hours behind local time" sync with Martian time; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
Different calendars and time standards should have a place in the Semantic Web. <br />
<br />
===The reference system===<br />
Although the geo microformat specification states WGS84 as the reference system used, this is not a trivial issue: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from a location, since the reference system used at that time was different than WGS84. Furthermore, the same coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again. Besides this, there is a number of other coordinate systems that are used extensively today, like the Universal Transverse Mercator (UTM) system, that are excluded from the geo specification. The problem is that tying a microformat specification to a particular reference system, and only that, may be a limiting factor for the microformat.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates ([http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map])<br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
When geo tagging information about other celestial bodies, the need for a reference system is even more pronounced; lacking familiar country or city names makes feature identification a difficult task. Existing reference systems are bound to change many times, as more data becomes available for these bodies.<br />
<br />
For a microformat to be able to convey accurate information, well defined and known reference systems should be specified together with the data. Geo reference systems, such as WGS84, also make references to the time standard used [http://earth-info.nga.mil/GandG/publications/tr8350.2/wgs84fin.pdf WGS84 Definition]. Transformations among the various reference systems can make content referenced by geo data in one system understandable and usefull on another.<br />
<br />
==Thoughts on specification extension==<br />
The geo microformat as it stands today, offers a representation of a point in a 2D space. Both expanded and compact forms of geo provide decimal number representations of coordinates suitable for machines.<br />
<br />
===Expanded form===<br />
The new properties to implement the additional dimensions of altitude and time could be:<br />
* dtstamp, as found in hCalendar<br />
* altitude, or the z direction<br />
* georef<br />
<br />
The dimension of time could be represented by reusing the ''dtstamp'' property found in [http://microformats.org/wiki/hcalendar hCalendar]. The calendar to be used, depends on the reference system, and for WGS84 is the Gregorian calendar.<br />
<br />
The dimension of altitude could be represented by the use of an ''altitude'' property, expressed in the WGS84 reference system in meters.<br />
<br />
The ''georef'' property is a string determining the reference system, e.g. "WGS84". Additional fields could be allowed with the use of the delimiter ":", e.g. "MARS:J2000" (fictional).<br />
<br />
===Compact form===<br />
The value of an extended geo location/event resides in the ''title'' attribute of an (X)HTML element as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u''<br />
''v2'' is either longitude or y, depending on ''u''<br />
''z'' is the altitude<br />
''t'' is the time<br />
''u'' is the reference system code<br />
<br />
The original form ''lat;lon'' is a valid form. To disambiguate this data, the reference system used in this case should have been specified globally for the page.<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted if they are at the end of the tuple. However, if omitting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''.<br />
<br />
Dimensions v1 and v2 could also theoretically be omitted, e.g. ''23.5'' may represent the tropic of Cancer, '';0.0'' the Greenwich Meridian, while '';;;2007'' expresses the time (assuming a WGS84 reference system), although the latter could be better represented by a ''dtstamp'' property. However, such representations are obscure and do not add to the clarity of the data. <br />
<br />
===Default Reference System===<br />
The vCard, RCF2426 specification, which has been the basis for the geo microformat, does not specify a reference datum, but it specifies ISO-8601 as the standard for the UTC-OFFSET value type used in the TZ (timezone) type. hCalendar uses ISO-8601 (date)time formats.<br />
<br />
The reference system specified by the geo microformat is WGS84. WGS84 in turn uses UTC to count (date)time which is based on the Gregorian calendar. It should be possible for the reference system to be explicitly stated either globally or within the geo data tuple. Units for data in the geo microformat are those specified in the reference system used.<br />
<br />
===Meta data===<br />
The default reference system could be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="georef" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
Only the ''z'' dimension (altitude, in WGS86) when omitted assumes a '''0.0''' meters value.<br />
<br />
The default reference system for an (X)HTML page should be set by using meta data properties, if the geo data tuple defines no reference system. The inclusion of the meta data element ensures the validity of the spacetime data for as long as the page exists, while keeping geo values compact. By adding the '''georef''' metadata property, a transition to the extended geo microformat would require no further change to the markup.<br />
<br />
===Significant digits===<br />
A human reader interpretes the number of signifficant digits given in a number as a measure of the accuracy of the number. The number of significant digits in the coordinates could be related to the '''scale''' that a particular cartographic (or other) representation of a 4D point should be rendered in.<br />
<br />
An application could use this expression accuracy, e.g. the number of decimal digits present in a coordinate to derive the '''zoom''' factor for a map showing the specific location.<br />
<br />
===Reference systems===<br />
Other reference systems include:<br />
* UTM:''zone''<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
** ''zone'' is the UTM zone<br />
...more<br />
<br />
==Examples==<br />
====Example 1====<br />
Hidden 4D coordinates, no content<br />
<pre><nowiki><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
<abbr class="geo" title="37.971508;23.72658;;1687"><br />
</nowiki></pre><br />
<br />
====Example 2====<br />
Hidden 2D coordinates and georef, free text content, expanded form<br />
<pre><nowiki><br />
<span class="geo"><br />
The Parthenon was ruined by a Venetian cannonball in <br />
<abbr class="dtstamp" title="1687">1687</abbr><br />
<abbr class="latitude" title="37.971508"></abbr><br />
<abbr class="longitude" title="23.726580"></abbr><br />
<abbr class="georef" title="WGS84"></abbr><br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="geo">The Parthenon was ruined by a Venetian cannonball in <abbr class="dtstamp" title="1687">1687</abbr><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.726580"></abbr></span>''<br />
<br />
The same in compact form:<br />
<pre><nowiki><br />
<span class="geo" title="37.971508;23.72658;;1687;WGS84"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
<br />
====Example 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="geo" title="37.971508;23.72658;;1687;WGS84">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="geo" title="37.971508;23.72658;;1687;WGS84">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Example 4====<br />
Minimal HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="georef" content="WGS84"/><br />
</head><br />
<body><br />
<div class="geo" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Example 5====<br />
A fictitious Mars reference system, using Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="geo" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="geo" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
===Implementation example===<br />
A page with the above examples and a minimal javascript helper, opening a Google map in a separate window, using the number of significant digits as a guide for the zoom:<br />
<br />
Only for Firefox at the moment:<br />
<br />
[http://microformats.telemetry.gr Extended geo format examples]<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
==Further discussion==<br />
Comments and criticism about this page:<br />
<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12753thoughts-on-extending-the-geo-microformat2007-01-19T00:32:42Z<p>DimitriosZachariadis: </p>
<hr />
<div>'''This page and effort is failing to follow the microformats [[process]]. If you are the author of this page, please join the [http://microformats.org/discuss #microformats IRC channel and/or microformats-discuss mailing list] so that the community can help walk you through the process.''' - Tantek<br />
<br />
==A proposal for amendment of the geo microformat==<br />
<br />
<div style="width:800px;"><br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction. </div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an ammendment to the draft geo microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. With this in mind, a number of issues regarding time and the geo microformat reference system are presented for discussion.<br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an issue if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the problems that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS84, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption needs to be made about time, since the human reader will read the year written in the text.<br />
<br />
===Time===<br />
It is noticeable, that most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago, or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, and most probably a death. A vast amount of location information used by people on a daily basis on the web, is in fact an aggregation of events; stories, news and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
It is evident that the inclusion of a time dimension in the geo markup moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events. This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in texts are quite useless without a map. Humans use names to identify places, not numbers. The reason geographic coordinates exist in text, is merely to help humans manually identify places on maps. If things can be done electronically, then numbers don't seem to matter a lot any more.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed. Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could better "understand" the data based on nothing more but the information provided by the geo microformat.<br />
<br />
Dealing with time in multiple reference systems is not an easy. It might not be necessary for humans in their daily life, but it is important when when information on a global, or universal basis is involved. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to use a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
For a microformat to be able to convey accurate information, well defined and known reference systems should be identified together with the data. Transformations among the various reference systems can make content referenced in one system understandable and usefull on another.<br />
<br />
===Other celestial bodies===<br />
The amended geo microformat can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' using [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], or [[geo-extension-strawman]] reveals that reference systems are in place for all celestial bodies that man made spacecrafts have visited, and probably for a lot more than those.<br />
<br />
==Proposed specification amendments==<br />
===Values===<br />
The value of an amended geo location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, mandatory if not defined globally<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If ambiguities arise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''.<br />
<br />
<br />
===Default Reference System===<br />
The default reference system for the geo microformat is WGS84 and the Gregorian calendar.<br />
<br />
The proposed time dimension is to be expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
An interesting provision of the ISO-8601 time format is that it allows time durations to be defined in a consistant manner.<br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="geo.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, '''0.0'''<br />
''t'': time, no default<br />
''u'': reference system, '''WGS84'''<br />
<br />
The default reference system for an (X)HTML page should be set by using meta data properties, if the geo data tuple defines no reference system.<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping geo values compact. By adding the '''geo.reference''' metadata property, a transition to the amended geo microformat would require no further change to the markup.<br />
<br />
===Reference systems===<br />
Other reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
...more<br />
<br />
==Examples==<br />
====Example 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
<abbr class="geo" title="37.971508;23.72658;;1687"></abbr><br />
</nowiki></pre><br />
<br />
====Example 2====<br />
Hidden 4d coordinates, free text content<br />
<pre><nowiki><br />
<span class="geo" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="geo" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Example 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="geo" title="37.971508;23.72658;;1687;WGS84">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="geo" title="37.971508;23.72658;;1687;WGS84">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Example 4====<br />
Minimal HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="geo.reference" content="WGS84"/><br />
</head><br />
<body><br />
<div class="geo" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Example 5====<br />
A fictitious Mars reference system, using Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="geo" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="geo" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appearing here and a map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
==Further discussion==<br />
Comments and criticism about this proposal:<br />
<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12652thoughts-on-extending-the-geo-microformat2007-01-19T00:15:18Z<p>DimitriosZachariadis: /* Default Reference System */</p>
<hr />
<div>'''This page and effort is failing to follow the microformats [[process]]. If you are the author of this page, please join the [http://microformats.org/discuss #microformats IRC channel and/or microformats-discuss mailing list] so that the community can help walk you through the process.''' - Tantek<br />
<br />
==A proposal for amendment of the geo microformat==<br />
<br />
<div style="width:800px;"><br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction. </div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an ammendment to the draft geo microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. With this in mind, a number of issues regarding time and the geo microformat reference system are presented for discussion.<br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an issue if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the problems that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS84, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption needs to be made about time, since the human reader will read the year written in the text.<br />
<br />
===Time===<br />
It is noticeable, that most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago, or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, and most probably a death. A vast amount of location information used by people on a daily basis on the web, is in fact an aggregation of events; stories, news and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
It is evident that the inclusion of a time dimension in the geo markup moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events. This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in texts are quite useless without a map. Humans use names to identify places, not numbers. The reason geographic coordinates exist in text, is merely to help humans manually identify places on maps. If things can be done electronically, then numbers don't seem to matter a lot any more.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed. Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could better "understand" the data based on nothing more but the information provided by the geo microformat.<br />
<br />
Dealing with time in multiple reference systems is not an easy. It might not be necessary for humans in their daily life, but it is important when when information on a global, or universal basis is involved. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to use a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
For a microformat to be able to convey accurate information, well defined and known reference systems should be identified together with the data. Transformations among the various reference systems can make content referenced in one system understandable and usefull on another.<br />
<br />
===Other celestial bodies===<br />
The amended geo microformat can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' using [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], or [[geo-extension-strawman]] reveals that reference systems are in place for all celestial bodies that man made spacecrafts have visited, and probably for a lot more than those.<br />
<br />
==Proposed specification amendments==<br />
===Values===<br />
The value of an amended geo location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, mandatory if not defined globally<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If ambiguities arise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''<br />
<br />
===Default Reference System===<br />
The default reference system for the geo microformat is WGS84 and the Gregorian calendar. It is proposed that a geo reference system be explicitly provided with the data, either as a global setting at the begining of an (X)HTML page or with each geo coordinate tuple.<br />
<br />
The proposed time dimension is to be expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
An interesting provision of the ISO-8601 time format is that it allows time durations to be defined in a consistant manner.<br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="geo.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''u'': reference system, no default<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, defaults to '''0.0'''<br />
''t'': time, no default<br />
<br />
The default reference system for an (X)HTML page MUST be set by using meta data properties, if the geo data defines no reference system<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping geo values compact. By adding the '''geo.reference''' metadata property, a transition to the amended geo microformat would require no further change to the markup.<br />
<br />
===Reference systems===<br />
Other reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
...more<br />
<br />
==Examples==<br />
====Example 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
<abbr class="geo" title="37.971508;23.72658;;1687"></abbr><br />
</nowiki></pre><br />
<br />
====Example 2====<br />
Hidden 4d coordinates, free text content<br />
<pre><nowiki><br />
<span class="geo" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="geo" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Example 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="geo" title="37.971508;23.72658;;1687;WGS84">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="geo" title="37.971508;23.72658;;1687;WGS84">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Example 4====<br />
Minimal HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="geo.reference" content="WGS84"/><br />
</head><br />
<body><br />
<div class="geo" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Example 5====<br />
A fictitious Mars reference system, using Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="geo" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="geo" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appearing here and a map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
==Further discussion==<br />
Comments and criticism about this proposal:<br />
<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=4d&diff=326844d2007-01-18T21:20:20Z<p>DimitriosZachariadis: 4d moved to A proposal for amendment of the geo microformat</p>
<hr />
<div>#REDIRECT [[A proposal for amendment of the geo microformat]]<br />
</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12651thoughts-on-extending-the-geo-microformat2007-01-18T21:17:53Z<p>DimitriosZachariadis: </p>
<hr />
<div>'''This page and effort is failing to follow the microformats [[process]]. If you are the author of this page, please join the [http://microformats.org/discuss #microformats IRC channel and/or microformats-discuss mailing list] so that the community can help walk you through the process.''' - Tantek<br />
<br />
==A proposal for amendment of the geo microformat==<br />
<br />
<div style="width:800px;"><br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction. </div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an ammendment to the draft geo microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. With this in mind, a number of issues regarding time and the geo microformat reference system are presented for discussion.<br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an issue if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the problems that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS84, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption needs to be made about time, since the human reader will read the year written in the text.<br />
<br />
===Time===<br />
It is noticeable, that most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago, or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, and most probably a death. A vast amount of location information used by people on a daily basis on the web, is in fact an aggregation of events; stories, news and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
It is evident that the inclusion of a time dimension in the geo markup moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events. This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in texts are quite useless without a map. Humans use names to identify places, not numbers. The reason geographic coordinates exist in text, is merely to help humans manually identify places on maps. If things can be done electronically, then numbers don't seem to matter a lot any more.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed. Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could better "understand" the data based on nothing more but the information provided by the geo microformat.<br />
<br />
Dealing with time in multiple reference systems is not an easy. It might not be necessary for humans in their daily life, but it is important when when information on a global, or universal basis is involved. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to use a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
For a microformat to be able to convey accurate information, well defined and known reference systems should be identified together with the data. Transformations among the various reference systems can make content referenced in one system understandable and usefull on another.<br />
<br />
===Other celestial bodies===<br />
The amended geo microformat can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' using [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], or [[geo-extension-strawman]] reveals that reference systems are in place for all celestial bodies that man made spacecrafts have visited, and probably for a lot more than those.<br />
<br />
==Proposed specification amendments==<br />
===Values===<br />
The value of an amended geo location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, mandatory if not defined globally<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If ambiguities arise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''<br />
<br />
===Default Reference System===<br />
The default reference system is WGS84 and the Gregorian calendar.<br />
<br />
The time dimension is expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
An interesting provision of the ISO-8601 time format is that it allows time durations to be defined in a consistant manner. <br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="geo.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''u'': reference system, no default<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, defaults to '''0.0'''<br />
''t'': time, no default<br />
<br />
The default reference system for an (X)HTML page MUST be set by using meta data properties, if the geo data defines no reference system<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping geo values compact. By adding the '''geo.reference''' metadata property, a transition to the amended geo microformat would require no further change to the markup.<br />
<br />
===Reference systems===<br />
Other reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
...more<br />
<br />
==Examples==<br />
====Example 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
<abbr class="geo" title="37.971508;23.72658;;1687"></abbr><br />
</nowiki></pre><br />
<br />
====Example 2====<br />
Hidden 4d coordinates, free text content<br />
<pre><nowiki><br />
<span class="geo" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="geo" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Example 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="geo" title="37.971508;23.72658;;1687;WGS84">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="geo" title="37.971508;23.72658;;1687;WGS84">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Example 4====<br />
Minimal HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="geo.reference" content="WGS84"/><br />
</head><br />
<body><br />
<div class="geo" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Example 5====<br />
A fictitious Mars reference system, using Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="geo" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="geo" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appearing here and a map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
==Further discussion==<br />
Comments and criticism about this proposal:<br />
<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=invalidated&diff=32683invalidated2007-01-18T19:49:39Z<p>DimitriosZachariadis: </p>
<hr />
<div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=4d_brainstorming&diff=326894d brainstorming2007-01-18T19:49:02Z<p>DimitriosZachariadis: 4d brainstorming moved to invalidated</p>
<hr />
<div>#REDIRECT [[invalidated]]<br />
</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12629thoughts-on-extending-the-geo-microformat2007-01-18T15:14:59Z<p>DimitriosZachariadis: </p>
<hr />
<div>==4d: A geo microformat alternative proposal==<br />
<br />
<div style="width:800px;"><br />
<br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction</div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an alternative for the draft '''geo''' microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and used without problems. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues at hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in one single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the '''4d''' microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' and displayed on [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
==Specification==<br />
It is proposed that the '''4d''' microformat be formed as follows:<br />
<br />
===Root Class Name===<br />
The root class name for a '''4d''' location/event is ''4d''<br />
<br />
===Property List===<br />
The '''4d''' microformat has the following no properties.<br />
<br />
===Value===<br />
The value of a '''4d''' location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, optional<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If abiguities arrise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''<br />
<br />
===Default Reference System===<br />
The default reference system is WGS84 and the Gregorian calendar.<br />
<br />
The time dimension is expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="4d.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''u'': '''WGS84'''<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, defaults to '''0.0'''<br />
''t'': time, no default<br />
<br />
The default reference system for an (X)HTML page can be set by using meta data properties.<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping '''4d''' values compact. By adding the '''4d''' metadata element, a conversion from the '''geo''' microformat to the '''4d''' would only require the change of the root class, from ''geo'' to ''4d''.<br />
<br />
===Reference systems===<br />
Indicative reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
<br />
==Examples==<br />
The markup used in the discussion, transferred in the '''4d''' microformat:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="4d" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
====Example 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
<abbr class="4d" title="37.971508;23.72658;;1687"></abbr><br />
</nowiki></pre><br />
<br />
====Example 2====<br />
Hidden 4d coordinates, free text content<br />
<pre><nowiki><br />
<span class="4d" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="4d" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Example 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Example 4====<br />
Minimum HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="4d.reference" content="WGS86"/><br />
</head><br />
<body><br />
<div class="4d" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Example 5====<br />
A fictitious Mars reference system, using actual Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="4d" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="4d" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appering here and a small map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
==Further discussion==<br />
Pages for discussing this proposal:<br />
<br />
* [[4d brainstorming]]<br />
* [[4d implementation notes]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=User_talk:DimitriosZachariadis&diff=32687User talk:DimitriosZachariadis2007-01-18T14:11:16Z<p>DimitriosZachariadis: </p>
<hr />
<div>I guess this is a page for discussing the 4d microformat proposal, but I'm not sure. Anyway, if somebody arrives here, comments and criticism is welcome!</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=User_talk:DimitriosZachariadis&diff=12625User talk:DimitriosZachariadis2007-01-18T14:09:34Z<p>DimitriosZachariadis: </p>
<hr />
<div>I guess this is a page for discussing the 4d microformat proposal.</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12627thoughts-on-extending-the-geo-microformat2007-01-18T14:07:06Z<p>DimitriosZachariadis: </p>
<hr />
<div>==4d: A geo microformat alternative proposal==<br />
<br />
<div style="width:800px;"><br />
<br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction</div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an alternative for the draft '''geo''' microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and used without problems. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues at hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in one single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the '''4d''' microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' and displayed on [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
==Specification==<br />
It is proposed that the '''4d''' microformat be formed as follows:<br />
<br />
===Root Class Name===<br />
The root class name for a '''4d''' location/event is ''4d''<br />
<br />
===Property List===<br />
The '''4d''' microformat has the following no properties.<br />
<br />
===Value===<br />
The value of a '''4d''' location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, optional<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If abiguities arrise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''<br />
<br />
===Default Reference System===<br />
The default reference system is WGS84 and the Gregorian calendar.<br />
<br />
The time dimension is expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="4d.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''u'': '''WGS84'''<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, defaults to '''0.0'''<br />
''t'': time, no default<br />
<br />
The default reference system for an (X)HTML page can be set by using meta data properties.<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping '''4d''' values compact. By adding the '''4d''' metadata element, a conversion from the '''geo''' microformat to the '''4d''' one would only require the change of the root class, from ''geo'' to ''4d''.<br />
<br />
===Reference systems===<br />
Indicative reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
<br />
==Examples==<br />
The markup used in the discussion, transferred in the '''4d''' microformat:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="4d" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
====Example 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</nowiki></pre><br />
<br />
====Example 2====<br />
Hidden 4d coordinates, free content<br />
<pre><nowiki><br />
<span class="4d" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="4d" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Example 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Example 4====<br />
Minimum HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="4d.reference" content="WGS86"/><br />
</head><br />
<body><br />
<div class="4d" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Example 5====<br />
A ficticius Mars reference system, using actual Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="4d" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="4d" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appering here and a small map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
==Further discussion==<br />
Pages for discussing this proposal:<br />
<br />
* [[4d brainstorming]]<br />
* [[4d implementation notes]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12624thoughts-on-extending-the-geo-microformat2007-01-18T14:05:32Z<p>DimitriosZachariadis: </p>
<hr />
<div>==4d: A geo microformat alternative proposal==<br />
<br />
<div style="width:800px;"><br />
<br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction</div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an alternative for the draft '''geo''' microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and used without problems. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues at hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in one single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the '''4d''' microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' and displayed on [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
==Specification==<br />
It is proposed that the '''4d''' microformat be formed as follows:<br />
<br />
===Root Class Name===<br />
The root class name for a '''4d''' location/event is ''4d''<br />
<br />
===Property List===<br />
The '''4d''' microformat has the following no properties.<br />
<br />
===Value===<br />
The value of a '''4d''' location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, optional<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If abiguities arrise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''<br />
<br />
===Default Reference System===<br />
The default reference system is WGS84 and the Gregorian calendar.<br />
<br />
The time dimension is expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="4d.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''u'': '''WGS84'''<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, defaults to '''0.0'''<br />
''t'': time, no default<br />
<br />
The default reference system for an (X)HTML page can be set by using meta data properties.<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping '''4d''' values compact. By adding the '''4d''' metadata element, a conversion from the '''geo''' microformat to the '''4d''' one would only require the change of the root class, from ''geo'' to ''4d''.<br />
<br />
===Reference systems===<br />
Indicative reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
<br />
==Examples==<br />
The markup used in the discussion, transferred in the '''4d''' microformat:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="4d" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
====Usage 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</nowiki></pre><br />
<br />
====Usage 2====<br />
Hidden 4d coordinates, free content<br />
<pre><nowiki><br />
<span class="4d" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="4d" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Usage 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Usage 4====<br />
Minimum HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="4d.reference" content="WGS86"/><br />
</head><br />
<body><br />
<div class="4d" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
====Usage 5====<br />
A ficticius Mars reference system, using actual Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="4d" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="4d" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appering here and a small map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
==Further discussion==<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
* [[4d implementation notes]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12623thoughts-on-extending-the-geo-microformat2007-01-18T14:03:57Z<p>DimitriosZachariadis: </p>
<hr />
<div>==4d: A geo microformat alternative proposal==<br />
<br />
<div style="width:800px;"><br />
<br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<br />
; Editor/Author: [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)<br />
<br />
<div style="color:red;">Page under construction</div><br />
__toc__<br />
<br />
===Abstract===<br />
A compact microformat for defining locations and events is proposed, as an alternative for the draft '''geo''' microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and used without problems. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues at hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Default values and ambiguities===<br />
<br />
Disambiguation of the values used for tagging is an important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in one single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the '''4d''' microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help in getting a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map] <br />
<span class="geo"><br />
<abbr class="latitude" title="51.476864"></abbr><br />
<abbr class="longitude" title="-0.000518"></abbr><br />
</span><br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Mars related content can be readily ''microformatted'' and displayed on [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
==Specification==<br />
It is proposed that the '''4d''' microformat be formed as follows:<br />
<br />
===Root Class Name===<br />
The root class name for a '''4d''' location/event is ''4d''<br />
<br />
===Property List===<br />
The '''4d''' microformat has the following no properties.<br />
<br />
===Value===<br />
The value of a '''4d''' location/event resides in the ''title'' attribute of an (X)HTML tag as a semicolon separated 5-tuple:<br />
''v1;v2;z;t;u'' where:<br />
<br />
''v1'' is either latitude or x, depending on ''u'', mandatory<br />
''v2'' is either longitude or y, depending on ''u'', mandatory<br />
''z'' is the altitude, optional<br />
''t'' is the time, optional<br />
''u'' is the reference system code, optional<br />
<br />
Dimensions ''z'', ''t'', and ''u'' can be omitted. If abiguities arrise from such an omition, e.g. omiting the ''z'' and ''t'' dimensions but defining the ''u'' dimension, then the relevant field values must be left empty, e.g.: ''v1;v2;;;u''<br />
<br />
===Default Reference System===<br />
The default reference system is WGS84 and the Gregorian calendar.<br />
<br />
The time dimension is expressed in the ISO-8601 format ("YYYY-MM-DDThh:mm:ss.ssZ"), in any of its abbreviations and forms. [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] and [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
<br />
===Meta data===<br />
The default reference system may be set, using the ''name'' and ''content'' attributes of the ''meta'' (X)HTML element, as follows:<br />
<br />
<meta name="4d.reference" content="''reference-system''"/><br />
<br />
===Default coordinate values===<br />
When a dimension is omitted, the following default values are implied:<br />
<br />
''u'': '''WGS84'''<br />
''v1'': latitude, expressed in decimal degrees, no default<br />
''v2'': longitude, expressed in decimal degrees, no default<br />
''z'': altitude, expressed in meters, defaults to '''0.0'''<br />
''t'': time, no default<br />
<br />
The default reference system for an (X)HTML page can be set by using meta data properties.<br />
<br />
<span style="color:#080;font-weight:bold;">It is strongly recommended that web pages include a meta data element that defines the default reference system, in their HTML head section</span>. The inclusion of the meta data element ensures the validity of the 4d data for as long as the page exists, while keeping '''4d''' values compact. By adding the '''4d''' metadata element, a conversion from the '''geo''' microformat to the '''4d''' one would only require the change of the root class, from ''geo'' to ''4d''.<br />
<br />
===Reference systems===<br />
Indicative reference systems include:<br />
* UTM:zone<br />
** ''v1'' is ''x'', expressed in meters<br />
** ''v2'' is ''y'', expressed in meters<br />
** ''t'' is expressed in ISO-8601<br />
<br />
==Examples==<br />
The markup used in the discussion, transferred in the '''4d''' microformat:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="4d" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
====Usage 1====<br />
Hidden 4d coordinates, no content<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658"></abbr><br />
</nowiki></pre><br />
<br />
====Usage 2====<br />
Hidden 4d coordinates, free content<br />
<pre><nowiki><br />
<span class="4d" title="37.971508;23.72658;;1687"><br />
The Parthenon was ruined by a Venetian cannonball in 1687<br />
</span><br />
</nowiki></pre><br />
may be rendered as:<br />
<br />
''<span class="4d" title="37.971508;23.72658;;1687">The Parthenon was ruined by a Venetian cannonball in 1687</span>''<br />
<br />
====Usage 3====<br />
Visible 4d coordinates<br />
<pre><nowiki><br />
<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr><br />
</nowiki></pre><br />
<br />
may be rendered as:<br />
<br />
''<abbr class="4d" title="37.971508;23.72658;;1687">N 37° 58' 17.43, E 23° 43' 35.69</abbr>''<br />
<br />
====Usage 4====<br />
Minimum HTML page:<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" <br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html><br />
<head><br />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><br />
<meta name="4d.reference" content="WGS86"/><br />
</head><br />
<body><br />
<div class="4d" title="51.476864;-0.000518"><br />
The Greenwich Observatory<br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
===Usage 5===<br />
A ficticius Mars reference system, using actual Mars coordinates from Google Mars:<br />
<pre><nowiki><br />
<span class="4d" title="18.302380;-133.472900;;;MARS:J2000"><br />
Olympus Mons, Mars: The highest mountain in the solar system.<br />
</span><br />
</nowiki></pre><br />
<br />
rendered as:<br />
<br />
''<span class="4d" title="18.302380;-133.472900;;;MARS:J2000">Olympus Mons, Mars: The highest mountain in the solar system.</span>''<br />
<br />
<br />
====Real world example====<br />
[http:// A crafted page with the examples appering here and a small map demonstration]<br />
<br />
==Notes==<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
# [http://www.w3.org/TR/NOTE-datetime W3C, Date and Time Formats] <br />
# [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia, ISO-8601]<br />
==Further discussion==<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
* [[4d implementation notes]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Main_Page&diff=29397Main Page2007-01-18T09:06:46Z<p>DimitriosZachariadis: </p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.<br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]] <br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])<br />
* Does somebody want to see a Dutch translation???</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Main_Page&diff=29396Main Page2007-01-18T01:27:12Z<p>DimitriosZachariadis: </p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.<br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
*4d [[4d|4d: A geo microformat replacement proposal]] {{NewMarker}}<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]] <br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])<br />
* Does somebody want to see a Dutch translation???</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12622thoughts-on-extending-the-geo-microformat2007-01-18T01:24:35Z<p>DimitriosZachariadis: </p>
<hr />
<div><h2>4d: A geo microformat replacement proposal</h2><br />
<div style="font-size:small;color:#666;margin-top:-1em;">A wiki white paper by [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)</div><br />
<div style="width:800px;"><br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<div style="color:red;">Page under construction</div><br />
<br />
<h3>Abstract</h3><br />
A compact microformat for defining locations and events is proposed, as a replacement for the draft '''geo''' microformat. A tolerant five part, semicolon separated, spacetime and reference-system value, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
__toc__<br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and adopted by users on a global basis. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues in hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Ambiguities and default values===<br />
<br />
Disambiguation of the values used for tagging is a very important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in a single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the geo microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help get a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map]<br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Moon (Luna) or Mars related content can be readily ''microformatted'' and displayed on [http://moon.google.com/ Google Moon] and [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
===Specification===<br />
<br />
<div style="color:red;">Under construction</div><br />
<br />
===Notes===<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
<br />
===Further discussion===<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Main_Page&diff=29395Main Page2007-01-18T01:15:33Z<p>DimitriosZachariadis: </p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.<br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]] <br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])<br />
* Does somebody want to see a Dutch translation???</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=invalidated&diff=12631invalidated2007-01-18T01:15:06Z<p>DimitriosZachariadis: </p>
<hr />
<div>==4d brainstorming==<br />
<br />
Discussion and criticism about the proposed '''4d''' microformat is very welcome.</div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12611thoughts-on-extending-the-geo-microformat2007-01-18T01:03:58Z<p>DimitriosZachariadis: </p>
<hr />
<div><h2>4d: A compact spacetime microformat proposal</h2><br />
<div style="font-size:small;color:#666;margin-top:-1em;">A wiki white paper by [[User:DimitriosZachariadis|DimitriosZachariadis]] 17:03, 17 Jan 2007 (PST)</div><br />
<div style="width:800px;"><br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<div style="color:red;">Page under construction</div><br />
<br />
<h3>Abstract</h3><br />
A compact microformat for defining locations and events is proposed. A five part, semicolon separated, spacetime value with its reference system, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
__toc__<br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and adopted by users on a global basis. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues in hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Ambiguities and default values===<br />
<br />
Disambiguation of the values used for tagging is a very important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in a single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the geo microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help get a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map]<br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Moon (Luna) or Mars related content can be readily ''microformatted'' and displayed on [http://moon.google.com/ Google Moon] and [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
===Specification===<br />
<br />
<div style="color:red;">Under construction</div><br />
<br />
===Notes===<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
<br />
===Further discussion===<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12609thoughts-on-extending-the-geo-microformat2007-01-18T01:00:28Z<p>DimitriosZachariadis: </p>
<hr />
<div><h2>4d: A compact spacetime microformat proposal</h2><br />
<div style="font-size:small;color:#666;margin-top:-1em;">A wiki white paper by [[User:DimitriosZachariadis|DimitriosZachariadis]]</div><br />
<div style="width:800px;"><br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<div style="color:red;">Page under construction</div><br />
<br />
<h3>Abstract</h3><br />
A compact microformat for defining locations and events is proposed. A five part, semicolon separated, spacetime value with its reference system, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
__toc__<br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and adopted by users on a global basis. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues in hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Ambiguities and default values===<br />
<br />
Disambiguation of the values used for tagging is a very important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most known and used datum ''today'', due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as a single ''lat;long'' entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in a single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the geo microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help get a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map]<br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Moon (Luna) or Mars related content can be readily ''microformatted'' and displayed on [http://moon.google.com/ Google Moon] and [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
===Specification===<br />
<br />
<div style="color:red;">Under construction</div><br />
<br />
===Notes===<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
<br />
===Further discussion===<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12608thoughts-on-extending-the-geo-microformat2007-01-18T00:51:46Z<p>DimitriosZachariadis: /* Introduction */</p>
<hr />
<div><h2>4d: A compact spacetime microformat proposal</h2><br />
<div style="font-size:small;color:#666;margin-top:-1em;">A wiki white paper by [[User:DimitriosZachariadis|DimitriosZachariadis]]</div><br />
<div style="width:800px;"><br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<div style="color:red;">Page under construction</div><br />
<br />
<h3>Abstract</h3><br />
A compact microformat for defining locations and events is proposed. A five part, semicolon separated, spacetime value with its reference system, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
__toc__<br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>'''OCATION and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and adopted by users on a global basis. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues in hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Ambiguities and default values===<br />
<br />
Disambiguation of the values used for tagging is a very important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most used internationally datum due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as one lat;long entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in a single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the geo microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help get a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map]<br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Moon (Luna) or Mars related content can be readily ''microformatted'' and displayed on [http://moon.google.com/ Google Moon] and [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
===Specification===<br />
<br />
<div style="color:red;">Under construction</div><br />
<br />
===Notes===<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
<br />
===Further discussion===<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12607thoughts-on-extending-the-geo-microformat2007-01-18T00:50:29Z<p>DimitriosZachariadis: </p>
<hr />
<div><h2>4d: A compact spacetime microformat proposal</h2><br />
<div style="font-size:small;color:#666;margin-top:-1em;">A wiki white paper by [[User:DimitriosZachariadis|DimitriosZachariadis]]</div><br />
<div style="width:800px;"><br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<div style="color:red;">Page under construction</div><br />
<br />
<h3>Abstract</h3><br />
A compact microformat for defining locations and events is proposed. A five part, semicolon separated, spacetime value with its reference system, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
__toc__<br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
'''<span style="font-size:2em">L</span>ocation''' and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and adopted by users on a global basis. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues in hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Ambiguities and default values===<br />
<br />
Disambiguation of the values used for tagging is a very important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most used internationally datum due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as one lat;long entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in a single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the geo microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help get a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map]<br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Moon (Luna) or Mars related content can be readily ''microformatted'' and displayed on [http://moon.google.com/ Google Moon] and [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
===Specification===<br />
<br />
<div style="color:red;">Under construction</div><br />
<br />
===Notes===<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
<br />
===Further discussion===<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12606thoughts-on-extending-the-geo-microformat2007-01-18T00:42:09Z<p>DimitriosZachariadis: </p>
<hr />
<div><h2>4d: A compact spacetime microformat proposal</h2><br />
<div style="font-size:small;color:#666;margin-top:-1em;">A wiki white paper by [[User:DimitriosZachariadis|DimitriosZachariadis]]</div><br />
<div style="width:800px;"><br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the proposed microformat '''4d'''.<br />
<div style="color:red;">Page under construction</div><br />
<br />
<h3>Abstract</h3><br />
A compact microformat for defining locations and events is proposed. A five part, semicolon separated, spacetime value with its reference system, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
__toc__<br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
Location and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and adopted by users on a global basis. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues in hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Ambiguities and default values===<br />
<br />
Disambiguation of the values used for tagging is a very important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most used internationally datum due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as one lat;long entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in a single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the geo microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help get a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map]<br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Moon (Luna) or Mars related content can be readily ''microformatted'' and displayed on [http://moon.google.com/ Google Moon] and [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
===Specification===<br />
<br />
<div style="color:red;">Under construction</div><br />
<br />
===Notes===<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
<br />
===Further discussion===<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=thoughts-on-extending-the-geo-microformat&diff=12605thoughts-on-extending-the-geo-microformat2007-01-18T00:40:10Z<p>DimitriosZachariadis: </p>
<hr />
<div><h2>A compact spacetime microformat proposal</h2><br />
<div style="font-size:small;color:#666;margin-top:-1em;">A wiki white paper by [[User:DimitriosZachariadis|DimitriosZachariadis]]</div><br />
<div style="width:800px;"><br />
The term ''4d'' stands for ''four dimensions'' and is used interchangeably with ''spacetime'' in this page, as heaving the same meaning. When in bold, it means the microformat '''4d'''.<br />
<div style="color:red;">Page under construction</div><br />
<br />
<h3>Abstract</h3><br />
A compact microformat for defining locations and events is proposed. A five part, semicolon separated, spacetime value with its reference system, is argued to be sufficient to provide accurate information for uniquely identifying a place or an event in a four dimensional universe.<br />
<div>&nbsp;</div><br />
__toc__<br />
<br />
===Introduction===<br />
<br />
<div style="width:400px;"><br />
<br />
''Spacetimes are the arenas in which all physical events take place — for example, the motion of planets around the Sun may be described in a particular type of spacetime, or the motion of light around a rotating star may be described in another type of spacetime. The basic elements of spacetime are events. In any given spacetime, an event is a '''unique position''' at a '''unique time'''. Examples of events include the explosion of a star or the single beat of a drum.''[http://en.wikipedia.org/wiki/Timespace Spacetime, Wikipedia] (annotation by the author)<br />
</div><br />
<div>&nbsp;</div><br />
<br />
Location and geo referencing microformats proposed on this site, namely [[geo]], [[luna]] and [[mars]] have at present (Jan 2007) a status of draft. Dealing with the issue of geo tagging requires a consensus on the issues of importance, if the microformat is to be successful and adopted by users on a global basis. To that extend, a proposal for a new microformat might not be superfluous, if it can present and offer for discussion some of the issues in hand. With that ambition, the '''4d''' microformat is presented and discussed herein.<br />
<br />
===Brief discussion===<br />
<br />
Most of the location related information, whether about the Earth or another celestial body, have a time related aspect attached; historical places and events, geographical features, but also street names and addresses are tightly related to an act or an observation made at some point in time; addresses used today may have not been in use a century ago (assuming the place identified by the coordinates did exist), or may well change to something different tomorrow. Landmarks existing for centuries have an age, which means they have a birthday, but they may also one day disappear. <br />
<br />
A vast amount of information used by people on a daily basis in the web is in fact an aggregation of events; stories and descriptions are most of the time nothing more than annotations of events. As such, most of this information can be accurately tagged, stored and used for as long as it exists, if its spacetime dimensions are known. <br />
<br />
===Ambiguities and default values===<br />
<br />
Disambiguation of the values used for tagging is a very important issue, if the data tagged are to be valid, accurate and and useful outside the assumptions made at the time of their creation.<br />
<br />
Omitting dimensions from a 4d coordinate system introduces assumptions about their default values. To demonstrate the issues that need to be dealt with, the following example of a markup, tagged with the geo microformat, might prove useful:<br />
<br />
<pre><nowiki><br />
In 1687, a Turkish ammunition dump <br />
<br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
<abbr class="longitude" title="23.72658"></abbr><br />
</a> <br />
<br />
was ignited by a Venetian cannonball. The resulting explosion severely damaged <br />
the Parthenon and its sculptures.<br />
</nowiki></pre><br />
<br />
which may be rendered as:<br />
<br />
''In 1687, a Turkish ammunition dump [http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658&spn=0.002584,0.006083&t=k&om=1&iwloc=addr inside the building]'' <span class="geo"><abbr class="latitude" title="37.971508"></abbr><abbr class="longitude" title="23.72658"></abbr></span><br />
''was ignited by a Venetian cannonball. The resulting explosion severely damaged the Parthenon and its sculptures.'' [http://en.wikipedia.org/wiki/Parthenon Wikipedia, The Parthenon]<br />
<br />
In the case of the markup above, a human reader would ''assume'' that the coordinates involved in the code have been taken using WGS86, the most used internationally datum due to its global validity and the proliferation of the GPS receivers. The ambiguity of altitude leads to an assumption of a default value of 0, which is acceptable for 2D cartography. No assumption can be made about time.<br />
<br />
===Verbosity===<br />
<br />
If the geo portion of the above markup is reduced to:<br />
<pre><nowiki><br />
<a class="geo" href="http://maps.google.com/maps?q=37.971508,23.72658&ie=UTF8&z=18&ll=37.971508,23.72658<br />
&spn=0.002584,0.006083&t=k&om=1&iwloc=addr"><br />
inside the building<br />
<abbr class="latitude" title="37.971508"></abbr>, <br />
</a> <br />
</nowiki></pre><br />
<br />
the markup becomes useless for identifying locations, since it no more represents a location (but rather a geometric ''locus''). If this is the case, then it seems that there is no point in having latitude and longitude defined by separate tags; indeed, the meaning of a coordinate is that it is an ordered list of numbers, or a tuple. [http://en.wikipedia.org/wiki/Coordinates Wikipedia, Coordinates]. RFC2426[2] also specifies the GEO type as one lat;long entity.<br />
<br />
It could be argued that having a simpler, albeit verbose, format, helps content formating tools like XSLT processors, locate data easier. However, ''Microformats are a way of adding simple markup to human-readable data items such as events, contact details or locations, on web pages, so that the information in them can be extracted by software and indexed, searched for, saved, cross-referenced or combined''. Microformats are not meant to help format content for humans, but to help machines gather information in a Semantic Web. On the other hand, a machine can split the data of a '''4d''' tag in a single line of code.<br />
<br />
===Time===<br />
As argued above, the inclusion of a time dimension in geo markup can add significantly to the semantics of a piece of geo information, as it moves the focus of geo tagging from the realm of two dimensional cartography to the realm of events.<br />
<br />
This should come as no surprise: events are about stories; cartography is about navigation. People are interested in stories, news and events; few people can successfully navigate using a map and even fewer are interested in navigation and cartography as a science or art. Geographic coordinates shown in the text are quite useless without a map, and are even more useless if an electronic map is available for use. Humans use names to identify places, not numbers. The reason there is a need for showing geographic coordinates in text, is mostly to help humans manually identify places on maps. If this can be done electronically, then numbers don't seem to matter.<br />
<br />
A human visiting the page with the markup above (which was chosen for the length of the time dimension and the connotations involved), will have a chance to read the text (and the year of the event, which however is un-tagged), click at the link and get a Google Map centered at the Acropolis and the Parthenon. Semantic connotations for humans enhance their understanding of information presented to them.[1] However, a machine seeking information in the Semantic Web, will have no way of finding out if it is the 5th century BC Athenian state or the contemporary Greek state that this particular piece of information is referring to. Semantic information about that particular markup that could otherwise be cataloged by the machine, will pass unnoticed.<br />
<br />
Had this geo markup been amended with a time dimension, a robot crawling this and other similar pages could create a list of historical events, based on nothing else but the information provided by the geo microformat.<br />
<br />
Humans have learned to deal with time efficiently, in their locality, through the use of clocks. Wrist watches remind people of upcoming events in their lives. An event in a remote place is more difficult to conceive, but not entirely impossible. Although it involves a simple addition or subtraction, only people traveling a lot can do it with ease. <br />
<br />
Counting time in multiple reference systems is however a difficult task. It might not be necessary for humans in their daily life, but it is important when dealing with information on a global, or universal basis. Different cultures, use different reference systems to tell the time. [http://en.wikipedia.org/wiki/Islamic_calendar Islamic calendar] These need to be taken into account in a Semantic Web. <br />
<br />
In a similar manner, trying to addapt to a Martian reference system, while living on Earth, involves more than a simple addition/subtraction of a few hours. A Martian day, is not of the same duration as a Terran day, and the same is true for the duration of the seasons; a number of connotations, that would otherwise help get a gut feeling, fail helplessly.<br />
<br />
===The reference system===<br />
It should be noted that the assumption about the datum used in expressing the lat-long coordinates mentioned above, is not a trivial one: Only 20 years ago, the same coordinates would possibly point hundreds of meters away from the Parthenon, since the reference system used at that time was different than WGS84. Furthermore, assuming WGS84 was the datum for the markup above, these coordinates may not be accurate 10 years from today, when the WGS84 reference system will have been revised once again.<br />
<br />
A markable indication of the importance of the reference system, when expressing geo coordinates, is the fact that the Greenwich Observatory, which was by definition the origin for the longitude coordinate for more than a century, lies now about 102.5m West of the WGS84 0.0 meridian, at N 51° 28' 36.71, W 0° 0' 5.18", (in WGS84 datum) according to [http://en.wikipedia.org/wiki/Prime_Meridian Wikipedia, Prime_Meridian]. Interestingly, Google maps and Wikipedia do not seem to agree on these coordinates [http://maps.google.com/maps?f=q&hl=en&q=51.476864,-0.000518&ie=UTF8&z=19&ll=51.476861,-0.000515&spn=0.001067,0.002175&t=h&om=1&iwloc=addr map]<br />
<br />
It should be clear that, for a microformat to be able to convey accurate information, well defined and known reference systems should be used. By performing transformations among the various reference systems, the content referenced in one system can be understandable and usefull on another, on a global or universal basis.<br />
<br />
===Name convention===<br />
<br />
Naming a geo microformat '''4d''' helps avoid the problem of the geo-centric (i.e. Earth bound) root of the word '''geo'''; '''4d''' can be easily used on any celestial body for which a reference system, even rudimentary, has been defined. To that extend, Moon (Luna) or Mars related content can be readily ''microformatted'' and displayed on [http://moon.google.com/ Google Moon] and [http://www.google.com/mars Google Mars]. Obviously, matters regarding reference systems of other celestial bodies require expert knowledge, however, reading the news on NASA's site, e.g. for Titan, [http://www.nasa.gov/mission_pages/cassini/multimedia/pia09111.html Two Sides of Dunes], reveals that reference systems are in place for all celestial bodies visited by a man made spacecraft, and probably for a lot more than those.<br />
<br />
'''4d''' is a rather common acronym; Google yields about 53.9 million hits, while for '''3d''' it yields 310 million hits and for '''geo''' 82.9 million.<br />
<br />
===Specification===<br />
<br />
<div style="color:red;">Under construction</div><br />
<br />
===Notes===<br />
# Umberto Eco, A Theory of Semiotics, 1976<br />
# [http://www.ietf.org/rfc/rfc2426.txt RFC2426]<br />
<br />
===Further discussion===<br />
Pages for discussing of this proposal:<br />
<br />
* [[4d brainstorming]]<br />
</div></div>DimitriosZachariadishttp://microformats.org/wiki/index.php?title=Main_Page&diff=29394Main Page2007-01-17T22:21:30Z<p>DimitriosZachariadis: /* Drafts */</p>
<hr />
<div>__NOTOC__<br />
<h1>Microformats Wiki</h1><br />
<br />
'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.<br />
<br />
Please read [[how-to-play]] before making any edits.<br />
<br />
Please read [[process]] before proposing any new microformats.<br />
<br />
__TOC__<br />
<br />
==Getting Started==<br />
<br />
[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]? <br />
<br />
The [http://microformats.org/about/ about page], [http://microformats.org/ latest news], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information. Our [[cheatsheets]] are handy if you need a quick reminder about a particular microformat.<br />
<br />
Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]], and there is a [[glossary]]. <br />
<br />
Want to learn more in person? Check out [[events|microformats events]].<br />
<br />
==Definition==<br />
<br />
One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br />
:simple conventions<br />
:for embedding semantic markup<br />
::for a specific problem domain<br />
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br />
::that normalize existing content usage patterns<br />
::using brief, descriptive class names <br />
::often based on existing interoperable standards<br />
:to enable decentralized development<br />
::of resources, tools, and services<br />
<br />
Simply put: "Microformats are a codification of convention." -- [http://easy-reader.net Aaron Gustafson]<br />
<br />
"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br />
<br />
== How to contribute ==<br />
<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
*Check out our open [[to-do|to do list]] for things to help get done.<br />
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.<br />
*[[advocacy|Advocate]] the use of microformats.<br />
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languages]] to make microformats globally accessible.<br />
<br />
== Specifications ==<br />
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hcalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hcard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[xoxo|XOXO]]<br />
<br />
== Drafts ==<br />
* [[4d|4d]]<br />
* [[adr|adr]]<br />
* [[geo|geo]]<br />
* [[hatom|hAtom]]<br />
* [[hresume|hResume]]<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hreview creator]<br />
* [[rel-directory]]<br />
* [[rel-enclosure]]<br />
* [[rel-home]]<br />
* [[relpayment-research | rel-payment]]<br />
* [[robots-exclusion|Robots Exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
*alternates [[alternates-brainstorming|alternates brainstorming]], [[alternates-examples|alternates examples]]<br />
*[[attention]]<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* citation [[citation|citation effort]], [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], and [[citation-faq|citation FAQ]]<br />
* comment [[comment-problem|comment problem]], [[comment-examples|comment examples]], and [[comments-formats|comment formats]] (Some stuff needs to be extracted from [[comments-formats]])<br />
* [[collection-description|collection description]] {{NewMarker}}<br />
* [[course-catalog]]; [[course-catalog-examples]] {{NewMarker}}<br />
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]] <br />
* directions [[directions-examples|directions examples]] {{NewMarker}}<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (see also [[rel-directory]])<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]], [[distributed-conversation-examples|distributed conversation examples]], and [[distributed-conversation-formats|distributed conversation formats]]<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-formats|genealogy examples]]<br />
* group [[group-brainstorming|group brainstorming]] and [[group-examples|group examples]]<br />
* items [[items-brainstorming|items brainstorming]] and [[items-examples|items examples]<br />
* hash [[hash-examples|hash examples]]<br />
* job listing [[job-listing-examples|job listing examples]] and [[job-listing-brainstorming|job listing brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* [[product|hProduct]] - [[product-brainstorming|hProduct brainstorming]] | [[product-examples|hProduct examples]]<br />
* location [[location-formats|location formats]]. (see also [[adr]] and [[geo]])<br />
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) - see also [[geo-extension-strawman]] a possible implementation {{UpdateMarker}}<br />
* measures and measurement units [[measure]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]]) <br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] {{NewMarker}}<br />
* microsummary [[microsummary-brainstorming|microsummary brainstorming]]<br />
* [[mfo-examples|MFO examples]]<br />
* music [[music-examples|music examples]]<br />
* photo note [[photo-note-examples|photo note examples]]<br />
*[[question-answer]], [[question-answer-brainstorming]]; [[question-answer-examples]] {{NewMarker}}<br />
* recipe [[recipe-examples|recipe examples]], [[recipe-brainstorming]] {{UpdateMarker}}<br />
* rel-product [[rel-product-brainstorming|rel-product brainstorming]]<br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]]<br />
* resume [[resume-brainstorming|resume brainstorming]], and [[resume-formats|resume formats]]<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] (yielded the [[hreview|hReview]] draft)<br />
* search results [[search-results-example|search results example]]<br />
* show [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-brainstorming|brainstorming]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{UpdateMarker}}<br />
* table [[table-examples|examples]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[uid]]<br />
* widget [[widget-examples|widget examples]], and [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]] <br />
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])<br />
<br />
== Examples ==<br />
* [[examples]]<br />
* [[zen-garden]]<br />
<br />
== Tools, Test Cases and Additional Research ==<br />
<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br />
<br />
*[[accessibility]]<br />
*[[faqs-for-rdf]]<br />
*[[icalendar-implementations]]<br />
*[[parsing-microformats]]<br />
*[[selected-test-cases-from-the-web]]<br />
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]<br />
*[[vcard-implementations]], [[vcard-errata]], [[vcard-suggestions]]<br />
*[[why-are-content-standards-hard]]<br />
<br />
== shared work areas ==<br />
* [[buttons]]<br />
* [[icons]] {{NewMarker}}<br />
* [[spread-microformats]] {{NewMarker}}<br />
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.<br />
* [[events]]<br />
* [[to-do]]<br />
* [[user-interface]]<br />
* [[marked-for-deletion]]<br />
* [[microformats-issues]] {{NewMarker}} - issues related to more than one microformat.<br />
<br />
== microformats wiki in other languages ==<br />
<br />
You may read and edit microformats articles in many other languages:<br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}<br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br| Português (Brazilian Portuguese)]] {{NewMarker-pt-br}}<br />
** [[Main_Page-ja|日本語 (Japanese)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-es|Español (Spanish)]]<br />
** [[Main_Page-de|Deutsch (German)]]<br />
<br />
==== microformats translations elsewhere ====<br />
These are off-site pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!<br />
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker-de}}<br />
<br />
=== Start a microformats wiki in another language ===<br />
<br />
Don't see the language you want? Help translate the microformats wiki into another language!<br />
<br />
We're still figuring this out. <br />
<br />
For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.<br />
<br />
You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).<br />
<br />
Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. [http://google.con google] E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].<br />
<br />
==== more languages folks want to see ====<br />
<br />
* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])<br />
* Does somebody want to see a Dutch translation???</div>DimitriosZachariadis