Versions Compared

Old Version 3

changes.mady.by.user Drummond Reed

Saved on

compared with

New Version 4

changes.mady.by.user Drummond Reed

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When a WG/TF is ready to begin drafting, it must decide which collaboration tools it will use. ToIP offers two choices:

  1. Google docsDocs. This option is a good choice if it is important to minimize barriers to contributions if the deliverable is not a technical specification or doesn't recommended if the WG/TF wants to minimize barriers for contributors. It can work well for non-technical deliverables, where intellectual property rights (IPR) for contributions are usually not an issue. In addition, it can be used for the early stages of drafting technical specifications—though it is still important to keep a clear record of which ToIP members make which contributions.
  2. GitHub Markdown documents. This option MUST be used for the final form of all ToIP technical specifications. It has the advantage of keeping a strict, verifiable datestamped record of all contributions by author. It is also recommended as the final form for any ToIP deliverable that wishes to take advantage of our Terminology Engine tools (produced by our Concepts and Terminology WG) for automatic linking and annotation of glossary termsGitHub. 

Stage 8: Implementers Drafts

...