From MultilingualWeb-LT EC Project Wiki
1 WP2: Standardization Process
Co-ordinate the standardization process for LT-Web metadata, in particular the gathering of requirements, developments of drafts of the LT-Web metadata standard, and the finalization of the LT-Web metadata standard.
This work package serves as a backbone for the other, implementation focused work packages 3, 4 and 5. Proposals for LT-Web metadata will be implemented in these work packages, and implementation and usage feedback will feed into the update of drafts and the finalization of the standard. The community involvement provided by work package 6 will help to gather feedback on the standard development and to foster usage of LT-Web metadata.
1.2 Task 2.1: Requirements and Use Cases [Task leader: TCD; contributors: DFKI, UEP, MS ECD, ENLASO, UL, Cocomore, LinguaServe, VistaTEC, Lucy]
Deliverables resulting from this task: D2.1 Requirements and Use Cases Document.
The goal of this task is put the requirements and use cases for LT-Web metadata gathered in task 6.1. into the W3C standardization process, as an input to the actual standardization. The participants will hold weekly telephone conferences, have discussions via a dedicated W3C mailing list, and will meet two times face-to-face. A one-day, public workshop hosted by TCD will be hold to gather public feedback on requirements and use cases. The results of the participant’s discussions and public feedback will be summarized in a document to be published on the W3C TR site http://www.w3.org/TR/
1.3 Task 2.2: Draft Development [Task leader: DFKI; contributors: TCD, UEP, MS ECD, ENLASO, UL, Cocomore, Linguaserve]
Deliverables resulting from this task: D2.2 LT-Web Metadata Draft Documents.
The goal of this task is to develop a stable draft document defining LT-Web metadata. The draft document will be published several times on the W3C TR site. Feedback will be gathered from: implementation experience in the work packages 3, 4 and 5; workshop attendees and the general public; the community to be involved via work package 6. The outcome of this task will be a stable definition of LT-Web metadata, to be finalized within the W3C process (see task 2.4).
1.4 Task 2.3: Test Suite [Task leader: TCD; contributors: DFKI, UEP, MS ECD, UL, ENLASO, Cocomore, Linguaserve]
Deliverables resulting from this task: D2.3 LT-Web Metadata Test Suite.
As required by the W3C process, a test suite will be developed. It serves as a means for testing the behaviour of content that includes LT-Web metadata. A test suite consists of input data (e.g. HTML files with LT-Web metadata) and expected output (e.g. content being machine translated with awareness of the metadata). The W3C process requires that for each feature defined within a standard, at least two implementations are available.
This task will provide the test suite as well as test execution, analysis and logging services. Where interoperability validation involves more than one exchange, e.g. when validating round-trip capabilities, a navigable interface will be provided to facilitate the correlation of behaviour expectation between the exchanges. The task will support the interoperability validation work conducted in WP3, 4 and 5 by providing LT-Web compliant data both for internal validation testing and for publicly showcasing the results. Such a separation must be accommodated when the larger volumes of data needed for some use scenarios, e.g. involving SMT training, could not necessarily be made available outside the consortium. The test suite will also provide sample sets of open test data that may be used by third party implementers planning to use the test suite.
1.5 Task 2.4: Finalization of LT-Web Metadata Standard [Task leader: DFKI; contributors: TCD, UEP, MS ECD, UL, ENLASO, Cocomore, Linguaserve]
Deliverables resulting from this task: D2.4 LT-Web Metadata Standard.
The goal of this task is to publish the final LT-Web metadata standard. The publication of the final draft as a W3C Recommendation (a W3C standard) follows the period of successful testing and will be aligned with the finalization of implementations.