A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).


From WHATWG Wiki
Revision as of 19:11, 9 December 2007 by Hsivonen (talk | contribs) (Docs for vague times in attributes)
Jump to navigation Jump to search

The purpose of this page is to enable collaborative creation of brief advisory text for each HTML5 microsyntax so that when an attribute value does not conform to a given microsyntax, a validator can display the advisory text about the syntax to guide the author to fix the value. Note that like the rest of this wiki, editing requires you to agree to release your contributions under the MIT license (see wiki footer). Please note that while copying text from the WHATWG version of HTML 5 is OK, copying text from RFCs or W3C specs is not OK.

Note that some formats pertain to Web Forms 2.0 (e.g. datetime-local).

Please keep descriptions short: one paragraph in length.


A browsing context name is any string that does not start with an underscore (_), or, a string that case-insensitively matches one of: _self, _parent, or _top.


(form accept-charset value)


A circle is specified as three comma-separated (no spaces allowed) integers the last one of which is non-negative. An integer consists of one or more digits (09), optionally preceded by a hyphen (-). Examples of circles: 5,5,10 and -5,0,20


An ISO 8601 date, i.e. YYYY-MM-DD. Example: 2002-09-29.


An ISO 8601 date (i.e. YYYY-MM-DD.), time (i.e. hh:mm optionally followed by :ss optionally followed by . and digits) optionally with a time zone designator (i.e. either Z, +hh:mm or -hh:mm) or both separated by a T or a white space character. The separator may be surrounded by whitespace.


(time element text content version)


An ISO 8601 date and time in the UTC time zone, i.e. YYYY-MM-DDThh:mm optionally followed by :ss for the seconds, optionally followed by . and one or more digits for the fraction of a second, and finally followed by Z. Examples: 1996-01-01T12:05Z, 1996-01-01T12:05:25.6Z.


An ISO 8601 date and time with no time zone information, i.e. YYYY-MM-DDThh:mm optionally followed by :ss for the seconds, optionally followed by . and one or more digits for the fraction of a second. Examples: 1996-01-01T12:05, 1996-01-01T12:05:25.6.


(This format deviates from the spec draft.) An ISO 8601 date and time with a time zone designator, i.e. YYYY-MM-DDThh:mm:ss optionally followed by . and one or more digits for the fraction of a second, and finally followed by either Z, +hh:mm or -hh:mm. Examples: 1996-01-01T12:05:25Z, 1996-01-01T12:05:25.6+02:00.


An e-mail address must match the addr-spec production defined in RFC 2822 section 3.4.1 excluding the CFWS production everywhere and excluding the FWS production everywhere except in the quoted-string production.








(WF2 float)


(positive WF2 float)




An ID consists of at least one character but must not contain any whitespace.


One or more digits (09), optionally preceded by a hyphen (-). For example: 42 and -273 are valid, but +42 is not.


One or more digits (09). For example: 42 and 0 are valid, but -273 is not.


One or more digits (09), with at least one which is non-zero. For example: 42 is valid, but 00 is not.


An absolute URL. For example: http://example.org/hello, but not /hello.


Any URL. For example: /hello, #canvas, or http://example.org/.


An RFC 4646 language tag consists of hyphen-separated ASCII-alphanumeric subtags. There is a primary tag identifying a natural language by its shortest ISO 639 language code (e.g. en for English) and zero or more additional subtags adding precision. The most common additional subtag type is a region subtag which most commonly is a two-letter ISO 3166 country code (e.g. GB for the United Kingdom). IANA maintains a registry of permissible subtags.




(RFC2616 version)




An ISO 8601 date with year and month, i.e. YYYY-MM. Example: 2007-11.






(progress content)




A time (hour, minute, seconds, fractional seconds) is encoded according to ISO 8601 with no time zone: two digits (09) for the hour, a colon, two digits for the minute, optionally a colon and two digits for the second, and optionally (if the seconds are present) a period (.) and one or more digits for the fraction of a second. All the numbers must be in base ten and zero-padded if necessary. For instance: 23:59:00.00000 or 00:00:05.


A week consists of a year and a week number encoded according to ISO 8601: four or more digits (09) representing the year, a hyphen (-), a literal W, and two digits for the week, zero-padded if necessary. The week number must be a number greater than or equal to 01. Week 01 of a given year is the week containing the 4th of January; weeks start on Monday. For instance: 2005-W52 is the week that ended on Sunday the first of January, 2006.