Hi Christian:
The changes to the charter are:
Ø
Added reference to updating
the spec to 1.2 version in order to support Segmentation / Alignment
Ø
Changed version numbers
from 1.1 to 1.2 where relevant
Ø
Removed RTF from list of
representation guides to be delivered
Ø
Removed all references to
a reference implementation
Ø
Removed reference to Localisation
Directives Library (doesn’t seem to be any progress on this)
Ø
Added reference to working
with 3rd party group (IGNITE) to implement certification programme
The revisions are limited to the final
paragraph of the text and the list of deliverables and dates.
The OLD final
paragraph was:
The first phase, completed 31 October 2003, created a committee
specification that concentrated on
software UI resource file localisable
data requirements. The next phase consists
of promoting the adoption of
XLIFF throughout the industry through
additional collateral and
specifications, continuing to advance the
committee specification
towards an official OASIS standard,
contributing to the development of a
standard localisation directives tag
library and consuming it when
available, and defining and publishing an
implementation guide for
document based content that addresses
segmentation and alignment
requirements. To encourage adoption of
XLIFF, the TC will define and
publish implementation guides for the most
commonly used resource
formats (HTML, RTF, Window Resources, Java
Resource Bundles, and gettext
PO Files), and will include reference
implementations of XLIFF 1.1.
The NEW final
paragraph is now:
The first phase, completed 31
October 2003, created a 1.1 version committee
specification that concentrated on software UI
resource file localisable
data requirements. The next phase consists of
promoting the adoption of
XLIFF throughout the industry through additional
collateral and
specifications, continuing to advance the committee
specification
towards an official OASIS standard, contributing to
the development of a
standard localisation directives tag library and
consuming it when
available, and revising the XLIFF spec to 1.2 version
to support
document based content segmentation and alignment
requirements. To
encourage adoption of XLIFF, the TC will define and
publish implementation
guides for the most commonly used resource formats
(HTML, Window Resources,
Java Resource Bundles, and gettext PO Files).
The deliverables
have changed FROM (OLD):
XLIFF TC work and deliverables adhere to
OASIS IPR policy.
List of Deliverables
- XLIFF 1.1 Document
Segmentation & Alignment Content Implementation
Guide, including separate XHTML/HTML
and RTF Representation Guides -
June 21, 2005
- XLIFF 1.1 Java Resource Bundle
Representation Guide - June 21, 2005
- XLIFF 1.1 Windows Resources
Representation Guide - June 21, 2005
- XLIFF 1.1 PO File Representation
Guide - June 21, 2005
- XLIFF 1.1 XML Representation guide - June 21, 2005
- Submit XLIFF 1.1 for consideration as
OASIS Standard - June 21, 2005
In addition, the XLIFF TC will endeavour
to deliver the following as
time and resources permit:
- XLIFF 1.1 Reference Implementation (as
Open Source and probably in
collaboration with Trans-WS OASIS
TC), will at least include filters
for conversion to/from Java - Resource
Bundles and PO Files
- XLIFF 1.1 ResX Representation Guide
- Review and input to development of
Standard Localisation Directives
Tag Library
- XLIFF 1.1: Consume / Implement Standard Localisation
Directives Tag
Library (if available)
The new
deliverables section now reads (NEW):
XLIFF TC work and deliverables adhere to OASIS IPR
policy.
List of Deliverables
- XLIFF 1.2 Specification and XSD to support
Segmentation & Alignment - December 2005
- XLIFF 1.2 XHTML/HTML Representation Guides -
December 2005
- XLIFF 1.2 Java Resource Bundle Representation Guide
- January 2006
- XLIFF 1.2 Windows Resources Representation Guide -
January 2006
- XLIFF 1.2 PO
File Representation Guide - December 2005
- XLIFF 1.2 XML Representation guide - January 2006
- Submit XLIFF 1.2 for public review and
consideration as OASIS Standard - February 2006
In addition, the XLIFF TC will endeavour to deliver
the following as
time and resources permit:
- XLIFF 1.2 ResX Representation Guide
- Review and input to development of Standard
Localisation Directives
Tag Library
- IGNITE Certification Programme
-----Original Message-----
From: Lieske, Christian
[mailto:]
Sent: 15 November 2005 08:01
To: Tony Jewtushenko;
Subject: RE: [xliff] revised
Charter
Hi Tony,
Would it
be posible to get a summary/overview of the changes?
Best
regards,
Christian
From: Tony Jewtushenko
[mailto:]
Sent: Dienstag, 15. November 2005
00:15
To:
Subject: [xliff] revised Charter
Due to the number of
changes that we’ve made to the spec that forced us to revise our
specification to 1.2, our TC must recharter. Our most recent charter
revision is posted at the following URL-> http://www.oasis-open.org/archives/xliff/200502/msg00000.html
We’ll discuss and
attempt a ballot (or agree to a ballot) on the proposed re-charter at
tomorrow’s meeting.
Below is the draft
I’ve authored – note there are minimal changes from the original.
Regards,
Tony
XML Localisation Interchange
File Format (XLIFF)
Statement of Purpose
The purpose of the OASIS
XLIFF TC is to define, through extensible XML
vocabularies, and promote
the adoption of, a specification for the
interchange of
localisable software and document based objects and
related metadata. To
date, the committee has published two
specifications - XLIFF
1.0 and XLIFF 1.1 - that define how to mark up
and capture localisable
data that will interoperate with different
processes or phases
without loss of information. The specifications are
tool-neutral, support the
entire localization process, and support
common software and
document data formats and mark-up languages. The
specifications provide an
extensibility mechanism to allow the
development of tools
compatible with an implementer's data formats and
workflow
requirements. The extensibility mechanism provides controlled
inclusion of information
not defined in the specification.
The state of software and
documentation localisation before XLIFF was
that a software or
documentation provider delivered their localisable
resources to a
localisation service provider in a number of disparate
file formats. Once
software providers and technical communicators
commenced implementing
XLIFF, the task of interchanging localisation
data was simplified.
Using proprietary and/or non-standard resource
formats force either the
source provider or the localisation service
provider to implement
costly and inefficient pre-processing of
localisable content. For
publishers with many proprietary or
non-standard formats,
this requirement becomes a major hurdle when
attempting to localise
their software. For software developers and
technical communicators
employing enterprise localisation tools and
processes, XLIFF defines
a standard but extensible vocabulary that
captures relevant
metadata for any point in the lifecycle which can be
exchanged between a
variety of commercial and open-source tools.
The first phase,
completed 31 October 2003, created a 1.1 version committee
specification that
concentrated on software UI resource file localisable
data requirements. The
next phase consists of promoting the adoption of
XLIFF throughout the
industry through additional collateral and
specifications, continuing
to advance the committee specification
towards an official OASIS
standard, contributing to the development of a
standard localisation
directives tag library and consuming it when
available, and revising
the XLIFF spec to 1.2 version to support
document based content
segmentation and alignment requirements. To
encourage adoption of
XLIFF, the TC will define and publish implementation
guides for the most
commonly used resource formats (HTML, Window Resources,
Java Resource Bundles,
and gettext PO Files).
XLIFF TC work and
deliverables adhere to OASIS IPR policy.
List of Deliverables
- XLIFF 1.2 Specification
and XSD to support Segmentation & Alignment - December 2005
- XLIFF 1.2 XHTML/HTML
Representation Guides - December 2005
- XLIFF 1.2 Java Resource
Bundle Representation Guide - January 2006
- XLIFF 1.2 Windows
Resources Representation Guide - January 2006
- XLIFF 1.2 PO File
Representation Guide - December 2005
- XLIFF 1.2 XML
Representation guide - January 2006
- Submit XLIFF 1.2 for
public review and consideration as OASIS Standard - February 2006
In addition, the XLIFF TC
will endeavour to deliver the following as
time and resources
permit:
- XLIFF 1.2 ResX
Representation Guide
- Review and input to
development of Standard Localisation Directives
Tag Library
- IGNITE Certification
Programme
Tony Jewtushenko
Director- R&D - Product
Innovator Ltd. (Ireland)
P: +353.1.8875183; M:
+353.87.2479057; W: www.productinnovator.com
