Bryan, Tom, all,
same as Tom I "volunteer" (succumbing to only mild and friendly pressure by the acting editor) for the spec editor. I guess that together with Tom we should be able to steer the spec to a ballot resolution in January 2013.
Now, looking for a license of Oxygen XML Author :-0 I hear they donate them to W3C editors, any chance to get one for an OASIS editor?
Best regards
dF
Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
mailto:
On Tue, Nov 27, 2012 at 2:28 PM, Schnabel, Bryan S <> wrote:
Tom,
This is very good to hear. Thank you very much for this good news. As I re-read the duties of the XML Schema Editor, I am confident you have the skills to do a great job!
Many thanks,
Bryan
________________________________
From: [] on behalf of Tom Comerford []
Sent: Monday, November 26, 2012 11:40 PM
To:
Subject: RE: [xliff] Call for XLIFF 2.0 Editor(s)
Bryan, all,
I can to take on responsibilities for the schema. It’s been difficult to stay engaged here, having neither current clients nor any product involving localization. But I know my way around XML schema and I’m sure I can contribute something to the TC beyond just helping to achieve quorum.
Regards,
Tom
From: [mailto:] On Behalf Of Schnabel, Bryan S
Sent: Tuesday, November 20, 2012 3:09 PM
To:
Subject: [xliff] Call for XLIFF 2.0 Editor(s)
Hello,
As we mentioned in the meeting today, sadly, Rodolfo is resigning from his role as XLIFF 2.0 editor. I wish to personally express my gratitude for the amazing work he’s done.
As it stands I will be the acting editor until we find a qualified new editor. I assume Yves will continue to be the Inline Text spec and schema editor.
The duties of the XLIFF 2.0 editor fall into two categories, and could be filled by separate people.
1. Specification editor: needs to collate, edit, and compile DocBook files into the XLIFF 2.0 specification. This includes a version for core, and for modules. This will start with the unofficial editor draft (currently posted on the wiki), with the official committee draft as the next step, and ending up as the full OASIS specification.
2. XML Schema editor: needs to be proficient in XML and XML Schema. Duties include taking over ownership of the current editor draft, merging core, inline text, and core, and managing the XLIFF namespaces.
I might be leaving some details out, but this is the general direction.
Please contact me if you are interested in either role, the sooner the better. General questions are quite welcome.
Thanks,
Bryan
---------------------------------------------------------------------
To unsubscribe, e-mail:
For additional commands, e-mail:
