WebPlat charter: Deliverable state

[LJWatson]

Feedback from AC review:
Please clarify why there is a state attached to some deliverables in the charter? Surely a deliverable is a Recommendation not an Editor's copy (what is an Editor's copy anyway)?

[LJWatson]

Agree with this suggestion. Having links to Editor's Drafts in the Deliverables section of the charter seems unnecessary. If it is decided that they're necessary, they should be correctly labelled.

[chaals]

There are two reasons for linking to draft deliverables. One is to clarify the patent status and current drafts, in line with the Process document updates for things that are taken up by a new charter, and the other is to give people an idea of what a particular deliverable means in practice.

I agree that it would be helpful if links to something explained what they were linking to, including its status, and I'll make a Pull Request that tries to achieve that.

[LJWatson]

Doesn't the content of section 11 fulfil both those purposes? Putting links to EDs in section 3 seems superfluous.

[chaals]

There is no indication in section 3 that the links exist in section 11, so repeating them seems reasonable to me.

[dwsinger]

To be clear, I don't mind linking to a draft of what the group hopes will become a deliverable. What I do mind is describing the deliverable itself as an editor's draft.

so, not

Deliverables

Chocolate-coated wombats Editor's Draft

but

Chocolate-coated wombats

The former implies that an Editor's Draft is the expected deliverable.