Search results

Jump to navigation Jump to search
  • 16 KB (2,413 words) - 22:58, 8 June 2018
  • 4 KB (547 words) - 16:21, 18 July 2020
  • ...we constrain REST to work with existing web browser clients -- yet also be machine-parseable. This means:
    5 KB (833 words) - 20:05, 6 November 2006
  • 17 KB (2,704 words) - 04:06, 18 December 2008
  • 11 KB (1,664 words) - 16:21, 18 July 2020
  • 6 KB (943 words) - 13:29, 5 August 2007
  • 5 KB (664 words) - 16:22, 18 July 2020
  • 17 KB (2,173 words) - 15:56, 30 September 2008
  • ...esting and/or Validation of microformats ''should'' attempt to compare the machine-data and human legible forms of the property data, and warn authors if the f ...that the value-title pattern hides some amount of data which tends to be a machine-specific duplicate of data that is provided in the human readable content, t
    34 KB (2,879 words) - 16:34, 18 July 2020
  • 7 KB (976 words) - 04:48, 1 December 2009
  • 9 KB (1,383 words) - 21:14, 27 February 2021
  • 13 KB (1,942 words) - 23:04, 20 June 2024
  • 30 KB (1,940 words) - 16:26, 18 July 2020
  • 8 KB (1,257 words) - 01:09, 14 December 2016
  • 8 KB (1,205 words) - 23:29, 23 May 2007
  • 27 KB (1,828 words) - 16:27, 18 July 2020
  • ...rtues!</p><p>But in making it easy to add [[microformats]], which are just machine-readable, coded bits of structure, we let machines talk to machines and ambi
    13 KB (1,822 words) - 16:43, 16 February 2022
  • <abbr class="geo" title="machine-readable-geo-info">
    11 KB (1,673 words) - 22:41, 21 October 2007
  • ===Using <code>value-title</code> to publish machine-data=== ===Parsing machine-data <code>value-title</code>===
    39 KB (5,876 words) - 03:04, 25 June 2022
  • ...e standard names. You don't have to make your own up, and now your page is machine-readable too. Bonus! ...rmat), it can be transitioned to a Specification (so as to encourage other machine-based implementations).
    22 KB (3,258 words) - 05:58, 24 January 2012

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