hresume-issues: Difference between revisions
Jump to navigation
Jump to search
Steve Ganz (talk | contribs) (→Issues: Adding contact info classification issue) |
Steve Ganz (talk | contribs) (→Issues) |
||
| Line 15: | Line 15: | ||
* {{OpenIssue}} 2006-10-19 raised by [[Steve Ganz]]. | * {{OpenIssue}} 2006-10-19 raised by [[Steve Ganz]]. | ||
*# ''There's currently no way to distinguish an hCard in hResume as the | *# ''There's currently no way to distinguish an hCard in hResume as the subject's contact info'' | ||
*#* In Draft, version 0.1 it is specified that a parent element of <code>address</code> should be used to the distinguish an hCard as the subjects contact info. This proves problematic to implement because <code>address</code> is an inline element and thus cannot contain block level elements. To avoid sacrificing semantic value by restricting the child elements of an hCard to inline elements, we need to settle on an alternate method to classify a | *#* In Draft, version 0.1 it is specified that a parent element of <code>address</code> should be used to the distinguish an hCard as the subjects contact info. This proves problematic to implement because <code>address</code> is an inline element and thus cannot contain block level elements. To avoid sacrificing semantic value by restricting the child elements of an hCard to inline elements, we need to settle on an alternate method to classify a subject's hCard as thier contact info. | ||
== Template == | == Template == | ||
Revision as of 04:20, 21 October 2006
hResume issues
These are externally raised issues about hResume with broadly varying degrees of merit. Thus some issues are 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
See related hcalendar-issues. See related hcard-issues.
Issues
- open issue! 2006-10-19 raised by RyanKing.
- There's currently no way to say 'present' in hCalendar
- Many job experience listings will include jobs that the person is presently working at. Ciaran McNulty correctly pointed out that a blank DTEND does not indicate that the event is still ongoing. We need to find an easy way to make this work in hResume.
- There's currently no way to say 'present' in hCalendar
- open issue! 2006-10-19 raised by Steve Ganz.
- There's currently no way to distinguish an hCard in hResume as the subject's contact info
- In Draft, version 0.1 it is specified that a parent element of
addressshould be used to the distinguish an hCard as the subjects contact info. This proves problematic to implement becauseaddressis an inline element and thus cannot contain block level elements. To avoid sacrificing semantic value by restricting the child elements of an hCard to inline elements, we need to settle on an alternate method to classify a subject's hCard as thier contact info.
- In Draft, version 0.1 it is specified that a parent element of
- There's currently no way to distinguish an hCard in hResume as the subject's contact info
Template
Please use this format (copy and paste this to the end of the list to add your issues):
- open issue! YYYY-MM-DD raised by YOURNAME.
- Issue 1: Here is the first issue I have.
- Issue 2: Here is the second issue I have.