XLIFF 1.2 phase-name attribute inconsistency

["Asgeir Frimannsson" <asgeirf@gmail.com>]

Hi all,

(again referring to XLIFF 1.2 Public Review Draft 03 - 25 Mar 07)

Another quick observation, now regarding the 'phase-name' attribute. Here is
a list showing the existing descriptions for this attribute (excluding the
<phase> element):

<count> "The optional
phase-name<file:///home/asgeir/xliff/xliff-core/xliff-core.html#phase-name>attribute
references the
<phase> <file:///home/asgeir/xliff/xliff-core/xliff-core.html#phase> in
which the count was produced."
<trans-unit> "The optional
phase-name<file:///home/asgeir/xliff/xliff-core/xliff-core.html#phase-name>attribute
references the phase that the
<trans-unit> is in."
<target> "The optional
phase-name<file:///home/asgeir/xliff/xliff-core/xliff-core.html#phase-name>attribute
references the
<phase> <file:///home/asgeir/xliff/xliff-core/xliff-core.html#phase> in
which the <target> was last modified."
<alt-trans> (missing)
<bin-unit> "The optional
phase-name<file:///home/asgeir/xliff/xliff-core/xliff-core.html#phase-name>attribute
references the phase that the
<bin-unit> is in."
<bin-target> "The optional
phase-name<file:///home/asgeir/xliff/xliff-core/xliff-core.html#phase-name>attribute
references the phase that the
<bin-target> is in."

Note:
1) the missing description for <alt-trans>. - Perhaps the phase-name value
is here tightly coupled with the alttranstype attribute, which also isn't
described here.
2) the inconsistency between <target> and <bin-target>: "is in" vs "was last
modified".
3) Some descriptions references the '<phase>' element, other use the textual
'phase'.


cheers,
asgeir

-- 
Asgeir Frimannsson
PhD Candidate
School of Software Engineering and Data Communications
Queensland University of Technology
126 Margaret Street, Level 3
Brisbane QLD 4001, Australia

Phone: (+61) 7 3138 9332 Mob: (+61) 405 412 696
Email: asgeirf@gmail.com