XLIFF wiki updated to reflect 2009 roadmap

Title: Message

Hello,

 

I 
updated the wiki "News Section" to show the direction the TC decided upon.  
Please take a look at that section and let me know if we need to adjust it (http://wiki.oasis-open.org/xliff/FrontPage).

 

Rodolfo, if this meets with approval we might want to 
update the OASIS XLIFF pages with this information as well (public and 
TC).

 

Thanks,

 

Bryan

 

  

  
-----Original Message-----
From: 
   [mailto:] 
  
Sent: Monday, February 02, 2009 10:03 AM
To: 
  
Subject: [xliff] Offline work to get 
  XLIFF 1.2.1 done (and getting our meeting schedule back in 
  synch)

  
Hello,

  
 

  
Since we met on 
  Tuesday, and because of scheduling conflicts this week, I'll set up our 
  meeting for February to be our regular third Tuesday, February 
  17.

  
 

  
Meanwhile, as I 
  said in the meeting, I'll work behind the scenes to contact individuals to try 
  to get our XLIFF 1.2.1 Committee Draft ready for a TC vote (http://www.oasis-open.org/committees/process.php#standApprovProcess). 
  Perhaps we could have the Draft Spec, schemas, and Representation Guides in 
  the proper templates, and posted to the proper URLs by next meeting. I think 
  it is quite possible that we could have our Committee Draft (http://www.oasis-open.org/committees/process.php#committeeDraft) 
  approved by the TC in February, and begin the Public Review in March (http://www.oasis-open.org/committees/process.php#publicReview). 
  If the 60 day review does not turn up any substantive flaws, we could then try 
  to pass the Committee Specification (http://www.oasis-open.org/committees/process.php#committeeSpec) by 
  June.

  
 

  
And I will 
  also work behind the scenes to see about revamping our charter (http://www.oasis-open.org/committees/process.php#rechartering).

  
 

  
Thanks for getting 
  us to the point of turning XLIFF 1.2.1. Please, let's be prepared to do some 
  posting reviewing and voting.  And let's then get ready to turn our focus 
  to XLIFF 2.0.

  
 

  
Thanks,

  
 

  
Bryan