OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  OASIS guide to writing a conformance clause

    Posted 07-21-2009 17:45 
    Here's a guide to writing a conformance clause from OASIS

http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html


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

    Posted 07-21-2009 18:42 
    On Tue, 21 Jul 2009 10:44:03 -0700


  • 3.  RE: [xliff] OASIS guide to writing a conformance clause

    Posted 07-22-2009 13:12 
    Rodolfo,

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

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 ".

Regards,
Doug


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


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

    Posted 07-22-2009 13:44 
    On Wed, 22 Jul 2009 09:12:16 -0400
"Doug Domeny"


  • 5.  RE: [xliff] OASIS guide to writing a conformance clause

    Posted 07-22-2009 18:14 
    Rodolfo,

I like the new proposed paragraph and would include part b) even if we
decide applications must preserve custom extensions. The redundancy
stresses its importance and more obvious to the casual reader.

If a processing tool removes custom extensions, then it will almost
certainly cause a failure downstream when the tool that initially
inserted the extensions processes the modified XLIFF file without them.

A processing tool can remove custom extensions that it understands, but
must retain unknown extensions.

Regards,
Doug


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 6.  RE: [xliff] OASIS guide to writing a conformance clause

    Posted 07-22-2009 22:14 
    Hi all,

Another thought on this topic: Custom elements is just one part of what
would be expected to be preserved during processing of an XLIFF document
by tools that are 'compliant'. 

For example if the


Related Content