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] | [List Home]

Subject: Re: [xliff] RE: Filenaming

Yves - hold off on any renaming for now.

I see four options for document naming:
  1. Leave the names as they are,  change them only if peer-review / standards approval process flunks us on the basis of the document naming.
  1. Physically rename all the documents now.
  1. Create URL's that logically reference the existing documents - leave physical document names as they are.
  1. Create a second version of the documents - maintain originals as well 

I'm recommending option #1 as the best course of action - we will address the naming convention issue at the end of the peer review period,  if and when it becomes an issue.  Renaming in haste is a bit too risky,  and could create technical problems during the peer - review period.  It's very likely that we'll have to change the names after the peer review concludes,  before we submit to OASIS for standards review.  Over the next 45 days we must develop a plan for renaming with minimum disruption and re-work. After we've renamed the spec & supporting documents (by mid - Sept),  we'll have a ballot to accept the renamed and possibly revised documents as Committee Specification and supporting documents.

Any comments / disagreements / alternative suggestions?

If there's no further discussion on the issue of renaming,  then below is the proposed text of the XLIFF 1.1. peer review announcement that I intend to have Karl distribute on Friday.  Feel free to comment - but please be aware that I'm planning to send this to Karl tomorrow (Thursday):  

OASIS members, XML developers, standards and localisation industry colleagues:

The OASIS XLIFF TC has approved XLIFF 1.1 as a Committee Specification, and now starts a 45 day public review prior to submitting this specification to OASIS members for consideration as an OASIS Standard, in accordance with "Section 2 Standards Process" of the OASIS Technical Committee Process document (see http://www.oasis-open.org/committees/process.shtml#approval_spec).

The public review starts 11 Aug and ends 24 September 2003.

Link to the XLIFF 1.1 Specification documents are available at:

Link to XLIFF 1.1 Schema is available at:

Link to XLIFF 1.1 Whitepaper is available at:

Comments are welcome from all interested parties and may be submitted to the XLIFF comment list:

Persons who are not subscribed to this list may post comments to it but will have to confirm the message via a token return.

Any comments made can be viewed at http://lists.oasis-open.org/archives/xliff-comment/

Gerard Cattin des Bois wrote:
I agree. This naming convention needs revisiting. 

-----Original Message-----
From: Yves Savourel [mailto:ysavourel@translate.com] 
Sent: Tuesday, August 05, 2003 11:19 AM
To: Tony Jewtushenko
Cc: XLIFF list
Subject: [xliff] RE: Filenaming

Looks like we'll have to change the name of the spec to conform to the 
OASIS naming conventions.  Any chance you can do that over the next 
couple of days,  or if not can you send the doc to me and I'll do it?  
I could make the changes and forward to the webmaster by Thurday.
I can make the changes:

1- Rename the latest revision of 1.1 to xliff-core-1.1-cs.htm and the revision copy xliff-core-1.1-cs-4.htm (it will be the fourth revision).
2- Change the content of xliff-specification.htm to list the various versions and link to them.
3- Rename the schema to xliff-core-schema-1.1-cs.xsd

Note the change #3 has more implications than renaming the specification document. Tools have been already developed for 1.1 and have pointers to the schema's URL. It's also all over the example in the specification document.
We'll have to update it too. I don't think having two copies is a good thing, but it's an XSD file, not a HTML and can't be re-directed. Maybe doing an include of the new file would solve the problem, or should we just forget about allowing graceful modification.

The URL will apparently also change once again when it becomes an OASIS
standard: will it have also to be modified in the specification then? It is a little messy to have a public schema URL that keeps changing.

I'll do this tomorrow, except contrary notice.

You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/xliff/members/leave_workgroup.php


Tony Jewtushenko					mailto:tony.jewtushenko@oracle.com
Principal Product Manager				direct tel: +353.1.8039080
ST Tools Technology Team
Oracle Corporation, Ireland

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