Subject: Re: [xliff] RE: Filenaming
- Advantage is that we don't have to make any changes, and existing applications continue to reference the document.
- Disadvantage is that this may lead to issues being raised during peer review, possibly leading to rejection of the spec on the basis of the doc naming convention. And we will ultimately need to rename, if/when the spec becomes an approved OASIS standard.
- Advantages: naming convention doesn't become an issue during peer / standards review processes; we define a process for renaming that can be used in the future.
- Disadvantages: work required renaming and editing documents; rename will impact existing implementations that reference the online XSD document
- Advantages: Low impact, superficial modification. Existing implementations unaffected.
- Disadvantages: Doesn't address the root problem - naming convention could still become an issue during peer review that leads to rejection; Will still need to rename physically if/when XLIFF becomes a standard
- Advantages: Moderate level of work. Addresses naming convention requirements; Existing implementations unaffected.
- Disadvantages: Creates a level of uncertainty which could lead to confusion - which document names do implementors reference; Complicates rollout of future revisions; Potential for documentation getting out of sync;
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/
I agree. This naming convention needs revisiting. Cheers, -Gérard -----Original Message----- From: Yves Savourel [mailto:email@example.com] Sent: Tuesday, August 05, 2003 11:19 AM To: Tony Jewtushenko Cc: XLIFF list Subject: [xliff] RE: FilenamingLooks 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. Cheers, -yves 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:firstname.lastname@example.org Principal Product Manager direct tel: +353.1.8039080 ST Tools Technology Team Oracle Corporation, Ireland