hresume-issues

(Difference between revisions)

Jump to: navigation, search
(Issues: Adding rel-tag on 'skills' issue)
m (Issues)
Line 10: Line 10:
== Issues ==  
== Issues ==  
-
* {{OpenIssue}} 2007-06-21 raised by [[Steve Ganz]].
+
* {{OpenIssue}} 2007-06-21 raised by [[User:Steve_Ganz|Steve Ganz]].
*# ''rel-tag can be difficult to implement for "skill" ''
*# ''rel-tag can be difficult to implement for "skill" ''
*#* In Draft, version 0.1 it is required that each "skill" be marked up with rel-tag. While this is a good idea, and easy to do for individuals, it poses some challenges in the real world for large publishers of user generated resume data.  If rel-tag was optional for "skills", it would be easier to implement.  
*#* In Draft, version 0.1 it is required that each "skill" be marked up with rel-tag. While this is a good idea, and easy to do for individuals, it poses some challenges in the real world for large publishers of user generated resume data.  If rel-tag was optional for "skills", it would be easier to implement.  
Line 21: Line 21:
*#* Many job experience listings will include jobs that the person is presently working at. Ciaran McNulty [http://microformats.org/discuss/mail/microformats-discuss/2006-October/006477.html 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.
*#* Many job experience listings will include jobs that the person is presently working at. Ciaran McNulty [http://microformats.org/discuss/mail/microformats-discuss/2006-October/006477.html 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.
-
* {{OpenIssue}} 2006-10-19 raised by [[Steve Ganz]].
+
* {{OpenIssue}} 2006-10-19 raised by [[User:Steve_Ganz|Steve Ganz]].
*# ''There's currently no way to distinguish different hCard types in hResume''
*# ''There's currently no way to distinguish different hCard types in hResume''
*#* 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 subject's contact info. This proves problematic to implement because <code>address</code> 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 <code>address</code> should be used to the distinguish an hCard as the subject's contact info. This proves problematic to implement because <code>address</code> 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.

Revision as of 06:00, 22 June 2007

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.

Contents


Issues

  • Agreed, when adding my references in hCard to the bottom of my hResume it became apparent there was no way I could mark 'my' hCard as the one belonging to the subject of the hResume. Perhaps @class="hcard subject" as a child of the hResume? Ciaran McNulty

Template

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

Related Pages

Research

Previously

hResume is the classic microformats predecessor for h-resume. Work on hResume is documented at the following for historical purposes. Much of the general discussion and research likely still applies.

The hResume specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

hresume-issues was last modified: Wednesday, December 31st, 1969

Views