|
|
| (112 intermediate revisions by 30 users not shown) |
| Line 1: |
Line 1: |
| = hCalendar Issues =
| | {{DISPLAYTITLE:hCalendar issues}} |
| | __TOC__ |
| | These are externally raised issues about [[hcalendar|hCalendar]] 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. |
|
| |
|
| These are externally raised issues about [[hcalendar|hCalendar]] 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. — [http://tantek.com/log/ Tantek]
| | '''IMPORTANT''': Please read the [[hcalendar-faq|hCalendar FAQ]] and the [[hcalendar-issues-resolved|hCalendar resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. |
|
| |
|
| See related [[hcard-issues]].
| | 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. — [[User:Tantek|Tantek]] |
|
| |
|
| == Issues ==
| | For matters relating to the iCalendar specification itself, see [[icalendar-errata]] and [[icalendar-suggestions]]. |
|
| |
|
| Please use this format:
| | See related [[hcard-issues]]. |
| * YYYY-MM-DD raised by AUTHORNAME
| |
| *# ''Issue 1: Here is the first issue I have.''
| |
| *# ''Issue 2: Here is the second issue I have.''
| |
|
| |
|
| | == closed issues == |
| | See: [[hcalendar-issues-closed]]. |
|
| |
|
| * 2005-07-21 raised by Neil Jensen
| | == resolved issues == |
| *# should we create a vfreebusy class for HTML representations of freebusy data? Discussion [http://www.ifreebusy.com/cyclical/blog/calendar/3.html here].
| | Issues that are <span id="Resolved_Issues">resolved</span> but may have outstanding [[to-do]] items. See: [[hcalendar-issues-resolved]]. |
|
| |
|
| * 2005-07-11 raised by Kragen
| | == Issues == |
| *# ''The specification of class="url" as <a href="..."> should be a "should", not a "must". Other ways of referencing the event URL, such as <iframe src="..."> and <embed src="...">, shoul be mentioned. At present X2V doesn't appear to handle them. This came up in a discussion about [[xfolk|xFolk]].''
| | Please add new issues to the '''bottom''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted. |
|
| |
|
| * 2005-06-21 raised by Hixie
| | === issues 20010 === |
| *# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCalendars must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content? | | <div class="hentry"> |
| | {{OpenIssue}} |
| | <span class="entry-summary author vcard"> |
| | <span class="published">2010-MM-DD</span> |
| | raised by <span class="fn">[[User:Toby|Toby]]</span> |
| | </span> |
| | <div class="entry-content discussion issues"> |
| | * <strong class="entry-title">non-ending events</strong>. How to deal with events that do not end, or even as such occur, just "applied" to a person. Such as in hResume, an award, under experience, would use hCalendar. it does not have an end nor does it continue, I am awarded a certain status and now have that status or recognition of ability. It is awarded on a certain date but it does not end, I do not lose ability, but nor does the awarding continue, I am not re-awarded every single day, so the solution of "to present" for an ongoing event etc, is not really suitable. |
|
| |
|
| * 2005-02-22 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html on the whatwg list]:
| | Some new way to do this could be added to hCal that is not linked to vCal so that online extractors of hCal (and not vCal) would not automatically represent events with no end date as ending "present" (as with madgex hres to word) unless otherwise specified that this is intended. |
| *# ''There is no copyright statement and no patent statement.''
| | </div> |
| *#* ACCEPTED. I have updated ["hCalendar"] (and ["hCard"], and all other MicroFormats) with a standard copyright statement and patent statement.
| | </div> |
|
| |
|
| * 2005-02-18 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:
| | == Template == |
| *# ''There is no way for some reading the markup to tell if a class name is the name of an attribute or simply the name of a class used for styling.''
| | {{issues-format}} |
| *#* REJECTED (strawman, poor assumption). There is no need to differentiate in the general case. In the specific case, a vocabulary is defined within a context.
| |
| *# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as "x-mozilla-alarm-default-length" (which is an actual extension used in Sunbird).''
| |
| *#* REJECTED (out of scope). Extension properties are outside the current scope of hCalendar.
| |
| *# ''The use of <abbr> for dates is incorrect. "August 5th, 2004" is not the abbreviation of 2004-09-05. In fact, the opposite is closer to the truth.''
| |
| *#* REJECTED (false statement). This is simply a false statement. See this article for an explanation of this use of <abbr>: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]
| |
| *# ''You have to create a complex set of rules for all possible uses of legacy markup within <span class="vcalendar"> which can easily be implemented incorrectly.''
| |
| *#* REJECTED (false statements, strawman). There is no legacy markup. There is no need to create rules for all possible uses of legacy markup. There is no need to create a complex set of rules.
| |
| *#* ''There are styling and tooltip issues that are unresolved.''
| |
| *#* REJECTED (empty statements). See the ["hCalendarFAQ"] for answers to specific styling and tooltip questions. Otherwise, please raise specific issues here with clear valid examples.
| |
| *# ''hCalendar/hCard is more complicated for webmasters to read and understand and more complicated for developers to implement.''
| |
| *#* REJECTED (empty statements, invalid comparator). Please state specific examples which show the perceived complexity. The comparison "more complicated" requires two items, no second item was provided.
| |
| *# ''I dislike the entire system of using class names as markup. Class names should be reserved for user-defined semantics.''
| |
| *#* ACCEPT-PARTIAL. When specific elements are available, they should be used instead of class names, but even then class names work well to "subclass" specific elements. This is thoroughly discussed in the essay [http://tantek.com/log/2002/12.html#L20021216 A Touch of Class]. And yes, class names can and should be used for user-defined semantics. [[hcalendar|hCalendar]] is one such user, and it is reasonable for users to use each others class names.
| |
|
| |
|
| * ''Would it be more in the spirit of HTML to define these classes in a [http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 metadata profile], so that "User agents may... perform some activity based on known conventions for that profile"? Should this be a part of [[microformats]] specifications in general? (If not, why not?)''
| | == Related Pages == |
| ** ACCEPTED. Yes, all [[microformats]] that introduce new classnames SHOULD include an [http://gmpg.org/xmdp/ XMDP] profile (which itself is a microformat for defining HTML metadata profiles) that defines those classnames.
| | {{hcalendar-related-pages}} |
These are externally raised issues about hCalendar 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.
IMPORTANT: Please read the hCalendar FAQ and the hCalendar resolved issues 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. — Tantek
For matters relating to the iCalendar specification itself, see icalendar-errata and icalendar-suggestions.
See related hcard-issues.
closed issues
See: hcalendar-issues-closed.
resolved issues
Issues that are resolved but may have outstanding to-do items. See: hcalendar-issues-resolved.
Issues
Please add new issues to the bottom of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
issues 20010
open issue!
2010-MM-DD
raised by Toby
- non-ending events. How to deal with events that do not end, or even as such occur, just "applied" to a person. Such as in hResume, an award, under experience, would use hCalendar. it does not have an end nor does it continue, I am awarded a certain status and now have that status or recognition of ability. It is awarded on a certain date but it does not end, I do not lose ability, but nor does the awarding continue, I am not re-awarded every single day, so the solution of "to present" for an ongoing event etc, is not really suitable.
Some new way to do this could be added to hCal that is not linked to vCal so that online extractors of hCal (and not vCal) would not automatically represent events with no end date as ending "present" (as with madgex hres to word) unless otherwise specified that this is intended.
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
This 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.