- From: Sebastian Rahtz <Sebastian.Rahtz@oucs.ox.ac.uk>
- Date: Thu, 16 Mar 2006 14:52:06 +0000
- To: Jirka Kosek <jirka@kosek.cz>
- CC: Felix Sasaki <fsasaki@w3.org>, public-i18n-its@w3.org
Jirka Kosek wrote: > Because you have to declarace ITS namespace twice and attributes have to > be prefixed, even if elements are not (thanks to default namespace). ok, understood. it's not ideal. > What is more important, is that current proposal doesn't allow to use > attributes like its:translate on rule elements in the same way as on > arbitrary other elements. I mean that you can't use ITS to annotate > itself. (Other question is, whether this could be useful for something.) that's an interesting argument. I think I might start being convinced. "@its:translate" means "translateability of my parent element" "@translate" means "a translateabilty record I intend to take elsewhere" So I think you are right; not on grounds of verbosity or elegance, but because the syntax is _slightly_ different. -- Sebastian Rahtz *Open Source and Sustainability* 10-12 April 2006, Oxford http://www.oss-watch.ac.uk/events/2006-04-10-12/ Information Manager, Oxford University Computing Services 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 OSS Watch: JISC Open Source Advisory Service http://www.oss-watch.ac.uk
Received on Thursday, 16 March 2006 14:54:03 UTC