Search results

Jump to navigation Jump to search
  • ...ogle.com/ Google.com] はメインの検索で [[rel-nofollow-ja|rel-nofollow]]、[[hcard-ja|hCard]]、[[hreview-ja|hReview]]、[[hreview-aggregate|hReview の収集]]、[[hP
    4 KB (370 words) - 16:20, 18 July 2020
  • The [http://www.yandex.com/ Yandex] search engine supports [[hCard]], [[hRecipe]], [[hReview]], and [[hProduct]] microformats in main search, * [[hCard]] ([http://help.yandex.ru/webmaster/?id=1111573])
    1 KB (149 words) - 16:35, 18 July 2020
  • ...eing developed, it was clear to me from experience with developing [[hcard|hCard]] and [[hcalendar|hCalendar]] that each property, value, and structure bein ...In fact, much of this will be clearly recognized by anyone familiar with [[hcard-parsing]] as having been copypasted from that source. At some point (perhap
    2 KB (384 words) - 18:47, 20 December 2008
  • ** hResume uses [[hCard]] ...ace of death and date of death for a person. '''bday''' is already part of hCard.
    5 KB (710 words) - 18:48, 20 December 2008
  • ...productions.net 3AM Productions] utilise l'include-pattern pour remplir en hCard les morceaux dans la page. Initialement utilisé <code>object</code> mais s ...ject</code>, pour inclure le logo à partir du haut de chaque page, dans la hCard de pied de page (par ex. sur [http://www.westmidlandbirdclub.com/new.htm la
    1 KB (183 words) - 09:01, 5 February 2007
  • {{DISPLAYTITLE:hCard représentative}} ...spécialement pour imaginer comment spécifier explicitement et découvrir la hCard représentative d'une page.
    5 KB (724 words) - 16:32, 18 July 2020
  • ...anisation,s and their contact information? Then mark those up with [[hcard|hCard]].
    2 KB (261 words) - 22:39, 20 December 2008
  • <h1>hCard design methodology</h1> This page is an ''informative'' explanatory section of the [[hcard|hCard specification]].
    5 KB (790 words) - 19:25, 30 March 2013
  • {{DISPLAYTITLE:representative hCard parsing}} ...e a [[representative hCard]] for a page using the current [[representative-hcard-brainstorming]] proposal.
    6 KB (854 words) - 16:32, 18 July 2020
  • <td>[[hcard-ru|hCard]] </td> <td>Используется совместно с hCard организации для уточнения принадлежност
    14 KB (1,257 words) - 02:00, 4 July 2008
  • =Date de Décès dans la hCard= ...rnant la proposition d'ajouter un champ "date of death" dans la [[hcard-fr|hCard]].
    4 KB (610 words) - 06:29, 29 September 2007
  • ...ed-microformats . The first of those two have been well defined by [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats. Web applications that bear thes
    1 KB (201 words) - 21:49, 20 December 2008
  • * No, nor is it a goal to do so. The [[hcard|hCard]] microformat can represent the 80% of common information across social net With [[hcard|hCard]], one can easily capture, publish and share the 80/20 of common profile in
    5 KB (833 words) - 18:40, 27 November 2007
  • ** [[hcard-issues-resolved]] ([[hcard-issues-closed]]) * Google Rich Snippets launched with support for [[hCard]], [[hReview]], [[hReview aggregate]], [[hProduct]]
    2 KB (257 words) - 21:43, 5 February 2010
  • ...transformer and validator that supports numerous microformats including [[hCard]], [[hCalendar]], [[hReview]], [[hAtom]] (note: [[optimus-issues#hAtom_vali === [[hCard]] ===
    2 KB (255 words) - 16:21, 18 July 2020
  • hcard hCard
    1 KB (163 words) - 21:07, 20 December 2008
  • ...edded" microformats. For example, "adr", "geo" and "agent vcard" within an hCard. ...hAtom ''at all'' -- but they must parse it completely independently of the hCard.
    3 KB (425 words) - 09:23, 7 March 2008
  • * [[hcard-supporting-user-profiles]] * [[hcard-xfn-supporting-friends-lists]]
    3 KB (320 words) - 01:16, 16 November 2007
  • * [[hcard-examples-in-wild-fr|hCard exemples dans la jungle]]
    1 KB (140 words) - 09:44, 2 February 2008
  • ** [[hcard|hCards]] for restaurant listings e.g. [http://www.foodbuzz.com/restaurants/ ** [[hcard-supporting-user-profiles|hCards for user profiles]] e.g. [http://www.foodbu
    4 KB (582 words) - 08:40, 12 February 2010

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