RE: [xliff] RE: Problems validating XLIFF files with 2.0 schemas

["Schnabel, Bryan S" <bryan.s.schnabel@tektronix.com>]

Hi Tom and Yves,

Thanks for this fix. It cut my reported errors from Oxygen down to just three "Unique Particle Attribution."  And I am suspicious of these.

Do we trust these error reports?

System ID: C:\Program Files\Oxygen XML Editor 14\frameworks\xliff02\modules\matches.xsd
Description: cos-nonambig: "urn:oasis:names:tc:xliff:document:2.0":originalData and WC[##other:"urn:oasis:names:tc:xliff:matches:2.0",""] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
Start location: 44:25
URL: http://www.w3.org/TR/xmlschema-1/#cos-nonambig
============================
System ID: C:\Program Files\Oxygen XML Editor 14\frameworks\xliff02\xliff_core_2.0.xsd
Description: cos-nonambig: "urn:oasis:names:tc:xliff:metadata:2.0":metadata and WC[##other:"urn:oasis:names:tc:xliff:document:2.0",""] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
Start location: 139:21
URL: http://www.w3.org/TR/xmlschema-1/#cos-nonambig
===============================
System ID: C:\Program Files\Oxygen XML Editor 14\frameworks\xliff02\xliff_core_2.0.xsd
Description: cos-nonambig: "urn:oasis:names:tc:xliff:matches:2.0":matches and WC[##other:"urn:oasis:names:tc:xliff:document:2.0",""] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
Start location: 169:21
URL: http://www.w3.org/TR/xmlschema-1/#cos-nonambig

Thanks,

Bryan

-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Tom Comerford
Sent: Monday, October 07, 2013 3:07 PM
To: 'Yves Savourel'; xliff@lists.oasis-open.org
Subject: RE: [xliff] RE: Problems validating XLIFF files with 2.0 schemas

Hi Yves,

The problem is that in the metadata schema, meta is defined with the type attribute, but its (schema) type is set to xlf:attrType_type instead of xs:string. I'll get this fixed ASAP, and I'll also look for other potential issues of this kind. Thanks for finding this.

Regards,

Tom

-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Yves Savourel
Sent: Monday, October 07, 2013 01:23 PM
To: xliff@lists.oasis-open.org
Subject: [xliff] RE: Problems validating XLIFF files with 2.0 schemas

Hi Tom, all,

The changes you made (rev 328) seem to have solved most of the issues, thanks.
(there is obviously still the issue of making a distinction between extended elements vs modules, but that is another discussion).

I'm getting errors on the values for mda's type attribute.
For example with this:

<file id="f1">
  <mda:metadata xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0">
   <mda:metagroup category="someCat">
    <mda:meta type="mtype1">info-mtype1</mda:meta>
    <mda:metagroup category="subCat">
     <mda:meta type="mtype2">info-mtype2</mda:meta>
    </mda:metagroup>
   </mda:metagroup>
  </mda:metadata>
...

I'm getting a bad value for mtype1 and mtype2 and the error refers to the value for the type attribute in the core.
The validator seems to think type if of the core namespace (which is declared in <xliff> in my example). As far as I know an un-qualified attribute is considered part of the namespace of the element where it is declared no?

Any thoughts?

-yves




---------------------------------------------------------------------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 


---------------------------------------------------------------------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php