The mission of this task force is to create documents about requirements for Indic Text layout realized with standards related to CSS, Mobile Web and Unicode. The documents will be mainly based on W3C standards affected by Indic Text layout and Unicode Algorithms for line breaking and segmentation e.g. - UAX# 14 and UAX#29. This task force will gather and integrate feedback from the participating members about the need and technical feasibility of various requirements.
The Task Force is part of the Internationalization Interest Group.
The aim of this task force is to collect information about specific use cases in India for technologies defined in those specifications for Indian languages, and to report the results of its activities as a group back to the Internationalization Core Working Group, as well as to other relevant groups and to the W3C membership and community.
|End date||31 December 2014|
|Confidentiality||Proceedings are public|
|Initial Chair||Swaran Lata|
|Initial Team Contacts
(FTE %: 2)
|Usual Meeting Schedule||
Teleconferences: On an as-needed basis.
Face-to-face meetings: On an as-needed basis.
Video Conferences: On an as-needed basis.
The proposal for the group originated from consultation with stakeholders and W3C members in India on how to help facilitate increased involvement in W3C activities around CSS, E-publishing, and related technologies for Indian languages.
In addition to the related specifications, the group may review (but is by no means explicitly limited to reviewing) the following:
The group may also review draft specifications produced by Web API related working groups. Along with reviewing the above mentioned specifications and related specifications, it is expected that the group will also gather comments and questions about those specifications, collect information about specific use cases in India for technologies defined in those specifications, and report the results of its activities as a group back to the Internationalization Working Group, as well as to other relevant groups — such as the Web Applications Working Group, CSS Working Group, etc.
The success of the Task Force will be evaluated based on how productively it engages with W3C members and the community in India to promote discussion of Indic Text layout related specifications, and how effectively it is able to produce additional documents for the refinement, implementation, and adoption of Indic text layout and related technologies in India and worldwide.
The Indic Task Force will not produce Recommendation-track deliverables but may produce Working Group Notes on Indic text layout and related technologies, the contents of which might include (but by no means be explicitly limited to) the following:
The group may also choose to produce other non-normative deliverables, such as test cases and error reports — under the terms of the Policies for Contribution of Test Cases to W3C, and in coordination with any relevant working groups.
Plans for the main document deliverable are as follows:
|Note: The group will document significant changes from this initial schedule on the group home page.|
|Specification||FPWD||IG Note||WD for final review||WG Note|
|Requirements for Indic Text Layout||Q4 2013||Q2 2014||Q3 2014||Q4 2014|
W3C India has already done some extensive work on CSS requirements in Indian Languages. A draft report is available on the W3C India Web Site.
Other WG deliverables are produced on an ongoing basis throughout the life of the charter, and the specific topics to be addressed by the task force and schedule information cannot be determined far in advance, but are driven by the needs of the Web community.
Hindi, Marathi, Punjabi, Bengali, Telugu. Additional languages will be included based on the availability of linguistic and typographic experts.
To be successful, the Indic Text Layout Task Force is expected to have 10 or more active participants for its duration. Effective participation to Indic Text Layout Task Force is expected to consume one work day per week for each participant; two days per week for editors.
Participants are reminded of the Good Standing requirements of the W3C Process.
Indic Text Layout Task Force discussions take place in India. However, any Notes or other reports eventually contributed by a group back to the W3C will be made available in English.
The Indic Text Layout Task Force primarily conducts its work on the publicly archived mailing list firstname.lastname@example.org (archive).
The group will use the Internationalization Activity home page to provide updated public information about its activities.
Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the Internationalization Working Group home page.
As explained in the Process Document (section 3.3), this group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its Chair will put a question about the issue to the group and gather responses (including any formal objections); then, after due consideration of all the responses, the Chair will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).
Participants in the Indic Text Layout Task Force are obligated to comply with W3C patent-disclosure policy as outlined out in Section 6 of the W3C Patent Policy document. Although the Indic Text Layout Task Force is not chartered to produce Recommendation-track documents that themselves require patent disclosure, participants in the group are nevertheless obligated to comply with W3C patent-disclosure policy for any Recommendation-track specifications that they review or comment on.
For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
This charter for the Task Force within the Internationalization Interest Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
$Date: 2012/06/20 19:16:44 $