More XLIFF schema changes

All,

 

Rodolfo pointed out to me that <group id>,
<trans-unit id> and <bin-unit id> must be unique within a
<file> because they are used to identify the element “within the
file”. More specifically, all the <group id> values must be unique
within <file> with respect to other <group> tags. All
<trans-unit id> and <bin-unit id> values must be unique within
<file> with respect to other <trans-unit> or <bin-unit> tags.
That is, a <group> and a <trans-unit> may have the same id value,
but a <trans-unit> and a <bin-unit> may not have the same id value.

 

I recommend explicitly stating that the id attribute must be
unique (as stated above) in the specification.

 

With this understanding, the constraints for the xid
attribute were also possible.

 

I haven’t added constraints for the id attribute in
inline tags (e.g., g, ph).

 

I’ve added the constraints to the XLIFF 1.1 strict and
XLIFF 1.2 core & strict schemas, which are attached.

 

Attached is a zip with 3 schema files.

 

xliff-core-1.2-20060302.xsd

 

The tool-id attribute was missing from the elements that should
have it (except the ‘tool’ tag).

Constraints were also added, including group id, trans-unit
id, bin-unit id and xid.

 

xliff-strict-1.1-20060302.xsd

 

The tool-id attribute was missing from the elements that
should have it (except the ‘tool’ tag).

Constraints were also added, including group id, trans-unit
id, bin-unit id and xid.

Deprecated elements and attributes are prohibited.

 

xliff-strict-1.2-20060302.xsd

 

The tool-id attribute was missing from the elements that
should have it (except the ‘tool’ tag).

Constraints were also added, including group id, trans-unit
id, bin-unit id and xid.

Deprecated elements and attributes are prohibited.

 

Regards,

 

Doug Domeny

Software Analyst

 

Ektron, Inc.

+1 603 594-0249 x212

http://www.ektron.com

 

 

XliffSchemas20060302.zip