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,918 words) - 17:47, 23 May 2024

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