gmane.text.docbook.misc

DocBook Technical Committee Meeting Agenda: 19 June 2013

Bob Stayton — 2013-06-17T20:21:13

DocBook Technical Committee Meeting Agenda: 19 June 2013
=============================================================

The DocBook Technical Committee will meet on Wednesday, 19 June 2013 at
1:00pm ET for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
 Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 17 July 2013
4. Review of the agenda.
5. Review of open action items

  a.  Norm to publish an XSD for 5.1 when it is finished.

  b.  Norm to follow up on OASIS mirroring the schema directory.

  c.  Larry to try mapping slides to assembly.

  d.  Norm to clarify bridgehead entry in TDG to indicate
      that bridgeheads are not numbered like sections.

  e.  Norm to update The Definitive Guide that the
      behavior of nested links is undefined by the standard.

  f.  Norm to prevent link element nested within link element in DocBook 
5.1.

  g.  Norm to produce a DocBook 5.1 candidate release.

  h.  Norm to follow up on RFE 3491860 license tag

  i.  Norm to add result element to DocBook 5.1 schema.

  j.  Dick to fix the DocBook5 conversion stylesheet on SourceForge.

  k.  Bob to review Dick's fixes to the conversion stylesheet.

  l.  Norm to change info from "zero or one" to "zero or more"
      in DocBook 5.1.

  m.  Norm to pull the rdfalite schema together as a non-normative
      release candidate.

  n.  Norm to provide Jirka with access to the schema repository
      for ITS 2.0.

6.  OASIS website issues

7.  Publisher's and eLearning subcommittee reports

8.  Transclusion in DocBook

9.  DocBook 5.1 release

10.  Change info instance from one to many.

Continued from last meeting.

11.  Review of Requests for Enhancement

*****************************************
Note that SourceForge renumbered all tracker
items during the recent project upgrade.
The unique numbers across projects have been
replaced by a new sequence within each tracker
(now called Tickets).  You can still search
on the old tracker number.  I include the
new ticket numbers below.
*****************************************

    To browse a specific RFE, enter the URL (on one line):

      https://sourceforge.net/p/docbook/rfes/300/

    RFEs to revisit for 6.0

    247   1907003  biblioid content model too broad

   RFEs under discussion

   Ticket  Tracker
    260   2820947  Ability to transclude text
    273   3035565  Allow sections at any level
    291   3491860   license tag
    300   3593209   Add see/seealso under
    301   3599576   'info' wrapper element for processing titlepage elements
    302   3608790   Microdata or RDFa 1.1 Lite support for schema.org

   No New RFEs


-----

[1] https://lists.oasis-open.org/archives/docbook-tc/201305/msg00013.html


Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

Recommendation for XSLT book?

ольга крыжановская — 2013-06-16T12:36:04

Can any one recommend a programmers book for learning XSLT?

Olga

Book series data

Brad Scott — 2013-06-11T10:13:41

Hi

I'm working on documentation to standardise DocBook usage for an 
academic publisher for (mostly) humanities and social science titles, 
and am using DocBook Publisher as my starting point. Most of the time 
I'm simply enforcing < at >role values in our local customisation layer.

The plan is to use this for backlist conversion as well as an XML first 
workflow in the near future.

I'd be interested to know how people have marked up some prelims 
content, especially book series data (ie metadata about the <book> not 
any bibliographic references therein).

Initially, I was thinking of something like this:

<bibliomisc role="series">
<phrase role="seriesVolNo">10</phrase>
<phrase role="seriesISSN">1234-5678</phrase>
<phrase role="seriesName">The Library of Aramaic Studies</phrase>
</bibliomisc>

but am also aware that sometimes the half title verso (or even the half 
title itself) includes more comprehensive series data, or lists of 
related titles. How have other people resolved this? I've seen this kind 
of thing in some book/info examples:

