Drafting suggestions from Chet Ensign

[Patrick Durusau <patrick@durusau.net>]

Greetings!

I forgot to share the suggestions from Chet Ensign that were sent to
Svante, Francis, and myself, in response to the question about what to
add in the charter:

*****

I suggest keeping the Scope section general and flexible enough to
enable you to adjust your work to circumstances and lessons-learned over
time, while specific enough to put boundsÂaround the work. For example,
the CodeList TC just had to do a recharter because their original
charter specified XML serializations. Writing that the TC would produce
'schema for code lists in serializations such as XML' would have given
them the ability to add JSON with it being an increase in scope. My
concern is that by including specific projects in the Scope statement,
you may force the TC to recharter in the future to add new ones.Â

If you want to add specific projects, I suggest adding them in the
Deliverables section, something like this...Â

The TC may also undertake development of supporting specifications such as:Â

- INFO-Set for ODF
...Â

That way, you have them listed as sub-projects that the TC may develop
but you're not locked in to them and you've given yourself flexibility
to add to the extensions as a clarification rather than an increase in
Scope.
*****

Talk to everyone in just a few minutes!

Patrick

-- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau