Hi Kris,
Sorry - the last few days have been filled with dr's appts and other stress-inducing activities.
The design below is correct - only the top level (Appendix A, Appendix B, etc.) start a new page (just like sections); A.1, etc. are run-ins.
Thanks!
Mary
On Jun 25, 2010, at 8:45 AM, Kristen James Eberlein wrote:
Hi, Mary.
I haven't back from you, so I'm going to telephone you this morning. Is
(603) 232-9090 your work phone number?
I don't want to touch on the namespace issue -- I'm leaving that in Don
Day's hands -- but I do want to ensure that I clearly understand all of
the other points so that we can avoid the sort of churn that we've been
experiencing.
I also want to check with you about the appendices. The draft of the
DITA 1.2 spec that the TC approved as CD 03 has the following structure
(which I implemented based on the design shown in the OASIS template at
http://docs.oasis-open.org/templates/OASISSpecificationTemplateV4.1.html#AB):
<pdf-toc.png>
Do you want each appendix topic -- for example, B.1, B.1.1, and B.1.2
-- starting on a separate page with a Level 1 header? Or should only
Appendix A and Appendix B be treated that way?
Looking forward to your help in resolving these
final formatting issues,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Secretary, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
-------- Original Message --------
Hi, Mary.
Please see my comments or questions below in <kje> tags.
Kris
BA930D6B-2C60-4803-BCDC-63151330EA4E@oasis-open.org" type="cite">
In the PDF version:
1. This Version URIs: text on the cover is fine, but the actual
hypertext links point to cd01
> The URI has been incorrectly changed to point to the
generic version rather than cd02; the URI was fine before - it was the
hypertext link that was incorrect
<kje>Help me understand,
since I obviously misunderstood your earlier comments. Is it the case
that the links in the "This version" section always point to a specific
version -- cd01, cd02, cs -- but the links in the "Latest version"
section always are the generic URIs? If so, is the following what you
want in the "This version" section?"
http://docs.oasis-open.org/dita/v1.2/cd02/spec/DITA1.2-spec.html
(Authoritative version)
http://docs.oasis-open.org/dita/v1.2/cd02/spec/DITA1.2-spec.pdf
http://docs.oasis-open.org/dita/v1.2/cd02/spec/DITA1.2-spec-chm.zip
http://docs.oasis-open.org/dita/v1.2/cd02/spec/DITA1.2-spec.zip
</kje>
BA930D6B-2C60-4803-BCDC-63151330EA4E@oasis-open.org" type="cite">
3. Namespace: this must be an actual hypertext link
<kje>By "actual hypertext link," do you mean a link to what you
call the "namespace document"? If so, where do you want to locate the
"namespace document"? Give us a URL, and we will reference it. (I am not sure why you mention the
focus area.)
The nomenclature is problematic, since the actual "Declared XML
namespace" is
xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/"
Perhaps this section should be retitled "Location of OASIS namespace
document"?</kje>
BA930D6B-2C60-4803-BCDC-63151330EA4E@oasis-open.org" type="cite">
5. There are some rules showing up that seem to be tied to examples and
should be removed; they appear to be tied to the heading below them.
> rules still appearing; see pg 33 - just prior to 2.1.2.2.5
<kje>I'll open an action
item to correct this aspect of the PDF formatting.</kje>
BA930D6B-2C60-4803-BCDC-63151330EA4E@oasis-open.org" type="cite">
6. Each Appendix should start a new page; same styling as 1st
level headings
> The section labeled 'appendices' should be removed or
turned into Appendix A.
<kje>I am reluctant
to have a lengthy list of appendices which would be at the same level
as major content. For example, if I followed your suggestion, the TOC
would look like this:
Introduction
Architecture specification
Language reference
Conformance
Appendix A
Appendix B
Appendix C
Appendix
D
Appendix E
Appendix F
Appendix
H
Appendix I
Appendix J
Instead, I'll reorganize the material as follows, which provides a better
alignment with the OASIS specification template:
Introduction
Architecture specification
Language reference
Non-normative information
Conformance
Appendix A. Acknowledgments
Please let me know ASAP if you think such a reorganization will require
a new TC vote.
</kje>
BA930D6B-2C60-4803-BCDC-63151330EA4E@oasis-open.org" type="cite">
NOTE: In the top section level head, the rule should be the same
purple as the headings themselves.
BA930D6B-2C60-4803-BCDC-63151330EA4E@oasis-open.org" type="cite">
3. The link back to the main page points to cd01
> this now incorrectly points to the generic URI rather than
cd02-specific
BA930D6B-2C60-4803-BCDC-63151330EA4E@oasis-open.org" type="cite">
On Jun 21, 2010, at 8:39 AM, Kristen James Eberlein wrote:
Mary,
you can get the latest ZIP file from the
following URL:
http://www.oasis-open.org/apps/org/workgroup/dita/download.php/38368/DITA1.2-CD02.zip
All the changes that you requested have been completed.
Best,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Secretary, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
-------- Original Message --------
Thanks to Seth Park for his work on the weekend:
Changes to PDF:
* Modified footer
* Modified styling of <example>
* Appendices each start on new page
-- Kristen Eberlein
The document revision named DITA 1.2, CD 02 submission (DITA1.2-CD02.zip)
has been submitted by Kristen Eberlein to the OASIS Darwin Information
Typing Architecture (DITA) TC document repository. This document is
revision #3 of DITA1.2-CD01-submission.zip.
Document Description:
View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=38368
Download Document:
http://www.oasis-open.org/committees/download.php/38368/DITA1.2-CD02.zip
Revision:
This document is revision #3 of DITA1.2-CD01-submission.zip. The document
details page referenced above will show the complete revision history.
PLEASE NOTE: If the above links do not work for you, your email application
may be breaking the link into two pieces. You may be able to copy and paste
the entire link address into the address field of your web browser.
-OASIS Open Administration
|