OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: XLIFF 1.2 phase-name attribute inconsistency


Some formatting errors in the first email making it hard to read, so
resending:

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 attribute references the <phase> in which
the count was produced."
<trans-unit> "The optional  phase-name attribute references the phase that
the <trans-unit> is in."
<target> "The optional phase-name attribute references the <phase> in which
the <target> was last modified."
<alt-trans> (missing)
<bin-unit> "The optional phase-name attribute references the phase that the
<bin-unit> is in."
<bin-target> "The optional 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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]