Re: [w3c/editing] [charter] Define the Success Criteria (#281)

> @BoCupp-Microsoft what do you think? How can we include both the original intention and these criteria of what we expect of specifications we develop?

I think the original intention is well captured by our proposed scope and proposed deliverables section.  I would support amending those sections further if you think they do not.

I'm opposed to the phrase "basic JS text editor" as a success criterion because I don't think it's measurable.

I would prefer just these three sentences:

1. In order to advance to [Proposed Recommendation](https://www.w3.org/Consortium/Process/#RecsPR), each specification is expected to have at least two independent implementations of each feature defined in the specification.
2. Each specification must have an accompanying test suite, which is ideally developed in parallel to the specification.
3. Where there are implications for implementors, developers, or users, in the areas of accessibility, internationalization, privacy, and security, each specification must have a section that describes relevant benefits, limitations, and best practice solutions for that particular area.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/281#issuecomment-816387476