[no subject]

	A. 'id' attribute:
		In quite a number of context it would be better if one
could use GUIDs
		(since they are available and used for other types of
referencing anyhow)
	B. ordering according to input file:
		This is constraints would for example prevent people
from using the 'group'
		element (see next remark) in order to provide a
container e.g. for all error messages

8. Allow or recommend the 'group' element
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

A representation like

	<group restype=3D"string">
		<trans-unit id=3D"3"  resname=3D"s3"> <source>My
Disk</source></trans-unit>=20
		<trans-unit id=3D"4" resname=3D"s4"> <source>no
files</source></trans-unit>=20
	</group>

Looks as natural to me as one where the 'restype' attribute is repeated
on each and every 'trans-unit' element. In addition, it causes less
repetition/volume and might facilitate/accelerate certain processing
tasks.

9. Define a schema for validation and conformance testing
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D

The profile from my understanding does not use all XLIFF capabilities.
Accordingly, one could consider the creation of a schema (in a general
sense, not necessarily an XSD). Content producers and tool implementers
could use this schema as an additional guidance.

10. Specify conformance levels
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

Since some features may be hard to implement (cf. Florians posting
http://lists.oasis-open.org/archives/xliff/200509/msg00013.html) one
could imagine a distinction of different levels of conformance. This is
an approach which for example is taken for XSL:FO (cf.
http://www.w3.org/TR/2001/REC-xsl-20011015/slice8.html#conform). In our
case, we could for example specify go for

	A. basic conformance:

	Wrt. variable handling, an implementatiion with basic
conformance keeps the original format for example
=09
		template =3D At {2,time,short} on {2,date,long}, we
detected the planet.

	Wrt. to capability X, and implementation with basic conformance
...

	B. complete conformance:=20

	Wrt. variable handling, an implementatiion with complete
conformance uses the placeholder mechanism for example

		At <ph id=3D"1">{2,time,short}</ph> on <ph
id=3D"2">{2,date,long}</ph>,
		we detected the planet.

	Wrt. to capability X, and implementation with complete
conformance ...