process-issues: Difference between revisions
AndyMabbett (talk | contribs) (accessibility fixes) |
AndyMabbett (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
<h1>process issues</h1> | <h1>process issues</h1> | ||
These are issues that have been raised about the microformats [[process]] with broadly varying degrees of merit. Thus some issues are <span style=text-transform:uppercase">rejected</span> 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 <span style=text-transform:uppercase">accepted</span>and perhaps cause changes or improved explanations in the spec. | These are issues that have been raised about the microformats [[process]] with broadly varying degrees of merit. Thus some issues are <span style=text-transform:uppercase">rejected</span> 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 <span style=text-transform:uppercase">accepted</span> and perhaps cause changes or improved explanations in the spec. | ||
<strong style=text-transform:uppercase">Important</strong>: Please read the [[process-faq|process FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. | <strong style=text-transform:uppercase">Important</strong>: Please read the [[process-faq|process FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. | ||
Revision as of 00:27, 8 September 2007
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. — Tantek
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 copy and pasting the Template. Please follow-up to resolved/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
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.