Talk:MetaExtensions

2008-10-10T01:46:14Z

Rfc2549: /* "description" meta name */ update

== "description" meta name ==
I think the description name should be added to the HTML 5 specifications. Yes, search engines have made the keywords name obsolete. However search engines are not ''that'' good. It is still only the document author that can provide a reliable, short description of the documents contents. I think there should be constrains on how long, what it contains, and the structure of the description. Short sentences, and plain English descriptions would be the best.
:It looks like "description" is in the latest specification. [[User:Rfc2549|Rfc2549]] 01:46, 10 October 2008 (UTC)

OpenIssues

2008-10-10T01:39:51Z

Rfc2549: OpenIssues moved to Open issues: fix title

#REDIRECT [[Open issues]]

Open issues

2008-10-10T01:39:51Z

Rfc2549: OpenIssues moved to Open issues: fix title

There are quite a few places in HTML5 that have issue boxes. This page lists the remaining items that are not yet included into the main specification properly:

* Ruby (http://www.w3.org/TR/ruby/)
* Rendering
* Forms (Web Forms 2.0)

If enough experience is gained on time the following features will be looked at as well:

* SVG and MathML support in the HTML syntax
* Extensibility in HTML

There are several other features considered for future versions of HTML:

* ECMAScript Threading API (based on Google Gears WorkerPool)
* API for 3D immediate mode graphics

MicrosyntaxDescriptions

2008-10-10T01:37:19Z

Rfc2549: /* date */ clarify: that's not the only ISO 8601 format

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 [http://www.whatwg.org/specs/web-apps/current-work/ 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. <code>datetime-local</code>).

Please keep descriptions short: one paragraph in length.

==browsing-context==
A browsing context name is any string that does not start with an underscore (<code>_</code>).

==browsing-context-or-keyword==
A browsing context name or keyword is either any string that does not start with an underscore (<code>_</code>) or a string that case-insensitively matches one of: <code>_blank</code>, <code>_self</code>, <code>_parent</code>, or <code>_top</code>.

==charset==

The IANA maintain a [http://www.iana.org/assignments/character-sets list of registered encoding names]. Example: <code>utf-8</code>

==charset-list==
(form accept-charset value)

==circle==
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 (<code>0</code>–<code>9</code>), optionally preceded by a hyphen (<code>-</code>). Examples of circles: <code>5,5,10</code> and <code>-5,0,20</code>

==date==
An ISO 8601 date, for example in the format <code>YYYY-MM-DD</code>. Example: <code>2002-09-29</code>.

==date-or-time==
(''[http://canvex.lazyilluminati.com/misc/cgi/issues.cgi/folder/microsyntaxes-dates This format deviates from the spec draft.]'') An ISO 8601 date (i.e. <code>YYYY-MM-DD</code>.), time (i.e. <code>hh:mm</code> optionally followed by <code>:ss</code> optionally followed by <code>.</code> and digits) optionally with a time zone designator (i.e. either <code>Z</code>, <code>+hh:mm</code> or <code>-hh:mm</code>) or both date and time separated by <code>T</code>. Examples: <code>1996-01-01T12:05:25</code>, <code>1996-01-01</code>, <code>12:05:25</code>, <code>1996-01-01T12:05:25.6-02:00</code>

==date-or-time-content==
(''[http://canvex.lazyilluminati.com/misc/cgi/issues.cgi/folder/microsyntaxes-dates This format deviates from the spec draft.]'') An ISO 8601 date (i.e. <code>YYYY-MM-DD</code>.), time (i.e. <code>hh:mm</code> optionally followed by <code>:ss</code> optionally followed by <code>.</code> and digits) optionally with a time zone designator (i.e. either <code>Z</code>, <code>+hh:mm</code> or <code>-hh:mm</code>) or both date and time separated by <code>T</code> or a Unicode space class character. Unicode space class (Zs) characters are allowed around the components (date, time, time zone designator). Examples: <code>1996-01-01 12:05:25</code>, <code>1996-01-01</code>, <code>12:05:25</code>, <code>1996-01-01 T 12:05:25.6 -02:00</code>

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

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

==datetime-tz==
(''[http://canvex.lazyilluminati.com/misc/cgi/issues.cgi/folder/microsyntaxes-dates This format deviates from the spec draft.]'') An ISO 8601 date and time with a time zone designator, i.e. <code>YYYY-MM-DDThh:mm:ss</code> optionally followed by <code>.</code> and one or more digits for the fraction of a second, and finally followed by either <code>Z</code>, <code>+hh:mm</code> or <code>-hh:mm</code>. Examples: <code>1996-01-01T12:05:25Z</code>, <code>1996-01-01T12:05:25.6+02:00</code>.

==email==
An e-mail address must match the <code>addr-spec</code> production defined in [http://tools.ietf.org/html/rfc2822#section-3.4.1 RFC 2822 section 3.4.1] excluding the <code>CFWS</code> production everywhere and excluding the <code>FWS</code> production everywhere except in the <code>quoted-string</code> production.

==float==
A floating point number consists of one of more digits (<code>0</code>–<code>9</code>), optionally with a single point (<code>.</code>) somewhere (either before these numbers, in between two numbers, or after the numbers), all optionally prefixed with a hyphen (<code>-</code>). Examples: <code>42</code>, <code>.42</code>, <code>-4.2</code>

==float-non-negative==
...
==float-positive==
...
==float-exp==
(WF2 float)

==float-exp-positive==
(positive WF2 float)

==hash-name==
...

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

==integer==
One or more digits (<code>0</code>–<code>9</code>), optionally preceded by a hyphen (<code>-</code>). For example: <code>42</code> and <code>-273</code> are valid, but <code>+42</code> is not.

==integer-non-negative==
One or more digits (<code>0</code>–<code>9</code>). For example: <code>42</code> and <code>0</code> are valid, but <code>-273</code> is not.

==integer-positive==
One or more digits (<code>0</code>–<code>9</code>), with at least one which is non-zero. For example: <code>42</code> is valid, but <code>00</code> is not.

==iri==
An absolute URL. For example: <code><nowiki>http://</nowiki>example.org/hello</code>, but not <code>/hello</code>.

==iri-ref==
Any URL. For example: <code>/hello</code>, <code>#canvas</code>, or <code><nowiki>http://</nowiki>example.org/</code>.

==language==
An [http://tools.ietf.org/html/rfc4646 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. <code>en</code> 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. <code>GB</code> for the United Kingdom). IANA maintains a [http://www.iana.org/assignments/language-subtag-registry registry of permissible subtags].

==media-query==
...

==meta-charset==

A legacy encoding declaration consists of <code>text/html;</code>, optionally followed by whitespace, followed by <code>charset=</code>, followed by an encoding name. The IANA maintain a [http://www.iana.org/assignments/character-sets list of registered encoding names]. Example: <code>text/html; charset=utf-8</code>

==mime-type==
(RFC2616 version)
==mime-type-list==
(WF2)

==month==
An ISO 8601 date with year and month, i.e. <code>YYYY-MM</code>. Example: <code>2007-11</code>.

==pattern==
(WF2)

==polyline==
...

==ratio==
(progress content)

==rectangle==
...

==time==
A time (hour, minute, seconds, fractional seconds) is encoded according to ISO 8601 with no time zone: two digits (<code>0</code>–<code>9</code>) 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 (<code>.</code>) 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: <code>23:59:00.00000</code> or <code>00:00:05</code>.

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

[[Category:Validator.nu Documentation]]

WHATWG Wiki - User contributions [en]

Talk:MetaExtensions

OpenIssues

Open issues

MicrosyntaxDescriptions