===== summary naming =====
* <code><summary></code> (inside <code><details></code>) ** need a more specific name. summary is too generic sounding of an element name for this special usage. Similar Moved to the problem with <code><address><[[HTML5/code> (special use - for contact information for the document, but used as a generic "address" for street addresses).** alternatively make a generic <code><summary><#summary_naming|HTML5/code> element - make it an actual summary inside <code><article></code> or <code><body></code>, as well as inside <code><details></code>. Another advantage is that this is close to the semantic of the Atom "summary" element, and the hAtom microformat 'entry-summary' property.]] * ===== expand <code><time></code> and new date/time <code><input></code> elements to be consistent and reflect more real world use cases=====** impedance match. handle the same set of year, month, date, time variants/subsets.** more inputs/times. expand both time/input Moved to handle additional real world cases*** YYYY*** --MM-DD* improve <code><time><[[HTML5/code> element to support uses analogous to the "value class pattern" date and time separation use case (compose nested <code><time><#expand_time|HTML5/code> elements into a single date and time)]]** perhaps even use a <code><===== nesting time></code> =====Moved to compose multiple nested date/time <code><input></code> elements for specific date[[HTML5/time components into a single date and#nesting_time|HTML5/or time.]]
==== lower priority improvements ====