<cover role="halfTitleVerso">
<bibliolist>
<bibliomisc role="series">
<phrase role="seriesVolNo">10</phrase>
<phrase role="seriesISSN">1234-5678</phrase>
<phrase role="seriesName">The Library of Aramaic Studies</phrase>
<!-- Lots more bibl details etc -->
</bibliomisc>
</bibliolist>
</cover>

Does this seem reasonable, or are there more standard methods that users 
have adopted?

Thanks

Brad

Changing the presentation of numbered lists and sections

Kevin Bird — 2013-06-07T11:19:22

Hello,

In an <orderedlist numeration="arabic">, <listitems> are rendered (in HTML);

1. lisitem one
2. listiem two
...

Are there any attributes that I can add to the orderedlist (and/or section elements) that will change the presentation (in HTML) to

1). listiem one
2). lisitem two

Or even ...

(1) lisitem one
(2) listiem two
 
If the answer is 'you need to create a customization layer', could someone please point me in the right direction?
For information, my section elements are nested to level 6.

Many thanks.

--
Kevin

Epigraph for parts

Christopher Culver — 2013-06-05T16:27:33

The document that I am preparing in Docbook 5 has an epigraph following
the part title. My XML editor is reporting that <epigraph> cannot occur
immediately inside <part>, only inside <chapter>. Is this really the
case?  Considering how common it is for books to have epigraphs on a new
part title page, this seems like a serious deficiency.

What workaround would the community propose? Putting epigraph after the
first chapter tag would not work, as that chapter already has its own
epigraph.

xml parsing

Alex Kleider — 2013-06-04T03:18:45

As a new comer to DocBook I've bee using the following tool chain:

jing /usr/share/xml/docbook/schema/rng/5.0/docbook.rng 
docbookDocument.xml
xmlto --skip-validation html bluebook.xml

It seems to work, but:

 From my reading:
DocBook.xml must first be checked for XML parsing errors before it is
validated against docbook.rng (RelaxNG grammer and Schematron rules.)
Jing is a RelaxNG validator (in Java.)

Does Jing also check xml parsing errors or should I be using another 
tool first?
I can't find clarification of this issue on the Jing site (or anywhere 
else, for that matter.)

I've been using vim as my editor, on a Linux (Ubuntu) platform.

Any advice/guidance appreciated.
Thanks.

alex

Quote over multiple paragraphs

Christopher Culver — 2013-06-03T11:53:36

What is the preferred way of marking up quotations that run over several
paragraphs (but which are not blockquotes)? The quote tag is not allowed
outside of the para tag.

In English-language publications, when a quotation runs over several
paragraphs, the paragraphs are usually preceded by an opening
quotation mark, but they do not have a closing quotation mark unless
they are the last paragraph. I need to find out how to achieve this
effect with Docbook and the XSL stylesheets, or to at least represent
this semantically within Docbook so that I can write my own XSL.

How to get a proper UTF-8 HTML with umlaut

2013-06-03T08:46:12

Hi,

I tried to get HTML with characters like Ü, Ä, Ö .
Just I used th ISO-8851-9 (default), but today we 
had to change the encoding to UTF-8. So I read 
many thing about that:

Using xsltproc with --stringparam chunker.output.encoding UTF-8
Or 
Setting the xslt-output to

  <xsl:output method="xml"
              encoding="UTF-8"
              doctype-system="http://www.w3.org/TR/html4/strict.dtd"
              doctype-public="-//W3C//DTD HTML 4.01//EN" />
  or
  <xsl:output method="html"
              encoding="UTF-8"
              doctype-system="http://www.w3.org/TR/html4/strict.dtd"
              doctype-public="-//W3C//DTD HTML 4.01//EN" />

But all I've got is .

  ShowExt Ã¼berarbeitet

Instead of
 
 ShowExt überarbeitet

Maybe somebody can give me a hint how to change this.
Thanks and
Best regards

Markus

DocBook Technical Committee Meeting Agenda: 22 May 2013

