Search results
Jump to navigation
Jump to search
- ...ents for a piece of content. It builds on other microformats which define specific uses of the rel attribute for links, such as [[rel-tag]] and [[rel-license]2 KB (253 words) - 16:32, 18 July 2020
- ...contain sample hReviews. The reason for this is that sites often highlight specific instances of "hX" on their summary pages. Amazon shows the most popular rev3 KB (495 words) - 04:27, 24 April 2009
- ...t fields seem suitable for unstructured address information. They all have specific meanings that we couldn't maintain by putting arbitrary address information4 KB (652 words) - 09:56, 11 April 2007
- ...EGIN:VEVENT END:VEVENT block, and optional "X-" properties, implementation specific "PRODID" property, and "CHARSET" parameter have been omitted (and thus impl5 KB (697 words) - 05:59, 4 April 2017
- A microformat is a specific collection of names, values, and accompanying structure defined through rig11 KB (504 words) - 01:45, 12 October 2007
- ...es. There seem to be two ones: an [http://phobos.apple.com/version iTunes-specific one], and a [http://swscan.apple.com/content/catalogs/index-1.sucatalog gen2 KB (320 words) - 16:21, 18 July 2020
- ...EGIN:VEVENT END:VEVENT block, and optional "X-" properties, implementation specific "PRODID" property, and "CHARSET" parameter have been omitted (and thus impl5 KB (690 words) - 10:49, 5 November 2009
- ...EGIN:VEVENT END:VEVENT block, and optional "X-" properties, implementation specific "PRODID" property, and "CHARSET" parameter have been omitted (and thus impl5 KB (695 words) - 05:57, 4 April 2017
- ...ies), and specify that any application use cases which appear to "require" specific properties must instead define how to imply sensible defaults for them. ...fications]] for latest thoughts along these lines, including the following specific mark-up implied generic properties across all microformats (based on existi23 KB (3,339 words) - 16:43, 3 April 2018
- ...EGIN:VEVENT END:VEVENT block, and optional "X-" properties, implementation specific "PRODID" property, and "CHARSET" parameter have been omitted (and thus impl5 KB (702 words) - 14:59, 5 November 2009
- * <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names ...d for another simpler way of expressing extended, one-off, custom, or site-specific semantics.9 KB (1,223 words) - 21:44, 14 December 2020
- ...endar</span> output, omitting optional "X-" properties, and implementation specific "PRODID" property:6 KB (755 words) - 20:26, 5 June 2012
- ...her <code>rel</code> values and other attributes to provide different more specific meanings, in particular:4 KB (535 words) - 21:33, 26 July 2023
- ...to mostly be content copied from [[hReview]] without removing the hReview-specific content such as the draft spec note, date, authors, etc. This can be fixe * Analyze what aspects are "comment" specific (rather than just copied from hReview)16 KB (2,413 words) - 22:58, 8 June 2018
- ...ed.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.4 KB (516 words) - 23:02, 14 October 2009
- ...endar</span> output, omitting optional "X-" properties, and implementation specific "PRODID" property:5 KB (665 words) - 17:56, 4 November 2009
- ...e classes and new rel values you are using as being defined by one or more specific microformats. With an XMDP validator, you will also be able to make sure t4 KB (666 words) - 21:50, 28 July 2008
- ...endar</span> output, omitting optional "X-" properties, and implementation specific "PRODID" property:5 KB (640 words) - 21:13, 4 January 2012
- * [[plain-old-xml-considered-harmful]] - feel free to add to this specific page from the below resources.4 KB (648 words) - 13:30, 11 October 2017
- ...t a person (except, when representing an author, use the more semantically specific AU element noted above instead).3 KB (399 words) - 16:28, 18 July 2020