OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-adoption message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: Styles for XHTML version of whitepapers ( Was "RE: [dita-adoption] Summary of new OASIS process")


Hi Kris,

My apologies; I default reaction is to  think specification template. I should have asked. I'll have to see what's wrong since neither of those links should be redirected. I haven't yet created one for either the white paper or the basic note format since there hasn't been any need up until now; most TCs use either the OpenOffice or Word templates to create them and just export to HTML and PDF. If you have the need, I can get that done for you over the weekend. 

 I'm attaching PDFs of both formats for you; let me know which one you would prefer - or at least which one you would prefer to have first. I would love to have a conversation with you about the DITA toolkit processing and get a better understanding; my assumption was that essentially the same stylesheet would be used for both PDF and HTML creation.

 I'm also incorporating below my email to JoAnn and Gershon noting the differences between the the pre- and post-15 Oct White Paper template in case you don't have a copy of that.

If there's some different formatting requirements or something special the Adoption TC would like we can create a new template type based on the TC's needs. Beyond presentations, white papers, and a generic template I was at a bit of a loss with regard to coming up with different types; instead I have tried my best to make everyone aware that additional templates can be developed upon request.

Best regards,

Mary

===


Mary McRae <mary.mcrae@oasis-open.org>
to

GIF image

Joann Hackos <joann.hackos@comtech-serv.com>
cc
Gershon Joseph <gerjosep@cisco.com>
date
Thu, Oct 14, 2010 at 6:31 PM
subject
Re: [dita] DITA 1.2 Schema Issues
mailed-by

GIF image


Hi JoAnn,

I'm attaching the PDFs of the White Paper templates which is what the adoption TC used.  For most users TC Admin will be generating the front matter template and then prepending it the working draft submitted by the TC; in your case you'll need to continue as you have been until we have the production tools in-house.

So, on the cover you'll see a change to Editors (rather than authored by) followed by the name of the TC (rather than 'on behalf of') and a boxed note at the bottom of the page hat this is a Non-Standards Track WP ...

The inside cover then has the same set of information that is currently maintained in the specification template, and again, there is running footer throughout containing the Non-Standards Track disclaimer as well as the Working Draft revision and date.

The thing is that none of that stuff should show up in anything that's just a Working Draft; no OASIS logo, no copyright notice, no URIs, etc. because as a Working Draft it has no official standing. I'm making the assumption that your working drafts are actually passed around as DITA files and not actually run through the toolkit until you're ready to approve them as a CND? In which case that's exactly the right thing; the only difference is that you'll need to create the CNDs for me so we can upload them to docs.oasis-open.org.

Anything that already exists doesn't need to be reprocessed unless it hasn't been approved yet; this is just going forward. In other words, you don't need to take all of your existing docs and all of a sudden submit them for review. They're golden. Anything that isn't yet 'final', however, will need to conform to the new template and process.

===


NoteTemplate.pdf


WhitePaperFrontMatter.pdf




On Nov 11, 2010, at 8:29 PM, Kristen Eberlein wrote:

Mary, when I go to the http://docs.oasis-open.org/templates/ page and click any of the following links, they simply redirect to the top of the page:
 
 
The CSS file referenced there seems to be what I used as a resource when I created CSS styles for the DITA 1.2 spec; where the is information about how you want XHTML styled for white papers?
Best regards,
Kris
Kristen James Eberlein l DITA Architect and Technical Specialist l SDL Structured Content Technologies Division l (t) + 1 (919) 682-2290 l keberlein@sdl.com
Please consider the environment before printing this e-mail
 
From: Mary McRae [mailto:mary.mcrae@oasis-open.org] 
Sent: Thursday, November 11, 2010 10:59 AM
To: Kristen Eberlein
Cc: DITA Adoption TC
Subject: Re: [dita-adoption] Summary of new OASIS process
 
Sorry; I wonder why it loses the change lines/indents ...
 
There is no official page for templates; templates are now provided upon request. The HTML template and associated CSS can still be downloaded from http://docs.oasis-open.org/templates/.
 
Regards,
 
Mary
 


 
On Nov 11, 2010, at 9:04 AM, Kristen Eberlein wrote:


Mary, I think that your in-line corrections will be hard for people to read. Here is what I think you corrected:
 
·         You changed the following URLs to the less-specific http://docs.oasis-open.org/templates/TCAdminRequests.html address:
·         You added the following information; clarifications added in [red]:
o   Mary McRae: “At the time of approval [of a committee note draft], the Chair or designate must notify TC Administration by submitting the Committee Note Draft Creation / Upload Request. Since it is anticipated that the DITA Adoption TC will be using DITA as its editable source, the TC will also be responsible for providing HTML and PDF formats. Note that the work product will be QC'd at the time of submission and must conform to the appropriate template.”
o   Mary McRae: ”All TCs have a comment list (dita-adoption-comment).”
Mary McRae: “any changes made to a Committee Note Draft must be submitted for Public Review, whether or not as the result of the public review.”
 