Bob Stayton — 2013-05-20T16:13:48

DocBook Technical Committee Meeting Agenda: 22 May 2013
=============================================================

The DocBook Technical Committee will meet on Wednesday, 22 May 2013 at
1:00pm ET for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
 Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 15 May 2013
4. Review of the agenda.
5. Review of open action items

  a.  Norm to publish an XSD for 5.1 when it is finished.

  b.  Norm to follow up on OASIS mirroring the schema directory.

  c.  Larry to try mapping slides to assembly.

  d.  Norm to clarify bridgehead entry in TDG to indicate
      that bridgeheads are not numbered like sections.

  e.  Norm to update The Definitive Guide that the
      behavior of nested links is undefined by the standard.

  f.  Norm to prevent link element nested within link element in DocBook 
5.1.

  g.  Norm to produce a DocBook 5.1 candidate release.

  h.  Norm to follow up on RFE 3491860 license tag

  i.  Norm to add result element to DocBook 5.1 schema.

  j.  Dick to prepare an example of "see under" index entries.

  k.  Dick to fix the DocBook5 conversion stylesheet on SourceForge.

  l.  Bob to review Dick's fixes to the conversion stylesheet.

  m.  Norm to change info from "zero or one" to "zero or more"
      in DocBook 5.1.

  n.  Jirka to prepare a proposal to support RDFa.

6.  OASIS website issues

7.  Publisher's and eLearning subcommittee reports

8.  Transclusion in DocBook

9.  DocBook 5.1 release

10.  Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):

      http://sf.net/support/tracker.php?aid=XXXXXX

    RFEs to revisit for 6.0
      1907003  biblioid content model too broad

    RFEs under discussion
      2820947  Ability to transclude text
      3035565  Allow sections at any level
      3491860   license tag
      3593209   Add see/seealso under
      3599576   'info' wrapper element for processing titlepage elements
      3608790   Microdata or RDFa 1.1 Lite support for schema.org

   No New RFEs


-----

[1] http://lists.oasis-open.org/archives/docbook-tc/201304/msg00003.html


Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

Implied author

Brad Scott — 2013-05-16T13:09:08

Hi again

