Crediting Others in Chapters & Sections

Hello all,

I have set up a docbook and am well along my way to finishing it, but
the one thing I can't seem to find any documentation on would be how
to credit a chapter or section to a different author.

Basically I'm writing the manual for the Koha Open Source ILS.  I have
written most of the manual, but there are some sections or chapters
that were submitted by others.  I want to credit those sections with
that author - is it possible?

Nicole C. Engard
Koha Documentation Manager

Re: Crediting Others in Chapters & Sections

In DocBook v5.0, this should be in the <info> element. For earlier 
versions, it would be in the <chapterinfo> or <sectioninfo>.

HTH,

--Scott

Nicole Engard wrote:
> Hello all,
> 
> I have set up a docbook and am well along my way to finishing it, but
> the one thing I can't seem to find any documentation on would be how
> to credit a chapter or section to a different author.
> 
> Basically I'm writing the manual for the Koha Open Source ILS.  I have
> written most of the manual, but there are some sections or chapters
> that were submitted by others.  I want to credit those sections with
> that author - is it possible?
> 
> Nicole C. Engard
> Koha Documentation Manager
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-unsubscribe <at> lists.oasis-open.org
> For additional commands, e-mail: docbook-help <at> lists.oasis-open.org
> 

Re: Crediting Others in Chapters & Sections

Thank you so much - I don't know why I thought that the <info> tag
could only be used at the beginning of the book. Time to go through
and add that for various chapters.

Thanks again,
Nicole C. Engard

On Wed, Dec 9, 2009 at 4:32 PM, Scott Hudson
<scott.hudson <at> flatironssolutions.com> wrote:
> In DocBook v5.0, this should be in the <info> element. For earlier versions,
> it would be in the <chapterinfo> or <sectioninfo>.
>
> HTH,
>
> --Scott
>
> Nicole Engard wrote:
>>
>> Hello all,
>>
>> I have set up a docbook and am well along my way to finishing it, but
>> the one thing I can't seem to find any documentation on would be how
>> to credit a chapter or section to a different author.
>>
>> Basically I'm writing the manual for the Koha Open Source ILS.  I have
>> written most of the manual, but there are some sections or chapters
>> that were submitted by others.  I want to credit those sections with
>> that author - is it possible?
>>
>> Nicole C. Engard

RE: DocBook: The Definitive Guide, Second Edition

|  -----Original Message-----
|  From: Dick Hamilton 
|  Sent: Saturday, June 27, 2009 12:21 AM
|  
|  I'm pleased to announce that O'Reilly will be publishing
|  the second edition of DocBook: The Definitive Guide in
|  collaboration with XML Press. Here is a link to the book
|  page at XML Press:
|  
|  http://xmlpress.net/publications/docbook-tdg-second-edition/
|  
|  Norm will again be the author, and I will be editor.
|  
|  The second edition will retain the basic structure of the
|  original edition, updated of course for DocBook 5.0.
|  
|  We are currently aiming for publication this year, but
|  do not have an exact publication date at this time.

This subject has been very quiet. 

Today, I noticed that there is a "Rough Cuts" version[1] of the second
edition, but I haven't seen any announcement about this. How close to a
"final cut" is it? 

There are several TDG doc requests at SourceForge[2]. Are there any plans to
fix (or comment on) these issues?

Mauritz

RE: DocBook: The Definitive Guide, Second Edition

Mauritz,

Work has been proceeding on the book, and it is currently in technical
review. I believe the version of the book in Short Cuts is identical to
the version being reviewed.

I think the book is getting pretty close, though that will of course
depend of the results of the technical review.

Thanks for the pointer to the sourceforge requests. I was unaware of
them, but I will look at them now.

Best Regards,
Dick
---------------------------------
XML Press
XML for Technical Communicators
http://xmlpress.net
(970) 231-3624 

> -----Original Message-----
> From: Mauritz Jeanson [mailto:mj <at> johanneberg.com] 
> Sent: Thursday, December 10, 2009 2:29 PM
> To: 'Dick Hamilton'; docbook <at> lists.oasis-open.org; 
> docbook-tc <at> lists.oasis-open.org
> Subject: RE: [docbook] DocBook: The Definitive Guide, Second Edition
> 
> 
> |  -----Original Message-----
> |  From: Dick Hamilton 

