process-issues

process issues

These are issues that have been raised about the microformats process 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 process FAQ 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.

Closed Issues

Resolved issues that have no further actions to take. These will likely be moved to a separate page like process-issues-closed.

• none yet.

Resolved Issues

Issues that are resolved, but may have outstanding to-do items. As issues are resolved, they will be moved from the top of the issues list to the bottom of this section.

• none yet.

Issues

Please add new issues to the bottom of the list by copying and pasting the template. Please follow-up resolved or rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

2007

• open issue! 2007-09-07 raised by Manu Sporny
  1. Issue 1: What constitutes "Enough Examples"
  2. Issue 2: Proper interpretation of W3C standards
  3. Issue 3: Keeping up with changes to the process becomes frustrating

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.
  1. Issue 1: Here is the first issue I have.
  2. Issue 2: Here is the second issue I have.

Related Pages

• process
• process-faq