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] OASIS guide to writing a conformance clause


Thank you for drafting the conformant statement. As usual, it is good

I agree that the last (unwritten) part about accepting XLIFF files
generated/processed by other tools is difficult.

From the CMS perspective, we work with XLIFF files at the end points.
The CMS extracts XLIFF from source content and, once translated, merges
the XLIFF into the target content. The Ektron CMS uses the skeleton
approach and includes Ektron extensions in the XLIFF files. The CMS can
successfully import XLIFF files that it generated. The XLIFF file must
have a matching skeleton and include the Ektron extension information
unique to that CMS web site. 

With this in mind, I would suggest rewording " conformant applications
SHOULD preserve existing custom extensions " to " conformant
applications MUST preserve existing custom extensions ".


-----Original Message-----
From: Rodolfo M. Raya [mailto:rmraya@maxprograms.com] 
Sent: Tuesday, July 21, 2009 2:40 PM
To: xliff@lists.oasis-open.org
Subject: Re: [xliff] OASIS guide to writing a conformance clause

On Tue, 21 Jul 2009 10:44:03 -0700
<bryan.s.schnabel@tektronix.com> wrote:

> Here's a guide to writing a conformance clause from OASIS

Here's a first draft for discussion:

   XLIFF is an XML vocabulary, thereafter conformant XLIFF documents
   MUST be well formed and valid XML documents. 

   Conformant XLIFF documents MUST be valid instances of at least one of
   the official XML Schemas (Strict or Transitional) that are part of
   the XLIFF specification. As not all aspects of the XLIFF
   specification can be expressed in terms of XML Schemas, conformant
   XLIFF documents MUST also comply with all requirements indicated in
   section 3 of the specification document. 

   XLIFF documents MAY contain custom extensions, as defined in section
   2.5 (Extensibility). Applications that process conformant XLIFF files
   that contain custom extensions are not required to understand and
   process non-XLIFF elements or attributes. However, conformant
   applications SHOULD preserve existing custom extensions when
   processing conformant XLIFF files. 

   Applications that generate XLIFF documents MUST generate conformant
   XLIFF documents to be considered XLIFF compliant. 

I don't know how to properly express that XLIFF compliant applications
should be able to accept compliant XLIFF files generated and/or
processed by other XLIFF compliant tools. In my view, this is essential
for allowing the "Interchange" part of the XLIFF acronym. 

Best regards,
Rodolfo M. Raya <rmraya@maxprograms.com>
Maxprograms http://www.maxprograms.com

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

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