RE: [xliff] Change to xliff schema for optional context-group name

Bryan,

Attached are the two samples. Each has two context-group tags. Both had a name attribute, now only one does.

Regards,

Doug Domeny
ektron, inc.
http://www.ektron.com

From: bryan.s.schnabel@exgate.tek.com [mailto:bryan.s.schnabel@exgate.tek.com]
Sent: Tuesday, March 20, 2007 2:26 PM
To: ddomeny@ektron.com; xliff@lists.oasis-open.org
Subject: RE: [xliff] Change to xliff schema for optional context-group name

Thanks for fixing this so quickly Doug. Would it be difficult for you to edit one of our sample documents (like Sample_AlmostEverything_1.2_transitional.xlf or Sample_AlmostEverything_1.2_strict.xlf) to illustrate the problem with the previous XSDs?

Thanks,

Bryan

-----Original Message-----
From: Doug Domeny [mailto:ddomeny@ektron.com]
Sent: Tuesday, March 20, 2007 10:00 AM
To: xliff@lists.oasis-open.org
Subject: [xliff] Change to xliff schema for optional context-group name

All,

The xsd:key tag requires that the identifier by defined (in this case, the ‘name’ attribute of the context-group). The xsd:unique tag is the same as xsd:key, except that the identifier may be undefined. I checked the other xsd:key elements in the schema and each of those identifiers are required and therefore xsd:key is appropriate.

The corrected schemas are attached.

Changed

    <xsd:key name="K_context-group_name">

      <xsd:selector xpath=".//xlf:context-group"/>

      <xsd:field xpath="@name"/>

</xsd:key>

To

    <xsd:unique name="U_context-group_name">

      <xsd:selector xpath=".//xlf:context-group"/>

      <xsd:field xpath="@name"/>

    </xsd:unique>

Regards,

Doug Domeny
ektron, inc.
http://www.ektron.com

xliff message