CSS Process Document Chapter 7th Technical Report development process Translation

Prior to participating in the CSSCONF conference, due to the publishing process of these are not very understanding, so translation of this article, one for the full picture, deepen the impression, the second for the training of capable translators, for beginners to provide small help. The text will inevitably be wrong, if found, please reply for me to correct in time to avoid misleading more readers.

Translate with words:

English description	Chinese translation	Abbreviation
Working Group	Drafting group
Technical Report	Technical reports	Tr
Technical Report Development process	TR Development process
Recommendation track	REC Process
Working Draft	Draft	Wd
Call for	Ask
Last Call announcement	LC Notice	LC
Candidate Recommendation	Candidate criteria	CR
Proposed recommendation	Recommended Standard	PR
Recommendation	Standard	REC
Working Group Note	Drafting group Comments	WGN
Proposed edited recommendation	Proposed revision of the standard	PER
Rescinded recommendation	Obsolete standard	Rr
Director	Director
Advisory Committee	Senior Committee
Call for	Ask
Modify	Modify
Endorse	Support
Edited	Edit | modify

Conventions:
1. If not stated, the "process" referred to in the text refers to the following: "TR development process" or "rec process"
2. If not stated, the "level" referred to in the text refers to: "Maturity level"
3. If not stated, the "documentation" referred to in the article refers to the following: "TR documentation"

Translation:

7.W3C Technical Report Development process (TR development process)
7.1 Level of maturity
7.1.1 level of maturity in progress
Maturity level for 7.1.2REC processes
Maturity level at end of 7.1.3TR
7.1.4 Editing Rec's maturity level
7.1.5 level of maturity for abandoned rec
7.1.6 maturity level of TR for interest groups and collaboration groups

General requirements for propulsion in the 7.2REC process
7.3 Review and review duties

7.4 Process of promoting TR documentation to REC
7.4.1 first draft release (WD)
7.4.2LC Notice
7.4.3 Solicit implementation
7.4.4 to solicit PR review
Release of 7.4.5W3C Rec
7.4.6 back to drafting group for follow-up study

Work at the end of 7.5TR
7.6 Modification of the REC
7.6.1 Errata Management
Classification of 7.6.2REC modifications
7.6.3 Request for review of post-editing rec
7.6.4 Request Rec Correction Review

7.7 Obsolete REC
7.7.1 proposed scrapping Rec
Release of 7.7.2 Waste rec

Information about the 7.8TR
7.8.1 Document Status Section

In order to standardize web technologies, the development process includes a series of steps and requirements, and the TR development process described in this section is implemented in accordance with the specifications and guidance defined by the drafting group, including:
Advance TR Development: From drafts to mature documents ("REC"), called: the REC process
TR at the end of the work: released as Rec or waived for release to Rec
Modify Rec
Waste Rec, i.e.: The REC is no longer supported by the

At the beginning of the design, the TR development process is to maximize the endorsement of the TR content, ensure technical, editorial quality, and improve the continuity between the norms, access to the industry and more community support. Slightly
This article then describes in turn:
Various steps of the TR development process (e.g. LC notification, solicit implementation)
Requirements for each step
For each step of the TR maturity level (e.g. WD, CR), please note that the TR development process and maturity level are not one by one corresponding. (Translator Note: The final Notice LC is a step in the development of TR, but maturity is still at the same maturity level as the previous WD)

Start with the maturity level, then the TR development process steps and requirements.

7.1 Maturity Level
The level of each published TR document represents its current position in the development process. "WD", "WGN" represents the possible initial state in the level, "REC", "WGN" represents the possible end state in the level.
7.1.1 in Progress
WD (draft)
WD refers to a community-based review of documents published by the group, which includes members of the public and other technical organizations. Part of WD intends to advance for Rec. See "Document status Subsections"
levels in 7.1.2REC procedures
In addition to the other levels in the WD,REC process are:
CR (candidate criteria)
If a document has been extensively reviewed and meets the technical requirements of the drafting group. A CR is released to get feedback on the technical implementation. The
PR (Recommended standards)
document has been reviewed and implemented by the technology circle, and the document will be submitted to senior members of the High Commissioner for review.
Rec (Standard)
After extensive endorsement of the voice of the accumulation, the world wide REC will become a norm, with the support of members and directors. The consortium recommends it to more practical applications. Note: REC is equivalent to the standard in other organizations.
7.1.3 TR level at the end of work
WGN (Drafting group comments)
Comments are issued by the appropriate drafting group, indicating that work on the topic has been completed. The drafters may release WGN after the previous WD release, or may not.
Note: In the development community and media, in order to avoid confusion: which document represents the results of the drafting group, which represents the source of the activity, the media has stopped using the unqualified level: "Note".
7.1.4 editing the rec level
PER (proposed modification criteria)
Rec's documentation is subject to review by the community and some may affect consistency. When these changes are recognized, they are released as per.
7.1.5 Waste rec Level
RR (discard standard)
Rec will no longer be supported once it has been scrapped and becomes obsolete.
7.1.6 level of TR for interest groups and collaboration groups
the "Interest group comments" ("Interest Group Notes") and "collaborative Group Notes" ("Coordination Group") are also published. This is known as "opinion" because "WD" is usually associated with the REC process, which publishes "Interest group opinion/Collaboration Group views" ("Interest/coordination Group Notes") for the documents of these groups.

