gmane.text.docbook.misc

Re: DocBook Technical Committee Meeting Agenda: 22 May 2013

Hudson, Scott — 2013-05-22T17:22:04

last minute regrets, but something has come up.

--Scott

On May 20, 2013, at 10:13 AM, Bob Stayton <bobs< at >sagehill.net> wrote:

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

Re: Punctuation after in ?

Bob Stayton — 2013-05-14T16:22:55

Hi Brad,
Yes, you can control that.  See this section in my book:

http://www.sagehill.net/docbookxsl/PersonNames.html

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

--------------------------------------------------
From: "Brad Scott" <brad.scott< at >brambletye-publishing.co.uk>
Sent: Tuesday, May 14, 2013 7:05 AM
To: <docbook< at >lists.oasis-open.org>
Subject: [docbook] Punctuation after <surname>in <bibliomixed>?

RDFa Lite support in DocBook

Jirka Kosek — 2013-05-14T15:11:18


Hi,

it seems that Norm actually already played with this, see:

https://github.com/docbook/docbook/blob/master/relaxng/extensions/rdfalite/rdfalite.rnc

RDFa Lite attributes doesn't clash with existing DocBook attributes, so
we can simply add them. The only drawback will be that there will be 5
additional global attributes.

Jirka

AW: how to have a structure in the HTML output

2013-05-14T14:21:56

Sorry ... I found it:
<book>
<?dbhtml dir="UserGuide" ?>


Von: Sticker Markus EXT FRD EPOS
Gesendet: Dienstag, 14. Mai 2013 15:34
An: docbook< at >lists.oasis-open.org
Betreff: [docbook] how to have a structure in the HTML output

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

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

Re: Academic publishing use of DocBook

Richard Hamilton — 2013-04-29T18:12:02

Hi Brad,

Welcome to the list. My experience with DocBook includes doing some books that are used as textbooks, though we haven't done anything quite as complex as what you describe below.

That said, we have used DocBook for books that had marginal notes, endnotes, and some pretty complex bibliographic entries. You will need to do some stylesheet customization to make some of those things look good, but I don't suspect that's a surprise:-).

You may want to check out the work of the DocBook Publisher's Sub-Committee at OASIS. This group addresses issues of interest to publishers and has developed extensions of the DocBook schema specifically for the publishing community. You can get more information about this sub-committee at: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook-publishers

If you've got questions about the DocBook schema, for example how to use mark up in a particular situation, this mailing list is a good place to go. 

If you've got questions about how to make the stylesheets handle a particular situation, the docbook-apps mailing list is the place to go.

I hope that helps.

Best Regards,
Dick Hamilton
-------
XML Press
XML for Technical Communicators
http://xmlpress.net
hamilton< at >xmlpress.net



On Apr 29, 2013, at 6:31 AM, Brad Scott wrote:

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

RE: Customizing Xrefs to Appendices

Morgan Hayward — 2013-04-26T13:17:47

Absolutely brilliant.  That did the trick.  Thank you, Bob!

Regards,
Morgan

-----Original Message-----
From: Bob Stayton [mailto:bobs< at >sagehill.net] 
Sent: April-25-13 7:33 PM
To: Morgan Hayward; docbook< at >lists.oasis-open.org
Subject: Re: [docbook] Customizing Xrefs to Appendices

Hi Morgan,
I don't think you can do this with just the gentext mechanism.  In the l10n files, "l:context" is a named context for gentext, not the XML context of an element in the document hierarchy.  So that file cannot distinguish if a section is in an appendix or not.

When an xref is being resolved, the stylesheet locates the target element, and applies templates in mode="xref-to" to generate the text for it. 
Normally those templates apply templates in mode="object.xref.markup", which triggers the gentext process using the l:template for that element.

You can create a custom template in mode="xref-to" for sections in an appendix and assemble your custom text there.  Something like this:

