DocBook Technical Committee Meeting Agenda: 22 May 2013

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.

Implied author

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> 

Punctuation after <surname>in <bibliomixed>?

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

how to have a structure in the HTML output

Academic publishing use of DocBook

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

DocBook Technical Committee Meeting Minutes: 17 April 2013

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

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

-- 
SUSE LINUX GmbH, Maxfeldstraße 5, D-90409 Nürnberg
Geschäftsführer: Jeff Hawn, Jennifer Guild, Felix Imendörffer
HRB 21284 (AG Nürnberg)

TDG 5: DocBook sources?

DocBook Technical Committee Meeting Agenda: 17 April 2013

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

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

--

-- 
Gruß/Regards,
    Thomas Schraitle