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

["Tom Comerford" <tom@supratext.com>]

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