This wiki has undergone a migration to Confluence found Here
Difference between revisions of "V3 Technical Editors Project"
Jump to navigation
Jump to search
(The Projects Page for the V3 Technical Editors Project) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | See the [[V3 Technical Editors Project FAQ]] | |
| + | |||
| + | |||
| + | See [[V3 Technical Editors Project Works in Progress]] | ||
| + | |||
| + | |||
| + | The V3 Technical Editors Project was initiated in response to specific issues with the consistency of V3 core artifacts -- the RIM, datatypes, and vocabulary specifications. The documents in scope have been through multiple iterations of editing, and project-based approach has drawn to a close. | ||
| + | |||
| + | The documents continue to evolve, and the editors make 3 recommendations: | ||
| + | |||
| + | > That an operational task be created to review materials with each ballot | ||
| + | |||
| + | > That the ballot cycles be reduced to two per year to support quality | ||
| + | |||
| + | > That the "document roadmap" concept be implemented by a collaboration between publishing, education, and marketing | ||
Latest revision as of 18:05, 26 March 2010
See the V3 Technical Editors Project FAQ
See V3 Technical Editors Project Works in Progress
The V3 Technical Editors Project was initiated in response to specific issues with the consistency of V3 core artifacts -- the RIM, datatypes, and vocabulary specifications. The documents in scope have been through multiple iterations of editing, and project-based approach has drawn to a close.
The documents continue to evolve, and the editors make 3 recommendations:
> That an operational task be created to review materials with each ballot
> That the ballot cycles be reduced to two per year to support quality
> That the "document roadmap" concept be implemented by a collaboration between publishing, education, and marketing
