RE: [xliff] Version Control Commit by DavidFilip

[Yves Savourel <ysavourel@enlaso.com>]

Hi all,

So, looking at the proposal for <item> in CTR, we would have:

[[
item

Container for a specific revision associated with a sibling element, or a child of a sibling element, to the change track module within the scope of the enclosing element.

Either:
	one or more <segment> or <ignorable> elements in any order.
Or:
	either:
		exactly one <source> element followed by at most one <target> element.
	or:
		exactly one <target> element.
Or:
	XLIFF Core Inline Elements and text in any order.
]]

A few initial notes:

I'm not sure that mixing four different content models in the same element is a good idea.
Parsing such content, even with automated mechanism like JAXB, is not easy.

I'm also not sure why we would need the second and third content (<source> and <source>+<target>) since they can be represented by the first and fourth content.

I'm also not understanding the definition part that says: "...to the change track module within the scope of the enclosing element."
What the "to" pertains to? It seems something is missing (or extra).

-ys