OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [xliff] Migration Policy Document

Title: Message
Hello Mark,
You do have a good point.
In addition, we were also trying to determine how to sift thru additional tags that may be there from other tools/namespaces and removing them would hurt the workflow process in particular nodes in the food chain.
So, I see two discussions threads here: one the need to clearly validate an XLIFF file, and second, the need to process an xliff file without cleaning it up of unknown tags.
We were thinking about exposing explicitly those unknown tags via a private or public namespace so validation could still take place. This, however does not address the second issue, thus the statement to be able to retain those unknown tags from older tools/scripts using xliff data.
THis issue is also related to extensibility which Yves is driving.
Gérard Cattin des Bois
Lead Program Manager, LocStudio Services
Windows Productivity Tools Team
gcatt@microsoft.com  (425) 706-1592
Symptom and sign of Inner Peace: An unmistakable ability to enjoy each moment...
-----Original Message-----
From: Mark Levins/Ireland/IBM [mailto:mark_levins@ie.ibm.com]
Sent: Tuesday, July 30, 2002 3:18 AM
To: Tony Jewtushenko <Tony.Jewtushenko
Cc: xliff@lists.oasis-open.org
Subject: Re: [xliff] Migration Policy Document

Hi Tony,

I've just one problem wrt the 'Cross-release compatibility guidelines' section. In this section you state that "Tools must not delete data that it does not understand" and "Tools must preserve unknown elements in the file". If a tool is validating, using either Schema or DTD, these comments cannot be applied if the version of the XLIFF in the file is later than the tool supports or if the tool uses an earlier Schema or DTD.
Perhaps the addition of something like "Tools should not try to validate later versioned XLIFF documents" might suffice.


Tony Jewtushenko <Tony.Jewtushenko@oracle.com>

07/25/02 06:33 PM

        To:        "xliff@lists.oasis-open.org" <xliff@lists.oasis-open.org>
        Subject:        [xliff] Migration Policy Document


I've revised the document based on discussions over the past two

Please reply with your comments by next Tuesday - if no major
contentious issues remain by then,  I will draft and distribute an email
ballot to approve the policy.


Tony Jewtushenko    mailto:tony.jewtushenko@oracle.com
Sr. Tools Program Manager   direct tel: +353.1.8039080
Product Management - Tools Technology Team
Oracle Corporation, Ireland

XLIFF 1.1 W.I.P. – 1.0 to 1.1 Migration Policy


Version Information:






11 June 02

Tony Jewtushenko

Initial Document


24 July 02

Tony Jewtushenko

Revisions based on 23 July 2002 TC Meeting.



Document Conventions:

The document is coded in the following way (adhering to Peter Reynolds's document convention):

Greenif there is agreement
Navy if more discussion is needed
and redif it is contentious.

Where I have made a change I have emphasised the changed word.



Migration Policy Proposals:

Rules for Major vs. Minor releases:

Support for Existing Users:

Rules for Name Changes:

Impact of Migration on Users Organisations:

Cross-release Compatibility Guidelines:

User Migration Assistance

Marketing, Public Relations and Education:


Rules for Major vs. Minor releases:
  1. Shall be comprised of small changes that would not require re-certification of supporting tools or technologies
  2. Shall deprecate but not remove any features present in the previous release.
  3. Shall increment the version number to the right of the decimal point.
  1. May be comprised of significant architectural changes that may require re-certification of supporting tools and technology.
  2. May delete features that were deprecated in previous releases.
  3. Shall result in an increment to the version number to the left of the decimal point.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC