Search results

• hreview-implementations
  ...and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
  7 KB (1,002 words) - 16:28, 18 July 2020
• hcalendar-pl
  * geo (latitude, longitude) ...o (latitude and longitude) <code>LOCATION</code> may be represented by a [[geo]].
  22 KB (3,192 words) - 16:24, 18 July 2020
• hcalendar-fr
  * geo (latitude, longitude) ...e et longitude) <code>LOCATION</code> PEUT être représenté par un [[geo-fr|geo]].
  24 KB (3,574 words) - 16:24, 18 July 2020
• hlisting-issues
  ...ich should encapsulate all the details like hCard | (fn || url || photo || geo || adr)? Should it be exactly class="item info" OR class="item-info"? This
  7 KB (944 words) - 16:26, 18 July 2020
• microformats2-ro
  * '''<code>p-geo</code>''' (or '''<code>u-geo</code>''' din RFC 5870 geo: URL) - nou in [[vCard4]] ([[RFC6350]]) * '''<code>p-geo</code>''' or '''<code>u-geo</code>''' with a RFC 5870 geo: URL, new in [[vCard4]] ([[RFC6350]])
  71 KB (10,282 words) - 16:30, 18 July 2020
• microformats2-prefixes
  ...'photo') are implied when there are no properties present. Example uses: s-geo and s-adr. This is being considered as a result of [[microformats-2-parsing ...of the examples given here have in-the-wild use cases for literal parsing: Geo's existing documented optimisation of <code>1.233;0.453</code> is applied i
  35 KB (5,273 words) - 15:32, 17 August 2021
• faq
  ===Q. ''What about using new URI schemes instead of class names, e.g. for geo information?''=== Authors aren't publishing links to geo information.
  34 KB (5,453 words) - 05:18, 9 October 2023
• xmdp-brainstorming
  ...ocation lat/long/altitude, however that's more of a composite type (e.g. [[geo]]) that is made of multiple atomic types ...ames (e.g. http://microformats.org/wiki/hcard defines "vcard", "adr", and "geo").
  17 KB (2,780 words) - 16:35, 18 July 2020
• hlisting
  ** ''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.
  21 KB (3,012 words) - 02:14, 12 February 2021
• hcard-examples-zh
  === GEO解析 === <span class="geo">
  19 KB (1,689 words) - 16:25, 18 July 2020
• implementations-fr
  ...tos de Flickr taguées avec geo] sont balisées avec le microformat [[geo-fr|geo]]. * supporte le microformat [[geo-fr|geo]] dans la page POI. exemple : [http://mymap.yam.com/place/point/charleschua
  36 KB (4,789 words) - 16:28, 18 July 2020
• hcard
  * geo Singular properties: 'fn', 'n', 'bday', 'tz', 'geo', 'sort-string', 'uid', 'class', 'rev'. For properties which are singular,
  29 KB (4,290 words) - 23:36, 24 August 2020
• implementations
  ...ttp://flickr.com/map/ Flickr's geo tagged photos] are marked up with the [[geo]] microformat. Unfortunately, as of August 2010, their new page design does * support [[geo]] microformat in the POI page. example: [http://mymap.yam.com/place/point/c
  34 KB (4,524 words) - 19:40, 11 January 2022
• hcard-fr
  * geo Les propriétés singulières : 'fn', 'n', 'bday', 'tz', 'geo', 'sort-string', 'uid', 'class', 'rev'. Pour les propriétés qui sont sing
  32 KB (4,986 words) - 16:26, 18 July 2020
• issues-closed
  ...ocation, or whatever, on a page, then <code>"id=hReview"</code>, <code>id="geo"</code> etc. are semantically valid and appropriate. [[User:AndyMabbett|And
  8 KB (1,152 words) - 16:28, 18 July 2020
• user-interface-fr
  *[[geo-fr|Geo]]
  15 KB (2,122 words) - 16:33, 18 July 2020
• hcard-issues-resolved
  ...minutes-seconds (e.g. [http://en.wikipedia.org/wiki/Birmingham]). Should [[geo]] be extended to allow for this, with parsers making the conversion to digi ...g. Wikipedia as cited), then it should be considered for addition to the [[geo]] property and thus hCard. This may help reduce the number of instances of
  60 KB (9,422 words) - 16:26, 18 July 2020
• microformats2-implied-properties
  ...d_h-geo_work_with_an_implied_name_property|how do instances of h-adr and h-geo work with implied names]]? short answer: (implied) names are useful for lab
  11 KB (1,761 words) - 16:29, 18 July 2020
• hatom-issues
  ====Geo==== ** We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element
  30 KB (4,760 words) - 16:23, 18 July 2020
• h-entry
  ...the entry was posted from, optionally embed [[h-card]], [[h-adr]], or [[h-geo]] ** Otherwise use an embedded [[h-geo]] microformat on a <code>p-location</code> property value.
  33 KB (4,908 words) - 20:53, 24 November 2023
• microformats2-fr
  * '''<code>p-geo</code>''' (ou '''<code>u-geo</code>''' avec un RFC 5870 geo: URL) - nouveau dans [[vCard4]] ([[RFC6350]]) * '''<code>p-geo</code>''' ou '''<code>u-geo</code>''' avec un RFC 5870 geo : URL, nouveau dans [[vCard4]] ([[RFC6350]])
  75 KB (11,559 words) - 16:29, 18 July 2020
• value-class-pattern-ja
  もう一つ例を示します。[[geo]] の座標に場所の名前を追加しています。 <span class="geo">
  34 KB (2,879 words) - 16:34, 18 July 2020
• hreview-examples-in-wild
  ...otels, Shopping, Nightlife and Attractions. There are approximately 20,000 geo-coded venue pages. Example: [http://travel.nytimes.com/travel/guides/north- ...s/places Course Finder] detail pages to publish user comments, ratings and geo. [http://www.golfdigest.com/courses/places/2483 example]
  42 KB (5,896 words) - 16:27, 18 July 2020
• value-class-pattern-fr
  Un autre exemple, ajouter un nom de lieu à des coordonnées [[geo-fr|geo]] : <span class="geo">
  37 KB (6,016 words) - 16:34, 18 July 2020
• hcalendar-examples-in-wild
  ...t] uses hCalendar for upcoming open houses held by real estate agents with geo information. ...al] uses hCards for locations, hCalendar for events and supports the draft Geo format when lat/lng data is provided. See [http://blog.mapquest.com/2008/09
  43 KB (6,323 words) - 16:24, 18 July 2020
• hlisting-fr
  ** item info. '''requis'''. (fn || url || photo || [[geo-fr|geo]] || [[adr-fr|adr]]) | [[hcard-fr|hCard]] (pour les personnes ou les comme * L'info item a été étendue pour prendre geo ou adr pour l'endroit de l'item.
  22 KB (3,321 words) - 16:26, 18 July 2020
• product-examples
  ...p unless fixed for a product to all customers that visit it, regardless of geo.--[[PaulLee|Paul Lee]] 21:57 20 Aug 2008)
  10 KB (1,229 words) - 18:57, 16 March 2021
• hcard-brainstorming
  == geo improvements == ''See [[geo-brainstorming]]''
  49 KB (7,275 words) - 16:25, 18 July 2020
• value-class-pattern
  Another example, adding a place name to a [[geo]] co-ordinate: <span class="geo">
  39 KB (5,876 words) - 03:04, 25 June 2022
• hreview-examples-in-wild-fr
  ...es Course Finder] pour publier les commentaires utilisateurs, notations et geo. [http://www.golfdigest.com/courses/places/2483 exemple] ...s et restaurants à Copenhague au Danemark. Chaque lieu critiqué a aussi un geo (cf [http://www.mitkbh.dk/node.php?node=238 exemple])
  28 KB (4,059 words) - 16:27, 18 July 2020
• hcard-examples-in-wild-fr
  ...31-bb8a-2c55cc29aed4 National Rural Knowledge Exchange] uses an hCard with geo tags when displaying an organisations information ...onic.com/ Deltronic Corporation] of Santa Ana, CA has posted an hCard with geo tags on its [http://www.deltronic.com/contact.shtml Contact] page. Backgro
  82 KB (12,852 words) - 16:25, 18 July 2020
• hcard-issues-closed
  *# We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element ...e. See [[vcard-suggestions#Elevation|vCard suggestions: elevation]], and [[geo-extension-elevation]].
  36 KB (5,726 words) - 16:26, 18 July 2020
• hmedia
  ...//doola.li/ Doolali] Video pages are marked-up using hmedia, together with geo and hcard mark-up. e.g. [http://doola.li/video/4d2328b4bac7b0a4770f0000]
  20 KB (2,820 words) - 16:27, 18 July 2020
• hcard-examples-in-wild
  * [http://starthilfeberlin.de/ Starthilfe Berlin] - uses hCard (and geo, XFN, rel-license, rel-profile) in (Joomla HTML5) '<#footer role="contentin ...es Church House Builder] uses hCard for property development addresses and geo latitude and longitude. See [http://www.charleschurch.com/carmarthenshire_a
  135 KB (20,460 words) - 16:25, 18 July 2020
• faq-fr
  Ils publient du *texte visible* de [[geo-fr|geo]]information. ...ment quelque chose. Si vous les forcez à utiliser à la place un protocole "geo" hypothétique, alors cela interférerait, parce que vous ne pouvez hyperli
  33 KB (5,303 words) - 16:22, 18 July 2020
• hcard-implementations
  ...Info, it geocodes your location and asks for your socialmedia handles and geo app venue or places ID like google place, gowalla, foursquare. You get a vC
  18 KB (2,672 words) - 16:26, 18 July 2020
• hmedia-fr
  ...//doola.li/ Doolali] Video pages are marked-up using hmedia, together with geo and hcard mark-up. e.g. [http://doola.li/video/4d2328b4bac7b0a4770f0000]
  21 KB (3,015 words) - 16:27, 18 July 2020
• hcalendar-brainstorming
  ...tio.com/ where all the events contain locations marked up as hCards with [[geo]] properties as well which then aid in locating the precise locations on a GEO:37.386013;-122.082932
  59 KB (8,988 words) - 16:24, 18 July 2020
• measure-brainstorming
  An example weather forecast using hmeasure, [[adr]], [[geo]] and [[hCalendar]] with the [[include-pattern|include pattern]]: (<span class="geo">50.8730;0.005</span>)
  56 KB (8,114 words) - 21:06, 26 July 2023
• hcalendar-examples-in-wild-fr
  ...al] uses hCards for locations, hCalendar for events and supports the draft Geo format when lat/lng data is provided. See [http://blog.mapquest.com/2008/09 ...less] - embarque des balises hCalendar pour chaque photo, avec un balisage GEO pour les photos de lieux géograhiques significatifs (comme avec [http://ww
  41 KB (6,228 words) - 16:24, 18 July 2020
• to-do
  ...ation on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]] * analyze [[hcard-cheatsheet]], [[adr-cheatsheet]], [[geo-cheatsheet]] for any assertions above and beyond what the specification its
  74 KB (10,709 words) - 18:56, 20 November 2022
• hreview-v0.2
  ...and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
  34 KB (5,152 words) - 16:28, 18 July 2020
• existing-rel-values
  | [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a
  89 KB (12,799 words) - 23:54, 30 November 2022

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