abbr-design-pattern-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (cotroc)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
cgetoloc
{{DISPLAYTITLE:abbr design pattern 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.  
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.  
Line 6: Line 5:
<!-- '''IMPORTANT''': Please read the [[abbr-design-pattern-faq|abbr-design-pattern FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. -->
<!-- '''IMPORTANT''': Please read the [[abbr-design-pattern-faq|abbr-design-pattern FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. -->


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]
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.
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__
== Closed Issues ==
Resolved issues that have no further actions to take.
* See [[abbr-design-pattern-issues-closed]].
 
== Resolved Issues ==
Resolved issues that have outstanding [[to-do]] items.
* See [[abbr-design-pattern-issues-resolved]].


== Issues ==
== Issues ==
 
No open issues currently.
 
* {{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 behavior 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].
 
* {{OpenIssue}} 2008-05-14 raised by [[User:LeeJordan|Lee Jordan]].
*# Search Engines indexing pages using abbr-design-design pattern may expand the title attribute in the text indexed for the description part of the search result. An example from a recent page created which was indexed by Google and included a hCalendar event marked up with the class dtstart: 2008-04-2121st April 2008. Notice the lack of white space between the dates? Perhaps search engines work in a similar way as assistive technology like screen readers in expanding abbreviations but but fail to add brackets around the abbreviation text or fail to suppress one or the other.
** Please supply an example in the wild to further determine/confirm this is an issue with the mark-up/spider/search engine
 
* See also [[accessibility-issues#abbr-design-pattern]].


== Template ==
== Template ==
Please use this format (copy and paste this to the end of the list to add your issues):
{{issues-format}}
 
* {{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 ==
== See Also ==
* [[abbr-design-pattern]]
* [[abbr-design-pattern]]
* [[abbr-design-pattern-issues-closed]]
* [[abbr-design-pattern-issues-resolved]]
* [[accessibility-issues]]
* [[accessibility-issues]]
* [[dfn-design-pattern]] (proposal)
* [[dfn-design-pattern]] (proposal)

Latest revision as of 16:20, 18 July 2020


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. — 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.

Closed Issues

Resolved issues that have no further actions to take.

Resolved Issues

Resolved issues that have outstanding to-do items.

Issues

No open issues currently.

Template

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter. 

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>

See Also

Retrieved from "http://microformats.org/wiki/index.php?title=abbr-design-pattern-issues&oldid=69526"