A print edition has an implied author for some of the bibliography (ie 
under the heading "Books by Brecht). I'd like to have the author in the 
bibliographic reference so I can generate an OpenURL query when it is 
online, but I'd also want to be able to suppress it for any display. Is 
this an occasion when I'd use < at >condition on the author?

<bibliomixed 
xml:id="bibl8"><author><personname><firstname>Berthold</firstname> 
<surname>Brecht</surname></personname></author><title><emphasis 
role="italic">Poems and Songs from the Plays</emphasis></title>, edited 
and mainly translated by <editor><personname><firstname>John</firstname> 
<surname>Willett</surname></personname></editor> 
(<address><city>London</city></address>: 
<publishername>Methuen</publishername>, 
<pubdate>1990</pubdate>)</bibliomixed>

Similarly, where there are multiple items in a bibliography by an 
author, I want to keep the long dash, but inherit (and not display) the 
implied author from the preceding item. So, this would give me something 
like this:

<bibliomixed><bibliomset relation="article"><author 
condition="condition1"><personname 
role="last-first"><surname>Adamson</surname> 
<firstname>Sylvia</firstname></personname></author><phrase 
condition="condition2">————</phrase>, ‘<title>The Literary 
Language</title>’</bibliomset>, in <bibliomset 
role="monograph"><editor><personname><firstname>Roger</firstname> 
<surname>Lass</surname></personname></editor> (ed.), <title><emphasis 
role="italic">The Cambridge History of the English Language: Volume 3, 
1476–1776</emphasis></title> (<address><city>Cambridge</city></address>, 
<pubdate>2000</pubdate>)</bibliomset>, pp. 539–653</bibliomixed>

This feels right, but I'd just be grateful for confirmation, or for a 
pointer to a preferred way of doing this.

Thanks

Brad

Punctuation after in ?

Brad Scott — 2013-05-14T14:05:04

We are using bibliomixed as the standard container for all reference 
items within a collection of humanities and social science texts.

The intent was to (effectively) take the text string as it appears in 
the print source and then apply the markup, leaving all the punctuation 
in situ as it appeared in print. So, starting with this:

Adamson, Sylvia, ‘The Literary Language’, in Suzanne Romaine (ed.), The 
Cambridge History of the English Language: Volume 4, 1776–1997 
(Cambridge, 1999), pp. 589–692

We apply markup:

<bibliomixed><bibliomset relation="article"><author><personname>Adamson, 
Sylvia</personname></author>, ‘<title>The Literary 
Language</title>’</bibliomset>, in <bibliomset 
relation="book"><editor><personname>Suzanne 
Romaine</personname></editor> (ed.), <title><emphasis role="italic">The 
Cambridge History of the English Language: Volume 4, 
1776–1997</emphasis></title> (<address><city>Cambridge</city></address>, 
<pubdate>1999</pubdate>)</bibliomset>, pp. 
<pagenums>589–692</pagenums></bibliomixed>

This is fine, BUT I really want to have <firstname> and <surname> within 
the personname, yet can't because of that comma between Adamson and Sylvia.

Is there a way around this, other than locally changing the content 
model for personname?

Thanks very much

Brad

how to have a structure in the HTML output

2013-05-14T13:33:49

Hi,

I tried to find some information about the structure cleanup in the output files, but I didn't found the right one on the web.
Today I got my output in one flat folder, so the output structure looks like this:

Root
|-- [img]
 |     |-- img1.png
|     |-- img2.png
|     '-- img3.png
|
|-- Sample.html
|-- Sample_frame.html
|-- Sample_main.html
|-- styles.css
'-- popup.js

My goal is to have the output like this:

Root
|-- [etc]
 |     |-- styles.css
|     '-- popup.js
|
|-- [html]
 |     |-- Sample_frame.html
|     '-- Sample_main.html
|
|-- [img]
 |     |-- img1.png
|     |-- img2.png
|     '-- img3.png
|
'-- Sample.html

So maybe, somebody can give me an idea how to customize docbook.
Thanks and
Best regards

Markus Sticker

Academic publishing use of DocBook

Brad Scott — 2013-04-29T13:31:25

Hi

I'm new to the list, if not to DocBook. I've been doing digital 
publishing stuff since the 90s, which often now includes helping 
publishers with data workflows, specs and documentation.

I was wondering if there are any folks out there who have experience of 
using DocBook for academic humanities and social science books. I'm keen 
to compare notes especially on any "standards" you may have adopted for 
some features, especially references and notes, and for more complex 
edition handling (distinguishing between authorial/editorial text, 
marginal notes, etc).

I've also got cases where I have endnotes, which also have surrounding 
editorial text, so one needs to be able to preserve the original context 
of the notes, as well as maintain the pointers to them in the text body.

I'm sure this isn't the first such use of DocBook, so I'm keen not to 
reinvent the wheel. I am, however, keen to develop some good examples.

Thanks

Brad Scott

e: brad.scott< at >brambletye-publishing.co.uk
LinkedIn: http://www.linkedin.com/in/bradscottuk

Customizing Xrefs to Appendices

Morgan Hayward — 2013-04-25T20:46:17

In our DocBook customization, we've removed all section numbering in our appendices, but we still have xref's in some of our manuals that reference those sections.  They end up displaying as "Section E.3, 'Section Title'".  We would like them to display as "Appendix E, 'Section Title'".

I understand how to create an l:template for a specific element, but I'm lost when it comes to defining the context.  Does anyone know how to tell DocBook to use a different xref format for a section in appendix compared to a section in a chapter?

Thanks in advance for your help.

Regards,
Morgan


Morgan Hayward
Technical Writer, Documentation

RuggedCom, A Siemens Company
Office: (905) 482-4599 | Toll Free: 1 (888) 264-0006
300 Applewood Cres. Concord, Ontario L4K 5C7

[cid:image001.png< at >01CE41D3.BA7D6CD0]<http://www.ruggedcom.com/rss.xml> [cid:image002.png< at >01CE41D3.BA7D6CD0] <https://twitter.com/#!/RuggedCom>  [cid:image003.png< at >01CE41D3.BA7D6CD0] <http://www.linkedin.com/company/77282?goback=.fcs_GLHD_RuggedCom_false_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2&trk=ncsrch_hits>

CONFIDENTIALITY NOTICE:
This e-mail and any attachments may contain proprietary information some
of which may be legally privileged. It is for the intended recipient only.
If an addressing or transmission error has misdirected this e-mail, please
notify the author by replying to it. If you are not the intended recipient
you may not use, disclose, distribute, copy, print or rely on this e-mail.

[cid:image005.png< at >01CE41D3.BA7D6CD0] Think Before You Print.

DocBook Technical Committee Meeting Minutes: 17 April 2013

Bob Stayton — 2013-04-19T15:50:41

DocBook Technical Committee Meeting Minutes: 17 April 2013
=============================================================

The DocBook Technical Committee met on Wednesday, 17 April 2013 at
1:00pm ET.

1. Roll call

Present: Dick Hamilton, Nancy Harrison,
Scott Hudson, Jirka Kosek, Larry Rowland, Bob Stayton

Regrets: Norm Walsh

Absent: Loren Cahlander

2. Accepted the minutes [1] of the previous meeting.

3. Next meeting: 15 May 2013

Scott gave regrets.

4. Review of the agenda.

Add item 7a, Moving Publishers Draft to OASIS standard.

5. Review of open action items

  a.  Norm to publish an XSD for 5.1 when it is finished.
      CONTINUE

  b.  Norm to follow up on OASIS mirroring the schema directory.
      CONTINUE

  c.  Larry to try mapping slides to assembly.
      CONTINUE

  d.  Norm to clarify bridgehead entry in TDG to indicate
      that bridgeheads are not numbered like sections.
      CONTINUE

  e.  Norm to update The Definitive Guide that the
      behavior of nested links is undefined by the standard.
      CONTINUE

  f.  Norm to prevent link element nested within link element in DocBook 
5.1.
      CONTINUE

  g.  Norm to produce a DocBook 5.1 candidate release.
      CONTINUE

  h.  Norm to follow up on RFE 3491860 license tag
      CONTINUE

  i.  Norm to add result element to DocBook 5.1 schema.
      CONTINUE

  j.  Dick to prepare an example of "see under" index entries.
      CONTINUE

  k.  Dick to propose the multiple info approach to the submittor
      of RFE 3599576.
      COMPLETED

6.  OASIS website issues

Continued.

7.  Publisher's and eLearning subcommittee reports

Scott reported that they have received no comments on the Draft 1.1
version of the Publisher's schema.  There were four changes to 1.1:

- epigraph now allows poetry
- admonitions are restored
- table accessiblity
- added stage direction markup

Nancy and Dick commented that it looks good.
Scott points out that because it is an extension of
DocBook 5.1, it should not be released as a standard
before 5.1.  He suggested that it be processed through
OASIS at the same time as 5.1.  Bob will discuss
the process with Norm.

8.  Transclusion in DocBook

Continued.

9.  DocBook 5.1 release

Continued.

10. DocBook 4-to-5 conversion stylesheet issues

a.  drops < at >class attribute from <productname/>?
b.  markup removed from <remark>?
c.  all <title>s moved to <info>?

The TC felt that these conversions did not align
with the DocBook 5 schema and should be changed.

ACTION: Dick to fix the conversion stylesheet on SourceForge.
ACTION: Bob to review Dick's changes.

11.  Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):

      http://sf.net/support/tracker.php?aid=XXXXXX

    RFEs to revisit for 6.0
      1907003  biblioid content model too broad

    RFEs under discussion
      2820947  Ability to transclude text
      3035565  Allow sections at any level
      3491860   license tag
      3593209   Add see/seealso under
      3599576   'info' wrapper element for processing titlepage elements

