The mission of this task force is to document requirements for the layout and presentation of text in languages written in the Hebrew script, when those languages are used by Web standards and technologies, such as HTML, CSS, SVG, Mobile Web, Digital Publications and Unicode.
The Hebrew script is used by communities in various parts of the world, speaking very different languages, and participation in this work by those communities is welcomed. This task force will gather and integrate feedback from the participating members about the need for and technical feasibility of various requirements.
The Task Force is part of the Internationalization Interest Group.
The aim of this Task Force is to follow the example of Requirements for Japanese Text Layout, Ethiopic Layout Requirements, and Arabic Layout Requirements, and collect information about specific use cases for technologies defined in various Web specifications as they relate to the aforementioned scripts. The Task Force will report the results of its activities as a group back to the Internationalization Working Group, as well as to other relevant groups and to the W3C membership and community.
|End date||31 December 2018|
|Confidentiality||Proceedings are public|
|Initial Chair||Lina Kemmel, IBM|
|Initial Team Contacts
(FTE %: 2)
|Usual Meeting Schedule||Teleconferences: On an as-needed basis. Preferably, a minimum of two status meetings per month.
Face-to-face meetings: On an as-needed basis.
Video Conferences: On an as-needed basis.
The main objective of the task force is to document typographic and layout requirements for languages using the Hebrew script. These requirements should be met in Web standards and technologies, such as HTML, CSS, SVG, and Digital Publication technologies.
Use of the Hebrew script extends beyond the Hebrew language. There are several other languages that are written in this script and not necessarily linguistically related to Hebrew: Yiddish, Ladino (a.k.a. Judeo-Spanish), Judeo-Arabic, Judeo-Persian, Aramaic. Although these languages and writing traditions are important, the initial focus of this Task Force will be on the usage associated with the Hebrew language.
In addition to those technologies mentioned above, the group may review (but is by no means explicitly limited to reviewing) the following:
Along with reviewing the above mentioned specifications and related specifications, the group will also gather comments and questions about those specifications, collect information about specific use cases affecting the Arabic script for technologies defined in those specifications or browser implementations, 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 HTML Working Group, CSS Working Group, SVG Working Group, and other Working Groups at the W3C as needed. It can also link to discussions about gaps between the requirements and the implementations from the Typography Index maintained by the Internationalization Working Group.
Initial set of languages to be covered consists of Hebrew. Information regarding other languages will be included based on the availability of linguistic and typographic experts.
Target deliverable is the document Hebrew Layout Requirements.
The Hebrew Text Layout Task Force will not produce Recommendation-track deliverables but will produce documents that can be published by the Internationalization Working Group as Working Group Notes about text layout and typography in the Hebrew script.
The group may also choose to produce other non-normative deliverables, such as test cases and bug reports – under the terms of the Policies for Contribution of Test Cases to W3C, and in coordination with any relevant working groups, browser vendors or application developers.
Plans for the main document deliverable are as follows. All deliverables will be made available in English.
|Note: The group will document significant changes from this initial schedule on the group home page.|
|Specification||FPWD||WD for final review||WG Note|
|Requirements for Hebrew Layout and Typography||Q4 2016||Q3 2018||Q4 2018|
Other deliverables may be 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.
The success of the Task Force will be evaluated based on how productively it engages with W3C members and the relevant script communities to promote discussion of specifications that affect layout and presentation of languages on the Web, and how effectively it is able to produce additional documents for the refinement, implementation, and adoption of text layout and related technologies in Hebrew.
Working Drafts and Notes will be published by the i18n WG, and the i18n WG will work with the task force closely to assist with development and review of the documents.
To be successful, the Hebrew Text Layout Task Force is expected to have participation, for its duration, from a representative section of the typographic and digital text publishing communities for each of the main languages covered. Effective participation in the Hebrew Text Layout Task Force is expected to consume up to 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.
People contributing substantive text to the deliverables must be public invited experts or work for W3C member organizations, in order to meet the policy requirements of section 7 of this charter.
Participants who join the Hebrew Script Layout Task Force must also agree to the following:
Copyright is a very important part of standardization activities. It allows the standards development organization to maintain vendor neutral control over a specification, and thus protect the consensus found within a Working Group.
In the course of the development of materials within the W3C, Task Force Participants will make contributions. Those contributions will be integrated into the jointly developed work thus creating shared copyright on the Task Force Participant's contribution. Most W3C Specifications contain a section with acknowledgement of contributions.
Task Force Participants grant to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any Task Force Participant's copyrights on his or her contributions, to copy, publish and distribute the contribution under a license of W3C's choosing. Additionally, the Task Force Participant grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, his or her contribution and that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C. Furthermore, the Task Force Participant understands that W3C will be able to exercise all rights as a copyright owner of Task Force Participant's contribution, including enforcement against infringers without additional agreement or notice.
Nothing in this agreement restricts the Task Force Participant from using their individual contributions as they wish, even if those have later been amalgamated into joint works. Where W3C releases materials under a permissive license such as the W3C Software License or CC-BY, nothing in this agreement should be read to restrict the Task Force Participant from exercising the permissions granted by that license. The Task Force Participant represents that they are legally entitled to grant the above license. If their employer(s) have rights to intellectual property that the Task Force Participant creates that includes the contributions, they represent that they have received permission to make contributions on behalf of that employer or that the employer has waived such rights for the contributions to W3C.
The Task Force Participant will participate in the W3C Group in a decent way. Task Force Participants will refrain from defaming, harassing or otherwise offending other participants. The Section 3.1 of the Process Document applies.
The Task Force Participant will refrain from sending unsolicited commercial messages to W3C mailing-lists and other promotional activities for personal matters or for third parties. This is especially required from Task Force Participants sending messages to public W3C Groups.
Hebrew Text Layout Task Force discussions take place via github, teleconferences and email, and face-to-face meetings may be called at locations that are convenient to participants in the project. Any publications or other reports eventually contributed by the Task Force back to the W3C will be made available in English. (Translations may be produced in addition to the English version, but the English version will remain the authoritative version.)
The task force reaches out to the wider international community with discussions and announcements in English on the email@example.com list (archive). That list will be used for technical discussions, where necessary, but the group will use github issues to handle most technical or editorial comments and discussions. The firstname.lastname@example.org list must archive or point to minutes and summaries of all teleconferences and face-to-face meetings. Meeting minutes will list all attendees at a given meeting.
An administrative list, public-i18n-hlreq-admin, will also be used for internal communication about practical matters, such as meeting agenda, which should be published before each teleconference or face-to-face meeting.
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 and from the home page of the Task Force.
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 Hebrew Text Layout Task Force are obligated to comply with W3C patent-disclosure policy as outlined in Section 6 of the W3C Patent Policy document. Although the Hebrew 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 Hebrew Layout 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.