OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xliff] ID value type

Hi Yves,

XML Schema does provide a way to enforce uniqueness within each <file>
element, while allowing repeated values within the xliff file (
http://www.w3.org/TR/xmlschema-0/#specifyingUniqueness ).  But I think you
mean assigning an attribute named "id" the simpleType "ID" prevents
assigning uniqueness in a certain scope (i.e., within each <file> element.
I agree that DTD and Schema require the type ID to be unique within an
entire file.

Traditionally attributes named "id" have had the type "ID."  The way the
XLIFF specification defines "id" though, it seems most appropriate for its
type to be string, from my point of view, rather than NMTOKEN.



-----Original Message-----
From: Yves Savourel [mailto:ysavourel@translate.com]
Sent: Wednesday, September 10, 2003 8:29 AM
To: XLIFF list
Subject: RE: [xliff] ID value type

Hi Enda,

> I have a question though regarding your sample...
> Would you not use the resname attribute for the text
> identifier, while the id is used as an internally unique
> id in the xliff file?
> <bin-unit id='1032' resname='work\image1.jpg' mime-type='image/jpeg'>

Yes, the resname should probably be there too and use that value. But the id
is driven by the tool, and it is not necessarily a numeric ID unique within
the XLIFF document (you could have several <file> elements using identical
IDs in a <xliff> element).

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]