Re: [chairs] Why the DITA Adoption TC cares about "templates"

[Jeff Mischkinsky <jeff.mischkinsky@oracle.com>]

hi kristen,
   one clarification below
On Dec 17, 2010, at 2:37 PM, Kristen Eberlein wrote:

> Based on off-list e-mails, I thought I should clarify some issues:
>
> ·         The DITA Adoption TC authors its white papers in DITA.
> ·         The new processes now require us to provide editable  
> source, PDF, and XHTML for the white papers.

I don't believe this is a new requirement. I searched back, and found  
the requirement going all the way back to the August 2006 version of  
the TC Process (where i stopped searching).
Whether it's been enforced is a different question. ;-)

For the record:  all the previous versions of the TC Process can be  
found on linked from http://www.oasis-open.org/committees/process.php

cheers,
   jeff

> ·         We cannot code the necessary transformations for XHTML  
> without knowing what the requirements (font, font size, font weight,  
> headers, footers, tables, etc.) are.
> ·         We want the requirements to be defined and stable:
> o   We want to have a clearly specified set of requirements so that  
> we can ensure that our work products meet them.
> o   We do not want to have to redevelop the transformations except  
> at specified and set intervals.
> Best regards,
> Kris
> Co-chair, OASIS DITA Technical Committee
> Charter member, OASIS DITA Adoption Committee
> Kristen James Eberlein l DITA Architect and Technical Specialist l  
> SDL Structured Content Technologies Division l (t) + 1 (919)  
> 682-2290 lkeberlein@sdl.com
>  <image001.jpg>
> Please consider the environment before printing this e-mail
>

--
Jeff Mischkinsky			          		jeff.mischkinsky@oracle.com
Sr. Director, Oracle Fusion Middleware 				+1(650)506-1975
	and Web Services Standards           			500 Oracle Parkway, M/S 2OP9
Oracle								Redwood Shores, CA 94065