Re: [xliff] OASIS guide to writing a conformance clause

["Rodolfo M. Raya" <rmraya@maxprograms.com>]

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
> 
> http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html

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
-- 
Rodolfo M. Raya <rmraya@maxprograms.com>
Maxprograms http://www.maxprograms.com