Search results

Jump to navigation Jump to search

Page title matches

  • 6 KB (983 words) - 16:28, 18 July 2020
  • ...escribing a location by name, but still wanting to include [[geo]] for the machine-readable location:
    11 KB (1,709 words) - 23:48, 17 November 2008

Page text matches

  • 826 bytes (119 words) - 23:59, 17 December 2008
  • ...free Q&A platform called Question2Answer, and would like its output to be machine-readable.
    258 bytes (43 words) - 10:45, 21 January 2010
  • ...ld publish an HTML page containing your contact information and a separate machine-readable vCard file that people could automatically import into their addres
    3 KB (464 words) - 23:50, 17 November 2008
  • A [http://www.markbaker.ca/2003/05/RDF-Forms/ RDF Form] is out there as a machine-friendly similar version of HTML Form.
    4 KB (678 words) - 21:10, 17 December 2008
  • 2 KB (374 words) - 02:19, 4 January 2009
  • ...enCalais, Zoominfo, Twine, social networks, DBpedia and web sites exposing machine-readable data using '''microformats''', RDFa, and GRDDL.
    612 bytes (84 words) - 07:35, 18 May 2008
  • * a 2D barcode can be used to encode small amounts of machine-readable information, even in places without internet access -- perhaps [[Wi
    638 bytes (96 words) - 13:43, 13 July 2009
  • ...e with a <code>abbr</code> whose <code>title</code> attribute contains the machine-readable numerical value (See [[abbr-design-pattern]]).
    4 KB (657 words) - 23:26, 18 March 2013
  • ...ense for something, i.e. All Rights Reserved. There is no Creative Commons machine-readable license that says as much, but I want to support and use this micro
    3 KB (560 words) - 09:57, 3 February 2008
  • 3 KB (447 words) - 03:33, 8 January 2008
  • ...ense for something, i.e. All Rights Reserved. There is no Creative Commons machine-readable license that says as much, but I want to support and use this micro
    4 KB (659 words) - 04:54, 7 April 2013
  • 2 KB (285 words) - 19:30, 3 January 2009
  • 5 KB (711 words) - 21:44, 11 January 2007
  • ...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
    6 KB (962 words) - 19:38, 3 January 2009
  • ** notice that this is a machine-defined value
    2 KB (228 words) - 19:11, 4 February 2011
  • 6 KB (983 words) - 16:28, 18 July 2020
  • 22 KB (2,243 words) - 05:42, 4 January 2008
  • ...s.info OpenURL COinS] offers a machine-parsable (albeit ugly) solution for machine-readable references. [http://buzzword.org.uk/cognition/ Cognition] supports
    5 KB (710 words) - 18:48, 20 December 2008
  • ...escribing a location by name, but still wanting to include [[geo]] for the machine-readable location:
    11 KB (1,709 words) - 23:48, 17 November 2008
  • * Is HTML Machine-Parseable? = Challenge #1: Machine-Parseability =
    7 KB (911 words) - 22:38, 20 December 2008
  • 7 KB (586 words) - 20:56, 17 July 2008
  • ...eb pages, so that you can create tools and scripts that losslessly extract machine-readable information from cleanly-formatted, human-readable HTML.
    5 KB (782 words) - 04:47, 7 April 2013
  • ** Machine-precise reference to the license ** Machine-precise semantic for what is licensed
    4 KB (514 words) - 16:28, 18 July 2020
  • 8 KB (1,160 words) - 16:32, 18 July 2020
  • 2 KB (357 words) - 03:29, 15 September 2016
  • ...research aiming to protect content, especially content that has been made machine-readable through the use of semantic annotations. I have plenty of ideas and
    2 KB (372 words) - 22:34, 5 January 2009
  • 17 KB (1,468 words) - 06:18, 10 May 2009
  • 11 KB (1,632 words) - 16:20, 18 July 2020
  • 3 KB (468 words) - 22:18, 20 December 2008
  • The idea with hNews is to add some machine-readable news-specific semantics to display-ready HTML. I see NewsML [http:/ hNews is a way to add some machine-readable news semantics to HTML. If you want to follow the hNews spec, you
    7 KB (1,262 words) - 02:15, 14 October 2009
  • There are a number of use-cases for having a standardized, machine-readable format for HTML error messages.
    3 KB (504 words) - 17:15, 28 June 2007
  • 3 KB (385 words) - 10:13, 6 July 2007
  • 5 KB (776 words) - 13:32, 24 March 2010
  • 10 KB (1,366 words) - 15:57, 14 June 2010
  • 4 KB (692 words) - 07:03, 28 October 2007
  • 2 KB (329 words) - 09:58, 8 July 2006
  • ...ode> as a sub-property of <code>tel</code>? That's one of the identified [[machine-data]] items that needs a means of including the publisher's choice text alo ...tent of the hAtom entry, using the value-excerption-pattern to include the machine-data datetime. However, with full descendent parsing, the hAtom model will c
    7 KB (1,050 words) - 16:34, 18 July 2020
  • 2 KB (286 words) - 16:33, 18 July 2020
  • 4 KB (648 words) - 13:30, 11 October 2017
  • 4 KB (590 words) - 22:00, 20 December 2008
  • 4 KB (530 words) - 16:46, 3 September 2010
  • 2 KB (334 words) - 16:23, 18 July 2020
  • 4 KB (517 words) - 16:22, 18 July 2020
  • 3 KB (390 words) - 16:33, 18 July 2020
  • 3 KB (481 words) - 16:21, 18 July 2020
  • 16 KB (2,523 words) - 18:28, 23 July 2014
  • 5 KB (766 words) - 14:09, 10 March 2008
  • 4 KB (667 words) - 18:04, 26 February 2007
  • 2 KB (311 words) - 06:21, 18 November 2022
  • to explain the meaning of the parameters (a machine-understandable way
    4 KB (584 words) - 16:11, 16 September 2010
  • 3 KB (473 words) - 16:22, 18 July 2020
  • 3 KB (487 words) - 16:22, 18 July 2020
  • 9 KB (1,413 words) - 00:55, 17 February 2021
  • 3 KB (460 words) - 16:22, 18 July 2020
  • 3 KB (433 words) - 16:22, 18 July 2020
  • ...format specifies how this can be done in a fashion that is both human- and machine-readable.
    5 KB (698 words) - 19:11, 4 February 2011
  • ...ms to protect the authenticity and authority of content that has been made machine-readable through the use of semantic annotations (e.g. Microformatted data).
    6 KB (850 words) - 10:09, 8 January 2009
  • 6 KB (881 words) - 16:20, 18 July 2020
  • 4 KB (519 words) - 16:22, 18 July 2020
  • 4 KB (542 words) - 16:22, 18 July 2020
  • 4 KB (542 words) - 16:22, 18 July 2020
  • 11 KB (1,580 words) - 16:20, 18 July 2020
  • ** Machine-parseable yet human-readable
    5 KB (766 words) - 19:08, 3 January 2009
  • 4 KB (553 words) - 16:22, 18 July 2020
  • 12 KB (1,889 words) - 16:21, 18 July 2020
  • This datetimes could be made machine-readable using [[datetime-design-pattern]].
    6 KB (820 words) - 11:26, 27 May 2016
  • 3 KB (489 words) - 16:21, 18 July 2020
  • 4 KB (567 words) - 22:30, 8 January 2008
  • 6 KB (842 words) - 12:26, 4 April 2007
  • ...we constrain REST to work with existing web browser clients -- yet also be machine-parseable. This means:
    5 KB (818 words) - 20:12, 4 January 2009
  • 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,947 words) - 16:22, 18 July 2020
  • 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
  • 3 KB (540 words) - 16:20, 18 July 2020
  • 12 KB (1,813 words) - 16:20, 18 July 2020
  • 5 KB (745 words) - 16:22, 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 data alongside the human form, without polluting visible formatted cont
    27 KB (3,793 words) - 16:34, 18 July 2020
  • 40 KB (2,092 words) - 16:28, 18 July 2020
  • 26 KB (3,851 words) - 22:51, 26 December 2009
  • ...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,180 words) - 20:46, 20 December 2008
  • ...the human text appears before the <code>value-title</code> element, so the machine-data value has a weaker association with the property declaration. The likel
    5 KB (643 words) - 21:40, 26 July 2023
  • 5 KB (739 words) - 16:27, 18 July 2020
  • 20 KB (2,906 words) - 16:24, 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,939 words) - 16:31, 18 July 2020
  • 5 KB (810 words) - 16:22, 18 July 2020
  • 5 KB (809 words) - 11:00, 6 January 2008
  • 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
  • 9 KB (1,453 words) - 21:19, 26 July 2023
  • 27 KB (4,665 words) - 19:24, 3 January 2009
  • 8 KB (1,164 words) - 16:33, 18 July 2020
  • 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,908 words) - 20:53, 24 November 2023
  • 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