The usual requirements in the 7.2REC process:
In the WD development process, the drafting group must meet the following requirements:
1. Record the decision in the development process of the request
2. Provide all public documents modified with the previous version (primary, secondary). (...)
3. Documentation of the drafting group's revision requirements
4. Reporting dependency change relationships with other teams
5. Show evidence of extensive review
6. Formal elaboration of all issues arising from the documentation
7. Report any formal objections

The following information is important for deciding whether to advance TR and must be publicly accessible:
1. TR modified all documents (such as: In addition to the summary of major changes, to provide specific "different" places)
2. Release statement: The document satisfies all conditions, or although only some of the conditions are satisfied, but still enough to advance the reasonable interpretation of the document
3. Provide proof that the document has been reviewed and the dependencies on other teams have been resolved
4. All formal questions raised by the reviewers have been answered
5. All official objections

7.3 Review and reviewer responsibilities
Slightly
7.4 The process of promoting TR to rec
The following steps are followed to advance the REC process:
1. Release the initial WD
2. Issuance of Final Notice LC
3. Request for implementation
Note: If all the conditions in the next step are met, the director can skip this step directly
4. Solicit PR Review
5. Released as Rec

In the end, the drafting group took the process to release REC, but the consortium might stop the job, or ask the team to explore it further, so it would repeat many steps.
Between the first WD and LC, the drafting group publishes revisions of several changes. Between any two steps after the LC, if there is a significant change, the drafting group will issue a new equivalent TR document,
(Translator Note: Not read the last sentence of the original sentence)

For revisions of CR and PR, the drafting group must inform the high-level Committee.
The rec process may last quite a while, so it is recommended to read this section: "Tips for speeding up the rec process"

7.4.1 First WD
Level: WD
Notice: The director must notify the group and the public of the first WD release
Purpose: Once WD is released for the first time, the community can review the document.
Slightly
7.4.2 Final Notice
Level: WD
Notice: The drafting group must inform the group and the public of the last WD, the notice must:
1. Specify the deadline for the review
2. Clearly known dependencies and review of all independent teams
3. Solicit Public review
Slightly
7.4.3 Solicit implementation
Level: CR
Notice: The director must inform the High Committee of the decision to seek implementation
Purpose: The TR document is stable and suitable for implementation, and the document may be modified based on implementation;
Slightly
7.4.4 Solicit PR Review
Level: PR
Notice: The director must inform the High Committee of the decision to seek a review
Slightly
7.4.5 the release of the Rec
Level: REC
Notice: The director must inform the High Council of Rec's release
Slightly
7.4.6 back to the drafting group for further study
The TR document will be called back to the drafting group if any of the following conditions are met:
1. The drafting group has made significant changes to the documentation during the LC and Rec period, in which case the Panel must republish the WD documentation, and if the major change refers to the CR phase removal of new features that are not easy to implement, it is not possible to call back.
2. The Director requested the drafting group to present a number of important issues that were referred to at the time of the review or technology implementation. In this case, the Director may request the Panel to republish a document as WD, even if the Panel does not have significant changes.

If the TR document is called back, the director must inform the High-level Committee and the Chairman of the panel.
After WD is re-released, the LC phase is next, and the LC may be released with WD at the same time.
The Director may request a re-release of the CR, while seeking technical implementation.

7.5 Stop TR Document work
The TR documentation may stop at any time, and when the drafting group completes the TR, the TR is either REC or WGN. For example, if the TR document is published as multiple WD, then the TR document is stopped by publishing WGN.
If the TR document does not make much headway, the work may be terminated. There may be reasons: The director closes the drafting group, the participant loses interest, and the document subject has been included in other TR documents. If the job is stopped, WGN will be released.

Possible Next steps:
End status: At WGN level, without deadlines
Restore WD Status: Recovers documents to WD level.

7.6 Modifying rec
The marketplace will do every step to maintain rec, such as errata management, providing test applications, helping build test sets, and encouraging a wide range of implementations. This is discussed below: errata management and proposed changes to the REC process.
7.6.1 Errata Management
Classification of 7.6.2REC modifications
This document distinguishes between the following types of modifications:
1. No modification of text content
such as: fix links, non-canonical tags
2. Changes that do not affect consistency
Such as: the modification of the concept of the elaboration, will not change the technical content
3. Impact consistency, but without adding new features
Such as:
1. Modify the consistency of the data, processing methods, consistent implementation of the party to the non-conforming party
2. Non-conforming implementation party to the implementation of the consistency
3. Remove the description of unclear or unspecified parts, resulting in the realization of the party from unclear to the implementation of consistency or inconsistency
4. New Features

The first two do not require a technical review, the third requires the following:
1. Community review, identify technical circles without objection
2. Even after posting the updated rec
The fourth one must go through the rec process again.
Slightly

7.6.3 Request for Revised REC review
Slightly
7.6.4 Request a review of proposed amendments
Slightly

7.7.1 proposed scrapping Rec
Slightly
Release of 7.7.2 Waste rec
Slightly

General information for 7.8 TR documents
Slightly
7.8.1 Document Status Section
Slightly

CSS Process Document Chapter 7th Technical Report development process Translation