RE: [xliff] Validation state in XLIFF 2.0

[Yves Savourel <ysavourel@translate.com>]

Thanks Bryan, I missed that bottom line.
I'll wait for Asgeir's input.
Thanks
-ys

> -----Original Message-----
> From: bryan.s.schnabel@tektronix.com [mailto:bryan.s.schnabel@tektronix.com]
> Sent: Monday, March 30, 2009 11:18 AM
> To: Yves Savourel; xliff@lists.oasis-open.org
> Subject: RE: [xliff] Validation state in XLIFF 2.0
> 
> Hi Yves,
> 
> I think you can go to this page http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking and find the
> text at the bottom of the page that says 'To create a new Feature, please use the form below, and enter
> a wiki-name such as "NameOfMyFeature" that identifies this feature. You will also need to edit this page
> and include the feature under the relevant section.' This is the tool Asgeir built for adding XLIFF 2.0
> features for consideration.
> 
> As we have informally identified Asgeir as the Wiki Gardener, it might be prudent to ask him to comment
> on this procedure as well.
> 
> By the way, I am also in favor of just using the state attribute to track status, and deprecating
> "approved."
> 
> Thanks,
> 
> Bryan
> 
> 
> -----Original Message-----
> From: Yves Savourel [mailto:ysavourel@translate.com]
> Sent: Monday, March 30, 2009 8:25 AM
> To: xliff@lists.oasis-open.org
> Subject: [xliff] Validation state in XLIFF 2.0
> 
> 
> Hi all,
> 
> What is the process to follow to add possible features to 2.0? (not content-related)
> 
> For example, I'd like the issue of the approved/state attribute to be solved. Should I just add an item
> in the wiki?
> 
> 
> Just a summary:
> 
> Currently a trans-unit can have a approved attribute set to "yes' and the state attribute of the <target>
> set to any value,
> including some clearly indicating that the translation is not ready. This is contradictory. It seems
> approved is just redundant for
> state="final".
> 
> In 1.2 in one place it says "The optional approved attribute indicates whether the translation has been
> approved by a reviewer":
> That is what the state attribute of <target> is for no?
> 
> In another place it says "Approved - Indicates whether a translation is final or has passed its final
> review." Is it final if the
> final review is done? If so why saying both? If not, what approved='yes' then means? that it is final or
> that the final review is
> done.
> 
> As XLIFF prime goal is to facilitate the exchange of data during a translation process, it is important
> to have a clear and well
> defined description of what are the expected behavior for the possible values of state and approved. I'm
> testing several XLIFF
> editor right now, and none of them do the same thing about setting state/approved: So it's almost
> useless for our localization
> process.
> 
> Thanks,
> -yves
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>