Search results

• rel-pavatar
  Use [[hcard|hCard]] with the <code>logo</code> property for visible icons instead.
  397 bytes (55 words) - 16:31, 18 July 2020
• hmedia-brainstorming
  == url property == Proposal: add the "url" property as another way for authors to indicate a media resource (in addition to hMe
  3 KB (426 words) - 16:27, 18 July 2020
• hresume-profile
  <dd>This optional property serves as an overview of qualifications and objectives. Re-used from hRevie <dd>This optional property provides information about the person who authored the resume. If the value
  5 KB (769 words) - 16:27, 18 July 2020
• hatom-profile
  <dd>This optional property provides the title or name of an entry, based on the definition of atom:fee <dd>This optional property provides the summary of an entry, based on the definition of atom:summary
  6 KB (902 words) - 16:23, 18 July 2020
• hreview-profile
  ...ty with content produced using earlier versions of the specification. This property is syntax compatible with, and thus reuses the semantics of "VERSION" as de <dd>This optional property serves as a short synopsis, title, or name of the review. Re-used from hCal
  7 KB (1,043 words) - 16:28, 18 July 2020
• hlisting-profile
  ...ty with content produced using earlier versions of the specification. This property is syntax compatible with, and thus reuses the semantics of "VERSION" as de <dd>This optional property serves as a short synopsis, title, or name of the listing. Re-used from hRe
  7 KB (1,048 words) - 16:26, 18 July 2020
• hreview-brainstorming
  ...cify a <code>url</code> property for the item (in hReview 0.3 having "url" property for the item is only a SHOULD) ...deprecating the <code>version</code> property. is the <code>version</code> property needed? currently it is optional and created invisibly by the [http://micr
  4 KB (666 words) - 16:27, 18 July 2020
• metaformats
  ==== parsing a p- property ==== ==== parsing a u- property ====
  5 KB (796 words) - 00:36, 2 December 2023
• representative-object-brainstorming
  ...tize hCards with <code>rel=me</code> or any object with a <code>uid</code> property on the same domain=== Where an object is in a page with a property <code>uid</code> pointing to the same domain as the current page, and/or ma
  4 KB (675 words) - 16:32, 18 July 2020
• h-review
  ...ting''', '''dt-published''', '''p-author''', '''e-content''' and the other property class names listed below defined elements as ''properties'' of the h-review ...ot class name'' that indicates an embedded '''[[h-item]]''' for the p-item property.
  11 KB (1,497 words) - 20:22, 5 February 2024
• representative-hcard-parsing
  ..." property whose value is the url of the page (source) and is also a "uid" property for the hCard, is the representative hCard for the page. ...step didn't find a representative hCard, then the first hCard with a "url" property that also has the <code>rel="me"</code> relation is the representative hCar
  6 KB (854 words) - 16:32, 18 July 2020
• microformats2-json
  ...ple shows an <code>h-entry</code> type microformats2 object, with a single property attached. The <code>h-entry</code> type is [[h-entry|documented on the wiki ...code> member contains an object where every member name is a microformats2 property name, and every member value is an array of the found microformats2 values.
  13 KB (1,808 words) - 22:38, 25 December 2021
• rel-shortlink
  ** Intellectual property issues:
  8 KB (1,202 words) - 16:32, 18 July 2020
• group-brainstorming
  ...draft-ietf-vcarddav-vcardrev-03.txt latest vCard 4.0 draft] includes a new property "member". This could be leveraged in hCard like so: * This is similar to how the "agent" property already works, so people should already be fairly familiar with it.
  5 KB (831 words) - 16:23, 18 July 2020
• hatom-tracking
  ** [[hatom-issues#|add url property to hentry]] (open)
  1 KB (147 words) - 16:23, 18 July 2020
• representative-h-card-parsing
  ...entative h-card was found, if the page contains an h-card with a '''url''' property value which also has a <code>rel=me</code> relation (i.e. matches a URL in ...the page contains '''one single''' h-card, and the h-card has a '''url''' property matching the page URL, that h-card is the representative h-card
  2 KB (288 words) - 12:45, 22 June 2021
• relationship-status
  === relationship-status property name === Simple brainstorm proposal: use the property name <code>'''relationship-status'''</code> as a class name on an element m
  8 KB (1,126 words) - 16:32, 18 July 2020
• microformats2-brainstorming
  ...iew" for backwards compatibility, detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to ...orporate rel property parsing either as just another property (like a 'u-' property) scoped to the microformat:
  10 KB (1,570 words) - 23:41, 14 December 2020
• h-recipe
  '''p-name''', '''e-instructions''', '''p-ingredient''' and the other property classnames listed below define elements as ''properties'' of the h-recipe. See [[microformats-2-parsing]] to learn more about property classnames.
  8 KB (1,095 words) - 23:52, 30 November 2022
• hcard-supporting-user-profiles-issues
  * The bio field should be marked up with the property <code>note</code>, i.e. <code>class="bio"</code> should be <code>class="bio
  5 KB (687 words) - 16:26, 18 July 2020

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