Thoughts on the F2F agenda

I haven’t seen any agenda for the XLIFF TC F2F meeting yet, so wanted to share some ideas for consideration. This is just food for thought – I’m interested in hearing what else people want to discuss and/or what default agenda items are  planned.

·
Completion of XLIFF 2.0:
o
Review any public comments / formulate response or recommendation
o
Plan timeframe and activities between now and release of XLIFF 2.0
·
Promotion of XLIFF 2.0:
o
How should this happen, what are the targets, how will we track progress?
o
Does it need a dedicated subcommittee?
o
How will we collect feedback from industry during 2.0 adoption/rollout?
o
What is needed to create healthy ecosystem around 2.0?
·
Consider certification authority for XLIFF 2.0 compatible tools?
o
Independent body that could certify compliance of XLIFF 2.0 tools, to encourage correct adherence to standard
·
Discuss process for making extensions publicly available and nominating them into the standard
·
Conformance criteria for XLIFF 2.0
o
What/how/when/etc. – I haven’t seen much detail regarding this
·
Future for XLIFF standard
o
Do we need 2.1, 2.2, etc. or do we jump to 3.0? What timeline should we consider for future versions?
o
Brainstorm potential features/direction for XLIFF 3.0
§
Convergence / connection with other standards
§
XLIFF API
§
…

Thanks,
Kevin.