hresume-issues

(Difference between revisions)

Jump to: navigation, search
(Using a date that's far ahead in the future for practical use)
m
Line 26: Line 26:
*#* 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.
*#* Any solution should also be a valid hCalendar, which makes things even more difficult.  One possible solution would be to use an event without a DTEND for the current period of employment but have some extra class that indicates that within the semantics of hResume it's an ongoing event and let the hCalendar version just indicate the start of the employment. --[[User:CiaranMc|Ciaran McNulty]]
*#* Any solution should also be a valid hCalendar, which makes things even more difficult.  One possible solution would be to use an event without a DTEND for the current period of employment but have some extra class that indicates that within the semantics of hResume it's an ongoing event and let the hCalendar version just indicate the start of the employment. --[[User:CiaranMc|Ciaran McNulty]]
-
*#* Although not the best solution, for the time being, a date far ahead in the future (e.g., 2049-12-31) may have practical use (Note: Google Calendar can handle up to but not including year 2050)
+
*#* Although not the best solution, for the time being, a date far ahead in the future (e.g., 2049-12-31) may have practical use (Note: Google Calendar can handle up to but not including year 2050) -- --[[User:Csarven|Csarven]] 21:34, 18 November 2008 (UTC)
* {{OpenIssue}} 2006-10-19 raised by [[User:Steve_Ganz|Steve Ganz]].
* {{OpenIssue}} 2006-10-19 raised by [[User:Steve_Ganz|Steve Ganz]].

Revision as of 21:34, 18 November 2008

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

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>

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