<!-- the context node here is appendix//section --> <xsl:template match="section[ancestor::appendix]" mode="xref-to">

  <!-- generate the word "Appendix" -->
  <xsl:call-template name="gentext">
    <xsl:with-param name="key">appendix</xsl:with-param>
  </xsl:call-template>

  <xsl:text> </xsl:text>

  <!-- generate the appendix letter -->
  <xsl:apply-templates select="ancestor::appendix" mode="label.markup"/>

  <!-- insert punctuation -->
  <xsl:text>, '</xsl:text>

  <!-- generate the title for the section -->
  <xsl:apply-templates select="." mode="title.markup"/>
  <xsl:text>'</xsl:text>
</xsl:template>

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

From: Morgan Hayward
Sent: Thursday, April 25, 2013 1:46 PM
To: docbook< at >lists.oasis-open.org
Subject: [docbook] Customizing Xrefs to Appendices

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

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.

 Think Before You Print.

Re: Customizing Xrefs to Appendices

Bob Stayton — 2013-04-25T23:33:24

Hi Morgan,
I don't think you can do this with just the gentext mechanism.  In the l10n 
files, "l:context" is a named context for gentext, not the XML context of an 
element in the document hierarchy.  So that file cannot distinguish if a 
section is in an appendix or not.

When an xref is being resolved, the stylesheet locates the target element, 
and applies templates in mode="xref-to" to generate the text for it. 
Normally those templates apply templates in mode="object.xref.markup", which 
triggers the gentext process using the l:template for that element.

You can create a custom template in mode="xref-to" for sections in an 
appendix and assemble your custom text there.  Something like this:

<!-- the context node here is appendix//section -->
<xsl:template match="section[ancestor::appendix]" mode="xref-to">

  <!-- generate the word "Appendix" -->
  <xsl:call-template name="gentext">
    <xsl:with-param name="key">appendix</xsl:with-param>
  </xsl:call-template>

  <xsl:text> </xsl:text>

  <!-- generate the appendix letter -->
  <xsl:apply-templates select="ancestor::appendix" mode="label.markup"/>

  <!-- insert punctuation -->
  <xsl:text>, '</xsl:text>

  <!-- generate the title for the section -->
  <xsl:apply-templates select="." mode="title.markup"/>
  <xsl:text>'</xsl:text>
</xsl:template>


Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net


From: Morgan Hayward
Sent: Thursday, April 25, 2013 1:46 PM
To: docbook< at >lists.oasis-open.org
Subject: [docbook] Customizing Xrefs to Appendices


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



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.

 Think Before You Print.

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.

Re: Attribute Set for

Stefan Knorr — 2013-04-23T08:54:31

Hi Bob.

Thanks for your answer – I'll give this a rest, then.

Stefan.

Re: DB4 to DB5 conversion stylesheet

Alexey Neyman — 2013-04-22T18:05:08

Hi Bob,

Thanks. I've also made some other modifications in db4-upgrade.xsl, attached, so the 
full list of changes is:
- <productname>: do not discard all < at >class specifiers (but see below)
- <remark>: do not discard markup
- <title>, <subtitle>, <titleabbrev>: do not reposition titles inside <info>. Instead, in 
<title> template, verify if parent element XXX contains another title inside 
XXX/XXXinfo - if it does, complain and skip the title outside of <XXXinfo>
- <productname>, <orderedlist>, <literallayout>: Suppress attributes with default 
values added by DTD (<literallayout class="normal">, etc.)
- Add an ability to set a custom < at >version via stylesheet parameter
- Slightly change the criteria used for determining where < at >version is set - set it on the 
topmost element without a namespace, or topmost element with DocBook 
namespace (we have a few documents that include DocBook inside some other 
elements using non-DocBook namespaces)

