Microformats Wiki - User contributions [en]

abbr-design-pattern-issues

2008-02-04T12:44:08Z

PaTrick: /* Issues */

<h1>abbr design pattern issues</h1>

These are externally raised issues about [[abbr-design-pattern]] with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.



Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

__TOC__

== Issues ==

* {{OpenIssue}} 2008-02-04 raised by [[User:PaTrick|Patrick van Aalst]].
*# The <nowiki><ABBR></nowiki> tag is not supported by IE6; to style it, you'll need to include extra html, for example: <nowiki><abbr title="2008-01-16T15:00:00-01:00"><span class="dtstart">16 januari 2008</span></abbr></nowiki>.

* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett|Andy Mabbett]].
*# Abbreviations in the middle of microformat element values should be parsed. e.g for <code><nowiki><span class="street-address">New John <abbr title="Street">St.</abbr> West</span></nowiki></code>, both Operator and X2V return, at the time of writing, vCards containing "New John St. West", not the expected "New John Street West". Data is thus being lost. See [http://www.westmidlandbirdclub.com/test example].

* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett|Andy Mabbett]].
*# How are empty (<code>title=""</code>) title attributes to be parsed? At the time of writing, X2V returns a null value; Operator uses the content of the abbr element. Such mark-up is valid, but semantically illogical. The former parser behaviour seems the most logical, but results in an invalid vCard. See [http://www.westmidlandbirdclub.com/test example].

* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett|Andy Mabbett]].
*# How are missing title attributes to be parsed? This is both valid and semantically-meaningful mark-up (the content is an abbreviation, but we know not of what) At the time of writing, X2V and Operator both use the content of the abbr element; this seems sensible, and should, perhaps, be ratified in the spec. See [http://www.westmidlandbirdclub.com/test example].

* See also [[accessibility-issues#abbr-design-pattern]].

== Template ==
Please use this format (copy and paste this to the end of the list to add your issues):

* {{OpenIssue}} YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
*# Issue 1: Here is the first issue I have.
*# Issue 2: Here is the second issue I have.

== Resolved Issues ==
Issues that are resolved but may have outstanding [[to-do]] items.

== Closed Issues ==
Resolved issues that have no further actions to take.
* ...

== See Also ==
* [[abbr-design-pattern]]
* [[accessibility-issues]]
* [[dfn-design-pattern]] (proposal)

abbr-design-pattern-issues

2008-02-04T12:43:48Z

PaTrick: /* Issues */

<h1>abbr design pattern issues</h1>

These are externally raised issues about [[abbr-design-pattern]] with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.



Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

__TOC__

== Issues ==

* {{OpenIssue}} 2008-02-04 raised by [[User:PaTrick|Patrick van Aalst]].
*# The <nowiki><ABBR></nowiki> tag is not supported by IE6; to style it, you'll need to include extra html, for example: <abbr title="2008-01-16T15:00:00-01:00"><span class="dtstart">16 januari 2008</span></abbr>.

* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett|Andy Mabbett]].
*# Abbreviations in the middle of microformat element values should be parsed. e.g for <code><nowiki><span class="street-address">New John <abbr title="Street">St.</abbr> West</span></nowiki></code>, both Operator and X2V return, at the time of writing, vCards containing "New John St. West", not the expected "New John Street West". Data is thus being lost. See [http://www.westmidlandbirdclub.com/test example].

* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett|Andy Mabbett]].
*# How are empty (<code>title=""</code>) title attributes to be parsed? At the time of writing, X2V returns a null value; Operator uses the content of the abbr element. Such mark-up is valid, but semantically illogical. The former parser behaviour seems the most logical, but results in an invalid vCard. See [http://www.westmidlandbirdclub.com/test example].

* {{OpenIssue}} 2008-01-01 raised by [[User:AndyMabbett|Andy Mabbett]].
*# How are missing title attributes to be parsed? This is both valid and semantically-meaningful mark-up (the content is an abbreviation, but we know not of what) At the time of writing, X2V and Operator both use the content of the abbr element; this seems sensible, and should, perhaps, be ratified in the spec. See [http://www.westmidlandbirdclub.com/test example].

* See also [[accessibility-issues#abbr-design-pattern]].

== Template ==
Please use this format (copy and paste this to the end of the list to add your issues):

* {{OpenIssue}} YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
*# Issue 1: Here is the first issue I have.
*# Issue 2: Here is the second issue I have.

== Resolved Issues ==
Issues that are resolved but may have outstanding [[to-do]] items.

== Closed Issues ==
Resolved issues that have no further actions to take.
* ...

== See Also ==
* [[abbr-design-pattern]]
* [[accessibility-issues]]
* [[dfn-design-pattern]] (proposal)