RE: DocBook: The Definitive Guide, Second Edition

Mauritz,

Thanks for pointing out the Doc Requests in the tracker. I have resolved
and closed all except 6 of the open requests in the 2nd Edition. The
ones that remain open are:

1) Requests to add Simplified, Slides, and Website to the document. We
will probably add at least some mention of these variants, but I'm not
sure of the details, so I left them open.

2) One request related to the errata page, which will need to be
addressed after publication.

3) Two requests related to examples that still need investigation.

Best Regards,
Dick
---------------------------------
XML Press
XML for Technical Communicators
http://xmlpress.net
(970) 231-3624 

> -----Original Message-----
> From: Mauritz Jeanson [mailto:mj <at> johanneberg.com] 
> Sent: Thursday, December 10, 2009 2:29 PM
> To: 'Dick Hamilton'; docbook <at> lists.oasis-open.org; 
> docbook-tc <at> lists.oasis-open.org
> Subject: RE: [docbook] DocBook: The Definitive Guide, Second Edition
> 

Status of Website DTD

Transclusion

Hello world,

There's an open RFE about transclusion

  http://sourceforge.net/tracker/?func=detail&aid=2820947&group_id=21935&atid=384107

The TC's initial position was to push back, suggesting that the right
technology for the task is XInclude.

Unforunately, XInclude isn't a complete solution because getting the
content transcluded doesn't solve the entire problem. And it doesn't
help that the the standardized XPointer schemes are fairly brittle.

The TC would like to collect a set of use cases and requirements for
transclusion. Here are the requirements that I can think of (with help
From the comments in the REF).

1. Transclusion can introduce duplicate xml:id values. It should be
possible to specify a strategy for changing xml:id values in the
transcluded content so that this is not the case.

2. Using the XInclude framework and element schemes, it's only
possible to transclude a single element. It should be possible to
specify ranges, at least ranges of sibling elements.

3. The XInclude framework and element schems are a little bit brittle.
Are there more robust schemes that we could encourage implementors to
support?

What other requirements are there?

                                        Be seeing you,
                                          norm

--

-- 
Norman Walsh <ndw <at> nwalsh.com>      | Wink at small faults; for thou has
http://www.oasis-open.org/docbook/ | great ones.--Thomas Fuller (II)
Chair, DocBook Technical Committee |

RE: Transclusion

4. Validation. The author needs a way to know if the document is still
going to be valid post-transclusion. 

David

> -----Original Message-----
> From: Norman Walsh [mailto:ndw <at> nwalsh.com] 
> Sent: Friday, December 11, 2009 3:17 PM
> To: docbook <at> lists.oasis-open.org
> Subject: [docbook] Transclusion
> 
> Hello world,
> 
> There's an open RFE about transclusion
> 
>   
> http://sourceforge.net/tracker/?func=detail&aid=2820947&group_
id=21935&atid=384107
> 
> The TC's initial position was to push back, suggesting that 
> the right technology for the task is XInclude.
> 
> Unforunately, XInclude isn't a complete solution because 
> getting the content transcluded doesn't solve the entire 
> problem. And it doesn't help that the the standardized 
> XPointer schemes are fairly brittle.
> 
> The TC would like to collect a set of use cases and 
> requirements for transclusion. Here are the requirements that 
> I can think of (with help From the comments in the REF).
> 
> 1. Transclusion can introduce duplicate xml:id values. It 
> should be possible to specify a strategy for changing xml:id 
> values in the transcluded content so that this is not the case.
> 
> 2. Using the XInclude framework and element schemes, it's 
> only possible to transclude a single element. It should be 
> possible to specify ranges, at least ranges of sibling elements.
> 
> 3. The XInclude framework and element schems are a little bit brittle.
> Are there more robust schemes that we could encourage 
> implementors to support?
> 
> What other requirements are there?
> 
>                                         Be seeing you,
>                                           norm
> 
> -- 
> Norman Walsh <ndw <at> nwalsh.com>      | Wink at small faults; 
> for thou has
> http://www.oasis-open.org/docbook/ | great ones.--Thomas 
> Fuller (II) Chair, DocBook Technical Committee |
> 

test

test