RE: [xliff] More XLIFF schema changes

Tony,

 

Good question. xs:unique means if the
attribute is present, then it must be unique, but is not required. The xs:key
constraint means it must be unique and is required.

 

I agree group id should remain optional.
Therefore, it’s not a spec change, just a clarification.

 

Regards,

 

Doug Domeny

Software Analyst

 

Ektron, Inc.

+1 603 594-0249 x212

http://www.ektron.com

 

From: Tony
Jewtushenko [mailto:] 

Sent: Friday, April 28, 2006 12:28
PM

To: 'Doug Domeny';


Subject: RE: [xliff] More XLIFF
schema changes

 

I’m in process of
revising the spec to address the ID uniqueness issue.   In the midst
of the edits, I’ve noticed that the <group> id is an optional
attribute.  Given that we’re adding a uniqueness constraint for id,
shouldn’t it be a required attribute?  Is it even possible (in the
normative context) to impose a unique constraint on an optional
attribute?  I think shifting group id to a required attribute would
represent a pretty big change, no? 

 

I’m going to
publish a new revision to the spec momentarily, and in that version I will
leave the group id as optional.

 

Anyone have thoughts on
this issue?

 

Regards,

Tony

 

-----Original Message-----

From: Doug Domeny
[mailto:] 

Sent: 02 March 2006 22:21

To: 

Subject: [xliff] 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