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