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

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

On Dec 23, 2010, at 11:52 AM, JoAnn Hackos wrote:

> Jeff,
> The Adoption TC has been developing feature articles, not committee
> notes. Our feature articles are only provided in PDF. Thus, HTML is a
> new requirements because our feature articles must now be released as
> committee notes.

What were they released as before?

 From the (old) TC Process:
"Editable formats of all versions of TC documents must be delivered to  
the TC’s document repository. TC Working Drafts may be in any format  
(i.e. produced by any application). All TC-approved versions of  
documents (i.e. Committee Drafts, Public Review Drafts, and Committee  
Specifications) must be delivered to the TC’s document repository in  
the (1) editable source, (2) HTML or XHTML, and (3) PDF formats; and  
the TC must explicitly designate one of those delivered formats as the  
authoritative document. Any links published by the TC shall be to the  
HTML, XHTML and/or PDF formats stored using repositories and domain  
names owned by OASIS and as approved by the TC Administrator."

cheers,
  jeff



>
> JoAnn Hackos
> Co-Chair DITA Adoption TC
>
> JoAnn Hackos PhD
> President
> Comtech Services, Inc.
> joann.hackos@comtech-serv.com
> Skype joannhackos
>
>
>
>
> -----Original Message-----
> From: Jeff Mischkinsky [mailto:jeff.mischkinsky@oracle.com]
> Sent: Thursday, December 23, 2010 12:11 PM
> To: Kristen Eberlein
> Cc: chairs@lists.oasis-open.org
> Subject: Re: [chairs] Why the DITA Adoption TC cares about "templates"
>
> 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
>
>
>
>
>
>
>
>
>

--
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