Implementing XLFF 2.0 test suite files

[Ryan King <ryanki@microsoft.com>]

Hi TC folks,

 

In creating the XLIFF 2.0 OM that we’ve pushed up to GitHub (https://github.com/Microsoft/XLIFF2-Object-Model) we found some issues with some of the test suite files (https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/test-suite/core/valid/#_trunk_xliff-20_test-suite_core_valid_) when implementing validation tests. Apologies if these are known issues. I haven’t been able to attend calls or follow the list as closely as I would have liked over the past couple of months.

 

The following files contain duplicated ids across siblings, which depending on how tests are implemented, may mask the actual issue being tested:

·         .\core\invalid\bad_invalidextensionattributeonpc.xlf

·         .\core\invalid\bad_nonisolatedecwithoutstartref.xlf

·         .\core\invalid\bad_nonisolatedecwithstartref.xlf

·         .\core\invalid\bad_unknowndatarefendvalue.xlf

·         .\core\invalid\bad_unknowndatarefstartvalue.xlf

·         .\core\invalid\bad_unknowndatarefvalue.xlf

·         .\modules\invalid\bad-res_resourceitem-not-unique.xlf

·         .\modules\valid\good-res_source-has-no-content-and-href.xlf

 

The following contain a <res:target> language that doesn’t match document language, which depending on how tests are implemented, may mask the actual issue being tested:

·         .\modules\invalid\bad-res_resourceitem-not-unique.xlf   

·         .\modules\invalid\bad-res_resourceitemref-not-unique.xlf

·         .\modules\invalid\bad-res_source-has-content-and-href.xlf

·         .\modules\invalid\bad-res_source-xml_lang-not-same-as-xliff.xlf

·         .\modules\valid\good-res_resourceitem-unique.xlf

·         .\modules\valid\good-res_resourceitemref-unique.xlf

·         .\modules\valid\good-res_source-has-no-content-and-href.xlf

·         .\modules\valid\good-res_source-xml_lang-same-as-xliff.xlf

 

The following have a <source> that should be from another namespace, so it should be pre-fixed, e.g. <res:source …><abc:source>Hi</abc:source></res:source>:

·         .\modules\invalid\bad-res_source-has-content-and-href.xlf -

·         .\modules\invalid\bad-res_source-xml_lang-not-same-as-xliff.xlf

·         .\modules\valid\good-res_source-xml_lang-same-as-xliff.xlf

 

There are two “orphan” reourceItemRef that don’t point to anything: <res:resourceItemRef ref="r1"/> AND <res:resourceItemRef ref="r2" id="rr1"/> in the following:

·         .\modules\invalid\bad-res_resourceitem-not-unique.xlf

·         .\modules\valid\good-res_source-has-no-content-and-href.xlf

·         .\modules\valid\good-res_source-xml_lang-same-as-xliff.xlf

 

The following contain more than one ChangeTrack Module:

·         .\modules\invalid\bad-ctr_appliesto-not-using-ref-to-resolvableid.xlf

·         .\modules\invalid\bad-ctr_property-not-content-or-valid-attribute-ref.xlf

·         .\modules\invalid\bad-ctr_ref-not-pointed-to-resolvableid.xlf

·         .\modules\invalid\bad-ctr_revisions-not-using-ref-to-resolvableid.xlf

·         .\modules\valid\good-ctr_appliesto-using-ref-to-resolvableid.xlf

·         .\modules\valid\good-ctr_property-content-or-valid-attribute-ref.xlf

·         .\modules\valid\good-ctr_ref-pointed-to-resolvableid.xlf

·         .\modules\valid\good-ctr_revisions-using-ref-to-resolvableid.xlf

 

Other issues:

·         .\core\invalid\bad_nonisolatedecwithstartref.xlf  - startRef should be added to it.

·         .\core\valid\sample1.xlf  - <gls:translation ref="#m2" source="myTermbase"> should be <gls:translation ref="t-#m2" source="myTermbase">

·         .\modules\invalid\bad-fs_subfs-not-allowed-w-o-fs.xlf

o   <note id="n3" fs:fs="paragraph"> should be <note id="n3" fs:fs="p">

o   <note id="n4" fs:subFs="noFS"> should be <note id="n4" fs:subFs="no,FS">

·         .\modules\invalid\bad-slr_equivstorage-ec-not-isolated.xlf - In order for the <ec> to not be isolated, it should be in the same unit and not have an id.

 

Thank you and please let me know if we misunderstood any of these issues!

 

Thanks,

Ryan