ODF New Proposal Template

Summary

Proposal owner:

The name of the TC member who is making the proposal and who will own it through the process

Proposal short name:

A short description, only a few words, something we can use in email subject lines, in agendas, etc.

Rationale

Use cases:

No need for elaborate formal use cases.  But give a few sentences that explain what this feature is and does from the perspective of the consumer of this feature.  The consumer might be the end user of the application.  It might be an application developer.  It might be an archivist.  It could be almost anyone.  But please give a few words on why this feature should interest us.

Alternatives considered:

There is often more than one way to accomplish a task.  For your use case, what other alternatives did you consider, and why did you find them inadequate?  

Requested changes to the ODF Standard

Text changes/additions (please state section numbers):

Enter specific text edits here

Schema changes/additions:

Enter specific Relax NG schema edits here

Impacts

Conformance:

Does this proposal add any mandatory features or behaviors to ODF documents or applications?

Backwards compatibility:

If we make this change, what will be the impact on existing ODF processors?

Accessibility impact:

Will this feature require review by the Accessibility Subcommittee?  For example, does it add structure to the document that can be navigated, store a user-viewable string or associate a label with content?

Workflow (to be filled in by TC Chairs)

Category: CategoryNewProposal

Date Proposal initially made:

Dates Proposal discussed on TC calls:

Date vote is requested:

Date vote is held:

Results of vote:

ProposalTemplate (last edited 2009-08-12 18:04:23 by localhost)