The submittor agreed with the TC proposal to allow multiple
info elements with profiling attributes.  The TC
approved that change.

ACTION: Norm to change info from "zero or one" to "zero or more"
in DocBook 5.1.

   New RFEs

      3608790   Microdata or RDFa 1.1 Lite support for schema.org

The TC would like more specifics on this proposal.

ACTION: Jirak to prepare a proposal to support RFDa.

-----

[1] https://lists.oasis-open.org/archives/docbook-tc/201303/msg00005.html


Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

Attribute Set for

Stefan Knorr — 2013-04-18T13:47:00

Hi all,

I created some custom fo:simple-page-masters for the DocBook/4, v.1.78.1
and while adding support for draft mode to them, I wondered why the
original authors bothered with putting

  <xsl:if test="$draft.watermark.image != ''">
    <xsl:attribute name="background-image">
      <xsl:call-template name="fo-external-image">
        <xsl:with-param name="filename" select="$draft.watermark.image"/>
      </xsl:call-template>
    </xsl:attribute>
    <xsl:attribute name="background-attachment">fixed</xsl:attribute>
    <xsl:attribute name="background-repeat">no-repeat</xsl:attribute>
    <xsl:attribute name="background-position-horizontal">center</xsl:attribute>
    <xsl:attribute name="background-position-vertical">center</xsl:attribute>
  </xsl:if>