Also attached is a Python script I wrote for cloaking the entities and other content. 
Inspired by the Perl script referred to from the DB4 to DB5 upgrade HOWTO, but 
different:
- Perl version is too greedy when looking for internal subset (in fact, it just assumes 
that internal subset is always present). It interprets anything from the "DOCTYPE" 
string to the next "]>" to be internal subset. In absence of internal subset, though, "]>" 
would be the next CDATA closing.
- My version also preserves the content outside of the root element (which is lost with 
Perl version, as XSLT step drops it)
- My version also duplicates the <?xml ...?> directive and the DTD when cloaking, which 
may be needed by XSLT step (DTD may define namespace prefixes; <?xml ...?> may 
define document encoding and XML version.

Feel free to use/publish this script.

Regards,
Alexey.

On Wednesday, April 17, 2013 02:06:01 PM Bob Stayton wrote:


Hi Alexey,
Thanks for pointing out these problems.  We discussed them in the DocBook Technical 
Committee meeting today, and concluded that you are correct.  The conversion 
stylesheet will get fixed.  If you find any other issues, please let us know.
 
Bob StaytonSagehill Enterprises

bobs< at >sagehill.net[1]


*From:* Alexey Neyman[2] 
*Sent:* Thursday, April 11, 2013 11:16 PM
*To:* docbook< at >lists.oasis-open.org[3] 
*Subject:* [docbook] DB4 to DB5 conversion stylesheet


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.



--------
[1] mailto:bobs< at >sagehill.net
[2] mailto:stilor< at >att.net
[3] mailto:docbook< at >lists.oasis-open.org

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe< at >lists.oasis-open.org
For additional commands, e-mail: docbook-help< at >lists.oasis-open.org

Re: Attribute Set for

Bob Stayton — 2013-04-22T17:38:17

Hi Stefan,
That would not work for everyone, because not everyone uses a watermark 
image for their draft mode.  I had a client whose draft page masters had 
"DRAFT" appearing rotated in the side margins and no watermark image.

The draft page masters may not be very different in the stock stylesheets, 
but they represent an opportunity for customizing with more extensive 
changes.

I certainly agree that it is burdensome to manage a complete set of draft 
and nondraft page masters, given the number of page masters and their 
properties, but I haven't figured out a way to simplify without losing 
individual customizability.

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

--------------------------------------------------
From: "Stefan Knorr" <sknorr< at >suse.de>
Sent: Sunday, April 21, 2013 9:50 AM
To: "Bob Stayton" <bobs< at >sagehill.net>
Cc: "DocBook List" <docbook< at >lists.oasis-open.org>
Subject: Re: [docbook] Attribute Set for

Re: Attribute Set for

Stefan Knorr — 2013-04-21T16:50:28

Hi Bob,

you're right of course. Sorry for the useless proposal.

Anyway, is there all that much of a difference between a normal
simple-page-master and a draft simple-page-master whose watermark has
been turned off? (My rather superficial diff seems to indicate that the
xsl:if in question is usually the only difference.)
So, how about only using the draft page-masters when the watermark image
is enabled, and using the normal masters when it isn't?
Or is that likely to be incompatible with overly many customisations?


Stefan.

Re: [docbook-tc] DocBook Technical Committee Meeting Minutes: 17 April 2013

Loren Cahlander — 2013-04-19T19:33:48

I am sorry that I was not on the call.  I was driving from Minneapolis, MN to Durham, NC for a new contract.

I will be attending the next call.

Regard,
Loren

Sent from my iPhone

On Apr 19, 2013, at 11:50 AM, "Bob Stayton" <bobs< at >sagehill.net> wrote:

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 

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

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

RE: TDG 5: DocBook sources?

Michael Valent — 2013-04-19T08:44:54

Thanks a lot!

-----Original Message-----
From: Jirka Kosek [mailto:jirka< at >kosek.cz] 


http://docbook.svn.sourceforge.net/viewvc/docbook/trunk/defguide5/

Re: Attribute Set for

Bob Stayton — 2013-04-18T16:19:13

Hi,
Yes, there is a reason: you cannot apply an attribute-set with xsl:if.  Many 
things in XSL would be simpler if you could.   If you need a conditional 
attribute set, you must either conditionalize the value of every attribute 
in the attribute-set (and you still get all the attributes), or you must 
create an awkward xsl:choose that generates the output element either with 
or without the attribute-set applied, and repeat the rest of the content in 
both.  The template with match="section" in fo/sections.xsl has such a 
construction for applying the different section level properties.

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

--------------------------------------------------
From: "Stefan Knorr" <sknorr< at >suse.de>
Sent: Thursday, April 18, 2013 6:47 AM
To: "DocBook List" <docbook< at >lists.oasis-open.org>
Subject: [docbook] Attribute Set for