abbr-design-pattern issues resolved
Jump to navigation
Jump to search
This page is for archiving resolved issues about the abbr-design-pattern that have pending actions. See:
- abbr-design-pattern-issues-closed for closed issues that have no remaining actions.
- abbr-design-pattern-issues for currently open issues.
resolved issues
Resolved issues that have further actions to take.
resolved 2008
Resolved issues that were raised in 2008.
- resolved issue 2008-01-01 raised by Andy Mabbett.
- How are empty (
title="") 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 example.- ACCEPTED.
- RESOLVED. to-do: hcard-parsing must specific how to handle to properly. Suggestion: analysis of any existing content that uses empty title attributes. If none found then simply treat it literally, that is, empty title means value for that property is also empty, though why provide the class name in that case. - Tantek
- How are empty (
- resolved issue 2008-01-01 raised by 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 example.
- ACCEPTED.
- RESOLVED. to-do: Clarify hcard-parsing and add an FAQ if necessary. - Tantek
- 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 example.
- resolved issue 2008-02-04 raised by Patrick van Aalst.