It is likely that all parsers at this stage read the xml attributes as
strings unless they have used special code generation products which create
classes based on a schema.
So, I think the most flexible is to allow the id be a string.
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'>
Regards,
Enda
-----Original Message-----
From: Yves Savourel [mailto:]
Sent: 09 September 2003 21:42
To: XLIFF list
Subject: [xliff] ID value type
Hi,
Working on some XLIFF example I ran into a small problem in our schema:
I noticed that the value type of our different id are sometimes 'string'
sometime 'NMTOKEN'.
So, for example, because of the '\' the following id value is not valid:
<bin-unit id='work\image1.jpg' mime-type='image/jpeg'>
...
This wouldn't be too bad if we could escape the backslash, but even then,
it's not easy. The only ASCII non-letter and non-digits allowed are: '.',
'_', ':', and '-'. We can't use '$', '&', '%', '/', etc. Which makes
potentially a lot of characters to escape.
The id value type for the id attributes in <x>, <bpt>, etc. are 'string',
which allow pretty much anything. So I have two questions?
1- Shouldn't all id attribute have the same value type?
2- If yes, should this type be string or NMTOKEN or something else.
Thanks for any comments, etc.
-yves
To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/xliff/members/leave_workgroup.p
hp.
