value-class-pattern

(Difference between revisions)

Jump to: navigation, search
m (Reverted edits by Feecf (Talk) to last version by Tantek)
Line 1: Line 1:
-
<entry-title>Value Class Pattern</entry-title>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
The '''<dfn>value class pattern</dfn>''' is a set of ways to markup the value of a microformats property in part of an element, a title attribute, or across multiple elements.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
; Editors
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
: <span class="h-card vcard"><span class="fn">[[User:BenWard|Ben Ward]]</span></span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
: <span class="h-card vcard"><span class="fn">[[User:Tantek|Tantek Çelik]]</span></span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
; Short URL
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
: <kbd>http://ufs.cc/w/vcp</kbd>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Use the value class pattern when you need to markup:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
# Only part of an element's content as the value of a property
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
# The displayed value written a certain way for design reasons, and a more universal value in the title attribute of an element
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
# Multiple elements that need to be combined to set the value of a property
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
For these purposes, the special class name <code>value</code> is used to mark-up the relevant data excerpt from larger element content.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
==Status==
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
The value-class-pattern is feature complete, ready for use in markup, and supported in implementations such as [[search engines]], [[parsers]], Firefox [[Operator]], and [[H2VX]]. See also the [http://microformats.org/blog/2009/05/12/value-class-pattern/ blog announcement].
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
==Simple Examples==
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Here is markup for a home phone number:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
vCard fragment:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<source lang=text>TEL;TYPE=HOME:+1.415.555.1212</source>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
hCard fragment:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<source lang=html4strict>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<span class="tel">
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
  <span class="type">Home</span>:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
  <span class="value">+1.415.555.1212</span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</source>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
In this case, the <code>value</code> of <code>tel</code> is <code>+1.415.555.1212</code>, not <code>Home: +1.415.555.1212</code>.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Sometimes the value for a microformats property must be split into multiple pieces in the content of the element representing that property. Multiple elements with a class name of "value" (value elements) can be used to extract and concatenate these pieces into a single value for microformats properties which expect simple strings or tel values.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Another example, this time using a localized (British) telephone number:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<source lang=html4strict>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<span class="tel">
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
  <span class="type">Home</span>:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
  <span class="value">+44</span> (0) <span class="value">1223 123 123</span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</source>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
In this case, the valid ''data'' for the telephone number is <samp>+441223123123</samp>, but the way in which phone number is presented in Britain will include the <samp>(0)</samp>, for local dialling. That is, from anywhere in the world you may dial <kbd>+441223123123</kbd>, or from within Britain you may dial <kbd>01223123123</kbd>. Common local publishing interferes with the data, since dialling <kbd>'''+440'''1223123123</kbd> is an invalid number.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
In the mark-up, two <code>value</code> classes target the part of the telephone number string that makes an international, valid number, whilst allowing conventional presentation.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Another example, adding a place name to a [[geo]] co-ordinate:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<source lang=html4strict>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<p>I'm loitering outside The Bricklayer's Arms
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
  <span class="geo">
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
    51° 30' 48.45", -0° 8' 53.23"
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
    (<span class="value">51.513458;-0.14812</span>)
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
  </span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</p>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</source>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Whilst the entire string is a geo point, it's only the decimal encoded co-ordinates which must be consumed by a microformats parser, so the <code>value</code> class isolates it from the degrees form, which the publisher includes for completeness.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
==Basic Parsing==
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
# The value class pattern only applies to properties which are simple strings, enumerated values, telephone numbers, and datetimes. The value class pattern does not affect parsing of properties of type email, URL, URI, UID.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
# Where an element with such a microformat property class name has a descendant with class name <code>value</code> (a "value element") not inside some other property element, parsers should use the following portion of that value element:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
## if the value element is an <code>img</code> or <code>area</code> element, then use the element's <code>alt</code> attribute value.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
## if the value element is a <code>data</code> element, then use the element's <code>value</code> attribute value if present, otherwise its inner-text.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
## if the value element is an <code>abbr</code> element, then use the element's <code>title</code> attribute value if present, otherwise its inner-text.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
## for any other element, use its inner-text.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
# Where there are multiple descendants of a property with class name of <code>value</code> (multiple value elements)
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
## if the microformats property expects a simple string, enumerated value, or telephone number, then the values extracted from the value elements should be concatenated ''without'' inserting additional characters or white-space.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
## if the microformats property expects a datetime value, see the [[#Date_and_time_parsing|Date Time Parsing]] section.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
# Descendants with class of <code>value</code> must not be parsed deeper than one level. That is, where an element <code>foo</code> with class <code>value</code> has a <em>descendant</em> <code>bar</code> with class <code>value</code>, the content of <strong><code>foo</code></strong> is taken as the <code>value</code>. Nesting additional elements with class of <code>value</code> cannot be used to further isolate a property's value.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
e.g.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<source lang=html4strict>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<p class="description">
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
  <span class="value">
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
    <em class="value">Puppies Rule!</em>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
    <strong>But kittens are better!</strong>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</p>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</source>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
In this example, <code>description</code> has a child ‘<code>value</code>’, and that child has a ''grandchild'' ‘<code>value</code>’. However, the parsing of <code>value</code> classes stops at the first level, so the data for <code>description</code> is: <samp><code>&lt;em class="value">Puppies Rule!&lt;/em>&lt;strong>But kittens are better!&lt;/strong></code></samp>, not just <samp>Puppies Rule!</samp>.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
== Date and time values ==
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
=== Summary ===
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Some microformats properties expect an ISO8601 datetime value, e.g. [[hCalendar]] <code>dtstart</code> and <code>dtend</code>, [[hAtom]] <code>published</code> and <code>updated</code>, and all [[microformats2]] <code>dt-*</code> properties.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Authors may use the value class pattern to separately specify the date and the time, which are then combined to specify a single datetime value.
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
Example, this hCalendar 'dtstart' property with 'value' elements:
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
 
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<source lang=xml>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
<p>The weekly dinner will be on
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
    <span class="dtstart">
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
        <time class="value" datetime="2008-06-24">this Tuesday</time>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
    at <time class="value">18:30</time>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
    </span>
+
MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.
-
</p>
+
-
</source>
+
-
 
+
-
Alternatively, if you're not able to use the [[HTML5]] &lt;time&gt; element:
+
-
 
+
-
<source lang=html4strict>
+
-
<p>The weekly dinner will be on
+
-
    <span class="dtstart">
+
-
        <abbr class="value" title="2008-06-24">this Tuesday</abbr>
+
-
    at <span class="value">18:30</span>
+
-
    </span>
+
-
</p>
+
-
</source>
+
-
 
+
-
both produce the following 'dtstart' value:
+
-
 
+
-
<source lang=text>
+
-
2008-06-24T18:30:00
+
-
</source>
+
-
 
+
-
and iCalendar converters produce the following DTSTART:
+
-
 
+
-
<source lang=text>
+
-
DTSTART:20080624T183000
+
-
</source>
+
-
 
+
-
The lack of a timezone indicates a "floating" datetime, that is a datetime independent of any particular timezone. Examples of floating datetimes could be an alarm clock you set to ring at 7am, or the common 9am-5pm workday.
+
-
 
+
-
=== Date and time parsing ===
+
-
For all date time properties (as defined in their respective microformats specifications), the following rules apply in addition to (and in some cases replacing) the above value class pattern parsing rules.
+
-
 
+
-
When a "value element" is found, parse a value from the element as follows:
+
-
* if the element is an <code>img</code> or <code>area</code> element, then use the element's <code>alt</code> attribute value.
+
-
* if the element is a <code>data</code> element, then use the element's <code>value</code> attribute value if present, otherwise its inner-text.
+
-
* if the element is an <code>abbr</code> element, then use the element's <code>title</code> attribute value if present, otherwise its inner-text.
+
-
* if the element is a <code>del</code>, <code>ins</code>, or <code>time</code> element, then use the element's <code>datetime</code> attribute value if present, otherwise its inner-text.
+
-
* for any other element, use its inner-text.
+
-
* if the value has both a specific ISO8601 date and a specific time, use those and stop looking for "value" elements.
+
-
* if the value has *only* a specific date, specifically, fits the following ISO8601 date patterns (i.e. as documented in the [http://en.wikipedia.org/wiki/ISO_8601 Wikipedia summary of ISO8601])
+
-
** YYYY-MM-DD
+
-
** YYYY-DDD
+
-
** then use that as the date value. For the purposes of the value class pattern, the hyphens "-" separating the year, month, day and/or ordinal day are required.
+
-
** ignore any further "value" elements that specify the date.
+
-
* if the value has *only* a specific time (with or without timezone), parse it for a time value that can match any of the following:
+
-
** HH:MM:SS-XX:YY
+
-
** HH:MM:SS+XX:YY
+
-
** HH:MM:SS-XXYY
+
-
** HH:MM:SS+XXYY
+
-
** HH:MM:SSZ
+
-
** HH:MM:SS
+
-
** HH:MM-XX:YY
+
-
** HH:MM+XX:YY
+
-
** HH:MM-XXYY
+
-
** HH:MM+XXYY
+
-
** HH:MMZ
+
-
** HH:MM
+
-
** HH is the 24 hour "hours" in the time, from 00 to 24, with optional leading 0 for values less than 10.
+
-
** MM are the minutes from 00 to 59
+
-
** SS are the optional seconds from 00 to 59 (60 for a leap second). If omitted, infer 00 seconds.
+
-
** XX is the time zone hours offset, from 00 to 12 with optional leading 0 for values less than 10.
+
-
** YY is the time zone minutes offset, from 00 to 59, though in practice only 00, 15, 30, 45 minute offsets are used in global timezones.
+
-
** Z is the literal 'Z' to indicate GMT.
+
-
** For the purposes of the value class pattern, the colons ":" separating the hour, minutes, seconds are required.  
+
-
** However the colons ":" separating the hours and minutes of any timezone offset are ''optional'' and discouraged in order to make it less likely that a timezone offset will be confused for a time.
+
-
** Case insensitive { }"am"|{ }"a.m." suffix to treat an HH value of 12 as 00, or a case-insensitive { }"pm"|{ }"p.m." suffix to add 12 to HH value less than 12 - per [http://en.wikipedia.org/wiki/12-hour_clock Wikipedia article on the 12 hour clock]. Note: [[X2V]] has implemented this.
+
-
*** HH:MM:SSam
+
-
*** HH:MM:SSpm
+
-
*** HH:MMam
+
-
*** HH:MMpm
+
-
*** HHam
+
-
*** HHpm
+
-
*** where "am" and "pm" mean "am or a.m." and "pm or p.m."
+
-
*** when MM is omitted, infer 00 minutes.
+
-
** ignore any further "value" elements that specify the time.
+
-
* if the value has *only* a specific timezone, parse it for a time zone value that can match any of the following:
+
-
** -XX:YY
+
-
** +XX:YY
+
-
** -XXYY
+
-
** +XXYY
+
-
** -XX
+
-
** +XX
+
-
** Z
+
-
** XX is the time zone hours offset, from 00 to 12 with optional leading 0 for values less than 10.
+
-
** YY is the time zone minutes offset, from 00 to 59, though in practice only 00, 15, 30, 45 minute offsets are used in global timezones.
+
-
** Z is the literal 'Z' to indicate GMT.
+
-
** ignore any further "value" elements that specify the timezone.
+
-
 
+
-
If by parsing the "value" element(s), at least a specific date has been found, then the "value" is overall valid, and the parser assembles the overall datetime value by concatenating the specific date, "T" and specific time (if time was specified, with 00 seconds implied if no seconds are provided), and specific timezone (if timezone and a specific time was specified).
+
-
* YYYY-MM-DD - no time specified
+
-
* YYYY-MM-DDTHH:MM:SS - time specified but no timezone. This is a floating time.
+
-
* YYYY-MM-DDTHH:MM:SS-XXYY or
+
-
* YYYY-MM-DDTHH:MM:SSZ or
+
-
* YYYY-MM-DDTHH:MM:SS+XXYY - both time and timezone were specified.
+
-
 
+
-
=== format specific details ===
+
-
The following are format specific details and <span id="format_specific_optimizations">optimizations</span> that make use of the value-class-pattern.
+
-
 
+
-
;<span style="font-size:smaller">short URL for this section</span>
+
-
:http://ufs.cc/w/vcpfso
+
-
 
+
-
==== hCalendar dtend implied date ====
+
-
Typically events that start and end the same day only display the date of the event once (makes sense per the DRY [[principle]]) (real world examples: [http://upcoming.yahoo.com/event/3010807/ Upcoming], ... more examples with URLs would help for thoroughness).
+
-
 
+
-
Thus it would be convenient if we could imply an [[hCalendar]] event "dtend" date from its "dtstart" date when only the time (and optionally timezone) was specified for its "dtend", e.g.:
+
-
 
+
-
<source lang=xml>
+
-
<span class="vevent">
+
-
The <span class="summary">party</span> will be on
+
-
<span class="dtstart">
+
-
  <time class="value">2009-06-26</time>, from
+
-
  <time class="value">19:00</time></span> to
+
-
<span class="dtend"><time class="value">22:00</time></span>.
+
-
</span>
+
-
</source>
+
-
 
+
-
and in HTML4/XHTML1:
+
-
 
+
-
<source lang=html4strict>
+
-
<span class="vevent">
+
-
The <span class="summary">party</span> will be on
+
-
<span class="dtstart">
+
-
  <span class="value">2009-06-26</span>, from
+
-
  <span class="value">19:00</span></span> to
+
-
<span class="dtend"><span class="value">22:00</span></span>.
+
-
</span>
+
-
</source>
+
-
 
+
-
To simplify this further for authors, hCalendar processors could treat the specifying of just the time per the value-class-pattern date and time value rules, and thus eliminate the need for the "value" span inside the "dtend" span:
+
-
 
+
-
<source lang=xml>
+
-
<span class="vevent">
+
-
The <span class="summary">party</span> will be on
+
-
<span class="dtstart">
+
-
  <time class="value">2009-06-26</time>, from
+
-
  <time class="value">19:00</time></span> to
+
-
<time class="dtend">22:00</time>.
+
-
</span>
+
-
</source>
+
-
 
+
-
and in HTML4/XHTML1:
+
-
 
+
-
<source lang=html4strict>
+
-
<span class="vevent">
+
-
The <span class="summary">party</span> will be on
+
-
<span class="dtstart">
+
-
  <span class="value">2009-06-26</span>, from
+
-
  <span class="value">19:00</span></span> to
+
-
<span class="dtend">22:00</span>.
+
-
</span>
+
-
</source>
+
-
 
+
-
hCalendar to iCalendar converters should produce the following iCalendar fragment (as part of a valid .ics file) from all of the above four examples:
+
-
 
+
-
<source lang=text>
+
-
BEGIN:VEVENT
+
-
SUMMARY:party
+
-
DTSTART:20090626T190000
+
-
DTEND:20090626T220000
+
-
END:VEVENT
+
-
</source>
+
-
 
+
-
Implementations:
+
-
* [[X2V]] has implemented dtend implied date from dtstart.
+
-
 
+
-
Examples "in the wild":
+
-
* http://microformats.org/wiki/events/2009-08-12-nyc-workshop (real world example, but on this wiki).
+
-
 
+
-
==== iCalendar generators ====
+
-
microformats implementations which consume [[hCalendar]] and generate iCalendar {{must}} in addition:
+
-
# remove any dash "-" separators in the date.
+
-
# remove any colon ":" separators in the time.
+
-
# add a whole day to any date-only (lacking a specified time) (date inclusive) hCalendar <code>dtend</code> property values in order to generate an (date exclusive) iCalendar <code>DTEND</code> property value with the same meaning, per the resolution to the [[dtend-issue]].
+
-
# perform datetime math on any +/- relative timezone value, and produce an effective UTC value ending with "Z".
+
-
 
+
-
==== hAtom updated implied date ====
+
-
Similarly, in blog posts that indicate both when they were "published" and "updated", the date is usually only displayed once, typically when "published" (real world examples with URLs would help for thoroughness).
+
-
 
+
-
Thus it would be convenient if we could imply an [[hAtom]] entry "updated" date from its "published" date when only the time (and optionally timezone) was specified for its "updated", e.g. for a blog post that was updated the same day:
+
-
 
+
-
<source lang=xml>
+
-
<span class="hentry">
+
-
<span class="entry-summary">short blog post example</span>
+
-
was published on <span class="published">
+
-
  <time class="value">2009-08-01</time> at <time class="value">12:06</time></span>
+
-
and updated at <span class="updated"><time class="value">12:10</time></span>.
+
-
</span>
+
-
</source>
+
-
 
+
-
and in HTML4/XHTML1:
+
-
 
+
-
<source lang=html4strict>
+
-
<span class="hentry">
+
-
<span class="entry-summary">short blog post example</span>
+
-
was published on <span class="published">
+
-
  <span class="value">2009-08-01</span> at <span class="value">12:06</span></span>
+
-
and updated at <span class="updated"><span class="value">12:10</span></span>.
+
-
</span>
+
-
</source>
+
-
 
+
-
To simplify this further for authors, hAtom processors could treat the specifying of just the time per the value-class-pattern date and time value rules, and thus eliminate the need for the "value" span inside the "updated" span:
+
-
 
+
-
<source lang=xml>
+
-
<span class="hentry">
+
-
<span class="entry-summary">short blog post example</span>
+
-
was published on <span class="published">
+
-
  <time class="value">2009-08-01</time> at <time class="value">12:06</time></span>
+
-
and updated at <time class="updated">12:10</time>.
+
-
</span>
+
-
</source>
+
-
 
+
-
and in HTML4/XHTML1:
+
-
 
+
-
<source lang=html4strict>
+
-
<span class="hentry">
+
-
<span class="entry-summary">short blog post example</span>
+
-
was published on <span class="published">
+
-
  <span class="value">2009-08-01</span> at <span class="value">12:06</span></span>
+
-
and updated at <span class="updated">12:10</span>.
+
-
</span>
+
-
</source>
+
-
 
+
-
==== Atom generators ====
+
-
microformats implementations which consume [[hAtom]] and generate
+
-
Atom {{must}} in addition:
+
-
* normalize all date and datetime values to [[RFC3339]].
+
-
 
+
-
==== microformats2 parsers ====
+
-
Proposal 2012-283:
+
-
 
+
-
Since microformats2 parsers are generic, instead of checking for specific properties (as above for hAtom and hCalendar), they may perform the following algorithm to imply dates for dt-* properties:
+
-
 
+
-
* if a dt-* property has a time but lacks a date
+
-
* then it adopts the date of the most recently seen dt-* property with a date in that microformat.
+
-
** if no previous dt-* properties have a date,
+
-
** then it adopts its date from the next dt-* property with a date seen in that microformat.
+
-
** otherwise it simply has a time (and no date).
+
-
 
+
-
This should result in a similar enough implementation/interpretation as the previous vocabulary dependent heuristics for hAtom and hCalendar that a microformats2 parser could produce similar results for h-entry and h-event without having to know about their specific dt-* properties.  
+
-
 
+
-
=== derivation and tests ===
+
-
This section is <em>informative</em>.
+
-
 
+
-
The handling of date and time values in the value class pattern was originally [[value-excerption-pattern-brainstorming#date_and_time_separation|brainstormed on the value-excerption-pattern-brainstorming]] page and derived from that analysis and feedback. For the curious, historical details may be found there, along with additional thoughts for extension.
+
-
 
+
-
See [[value-class-date-time-tests]] for test cases.
+
-
 
+
-
==Parsing value from a <code>title</code> attribute==
+
-
The <code>value-title</code> class name allows the publisher to indicate the data value for a parent property is contained in the <code>title</code> attribute of an element, rather than the inner-text.
+
-
 
+
-
This can be used to provide a synonym within content, or used to quietly publish alternate forms of information for microformats parsing, without affecting the consumption of content.
+
-
 
+
-
For example, you can use casual localization with dates:
+
-
 
+
-
<source lang=html4strict>
+
-
<p>It was
+
-
<span class='dtstart'>
+
-
  <span class='value-title' title='2008'>last year</span>
+
-
</span>
+
-
  that I realised my addiction to cashew nuts would cost this country so dear.
+
-
</p>
+
-
</source>
+
-
 
+
-
Parsing rules for <code>value-title</code> are the same as for <code>value</code> above, with the following change:
+
-
 
+
-
* Where a microformats property has a child element with class name of <code>value-title</code>, the content of the <code>title</code> attribute of that element must be parsed, rather than the portion of the element that would be parsed for a class name of <code>value</code>.
+
-
 
+
-
===Using <code>value-title</code> to publish machine-data===
+
-
 
+
-
The initial usage of <code>value-title</code> is used to publish alternate, parsable forms of property values in a visible context without the use of the <code>abbr</code> element whose semantics already support interpretation of the 'title' attribute as an expanded, more precise form of the content.  
+
-
 
+
-
Experience has found that there are some cases in microformats where a number of publishers want to include a precisely accurate and parsable value for a property but do not want it to be visible in their page, ''even as a tooltip''.
+
-
 
+
-
For example, full [[ISO8601]] datetimes may be confusing to readers of the page (as a tooltip or when read aloud by a screen reader), and enumerated values such as the <code>type</code> subproperty of hCard's <code>tel</code> property use US-English terms, which are not part of pages in any other language.
+
-
 
+
-
Since both of those scenarios have shown to be obstacles for a number of publishers, for these cases, and these alone, there exists a further extension of value-excerption. This extension allows the parsable form of the property to be published ‘silently’ in an ''empty'' element immediately adjacent with the respective local visible content.
+
-
 
+
-
Here is an example, with the required use of a first child element with class name <code>value-title</code>:
+
-
 
+
-
<source lang=html4strict>
+
-
<p class='tel' lang='en-gb'>
+
-
  <span class='type'>
+
-
    <span class='value-title' title='cell'> </span>
+
-
    mobile
+
-
  </span>
+
-
  <span class='value'>+44 7773 000 000</span>
+
-
</p>
+
-
</source>
+
-
 
+
-
'''Note:''' the <code>&lt;span class='value-title' title='cell'> &lt;/span></code> span is deliberately empty (just has a space between the open and close tags) so that it doesn't take up any space and therefore can't show a tooltip.
+
-
 
+
-
The <samp>cell</samp> value is parsed for the 'type' subproperty, but <samp>mobile</samp> is presented to the user.
+
-
 
+
-
In the case of dates:
+
-
 
+
-
<source lang=html4strict>
+
-
<p class='dtstart'>
+
-
  <span class='value-title' title='2009-03-14T16:28-0600'> </span>
+
-
  March 14th 2009, around half-past four
+
-
</p>
+
-
</source>
+
-
 
+
-
A microformats parser will read the ISO8601 format datetime <samp>2009-03-14T16:28-0600</samp>, but users will only see <samp>March 14th 2009, around half-past four</samp>. Testing has shown that the ISO8601 datetime above does not get exposed to any user at all.
+
-
 
+
-
===Parsing machine-data <code>value-title</code>===
+
-
 
+
-
Browsers collapse the <code>value-title</code> span down to a width of <code>0</code>, effectively providing no visual rendering, whilst keeping the element in the DOM. With no physical dimensions, there is no ‘hover’ state, so no tooltip is revealed. Furthermore, the empty element is not passed to assistive technology layers such as VoiceOver. Screen readers do not read the contents of the title attribute of an empty <code>span</code> element.
+
-
 
+
-
We conducted [[value-excerption-value-title-test|thorough testing]] of these parsing behaviors to ensure accessibility.
+
-
 
+
-
''Note: Whilst the <code>value-title</code> element is more gracefully written without whitespace inner-text (or as self-closing <code>&lt;foo /></code> element in XHTML), some tools such as WYSIWYG editors and HTML-Tidy will erroneously discard such elements, resulting in parsable data being thrown away by some tools. As such, <code>&lt;span class='value-title'> &lt;/span></code>, including a single whitespace character between the opening and closing tag, may also be used. In some situations, this whitespace may be rendered by the browser, and authors should test their output.''
+
-
 
+
-
Parsing this final <code>value-title</code> extension imposes some stricter restrictions on usage. These restrictions exist to reduce the impact of <abbr title="Don't Repeat Yourself">DRY</abbr> violations, reduce the opportunity for sites to spoof data, and encourage best practice for maintaining both forms of data accurately.
+
-
 
+
-
Where an element with class <code>value-title</code> is to be parsed as data for a property, and that element also contains no non-whitespace content (hereafter referred to as ‘empty’), the following rules apply:
+
-
 
+
-
* The ‘empty’ value-title element must be the '''first, non-whitespace child''' of the property element. That is, it should follow immediately after the property is declared, before the human-readable form, and without any additional nesting.
+
-
* The ‘empty’ value-title element can only be used for specific properties. Future microformat specifications (and updates to existing microformats) must explicitly state which properties may be used with this extension of the value-class-pattern. (Retroactive property support for existing microformats is documented below.)
+
-
* Where an ‘empty’ value-title element is to be used as the single property value, it must be the ''only'' such <code>value</code> content. That is, the first instance of a conforming <code>value-title</code> element overrides all other <code>value</code> and <code>value-title</code> siblings and/or cousins.
+
-
* Tools written to perform Conformance Testing 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 forms do not match.
+
-
 
+
-
=== limited use of value-title ===
+
-
Due to the fact 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, there are two microformats [[principles]] being compromised: '''visibility''' and '''<abbr title="Don't Repeat Yourself">DRY</abbr>'''. Thus the applicability of this pattern is deliberately restricted to properties that have demonstrated through experience a need for it, with no known better alternative.
+
-
 
+
-
In general authors should:
+
-
 
+
-
# First, try to directly specify microformats property values inline (the most visible, no duplication),
+
-
# Then consider using the value-class pattern
+
-
## Including multiple value elements for date and time properties
+
-
# and then only if those methods are insufficient, consider the value-title pattern.
+
-
 
+
-
This document post-dates other microformat specifications, such that they may not yet indicate which properties permit use of this pattern. In the interim, '''only''' the following types of properties should allow the value-title pattern.
+
-
 
+
-
* ISO8601 date, datetime, timezone, and duration values
+
-
* Enumerated values (such as the hCard tel/email/adr 'type' subproperties)
+
-
* Co-ordinates (such as the [[geo]] 'latitude' and 'longitude' properties)
+
-
* Telephone number properties (e.g. the hCard 'tel' property)
+
-
 
+
-
The [[machine-data]] page has documentation of some of the properties of some specs which experience has shown need a solution like the value-title pattern.
+
-
 
+
-
There are some simple reference examples and tests for this pattern on [[value-class-pattern-tests]].
+
-
* Note: [[value-class-pattern-tests#to_do_value-title_test_pages|to do value-title test pages]]
+
-
 
+
-
In future use, ''specification authors'' may inherit use of <code>value-title</code> by use of ISO8601 date and time formats, or reuse of other microformats, but specifications should _avoid_ introducing new data structures that depend on or encourage this pattern. New specifications are themselves expected to adhere to the principals of visible data and <abbr>DRY</abbr>.
+
-
 
+
-
== Test cases ==
+
-
See [[value-class-pattern-tests]].
+
-
 
+
-
== <abbr title='Frequently Asked Questions'>FAQ</abbr>==
+
-
This section is '''informative'''.
+
-
 
+
-
Frequently asked questions about the value-class-pattern. Once this section grows too big, we'll make a separate wiki page (like [[value-class-faq]]).
+
-
 
+
-
<div class='discussion'>
+
-
* '''Is the value-class pattern supported by any of the microformats tools?'''
+
-
** '''A: Yes'''. See the [[value-class-pattern#Implementations|implementations]] section.
+
-
* '''Why use an 'empty' element? Why not embed data in the class attribute?'''
+
-
** '''A: 'class' is for field names, not data.''' The class attribute is inappropriate for embedded data values, as per the HTML4 specification, which states <code>class</code> is for ‘general purposing processing’, which is defined as ‘e.g. for identifying fields when extracting data from HTML pages into a database, translating HTML documents into other formats, etc.. ‘General purpose processing’ does not extend to data itself. Furthermore, this method avoids inventing a new string pattern for embedding data.
+
-
* '''Why use an 'empty' element? Why not make up a new attribute, like ‘data’?'''
+
-
** '''A: New attributes are invalid.''' Microformats exist and function in ''valid'' HTML. Those are the current standards for web development, and microformats exist for use ''now''. In the future, perhaps revisions of HTML will offer up another solution. For now, this method has been tested against browsers, and creates a consistent document structure (where machine-form and human-form data are siblings).
+
-
* '''Shouldn't the <code>title</code> attribute only be used for content?'''
+
-
** '''A: 'title' is used for content, machine readable content.''' The <code>title</code> attribute ''is'' used for content and is read by microformats parsers. This exists for cases where data cannot be parsed with sufficient precision from just the commonly published, visible information. This pattern allows both forms of content to be included, whilst keeping it invisible to human consumers.
+
-
</div>
+
-
 
+
-
You can also refer to the general [[faq|Microformats FAQ]] and [[principles]].
+
-
 
+
-
== Examples in the wild ==
+
-
This section is '''informative'''.
+
-
 
+
-
The following sites and pages have started marking up content with the value-class-pattern, and are thus good places to go for examples with real world content to test with implementations (i.e. parsers). If you use the value-class-pattern in your content, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page (like [[value-class-examples-in-wild]]).
+
-
<!--
+
-
 
+
-
    add new items to the TOP of this list
+
-
 
+
-
-->
+
-
* [http://tantek.com Tantek's site] uses date and time value separation with nested [[HTML5]] &lt;time&gt; elements for the separate date and time values in his hAtom "dtpublished" properties.
+
-
* [http://visitmix.com/labs/oomph/2.0/tests/test.html Test Harness For Oomph] This pages uses a whole range of different patterns for both hCard and hCalendar, using both value and value-title, mostly derived from the specification above
+
-
* [http://georgebrock.com/ George Brocklehurst's activity stream] and [http://blog.georgebrock.com/ blog] use "value-title" for hAtom <code>published</code> property
+
-
* [http://ben-ward.co.uk/ Ben Ward's home page] uses:
+
-
** "value-title" for hCard <code>bday</code> property
+
-
** "value-title" for hAtom <code>updated</code> property
+
-
* [http://microformats.org/ microformats.org] uses:
+
-
** "value-title" for hAtom <code>updated</code> property in [http://microformats.org/ microformats.org blog posts]
+
-
** date and time value separation for hCalendar <code>dtstart</code> property in [[events|microformats.org recent and upcoming events wiki page]]
+
-
 
+
-
''Add your site/page(s) that use the value-class-pattern here, along with a brief description of what value-class-pattern features you use, with which microformat(s) and which of its/their properties.''
+
-
 
+
-
== Implementations ==
+
-
This section is '''informative'''.
+
-
 
+
-
The following implementations have been developed which either generate or parse value-class-pattern property values. If you have an value-class-pattern implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page (like [[value-class-implementations]]).
+
-
<!--
+
-
 
+
-
    add new items to the TOP of this list
+
-
 
+
-
-->
+
-
 
+
-
=== consuming and parsing tools ===
+
-
* [[Google]] parses <code>value-title</code> as part of their [http://googlewebmastercentral.blogspot.com/2010/01/introducing-new-rich-snippets-format.html support for hCalendar rich snippets], as documented specifically in the [https://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=164506 microformats example for rich snippet events].
+
-
* [[Oomph]] Version 2 passes [[value-class-pattern-tests#Date_and_time_values|Date and time values test cases]] and is a thorough implementation of the value class pattern.
+
-
* [[X2V]] v0.9.3 and later:
+
-
** implements [[#Date_and_time_values|Date and time values parsing]], including am/pm time values
+
-
*** thus passes [[value-class-pattern-tests#Date_and_time_values|Date and time values test cases]].
+
-
** implements [[#hCalendar_dtend_implied_date|hCalendar implied dtend date]]
+
-
* [[Operator]] has *some* implementation of the value-class-pattern according to Michael Kaply, but precisely how much is implemented, for which properties (property types) and which microformats is not currently known.
+
-
* [[Optimus]] v0.8 and later implements <code>value-title</code> as [http://twitter.com/DmitryBaranovsk/status/1891253248 announced by Dmitry Baranovskiy].
+
-
* HTML::Microformats and its predecessors support <code>value</code> excerpting. HTML::Microformats (though not its predecessors) supports <code>value-title</code>.
+
-
 
+
-
=== publishing tools ===
+
-
* [http://getk2.com/ K2] (WordPress Theme) is using "value-title" for the hAtom published property. [http://code.google.com/p/kaytwo/issues/detail?id=832]
+
-
 
+
-
== Background ==
+
-
The value class pattern is derived from [[hCard#Value_excerpting|value-excerpting]] in hCard.
+
-
 
+
-
Sometimes, only a part of an element's content is to be used as the value of a microformat property. This may occur when a property has optional subproperties, such as <code>tel: type</code> and <code>tel: value</code> in [[hCard]]. Other times, the most appropriate structure for a property may include other content.
+
-
 
+
-
== Articles ==
+
-
This section is '''informative'''.
+
-
 
+
-
Articles and <span id="Blog_Posts">blog posts</span>  discussing the value class pattern, most recent first.
+
-
When this section gets too big, create a separate page like: [[value-class-pattern-articles]]
+
-
* <span class="hentry"><span class="published">2009-08-25</span> <span class="entry-summary">MIX Online: <span class="entry-title">[http://visitmix.com/Articles/The-Value-Class-Pattern The Value Class Pattern]</span></span> by <span class="author vcard"><span class="fn">Jeremy Keith</span></span></span>
+
-
* [http://ablognotlimited.com/articles/getting-semantic-with-microformats-part-8-value-class-pattern Getting Semantic With Microformats, Part 8: Value Class Pattern] -- A very thorough writeup by Emily Lewis on the value class pattern
+
-
* [http://adactio.com/journal/1579/ 2009-05-17 Adactio: Microformation]
+
-
* [http://forabeautifulweb.com/blog/about/value_class_pattern/ For A Beautiful Web: Value Class Pattern]
+
-
* <span class="hentry"><span class="published">2009-05-12</span> <span class="entry-title">notizblog.org: [http://notizblog.org/2009/05/12/microformats-value-class-pattern/ Microformats: Value Class Pattern]</span> by <span class="author vcard"><span class="fn">Matthias Pfefferle</span></span></span> (german)
+
-
* [http://microformats.org/blog/2009/05/12/value-class-pattern/ 2009-05-12 microformats.org: Value Class Pattern]
+
-
 
+
-
== References ==
+
-
This section is '''informative'''.
+
-
* [http://www.useit.com/alertbox/9608.html Jakob Nielsen: International Web Usability]
+
-
 
+
-
==Related Pages==
+
-
This section is '''informative'''.
+
-
 
+
-
* [[value-class-pattern-tests]]
+
-
* [[value-excerption-pattern-issues]]
+
-
* [[hcard#Value_excerpting|hCard: Value Excepting]]
+
-
* [[value-class-pattern-brainstorming]]
+
-
* [[value-excerption-pattern-brainstorming]]
+
-
* [[machine-data|Machine Data in Microformats]]
+
-
 
+
-
== Translations ==
+
-
Read the value-class-pattern specification in additional <span id="languages">languages</span>:
+
-
* [[value-class-pattern-fr|français]]
+
-
* [[value-class-pattern-ja|日本語]]
+

Revision as of 23:35, 3 April 2013

MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH. MAKE GOD DO WHAT I WANT.MAKE ALLAH DO WHAT I WANT.PUT I TO HEAVEN GOD.PUT I TO HEAVEN ALLAH.

value-class-pattern was last modified: Wednesday, December 31st, 1969

Views