everywhere, instead of just adding an attribute set to param.xsl. Any
reasons?

Stefan

TDG 5: DocBook sources?

Michael Valent — 2013-04-18T07:12:03

Hello!

I dimly remember that years ago (4.4?) I could download the original DocBook sources of The Definitive Guide somewhere. This is the ideal showcase (where else can you find _all_ elements, properly used, in one place?).

Now I've tried to find the DocBook sources of TDG5, but had no success so far.

Can anybody help?

Thanks in advance
Michael Valent

DocBook Technical Committee Meeting Agenda: 17 April 2013

Bob Stayton — 2013-04-15T18:04:53

DocBook Technical Committee Meeting Agenda: 17 April 2013
=============================================================

The DocBook Technical Committee will meet on Wednesday, 17 April 2013 at
1:00pm ET for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
 Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 15 May 2013
4. Review of the agenda.
5. Review of open action items

  a.  Norm to publish an XSD for 5.1 when it is finished.

  b.  Norm to follow up on OASIS mirroring the schema directory.

  c.  Larry to try mapping slides to assembly.

  d.  Norm to clarify bridgehead entry in TDG to indicate
      that bridgeheads are not numbered like sections.

  e.  Norm to update The Definitive Guide that the
      behavior of nested links is undefined by the standard.

  f.  Norm to prevent link element nested within link element in DocBook 
5.1.

  g.  Norm to produce a DocBook 5.1 candidate release.

  h.  Norm to follow up on RFE 3491860 license tag

  i.  Norm to add result element to DocBook 5.1 schema.

  j.  Dick to prepare an example of "see under" index entries.

  k.  Dick to propose the multiple info approach to the submittor
      of RFE 3599576.

6.  OASIS website issues

7.  Publisher's and eLearning subcommittee reports

8.  Transclusion in DocBook

9.  DocBook 5.1 release

10. DocBook 4-to-5 conversion stylesheet issues

a.  drops < at >class attribute from <productname/>?
b.  markup removed from <remark>?
c.  all <title>s moved to <info>?


