Search results

Jump to navigation Jump to search
  • 12 KB (1,961 words) - 02:18, 4 January 2009
  • 11 KB (1,873 words) - 16:43, 16 February 2022
  • ID value, marking it as the machine-readable group name, and then any
    8 KB (1,173 words) - 08:07, 6 January 2009
  • 9 KB (1,416 words) - 04:25, 21 September 2012
  • 6 KB (860 words) - 16:22, 18 July 2020
  • 13 KB (2,048 words) - 16:22, 18 July 2020
  • ...a element]: "The HTML <data> element links a given piece of content with a machine-readable translation." The use suggested in this section does not provide a
    16 KB (2,360 words) - 04:47, 22 December 2020
  • 27 KB (4,077 words) - 16:23, 18 July 2020
  • <abbr class="geo" title="machine-readable-geo-info"> ...or putting both the latitude and longitude into the title attribute as the machine-readable-geo-info that is still human readable/listenable.
    17 KB (2,558 words) - 16:22, 18 July 2020
  • ...others can be discarded without further discussion, because they're either machine-only or just don't fit into the weblog use-case.
    30 KB (4,126 words) - 16:21, 18 July 2020
  • 8 KB (1,091 words) - 18:54, 19 April 2016
  • 22 KB (3,192 words) - 16:24, 18 July 2020
  • ...be used to resolve some long standing issues with including [[machine-data|machine-data in microformats]]; it's imperative we test thoroughly before adding it It allows you to include machine-form date and time data alongside the human form equivalents, without pollut
    27 KB (3,570 words) - 16:34, 18 July 2020
  • 9 KB (1,526 words) - 20:07, 8 January 2009
  • 10 KB (1,467 words) - 21:54, 20 December 2008
  • ...image. The title of the show is given with an image (and thus the actual machine-readable title is the ''alt attribute'' of the image) and is linked with the ...images. The title of the show is given with an image (and thus the actual machine-readable title is the ''alt attribute'' of the image) and is linked with the
    35 KB (5,193 words) - 04:57, 7 April 2013
  • 44 KB (1,578 words) - 15:50, 30 July 2008
  • ...k microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.
    11 KB (1,763 words) - 08:57, 21 February 2018
  • 17 KB (2,780 words) - 16:35, 18 July 2020
  • 10 KB (1,580 words) - 00:01, 18 December 2008
  • 9 KB (1,407 words) - 21:00, 9 July 2007
  • 26 KB (3,768 words) - 16:27, 18 July 2020
  • # Would using the title attribute of the abbr tag to encode the machine-readable date in fact cause a failure of WCAG 2.0 Accessibility? What about # In order to maintain accessibility, would it make sense to enclose the machine-readable date in a span with a style of "display:none" instead of using the
    42 KB (6,379 words) - 16:21, 18 July 2020
  • 29 KB (4,290 words) - 23:36, 24 August 2020
  • As a solution to the invisible data requirements sometimes presented by [[machine-data]] in microformats, a parsing rule is proposed where the <code>value</co * This pattern exists to solve the [[machine-data]] problem, and restricting it more will discourage it being mis-used fo
    51 KB (7,976 words) - 16:33, 18 July 2020
  • 13 KB (2,139 words) - 13:56, 30 April 2017
  • 8 KB (1,307 words) - 21:27, 26 July 2023
  • 27 KB (4,665 words) - 19:24, 3 January 2009
  • 8 KB (1,164 words) - 16:33, 18 July 2020
  • 10 KB (1,467 words) - 17:50, 23 May 2024
  • 8 KB (1,245 words) - 19:38, 18 December 2020
  • La page [[machine-data]] a de la documentation sur quelques-unes des propriétés de quelques * [[machine-data-fr|Machine Data in Microformats]]
    37 KB (6,016 words) - 16:34, 18 July 2020
  • 34 KB (5,169 words) - 19:38, 3 January 2009
  • 33 KB (4,902 words) - 16:24, 18 July 2020
  • 12 KB (1,929 words) - 16:24, 18 July 2020
  • 18 KB (2,485 words) - 11:24, 22 September 2013
  • # Would using the title attribute of the abbr tag to encode the machine-readable date in fact cause a failure of WCAG 2.0 Accessibility? What about # In order to maintain accessibility, would it make sense to enclose the machine-readable date in a span with a style of "display:none" instead of using the
    42 KB (6,350 words) - 16:21, 18 July 2020
  • 32 KB (4,788 words) - 20:37, 30 October 2023
  • 11 KB (1,475 words) - 16:22, 18 July 2020
  • 12 KB (1,668 words) - 16:21, 18 July 2020
  • 15 KB (1,946 words) - 13:02, 16 January 2008
  • 11 KB (1,595 words) - 21:14, 26 July 2023
  • ## The XMDP profile is a machine-readable description of your microformat. Every microformat must have a XMDP
    15 KB (2,470 words) - 05:10, 8 August 2007
  • 34 KB (5,124 words) - 16:28, 18 July 2020
  • 34 KB (5,152 words) - 16:28, 18 July 2020
  • 32 KB (4,986 words) - 16:26, 18 July 2020
  • 9 KB (1,415 words) - 21:28, 26 July 2023
  • ...e standard names. You don't have to make your own up, and now your page is machine-readable too. Bonus! ...se of the [[value class pattern]] <code>value-title</code> empty span with machine-readable information adjacent to a human-readable equivalent.
    34 KB (5,453 words) - 05:18, 9 October 2023
  • 21 KB (3,116 words) - 19:49, 25 August 2013
  • 14 KB (2,151 words) - 08:49, 29 January 2022
  • ...ecify a human-readable date in the value of the attribute, and the ISO8601 machine-readable date in the "datetime" property.
    33 KB (4,918 words) - 17:47, 23 May 2024
  • 23 KB (3,178 words) - 14:11, 9 September 2007
  • 17 KB (2,328 words) - 13:38, 18 February 2017
  • 12 KB (1,839 words) - 16:23, 18 July 2020
  • 13 KB (2,033 words) - 16:24, 18 July 2020
  • 36 KB (5,424 words) - 16:27, 18 July 2020
  • 55 KB (8,434 words) - 15:02, 26 May 2014
  • 15 KB (2,279 words) - 16:29, 18 July 2020
  • 20 KB (3,205 words) - 16:25, 18 July 2020
  • ...ith the [[value-class-pattern]] must opt in to using it.</strong>. See: [[machine-data]] for the current reference for which properties have value-class-patte
    41 KB (6,454 words) - 16:24, 18 July 2020
  • 56 KB (8,931 words) - 06:56, 27 January 2008
  • 15 KB (2,230 words) - 16:34, 18 July 2020
  • 21 KB (3,281 words) - 16:25, 18 July 2020
  • 58 KB (9,116 words) - 14:15, 24 June 2009
  • 36 KB (5,415 words) - 11:09, 22 September 2013
  • 49 KB (7,275 words) - 16:25, 18 July 2020
  • 48 KB (6,826 words) - 04:52, 7 April 2013
  • 27 KB (4,322 words) - 16:26, 18 July 2020
  • 53 KB (7,610 words) - 16:21, 18 July 2020
  • 60 KB (9,422 words) - 16:26, 18 July 2020
  • 44 KB (6,955 words) - 11:00, 14 January 2008
  • 34 KB (5,614 words) - 16:25, 18 July 2020
  • ...rmat), it can be transitioned to a Specification (so as to encourage other machine-based implementations). -->
    32 KB (1,079 words) - 09:13, 9 February 2014
  • 34 KB (4,524 words) - 19:40, 11 January 2022
  • 44 KB (6,231 words) - 21:11, 26 July 2023
  • 35 KB (5,273 words) - 15:32, 17 August 2021
  • 43 KB (6,297 words) - 22:14, 20 December 2008
  • 33 KB (5,303 words) - 16:22, 18 July 2020
  • 64 KB (10,413 words) - 23:22, 1 May 2007
  • | References a machine-readable privacy policy description in the P3P format
    89 KB (12,799 words) - 23:54, 30 November 2022
  • 82 KB (12,852 words) - 16:25, 18 July 2020

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