I understand that the forms currently located at mary.mcrae.com will be moved to an OASIS site as soon as OASIS can offer that functionality, but I wanted our TC members to be able to access the forms and be aware of their contents. (When you reply to this e-mail, please not change the URLs.)
 
Thank you for providing JoAnn and Gershon with the updated whitepaper templates. Where is the official page where these templates are located? Also, please provide us with the template for the HTML; has OASIS created a CSS file that is used with the HTML format?
Best regards,
Kris
Kristen James Eberlein l DITA Architect and Technical Specialist l SDL Structured Content Technologies Division l (t) + 1 (919) 682-2290 l keberlein@sdl.com
Please consider the environment before printing this e-mail
 
From: Mary McRae [mailto:mary.mcrae@oasis-open.org] 
Sent: Wednesday, November 10, 2010 11:57 PM
To: Kristen Eberlein
Cc: DITA Adoption TC
Subject: Re: [dita-adoption] Summary of new OASIS process
 
Hi Kristen et al,
 
A few corrections noted inline. Also, more details can be found in the TC Handbook pages here:
 

I provided JoAnn and Gershon with PDFs of the updated white paper templates along with the specific changes in mid-October; if there are any questions with regard to the templates or anything else related to the process, please feel free to contact me. I'm happy to help.

Best regards,
 
Mary
 
 
 
On Nov 10, 2010, at 11:24 PM, Kristen Eberlein wrote:



Key links:
 
OASIS Technical Committee Process: http://www.oasis-open.org/committees/process.php
 
 
Here is a summary of how the new OASIS processes will affect our feature articles
 
·         Our feature articles will need to follow the  guidelines outlined in “Section 2.1.8 Work Product Quality”:http://www.oasis-open.org/committees/process.php#specQuality . This means, among other items, that we need to provide editable source, XHTML (or HTML), and PDF.
·         Our feature articles (now called committee notes) must follow the processes outlined in “Section 3 Approval Process.”
http://www.oasis-open.org/committees/process.php#standApprovProcess

Here is my understanding of how the new process will affect our work:
o   We register the work product: http://docs.oasis-open.org/templates/TCAdminRequests.html
 
Please do not use that address; it is subject to change. Please use the form links directly as displayed here: 



o   We approve the work product as a “Committee note draft.” This requires a full majority vote of the TC.
At the time of approval, the Chair or designate must notify TC Administration by submitting the Committee Note Draft Creation / Upload Request. Since it is anticipated that the DITA Adoption TC will be using DITA as its editable source, the TC will also be responsible for providing HTML and PDF formats. Note that the work product will be QC'd at the time of submission and must conform to the appropriate template.



o   We decide to submit a committee note draft for public review; this also requires a full majority vote of the TC. If approved by the TC, this draft becomes a “Committee Note Public Review Draft”; it must be accompanied by a “recommendation from the TC of external stakeholders who should be notified of the review.”
o   We request a 30-day public review from Mary McRae:  http://docs.oasis-open.org/templates/TCAdminRequests.html. This request form requires the following information, among others:
§  URI for the committee note draft at http://docs.oasis-open.org/
§  Link to the minutes for the Adoption TC meeting at which the TC approved the committee note draft and voted to request a review
o   Mary McRae announces the public review to the OASIS membership list and “optionally on other public mail lists.”
o   Non-TC Members post comments to the TC's public-comment list. [Do we have such as list?]
Yes. All TCs have a comment list (dita-adoption-comment)



We must acknowledge the receipt of each comment and track the comments received; at the end of the review period, we need to post a list of how each comment has been handled to our e-mail list.
o   If we make ANY changes to the committee note draft
any changes made to a Committee Note Draft must be submitted for Public Review, whether or not as the result of the public review.
 
as a result of the public review, we need to start the whole process over. The review period this time is only 15 days.
o   After a public review that does not generates any comments that result in the changes to the committee note draft, we can approve the work product as a committee note. This requires a special majority vote of the TC. If the 15-day review generated any comments, this vote cannot be held before seven days have passed since the close of the public review. To conduct the special majority vote, we need to notify Mary McRae that the TC is ready to vote and provide her with the location of the editable versions of the files. She sets up and conducts the ballot.
 



It’s not clear to me whether we’ll need to request that OASIS create and upload the committee note draft for us; there is a form for this at http://docs.oasis-open.org/templates/TCAdminRequests.html
Yes; see above.



.
Best regards,
Kris
Kristen James Eberlein l DITA Architect and Technical Specialist l SDL Structured Content Technologies Division l (t) + 1 (919) 682-2290 l keberlein@sdl.com
Please consider the environment before printing this e-mail
 
 
 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]