11.  Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):

      http://sf.net/support/tracker.php?aid=XXXXXX

    RFEs to revisit for 6.0
      1907003  biblioid content model too broad

    RFEs under discussion
      2820947  Ability to transclude text
      3035565  Allow sections at any level
      3491860   license tag
      3593209   Add see/seealso under
      3599576   'info' wrapper element for processing titlepage elements

   New RFEs

      3608790   Microdata or RDFa 1.1 Lite support for schema.org

-----

[1] https://lists.oasis-open.org/archives/docbook-tc/201303/msg00005.html


Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

DocBook 5 Assemblies and XML Fragments

Thomas Schraitle — 2013-04-15T07:13:12

Hi,

DocBook 5 contains the new element "assembly" as definied in the TDG:

  http://docbook.org/tdg51/en/html/ch06.html

According to the TDG5, the resource contains a href attribute which is
definied as an anyURI datatype.

Does that mean, an ID fragment is allowed too? Something like:

  <resource href="foo.xml#intro"/>

Would that be supported? How it is supposed to work with other "XML
fragments"? Let's say, a user wants to refer to the first section
inside a file, but this section doesn't contain an xml:id attribute?
Should that be an XPointer expression? Or something else?

It seems, the current level of modularization with assemblies just
covers files and only files. However, sometimes the current situation
dictates a specific structure. As such using a more granular approach
would be very helpful.

This question originated from the docbook-apps mailinglist[1].


Thanks.


-----
[1]
https://lists.oasis-open.org/archives/docbook-apps/201304/msg00135.html

Status attribute

Togan Muftuoglu — 2013-04-14T11:03:52

Hi,

I have a document where I use status for "draft" or "final" phase of the
document.

However status attribute is not one of the common attributes, hence I
cannot use this attribute in variablelist or term elements (just to name
a few, as I am sure there are other cases as well).

Would it be possible to include status attribute in common attributes ?

Thanks

Togan

DB4 to DB5 conversion stylesheet

Alexey Neyman — 2013-04-12T06:16:28

Hi,

I am exploring possibility of conversion of our documents from DB4 to DB5 using the 
db4-upgrade.xsl stylesheet provided at docbook.org. I have a few questions regarding 
the stuff that the stylesheet drops from DB4 elements.

1. Is there a particular reason why that stylesheet drops < at >class attribute from 
<productname/>?

<xsl:template match="productname[< at >class]" priority="200">
  <xsl:call-template name="emit-message">
    <xsl:with-param name="message">
      <xsl:text>Dropping class attribute from productname</xsl:text>
    </xsl:with-param>
  </xsl:call-template>
  <xsl:copy>
    <xsl:call-template name="copy.attributes">
      <xsl:with-param name="suppress" select="'class'"/>
    </xsl:call-template>
    <xsl:apply-templates/>
  </xsl:copy>
</xsl:template>

As far as I can see from TDG5.1, it is perfectly legal in DocBook 5.0: 
http://www.docbook.org/tdg51/en/html/productname.html

At first I thought this removal is because of some element models changing before 
the final release of DocBook 5.0 specification (the stylesheet claims conformance to 
5.0CR5), but I don't see any productname/remark mentions in the specification change 
history.

2. Similar question: why all mark-up is removed from inside of the <remark/> element?

<xsl:template match="remark" priority="200">
  <!-- get rid of any embedded markup -->
  <remark>
    <xsl:copy-of select="< at >*"/>
    <xsl:value-of select="."/>
  </remark>
</xsl:template>

Again, TDG5.1 says most mark-up is allowed in <remark/>: 
http://www.docbook.org/tdg51/en/html/remark.html

3. Is there a reason why all <title>xxx</title> elements are converted to 
<info><title>xxx</title></info>? As far as I can see, both are legal in DB5. Is <title> 
going to be deprecated as a direct child of <sectX/> elements?

We don't use anything but titles on lower level elements (such as sections), so <info> 
just adds some clutter to the documents.


Regards,
Alexey.