Search results

Jump to navigation Jump to search
  • ...class="url">http://microformats.org/wiki/events/2010-05-02-microformats-2-0</span></span> ...ass="dtstart"><span class="value">2010-03-14</span> at <span class="value">1:10pm</span></span>: <span class="summary">[[events/2010-03-14-sxsw-microfor
    7 KB (946 words) - 16:21, 18 July 2020
  • <h1 class="summary">hCard 1 - single occurrence test</h1> <p>From: <a href="default.htm"><span class="format">hCard</span> testsuite 1.0</a></p>
    9 KB (1,295 words) - 16:33, 18 July 2020
  • &lt;abbr class="due" title="2007-01-01T13:10:05.0Z"&gt;January 1, 2007&lt;/abbr&gt; ...in the body, it can be ignored. The numerical part is assumed to be from 0-100. For example,
    1 KB (182 words) - 22:52, 14 December 2021
  • ...tton must dynamically assign orignator, timezone, creation date, duration, 0% progress, etc. --&gt; <br/> &lt;br /&gt; <br/> &lt;/p&gt; <br/> &lt;/ Step 1: Create an output function that takes the form data entered by the user and
    20 KB (2,819 words) - 05:06, 20 August 2021
  • - [[User:Tantek|Tantek]] 03:01, 18 December 2011 (UTC) These are 1:1 hCalendar examples for each example in {{RFC2445}}.
    24 KB (3,465 words) - 16:24, 18 July 2020
  • ...the last day of the event. It is an unintuitive leap to think to specify +1 day for machine consumption, and an additional cognitive load (in order to ...title attribute provides an expansion for the inner text. In no way is a +1 date an expansion of a date, it appears more like a completely different va
    12 KB (1,889 words) - 16:21, 18 July 2020
  • ...o the ISO 8601 form date: ‘January 1st’ is an abbreviated form of ‘2008-01-01’. The latter is also legible to humans (and can be exposed to them throug ...l form, whilst phone numbers can be presented in alpha-numeric form: e.g. +1-555-FORMATS
    6 KB (983 words) - 16:28, 18 July 2020
  • La propriété dtend [[hcalendar-fr|hCalendar]] de hCalendar 0.1. requiert que les dates de fin soient marquées comme arrivant un jour comp ...ier jour de l'événement. C'est un saut non intuitif de penser à spécifier +1 jour pour la consommation machine, et une charge cognitive supplémentaire.
    11 KB (1,664 words) - 16:21, 18 July 2020
  • <div class="p-comment h-entry" id="comment-1"><a href="" class="u-in-reply-to"></a> (<a class="u-url dt-published" href="#comment-1">YYYY-DD-MM HH:MM</a>)
    22 KB (3,311 words) - 22:58, 13 July 2022
  • ...ating but get there early to save adjacent tables - [[User:Tantek|Tantek]] 01:13, 8 January 2015 (UTC) ** +0 they require a group check. - [[User:Tantek|Tantek]]
    15 KB (2,279 words) - 16:29, 18 July 2020
  • * {{OpenIssue}} 2010-01-20 raised by [[User:BenWard|BenWard]] *#** +1 This sounds like a good idea and something worthy of being incorporated int
    30 KB (4,760 words) - 16:23, 18 July 2020
  • ...perience, requiring consensus among participating implementers (since 2015-01-21) as part of an explicit [[#change_control|change control]] process. Ther ...vendor prefix (series of 1+ number or lowercase a-z characters i.e. <code>[0-9a-z]+</code>, followed by '-'), then one or more '-' separated lowercase a
    25 KB (3,919 words) - 19:23, 8 February 2023
  • ** +1 I like this as a neutral term, <s>except that it would be better kept as a ...ser:Donohoe]] below is a good one thus I've changed my opinion from +1 to +0 on this option.
    23 KB (3,631 words) - 16:35, 18 July 2020
  • <span class='value-title' title='2009-01-06T22:54:00-0800'></span> ===hAtom#1: An hAtom <code>published</code>/<code>updated</code> Property===
    27 KB (3,793 words) - 16:34, 18 July 2020
  • :'''See: {{RFC2426}} section 3.1.5 :'''See: {{RFC2426}} section 3.3.1
    14 KB (2,056 words) - 16:34, 18 July 2020
  • 1. use "h-image" on any u-* on img elements to imply a structure with paired ...and using name for it implies that it is. [[User:Kevin Marks|Kevin Marks]] 01:50, 19 July 2016 (UTC)
    42 KB (6,235 words) - 16:29, 18 July 2020
  • Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339 Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar
    42 KB (6,379 words) - 16:21, 18 July 2020
  • Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339 Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar
    42 KB (6,350 words) - 16:21, 18 July 2020
  • {{DISPLAYTITLE:hReview-aggregate 0.2}} ...t</code>''' (par défaut :1.0) et/ou '''<code>best</code>''' (par défaut :5.0), aussi nombre entier avec une décimale, et '''<code>average</code> explic
    21 KB (3,089 words) - 16:27, 18 July 2020
  • id=6815841748&share_id=154954250775&comments=1#s154954250775</nowiki></pre></blockquote> ...Virtual). “Helicopter hovering above Abbottabad at 1AM (is a rare event).” 1 May 2011, 3:58 p.m. Tweet.</nowiki></blockquote> <blockquote>"The date and
    53 KB (7,610 words) - 16:21, 18 July 2020

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