Requirements for Translation Database

Users

Internal User

Team members who maintain the translation DB
Team members who contribute to the Call for Translation page

External User

Almost everybody who visits W3C Website. Special attention should be given to translators, people who have interests to translate documents, people who have comments for the translations, and people who want to report a bad link or error.

Function Description

UI for the team to maintain the DB

A UI for W3C to maintain the DB and collect team input for the translations. More details need input from Marcomm team who currently handle the translation mailing lists.

Call for Translation Page

Generate a Call for Translation Page and add it to a noticeable place on the homepage of W3C (somewhere on the sidebar?). This page should be linked to TR publication system so that the newly published completed Recommendations can be added to this page automatically; The Call for Translation Page should contain the list of documents that have important information helping global Web community, especially non-English Web community to understand and participate in W3C activities. Two categories of documents to be added to this list: the rule-based documents will be added automatically by the system once published while other documents will be added by the team manually if they think certain document that is not on the rule-based list worth to be translated.

Ruled-based documents

Completed Recommendations, but need to remove the outdated/obsoleted ones
Process Document and Patent Policy?
Press Releases: A mature current practice: PR translations done by the Offices and the translations are noted on the PR page
highlight reports? Suggested by Angel: Translating highlight reports is current practice in Chinese since 2013. Positive feedback from Chinese members as an important document for them to get an overview of W3C activities;

Manuel-added documents

Spec drafts and group notes, to be selected and added to this DB by W3C team
Other documents such as workshop reports and blogs
workshop reports: Good recruiting materials for new topics in W3C；selected workshop reports have been translated into Chinese, e.g. Web&VR Workshop Report

Hosting the Translation Content

The Translation DB should work as the host for the translation and provide a W3C URL for the translation documents to avoid the bad quality issues we have had. Make this DB linked with the translation mailing lists for more info. And maybe save the efforts of Marcomm team who manually handles the mailing list conversations?

Translations Status on Document Page

Add the Translations Status to all the documents on the Call for Translation Page, and add the translation encouragement sentences to that page, e.g. W3C encourages translations of this document so as to enable a broader global community to understand and implement this Recommendation. Add the Translation Status to all the To-Be-Translated Document pages. This is not something new. Some of the Completed Recommendations and other documents already have this info, e.g. ATAG2.0 and 2017 April Highlight Report. But these efforts are more spontaneous, not systematically organized in a unified way.

Ranking, Comment and Reporting

Rating: Like and Dislike Button, or 1 Star to 5 Star rating, or other rating methods; display the rating next to the translation URL;
Report: users should be able to report if the URL to the translation is misused or no longer valid so that W3C team can remove the URL from the translations page, W3C account login should be required for this function;
Comment (if possible): users should be able to comment and exchange ideas on the translations, this usually helps the original translator to improve the translation, W3C account login should be required for this function;

Translator/Keywords index

Make the Translations page translator/keywords indexable, if possible, make it easier for people to search for the translation of a certain translator or a certain document.