Search results

• put-it-on-the-wiki
  * [[geo-examples-in-wild|geo examples in the wild]]
  6 KB (900 words) - 16:31, 18 July 2020
• validators-fr
  ...hreview-aggregate-fr|hReview-aggregate]], [[hrecipe-fr|hRecipe]], [[geo-fr|geo]]
  6 KB (714 words) - 16:33, 18 July 2020
• h-review
  ...iness or person ([[h-card]]), event ([[h-event]]), place ([[h-adr]] or [[h-geo]]), product ([[h-product]]), recipe ([[h-recipe]]), website, url, or other ...the review was posted from, optionally embed [[h-card]], [[h-adr]], or [[h-geo]]
  11 KB (1,497 words) - 20:22, 5 February 2024
• h-card
  ...de>''' or '''<code>u-geo</code>''', optionally embed an [[h-geo]] {{main|h-geo}} ...cold32.com/about-the-author-and-contact.htm Cold32.com] uses h-card (and h-geo) on its about-the-author-and-contact page
  20 KB (2,929 words) - 23:42, 30 November 2022
• adr-fr
  Merci à tous ceux qui ont participé dans le [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], et tout particulière ...autres sites publient des informations d'adresses. Le [[geo-bof-2005-06-30|geo microformat BOF]] a discuté tout particulièrement de ce sujet et conclu a
  12 KB (1,813 words) - 16:20, 18 July 2020
• hatom-brainstorming
  == geo for georss == *# We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element
  9 KB (1,455 words) - 16:23, 18 July 2020
• parsers-fr
  ...Data::Microformat] est un module CPAN pour parser et créer hCard, adr, and geo. ** classes : [[adr-fr|adr]], [[figure]], [[geo-fr|geo]], [[hatom-fr|hAtom]], [[haudio-fr|hAudio]], [[User:TobyInk/hcalendar-1.1|h
  9 KB (1,256 words) - 16:31, 18 July 2020
• figure
  ** ''subject'' (text | [[hcard|hCard]] | [[geo]] | [[adr]] | [[hcalendar|hcalendar event]])* ..."geo" then the element should be considered to be the [[adr|address]] or [[geo|geographic location]] of the subject of the picture - for example the locat
  12 KB (1,748 words) - 16:22, 18 July 2020
• Main Page-pt-br
  * [[geo|geo]] * location [[location-formats|formatos]]. (ver também [[adr]] e [[geo]])
  11 KB (1,263 words) - 16:20, 18 July 2020
• measure
  ...ke) occurring at a specified time (dtstart/dtend) and location (embedded [[geo]]), by just embedding measured physical quantities in the 'descrition' span
  3 KB (373 words) - 16:28, 18 July 2020
• rfc-2426
  ...e" for "n", "Address" for "adr", "Organization" for "org", "Location" for "geo" (that's really bad)
  3 KB (392 words) - 16:32, 18 July 2020
• vcard-suggestions
  * See also [[geo-extension-nonWGS84]] === 3.4.2 GEO ===
  14 KB (2,056 words) - 16:34, 18 July 2020
• h-entry-fr
  ...ent embarqué dans [[h-card-fr|h-card]], [[h-adr-fr|h-adr]] ou [[h-geo-fr|h-geo]] ** Autrement, utilisez un microformat embarqué [[h-geo-fr|h-geo]] sur une valeur de propriété <code>p-location</code>.
  13 KB (2,030 words) - 16:23, 18 July 2020
• Main Page
  * [[h-geo]] * [[geo|geo]] - latitude &amp; longitude location ([http://en.wikipedia.org/wiki/WGS84
  9 KB (1,182 words) - 18:37, 1 March 2024
• previous-formats
  ** [[ISO6709]] - being considered for [[geo]] (and thus hCard, hCalendar) enhancements
  3 KB (467 words) - 16:31, 18 July 2020
• hlisting-brainstorming
  ** item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business). ** item info. optional. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business).
  9 KB (1,316 words) - 16:26, 18 July 2020
• parsers
  ...pm Data::Microformat] is a CPAN module to parse and create hCard, adr, and geo. ** class: [[adr]], [[figure]], [[geo]], [[hAtom]], [[hAudio]], [[User:TobyInk/hcalendar-1.1|hCalendar]], [[hCard
  11 KB (1,450 words) - 08:44, 14 September 2023
• events-fr
  ...nous pour discuter de tout le buzz récent autour des microformats [[geo-fr|geo]], [[adr-fr|adr]] et [[hcard-fr|hCard]] supportés par [[google-search-fr|
  25 KB (3,420 words) - 16:21, 18 July 2020
• hcard-zh
  * geo (latitude, longitude)
  21 KB (1,481 words) - 16:26, 18 July 2020
• hcard-faq
  === Can a GEO be inferred from an ADR in an hCard === ''Can I automatically add GEO from an address when transforming an hCard to vCard if it is not present?''
  34 KB (5,614 words) - 16:25, 18 July 2020
• hcard-examples
  === GEO parsing === <span class="geo">
  20 KB (3,205 words) - 16:25, 18 July 2020
• hcard-advocacy
  **Could use hCard, Geo, and others **hCard (& Geo) and hReviewRequested by e-mail, 2007-09-21 [[User:AndyMabbett|Andy Mabbett
  23 KB (3,398 words) - 16:24, 18 July 2020
• menu-brainstorming
  ...ty that can be an embedded [[h-adr]]; and p-geo with optionally embedded h-geo. Also, p-product is both intuitive and adaptable. Obviously, a menu normall
  8 KB (1,245 words) - 19:38, 18 December 2020
• search-engines
  ...com/cc Yahoo Creative Commons search]) and hCard, hCalendar, hReview, XFN, geo, rel-tag, adr through [http://developer.yahoo.com/search/boss/ Yahoo Search
  5 KB (686 words) - 07:08, 7 April 2022
• Main Page-ka
  * [[geo|geo]] - latitude &amp; longitude location ([http://en.wikipedia.org/wiki/WGS84
  8 KB (1,041 words) - 16:20, 18 July 2020
• Main Page-fa
  * [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic co
  8 KB (952 words) - 16:17, 18 July 2020
• hcalendar-profile
  <a href="http://microformats.org/wiki/geo">geo record</a>, or combination thereof.
  6 KB (910 words) - 16:24, 18 July 2020
• hcard-ja
  * geo ひとつの hCard は、一つ以上の 'fn'、'n'、'bday'、'tz'、'geo'、'sort-string'、'uid'、'class'、'reｖ' を持つことはありませ
  30 KB (1,940 words) - 16:26, 18 July 2020
• hreview-brainstorming
  * items of <code>type</code> <code>place</code> SHOULD use a nested [[geo]] or [[adr]] or [[hcard|hCard]] as the item itself.
  4 KB (666 words) - 16:27, 18 July 2020
• Main Page-id
  * [[geo|geo]] - untuk menandai [http://en.wikipedia.org/wiki/WGS84 WGS84] koordinat geo
  8 KB (981 words) - 16:20, 18 July 2020
• google-search
  * geo * geo
  12 KB (1,635 words) - 21:37, 26 July 2023
• h-review-aggregate
  ...iness or person ([[h-card]]), event ([[h-event]]), place ([[h-adr]] or [[h-geo]]), product ([[h-product]]), website, url, or other item ([[h-item]]).
  5 KB (700 words) - 21:24, 26 July 2023
• microformats2-brainstorming
  ...class="n-rating"&gt;7.5 out of 1 to 10&lt;/span&gt;</code>). similarly "n-geo" would specify the first number to be the latitude and the second to be the
  10 KB (1,570 words) - 23:41, 14 December 2020
• hcard-supporting-user-profiles-issues
  *** latitude, longitude --&gt; use [[geo]] markup with <code>latitude</code> and <code>longitude</code> subpropertie
  5 KB (687 words) - 16:26, 18 July 2020
• hcard-examples-fr
  === GEO parsing === <span class="geo">
  21 KB (3,281 words) - 16:25, 18 July 2020
• activity-streams
  ...[[blogging-tools|blog]], update their [[picoformats|status]], post their [[geo|location]], or [[photo-info|photos]], sites and tools have emerged to aggre
  5 KB (675 words) - 16:20, 18 July 2020
• hreview-profile
  <a href="http://microformats.org/wiki/geo">geo</a> (for a place), or
  7 KB (1,043 words) - 16:28, 18 July 2020
• books
  ...is a PDF book, part of the O'Reilly Short Cuts series. Covers the ADR and GEO microformats.
  5 KB (705 words) - 16:21, 18 July 2020
• validators
  ...hCard]], [[hCalendar]], [[hReview]], [[hReview-aggregate]], [[hRecipe]], [[geo]]
  5 KB (691 words) - 16:33, 18 July 2020
• hlisting-duplicated-for-discussions
  *** ''item info''. '''required'''. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business). * Item info expanded to take geo or adr for location of the item.
  22 KB (3,153 words) - 16:26, 18 July 2020
• hcalendar
  * geo (latitude, longitude) ...o (latitude and longitude) <code>LOCATION</code> may be represented by a [[geo]].
  20 KB (2,906 words) - 16:24, 18 July 2020
• firefox-extensions
  ...menu item to a page's context menu when you right click on an [[adr]] or [[geo]] microformat (even inside an [[hCard]]).
  5 KB (662 words) - 16:22, 18 July 2020
• hcard-profile
  <dt id="geo">geo</dt>
  8 KB (1,175 words) - 16:26, 18 July 2020
• parsing-brainstorming
  .../code> property you might reasonably expect to find an hCard, and adr or a geo!): ...ere this is beneficial is when parsing hCard, it is useful to save adr and geo from destruction. This enables the <code>fn</code> property to be set on ad
  23 KB (3,753 words) - 16:31, 18 July 2020
• microformats2
  * [[h-geo]] * '''<code>p-geo</code>''' (or '''<code>u-geo</code>''' with a RFC 5870 geo: URL) - new in [[vCard4]] ([[RFC6350]])
  67 KB (9,585 words) - 19:05, 1 March 2024
• user-interface
  *[[geo|Geo]]
  12 KB (1,791 words) - 16:33, 18 July 2020
• test-fixture
  <td class="test">vcard[0].geo.latitude</td> <td class="comment">The geo is a singular value</td>
  9 KB (1,295 words) - 16:33, 18 July 2020
• Main Page-fr
  * [[geo-fr|geo]] - latitude &amp; longitude de l'endroit (coordonnées géographiques [htt
  11 KB (1,418 words) - 16:20, 18 July 2020
• hcard-faq-fr
  === Est-ce que GEO peut être inféré à partir d'un ADR dans une hCard === ''Puis-je automatiquement ajouter GEO à partir d'une adresse au moment de transformer une hCard en vCard s'il n'
  41 KB (6,608 words) - 16:26, 18 July 2020
• events/2010-05-02-microformats-2-0
  * treat "geo" as a nested microformat ...class="n-rating"&gt;7.5 out of 1 to 10&lt;/span&gt;</code>). similarly "n-geo" would specify the first number to be the latitude and the second to be the
  19 KB (2,808 words) - 16:22, 18 July 2020

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)