date-design-pattern

(Difference between revisions)

Jump to: navigation, search
(Specificity: New section, add note about dates without months and days.)
Line 54: Line 54:
Concerns have raised about accessibility issues [http://www.webstandards.org/2007/04/27/haccessibility/] with the [[datetime-design-pattern]] when it is used in conjunction with the [[abbr-design-pattern]]. These concerns are significantly lessened with the [[date-design-pattern]] as only dates, rather than full datetimes, are represented
Concerns have raised about accessibility issues [http://www.webstandards.org/2007/04/27/haccessibility/] with the [[datetime-design-pattern]] when it is used in conjunction with the [[abbr-design-pattern]]. These concerns are significantly lessened with the [[date-design-pattern]] as only dates, rather than full datetimes, are represented
 +
== Specificity ==
 +
 +
ISO 8601 and W3CDTF (but not RFC 3339) allow less specific dates, excluding the day and month. e.g. "2008-09" (September 2008) or "2008" (the year 2008). It is unclear whether the date pattern is ''intended'' to allow such dates, but certainly most microformat parsers seem to support them.
== See Also ==
== See Also ==

Revision as of 08:38, 4 September 2008

This page is a draft.

Contents

Date Design Pattern

This is a page for exploring a date design pattern. This pattern is a subset of the datetime-design-pattern.

Purpose

Use the date-design-pattern to make dates that are human readable also formally machine readable.

Practical Need

The datetime-design-pattern arose as a result of solving the practical need for human readable dates for hCalendar. While concerns have been raised about the readability of complete datetimes, those concerns don't apply for date stamps that do not include time or timezone information.

The date design pattern provides an internationalized way of representing dates. For example, the string 02/03/01 could represent February 3rd 2001, March 2nd 2001 or even March 1st 2002 depending on the cultural context. The string 2001-03-02 is less ambiguous.

How to use it

The full datetime-design-pattern has the format:

YYYY-MM-DDTHH:MM:SS+ZZ:ZZ

The date design pattern, which is a subset of the datetime design pattern, has the format:

YYYY-MM-DD

The date design pattern can be used like any other value that uses the class-design-pattern:

<span class="foo">YYYY-MM-DD</span>

The date design pattern can also be used in combination with the abbr-design-pattern where authors want to provide an alternative representation of the date:

<abbr class="foo" title="YYYY-MM-DD">Date</abbr>

As with the datetime design pattern, the date design pattern is based on the ISO8601 standard. This standard allows for dates to be written without dashes (YYYYMMDD). This usage is strongly discouraged when publishing microformats as it significantly reduces the readability of the date.

Current uses

This pattern can be used in hCalendar for:

In hCard the date design pattern can be used for:

This pattern can be used in hReview for:

Accessibility issues

Concerns have raised about accessibility issues [1] with the datetime-design-pattern when it is used in conjunction with the abbr-design-pattern. These concerns are significantly lessened with the date-design-pattern as only dates, rather than full datetimes, are represented

Specificity

ISO 8601 and W3CDTF (but not RFC 3339) allow less specific dates, excluding the day and month. e.g. "2008-09" (September 2008) or "2008" (the year 2008). It is unclear whether the date pattern is intended to allow such dates, but certainly most microformat parsers seem to support them.

See Also

date-design-pattern was last modified: Wednesday, December 31st, 1969

Views