Nabble - docbook General

Re: upgrade 4.5 => 5.0 failed (on rather basic example)

2009-12-21T09:13:36Z

wolfgang haefelinger wrote:

> I'm getting an error on a rather simple document. Here it comes ..
>
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <!DOCTYPE article
> PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
> <article lang=3D"">
> <sect1>
> <title>Hello, ..</title>
> <para>world</para>
> </sect1>
> </article>
>
> This document is valid according to a) Emacs/nxml and b) MSV.

However this document is not proper DocBook V4.5 article as it misses
<title> element as direct child of <article> or <articleinfo>.
Validation hasn't spot this problem because expressing such constraint
in DTD/W3C XML Schema is impossible.

--
------------------------------------------------------------------
Jirka Kosek e-mail: jirka@... http://xmlguru.cz
------------------------------------------------------------------
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------

signature.asc (267 bytes) Download Attachment

Re: So, what's the current version of DocBook?

2009-12-21T09:09:03Z

wolfgang haefelinger wrote:

> Then I rephrase "current" as:
>
> 1. What is the latest version of DocBook?

5.0

> 2. What is the status of version 5.0?

It's OASIS Standard

> 3. Which version is recommended to be used?

The honest answer would be "it depends", but if you want straight answer
then it is recommended to use version 5.0.

Reasons for using V5.0 over V4.x are summarized there:

http://www.docbook.org/docs/howto/#introduction-why-to-switch

There is one reason to stick with V4.x -- if you already invested money
into V4.X tool chain which can't be easily upgraded to support V5.0.

> That's my point after all. If docbook.org is the "primary resource"
> about Docbook, then I expect to get well informed by this source. But
> perhaps I do not understand who actually maintains this site.

You are of course right, docbook.org could be definitively improved. But
whole DocBook effort is led by volunteers so you should understand if
not everything in auxiliary resources is perfect.

> With "official" I mean the primary resource, especially for regular
> users. However, my focus was not on "official" but rather what
> docbook.org is all about. The page itself states that it is the home
> page for a book which confuses me. Shouldn't that be changed to make
> it the primary resource for Docbook?

Probably yes.

>> In general this is good idea, but such information would anyway one time
>> became out-of-date.
>
> So does any information published :-)
>
> Seriously, don't understand your point here ..

It doesn't make sense to label some resources as fresh or updated if
there is no guarantee that such metainformation itself would be
perpetually keep up to date.

--
------------------------------------------------------------------
Jirka Kosek e-mail: jirka@... http://xmlguru.cz
------------------------------------------------------------------
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------

signature.asc (267 bytes) Download Attachment

Re: upgrade 4.5 => 5.0 failed (on rather basic example)

2009-12-21T09:07:23Z

Hello Wolfgang,
Your short article example happened to hit a long-standing problem with
DocBook 4 that DocBook 5 fixes.

Originally the article element in DocBook required a title element. As
DocBook evolved, the articleinfo container was added to hold metadata, then
it was decided that title could also reside in articleinfo. For backwards
compatibility, title was also left as a child of article, but made optional
so that one could put their title in articleinfo instead. The committee
wanted to enforce putting the title in one place or the other, but that was
so difficult to do with DTD syntax that it didn't happen. So in Docbook 4,
one could have zero, one, or two titles and the document would be valid.

DocBook 5 is defined using RelaxNG syntax. The RelaxNG syntax made it easier
to support the original intention to require a single title, in either
location. So DocBook 5 fixes this long standing problem with DocBook 4, and
is one of the few instances where DocBook 5 is not backwards compatible with
DocBook 4. A more sophisticated conversion script would flag that with a
warning that it be fixed in the output.

Bob Stayton
Sagehill Enterprises
bobs@...

----- Original Message -----
From: "wolfgang haefelinger" <whaefelinger@...>
To: <docbook@...>
Sent: Monday, December 21, 2009 4:58 AM
Subject: [docbook] upgrade 4.5 => 5.0 failed (on rather basic example)

Hello,

I'm upgrading a 4.5 Docbook document to 5.0 using db-upgrade.xsl and
I'm getting an error on a rather simple document. Here it comes ..

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<!DOCTYPE article
PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<article lang=3D"">
<sect1>
<title>Hello, ..</title>
<para>world</para>
</sect1>
</article>

This document is valid according to a) Emacs/nxml and b) MSV.

Then I upgraded this document with db4-upgrade.xsl (Release: $Id:
db4-upgrade.xsl 7660 2008-02-06 13:48:36Z nwalsh $) and I get:



<article xmlns=3D"http://docbook.org/ns/docbook" version=3D"5.0"
xml:lang="">
<section><info><title>Hello, ..</title></info>

<para>world</para>
</section>
</article>

which is !!! NOT !!! valid ( inserting a article/title element makes it
valid).

Is this bug known?
Is there a bug tracker?
Patches accepted?

Regards.

Wolfgang H=E4felinger
häfelinger IT - Applied Software Architecture
http://www.haefelinger.it

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: upgrade 4.5 => 5.0 failed (on rather basic example)

2009-12-21T07:32:11Z

Monday 21 December 2009

>
> I'm upgrading a 4.5 Docbook document to 5.0 using db-upgrade.xsl and
> I'm getting an error on a rather simple document. Here it comes ..
>
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <!DOCTYPE article
> PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
> <article lang=3D"">
> <sect1>
> <title>Hello, ..</title>
> <para>world</para>
> </sect1>
> </article>
>
> This document is valid according to a) Emacs/nxml and b) MSV.

I validated your document in oXygen and I can confirm it is valid. According
to the content model of article[1], a title is _optional_.

> Then I upgraded this document with db4-upgrade.xsl (Release: $Id:
> db4-upgrade.xsl 7660 2008-02-06 13:48:36Z nwalsh $) and I get:
>
> 
>
> <article xmlns=3D"http://docbook.org/ns/docbook" version=3D"5.0"
> xml:lang=""> <section><info><title>Hello, ..</title></info>
>
> <para>world</para>
> </section>
> </article>
>
> which is !!! NOT !!! valid ( inserting a article/title element makes it
> valid).

When I validate your file in oXygen, I get:

element "section" not allowed yet; expected element "info", "subtitle",
"title" or "titleabbrev"

So the best is to insert the missing title element right after article
_before_ applying the transformation.

According to the RELAX NG schema, an article[2] needs a title. The stylesheet
just doesn't know this case which creates an invalid DocBook 5 document. I
would consider it a bug.

>Is this bug known?

Look at [3], maybe there is already one.

>Is there a bug tracker?

See [3] on Sourceforge.

>Patches accepted?

Probably yes. :)

Tom

----------
[1] http://www.docbook.org/tdg/en/html/article.html
[2] http://www.docbook.org/tdg5/en/html/article.html
[3] http://sourceforge.net/tracker/?group_id=21935&atid=373747

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: So, what's the current version of DocBook?

2009-12-21T06:36:00Z

I brought up a lot of these same issues in this thread: http://markmail.org/thread/4t3c35hm7o2ugv6s
I understand Norman Walsh has an action item to think about how best to clean up the websites.

On Mon, Dec 21, 2009 at 8:20 AM, wolfgang haefelinger <whaefelinger@...> wrote:

Hello Jirka,

> It depends on what you mean but current? The latest version in 5.0, but
> it doesn't mean that can't successfully use 4.5 or even older versions.

Then I rephrase "current" as:

1. What is the latest version of DocBook?
2. What is the status of version 5.0?
3. Which version is recommended to be used?

>> Therefore I conclude that the official version of DocBook is version
>> 4.5 and 5.0 is still about to be released ...
>
> You shouldn't apply pure logic to information spread over web on several
> and sometimes un-updated web pages.

That's my point after all. If docbook.org is the "primary resource"
about Docbook, then I expect to get well informed by this source. But
perhaps I do not understand who actually maintains this site.

>> Wouldn't it be wise to make www.docbook.org the official DocBook page?
>
> It depends on what you mean by official? docbook.org is the primary
> resource about DocBook, but institutionally development is done inside
> OASIS -- but as OASIS doesn't provide the most flexible environment for
> managing web content.

With "official" I mean the primary resource, especially for regular
users. However, my focus was not on "official" but rather what
docbook.org is all about. The page itself states that it is the home
page for a book which confuses me. Shouldn't that be changed to make
it the primary resource for Docbook?

> If you want to get overview of versions, go to
>
> http://www.docbook.org/specs/
>
> there is missing recent important change that DocBook 5.0 was approved
> as an OASIS Standard.

Needs then to be updated.

>> Wouldn't it be wise further to state there the role of
>> other"official" sites like FAQ, TC etc, the current version and the
>> role of
>> older versions (supported, update) ??
>
> In general this is good idea, but such information would anyway one time
> became out-of-date.

So does any information published :-)

Seriously, don't understand your point here ..

--
Wolfgang Häfelinger

häfelinger IT - Applied Software Architecture
http://www.haefelinger.it

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: So, what's the current version of DocBook?

2009-12-21T05:20:53Z

Hello Jirka,

> It depends on what you mean but current? The latest version in 5.0, but
> it doesn't mean that can't successfully use 4.5 or even older versions.

Then I rephrase "current" as:

1. What is the latest version of DocBook?
2. What is the status of version 5.0?
3. Which version is recommended to be used?

>> Therefore I conclude that the official version of DocBook is version
>> 4.5 and 5.0 is still about to be released ...
>
> You shouldn't apply pure logic to information spread over web on several
> and sometimes un-updated web pages.

That's my point after all. If docbook.org is the "primary resource"
about Docbook, then I expect to get well informed by this source. But
perhaps I do not understand who actually maintains this site.

>> Wouldn't it be wise to make www.docbook.org the official DocBook page?
>
> It depends on what you mean by official? docbook.org is the primary
> resource about DocBook, but institutionally development is done inside
> OASIS -- but as OASIS doesn't provide the most flexible environment for
> managing web content.

With "official" I mean the primary resource, especially for regular
users. However, my focus was not on "official" but rather what
docbook.org is all about. The page itself states that it is the home
page for a book which confuses me. Shouldn't that be changed to make
it the primary resource for Docbook?

> If you want to get overview of versions, go to
>
> http://www.docbook.org/specs/
>
> there is missing recent important change that DocBook 5.0 was approved
> as an OASIS Standard.

Needs then to be updated.

>> Wouldn't it be wise further to state there the role of
>> other"official" sites like FAQ, TC etc, the current version and the
>> role of
>> older versions (supported, update) ??
>
> In general this is good idea, but such information would anyway one time
> became out-of-date.

So does any information published :-)

Seriously, don't understand your point here ..

--
Wolfgang Häfelinger
häfelinger IT - Applied Software Architecture
http://www.haefelinger.it

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

upgrade 4.5 => 5.0 failed (on rather basic example)

2009-12-21T04:58:11Z

Hello,

I'm upgrading a 4.5 Docbook document to 5.0 using db-upgrade.xsl and
I'm getting an error on a rather simple document. Here it comes ..

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<!DOCTYPE article
PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<article lang=3D"">
<sect1>
<title>Hello, ..</title>
<para>world</para>
</sect1>
</article>

This document is valid according to a) Emacs/nxml and b) MSV.

Then I upgraded this document with db4-upgrade.xsl (Release: $Id:
db4-upgrade.xsl 7660 2008-02-06 13:48:36Z nwalsh $) and I get:



<article xmlns=3D"http://docbook.org/ns/docbook" version=3D"5.0" xml:lang="">
<section><info><title>Hello, ..</title></info>

<para>world</para>
</section>
</article>

which is !!! NOT !!! valid ( inserting a article/title element makes it valid).

Is this bug known?
Is there a bug tracker?
Patches accepted?

Regards.

Wolfgang H=E4felinger
häfelinger IT - Applied Software Architecture
http://www.haefelinger.it

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: So, what's the current version of DocBook?

2009-12-21T04:32:15Z

wolfgang haefelinger wrote:

> What's the current version of DocBook?
>
> Wikipedia tells me it's 5.0, however ..

It depends on what you mean but current? The latest version in 5.0, but
it doesn't mean that can't successfully use 4.5 or even older versions.

> Therefore I conclude that the official version of DocBook is version
> 4.5 and 5.0 is still about to be released ...

You shouldn't apply pure logic to information spread over web on several
and sometimes un-updated web pages.

> Wouldn't it be wise to make www.docbook.org the official DocBook page?

It depends on what you mean by official? docbook.org is the primary
resource about DocBook, but institutionally development is done inside
OASIS -- but as OASIS doesn't provide the most flexible environment for
managing web content.

If you want to get overview of versions, go to

http://www.docbook.org/specs/

there is missing recent important change that DocBook 5.0 was approved
as an OASIS Standard.

> Wouldn't it be wise further to state there the role of
> other"official" sites like FAQ, TC etc, the current version and the
> role of
> older versions (supported, update) ??

In general this is good idea, but such information would anyway one time
became out-of-date.

Jirka

--
------------------------------------------------------------------
Jirka Kosek e-mail: jirka@... http://xmlguru.cz
------------------------------------------------------------------
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------

signature.asc (267 bytes) Download Attachment

So, what's the current version of DocBook?

2009-12-21T03:33:38Z

Hello,

I'm rather new to DocBool and I have a rather simple question:

What's the current version of DocBook?

Wikipedia tells me it's 5.0, however ..

1.) www.docbook.org states, that "DocBook V5.0 is the official
Committee Specification release of DocBook V5.0". Hmm, I guess that's
what everyone is expecting, right? Perhaps there is one V5.0 too much here ..

Besides, www.docbook.org states that it is official home page for a
book (i.e. DocBook: The Definitive
Guide). So, what's the official DocBook site then?

2.) The (official?) docbook FAQ
(http://www.dpawson.co.uk/docbook/reference.html) redirects me to
http://www.oasis-open.org/docbook if I want to get up-to-date
information about DocBook. There I read "Test releases of DocBook V5.0
is also available now."

Therefore I conclude that the official version of DocBook is version
4.5 and 5.0 is still about to be released ...

Wouldn't it be wise to make www.docbook.org the official DocBook page?

Wouldn't it be wise further to state there the role of
other"official" sites like FAQ, TC etc, the current version and the
role of
older versions (supported, update) ??

Regards,

Wolfgang H=E4felinger
häfelinger IT - Applied Software Architecture
http://www.haefelinger.it

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Is DocBook-xsl compatible with Ruby 1.9?

2009-12-19T09:08:37Z

Hi, all:

I tried to install docbook-xsl from Ubuntu 9.10 repository.
But, it automatically pick up Ruby 1.8 to install.
I know that to install both Ruby 1.8 and 1.9 is of no problem.
However, I'm just wondering

1) Is current docbook-xsl compatible with ruby 1.9 ?
2) If so, does that mean it's Ubuntu's problem that docbook-xsl ask for Ruby 1.8 but not Ruby 1.9?

I just want to keep every simple and clean.

Just don't want to install Ruby 1.8 on my computer.

Best Regards
JIA

--
Welcome to Vision Open
http://www.visionopen.com

Welcome to Vision Open
http://www.visionopen.com

Scilab 5.2 compilation - Could not find the Docbook root directory

2009-12-18T23:59:44Z

Hi, all:

After carefully set up Scilab 5.2 configuration, I still met the following configuration error at the very first stage.

configure: error: Could not find the Docbook root directory. If you have installed it on your system and we haven't been able to find it. Please report a bug

I'm using Ubuntu 9.10 + GCC 4.4.1

I grabbed Docbook 4.5-4 directly from Ubuntu 9.10 repository.

I'm now reporting this bug to both Scilab mailing list and DocBook mailing list.
Seriously hope somebody may give some hints on how to solve this configuration error?

Best Regards
JIA

--
Welcome to Vision Open
http://www.visionopen.com

Welcome to Vision Open
http://www.visionopen.com

Re: [docbook-apps] DocBook and Google Summer of Code ?

2009-12-18T08:21:16Z

On 12/16/2009 08:28 AM, Stefan Seefeld wrote:
>
> I have been wondering whether there was any interest in the DocBook
> community to apply to become a GSoC mentoring organization, too. I can
> see many projects that are doable in such a context (I have a couple
> of specific ideas that I would very much like to see realized, and I
> think GSoC would be an ideal framework for this).

OK, let me add some ideas I have for such potential DocBook tasks that
are IMO suitable as GSoC projects:

The Boost project has been working on a DB extension to help document
C++ APIs. DB itself has some vocabulary to describe programming language
artifacts, but they are by far not sufficient to cover modern C++.
(More information about the existing "BoostBook" extension can be found
at http://www.boost.org/doc/libs/1_41_0/doc/html/boostbook.html)
While some of the vocabulary is boost-specific, most is generic, and
would IMO be very useful to be maintained as an 'official' DB 5
extension, so any C++ author can use it. Thus, I propose that the
relevant bits be converted to DB 5, and integrated (as an extension)
into the docbook project itself.

Another project, somewhat similar in nature, is the addition of a
vocabulary specifically targetted at the software development process,
i.e. use-cases, requirements, specifications, and design documents. For
inspiration, see http://readyset.tigris.org/.

(Both of these projects include the definition of the vocabulary (Relax
NG ?), as well as some XSL stylesheets to process them into some media
(say, HTML and FO).

How does this sound ?

Stefan

--

...ich hab' noch einen Koffer in Berlin...

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

RE: How to markup a template function in c++

2009-12-17T14:04:15Z

Stefan Seefeld [mailto:seefeld@...] wrote:

>
The current DB vocabulary isn't quite enough to mark up such things
fully. After some experimentation, I have come to the conclusion that a
plain <synopsis> is better than any of the alternatives. (The vocabulary
itself is incomplete, and the stylesheet support is buggy, so for some
constructs / languages the output isn't what you would expect.)
<

I came to the same conclusion. We've gone simple in this instance, and don't bother with all the <synopsis> variations.

*************************
Rob Cavicchio
Principal Technical Writer
EMC Captiva
EMC Corporation
10145 Pacific Heights Boulevard, 6th Floor
San Diego, CA 92121-4234

P: (858) 320-1208
F: (858) 320-1010
E: Cavicchio_Rob@...

The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC.

RE: DocBook: The Definitive Guide, Second Edition

2009-12-17T13:46:20Z

Mauritz,

Thanks very much for taking the time to review the rough cuts version of
the book. I will take a look at all of your comments, discuss them with
Norm, and do my best to address them.

Best Regards,
Dick

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

> -----Original Message-----
> From: Mauritz Jeanson [mailto:mj@...]
> Sent: Thursday, December 17, 2009 2:41 PM
> To: 'Dick Hamilton'
> Cc: docbook@...
> Subject: RE: [docbook] DocBook: The Definitive Guide, Second Edition
>
>
> | -----Original Message-----
> | From: Dick Hamilton
> |
> | 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.
>
>
> Hi Dick,
>
> I hope you don't mind me submitting some more comments. The
> comments apply
> to the Rough Cuts version of TDG available on Safari Books
> Online (dated 19
> Nov 2009).
>
> * I think item 3) above definitely needs to be addressed. In
> the reference
> part of the book, markup examples are still missing for many elements.
> Having at least one representative example for every element
> would be very
> valuable.
>
> * The element reference at http://docbook.org/tdg5/en/html/
> has a "Parents"
> section for each element with a list of all possible parents. This
> information is not available in the Rough Cuts version.
>
> * The listings of Common Attributes and Common Linking Attributes are
> missing (page 73).
>
> * The glossary contains several references to SGML and SGML
> practices that
> are not relevant to DocBook 5. For example, see these entries: entity,
> exclusion, inclusion, parameter entity, processing instruction.
>
> * The discussion about "pernicious mixed content" (page 167)
> is about SGML
> parsers. AFAIK, this problem does not apply to XML and DocBook 5.
>
> * Many bibliography entries under "Books and Printed
> Resources" in appendix
> B (page 498) are garbled in some way.
>
> * Appendix C discusses DTDs and SGML issues, but it says
> nothing about RELAX
> NG schemas.
>
> Mauritz
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-unsubscribe@...
> For additional commands, e-mail: docbook-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

RE: DocBook: The Definitive Guide, Second Edition

2009-12-17T13:41:11Z

| -----Original Message-----
| From: Dick Hamilton
|
| 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.

Hi Dick,

I hope you don't mind me submitting some more comments. The comments apply
to the Rough Cuts version of TDG available on Safari Books Online (dated 19
Nov 2009).

* I think item 3) above definitely needs to be addressed. In the reference
part of the book, markup examples are still missing for many elements.
Having at least one representative example for every element would be very
valuable.

* The element reference at http://docbook.org/tdg5/en/html/ has a "Parents"
section for each element with a list of all possible parents. This
information is not available in the Rough Cuts version.

* The listings of Common Attributes and Common Linking Attributes are
missing (page 73).

* The glossary contains several references to SGML and SGML practices that
are not relevant to DocBook 5. For example, see these entries: entity,
exclusion, inclusion, parameter entity, processing instruction.

* The discussion about "pernicious mixed content" (page 167) is about SGML
parsers. AFAIK, this problem does not apply to XML and DocBook 5.

* Many bibliography entries under "Books and Printed Resources" in appendix
B (page 498) are garbled in some way.

* Appendix C discusses DTDs and SGML issues, but it says nothing about RELAX
NG schemas.

Mauritz

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

RE: Transclusion

2009-12-16T12:00:47Z

We implemented our own transclusion operators before XInclude was
stable enough to use. We use a number of DocBook derived grammars
for specific types of documents (like help systems and manpages)
that have extensions for the specific environments they deliver
content into. We found the addition of a grammar attribute to
be quite helpful to handle the specialized filtering and conversion
necessary to pull content from help systems and man pages into our
pretty much pure DocBook markup for books in PDF and HTML. The
preprocessor that handles the transclusion invokes transform
elements based on the grammar attribute.

The transclusion operators also handle the simplest (and we found
the most common) ID collision problem by allowing the ID on the
inclusion element to replace the ID on the included content. Most
of what we were including was small things like admonitions or
steps, which did not have internal IDs to deal with. Inclusion
on the section level did not tend to be repeated in the same
document, so this handled most of the problems. We did have to
come up with an ID naming scheme so that not everyone used the
same ID for the introduction or preface.

Regards,
Larry Rowland

From: "David Cramer" <dcramer@...>
To: "Norman Walsh" <ndw@...>,<docbook@...>
Date: Fri, 11 Dec 2009 16:17:24 -0600

--------------------------------------------------------------------------------

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@...]
> Sent: Friday, December 11, 2009 3:17 PM
> To: docbook@...
> 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@...> | Wink at small faults;
> for thou has
> http://www.oasis-open.org/docbook/ | great ones.--Thomas
> Fuller (II) Chair, DocBook Technical Committee |
>

=======================================================================
[ Larry Rowland | If you want to build a ship, don't drum ]
[ ESS/ATG | up the men to gather the wood, divide ]
[ Hewlett-Packard | the work, and give orders. Instead, ]
[ 3404 East Harmony Road | teach them to yearn for the vast and ]
[ Fort Collins, CO 80528 | endless sea. - Antoine de Saint Exupery ]
[ Phone: 970/898-2280 +-----------------------------------------]
[ E-Mail:larry.rowland@... ]
=======================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: DocBook and Google Summer of Code ?

2009-12-16T05:41:26Z

On Wednesday 16 Dec 2009 15:28:56 Stefan Seefeld wrote:

> All,
>
> Google is sponsoring each year many organizations to allow students to
> contribute to free software projects over the summer. This is known as
> the "Google Summer of Code".
> Such organizations would apply to become a "mentoring organization",
> sometime in early March. Being a mentoring organization means to provide
> project ideas, as well as mentors who would help the student(s) over the
> summer keep in touch with the community, as well as make progress on the
> project.
>
> I have been a mentor for different projects and mentoring organizations
> in the past (notably, the Python Software Foundation and Boost.org), and
> I know firsthand what a great way to help advance a project this is, as
> well as allow students to get involved with Free Software.
>
> I have been wondering whether there was any interest in the DocBook
> community to apply to become a GSoC mentoring organization, too. I can
> see many projects that are doable in such a context (I have a couple of
> specific ideas that I would very much like to see realized, and I think
> GSoC would be an ideal framework for this).
>
> Before diving into such details, I'd just like to ask for feedback about
> the general idea. What do you think ?
>

Sounds good to me, but until now I've only been a DocBook/XML end-user - not
an active developer (though I've reported and triaged a few bugs). I've also
been active to some extent in the Perl GSoC.

Regards,

Shlomi Fish

> (For details about the program, see
> http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs)
>
> Thanks,
> Stefan
>

--
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
My Aphorisms - http://www.shlomifish.org/humour.html

Bzr is slower than Subversion in combination with Sourceforge.
( By: http://dazjorz.com/ )

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

DocBook and Google Summer of Code ?

2009-12-16T05:28:56Z

All,

Google is sponsoring each year many organizations to allow students to
contribute to free software projects over the summer. This is known as
the "Google Summer of Code".
Such organizations would apply to become a "mentoring organization",
sometime in early March. Being a mentoring organization means to provide
project ideas, as well as mentors who would help the student(s) over the
summer keep in touch with the community, as well as make progress on the
project.

I have been a mentor for different projects and mentoring organizations
in the past (notably, the Python Software Foundation and Boost.org), and
I know firsthand what a great way to help advance a project this is, as
well as allow students to get involved with Free Software.

I have been wondering whether there was any interest in the DocBook
community to apply to become a GSoC mentoring organization, too. I can
see many projects that are doable in such a context (I have a couple of
specific ideas that I would very much like to see realized, and I think
GSoC would be an ideal framework for this).

Before diving into such details, I'd just like to ask for feedback about
the general idea. What do you think ?

(For details about the program, see
http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs)

Thanks,
Stefan

--

...ich hab' noch einen Koffer in Berlin...

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: How to markup a template function in c++

2009-12-14T15:40:23Z

On 12/14/2009 05:18 PM, Eric Böse-Wolf wrote:
> Hello!
>
> The subjects says it all.
>
> How do I markup a template function prototype like
>
> template<typename ArgumentType> void g( ArgumentType argument )
>

The current DB vocabulary isn't quite enough to mark up such things
fully. After some experimentation, I have come to the conclusion that a
plain <synopsis> is better than any of the alternatives. (The vocabulary
itself is incomplete, and the stylesheet support is buggy, so for some
constructs / languages the output isn't what you would expect.)

You may want to look into a DB extension that provides support for
extensive C++ markup, which is part of the Boost project:
http://www.boost.org/doc/libs/1_41_0/doc/html/boostbook.html

I have some ideas about how to merge that back into DB (5), and will
write about that shortly (if I can find the time).

Regards,
Stefan

--

...ich hab' noch einen Koffer in Berlin...

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

DocBook Technical Committee Meeting Agenda: 16 December 2009

2009-12-14T14:32:38Z

DocBook Technical Committee Meeting Agenda: 16 December 2009
=============================================================

The DocBook Technical Committee will meet on Wednesday, 16 December 2009 at
01:00p EDT (10:00a PDT, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
022:30p India+) 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: 20 January 2010
4. Review of the agenda.
5. Review of open action items

a. Gershon to develop a reltable example.

b. Larry to publish assembly schema with last month's changes.

c. Norm to prepare proposal for full and simplified assembly versions.

d. Bob to organize a meeting to discuss linking in modular DocBook.

e. Norm to develop a proposal for maintaining the DocBook websites.

f. Norm to develop schema changes for inlines for discussion at
next meeting.

g. Norm to develop a list of use cases and requirements for transclusion.

h. Bob to add agenda item for transclusion to next meeting.

i. Norm to better document indexterm placement.

6. Status of new edition of DocBook: The Definitive Guide

7. Publishing Subcommittee report.

8. eLearning Subcommittee report.

9. Linking in modular DocBook.

10. Transclusion in DocBook.

11. DocBook assembly schema.

12. Review of Requests for Enhancement

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

http://sourceforge.net/tracker/index.php?func=detail&;
group_id=21935&atid=384107&aid=XXXX

RFEs to revisit for 6.0
1907003 biblioid content model too broad

RFEs to be considered
1679665 Add better support for modular documentation
2770858 Add limited emphasis to ubiquitous inlines
2791288 add quote to corpauthor and gui elements
2820190 add a topic element
2820947 Ability to transclude text
2821653 indexterms in footnotes
2900425 Remove common linking attributes from indexterm
2900458 Make xml:id required on start-of-range indexterms
2907124 Allow personal name components directly in bibliomset
2907125 Remark should allow all inlines
2907126 msgaud/level/orig in simplemsgentry are spelled wrong
2907129 orgname in address
2907131 SImpleSect in Colophon?

-----

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

Bob Stayton
Sagehill Enterprises
bobs@...

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

How to markup a template function in c++

2009-12-14T14:18:47Z

Hello!

The subjects says it all.

How do I markup a template function prototype like

template<typename ArgumentType> void g( ArgumentType argument )

A solution I tried was

<funcsynopsis>
<funcprototype>
<funcdef>template<typename <replaceable>ArgumentType</replaceable>>
<type>void</type> <function>g</function></funcdef>
<paramdef>
<parameter><replaceable>ArgumentType</replaceable> <replaceable>argument</replaceable></parameter>
</paramdef>
</funcprototype>
</funcsynopsis>

but does that really describe a templated function as docbook was
intended?

And the generated html output by the norman walsh xsl gets ugly if the
line of <funcdef> doesn't fit the browser window .... but that might be
acceptable for a semantic searchable documentation.

Yours sincerely,

Eric Böse-Wolf

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

test

2009-12-14T14:02:10Z

test

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

RE: Transclusion

2009-12-11T14:17:24Z

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

David

id=21935&atid=384107

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Transclusion

2009-12-11T13:16:49Z

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@...> | Wink at small faults; for thou has
http://www.oasis-open.org/docbook/ | great ones.--Thomas Fuller (II)
Chair, DocBook Technical Committee |

attachment0 (191 bytes) Download Attachment

Status of Website DTD

2009-12-11T12:39:58Z

Just wondering what the status of the Docbook Website DTD is. It hasn't been updated for some time (I think since 2.6.0 in 2005). Are there any plans to do so?

Cheers

John

RE: DocBook: The Definitive Guide, Second Edition

2009-12-11T09:56:34Z

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@...]
> Sent: Thursday, December 10, 2009 2:29 PM
> To: 'Dick Hamilton'; docbook@...;
> docbook-tc@...
> Subject: RE: [docbook] 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
>
> ---
> [1] http://oreilly.com/catalog/9781449380311/
> [2] https://sourceforge.net/tracker/?group_id=21935&atid=381743
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-unsubscribe@...
> For additional commands, e-mail: docbook-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

RE: DocBook: The Definitive Guide, Second Edition

2009-12-10T13:55:58Z

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

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

RE: DocBook: The Definitive Guide, Second Edition

2009-12-10T13:29:05Z

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

---
[1] http://oreilly.com/catalog/9781449380311/
[2] https://sourceforge.net/tracker/?group_id=21935&atid=381743

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: Crediting Others in Chapters & Sections

2009-12-09T13:41:07Z

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@...> 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
>> Koha Documentation Manager
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: docbook-unsubscribe@...
>> For additional commands, e-mail: docbook-help@...
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: Crediting Others in Chapters & Sections

2009-12-09T13:32:27Z

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@...
> For additional commands, e-mail: docbook-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Crediting Others in Chapters & Sections

2009-12-09T13:29:12Z

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@...
For additional commands, e-mail: docbook-help@...

[ANN] Release of XMLmind XSL-FO Converter v4.3.2

2009-12-07T00:14:53Z

XMLmind XSL-FO Converter Personal Edition v4.3.2 can be downloaded from
http://www.xmlmind.com/foconverter/downloadperso.shtml

Professional Edition users, please upgrade using this form:
http://www.xmlmind.com/store/download.php

(The above form is usually accessed through
http://www.xmlmind.com/foconverter/upgrade.html.)
_____________________________________________

v4.3.2 (December 4, 2009):

More powerful, yet nicer and easier to use, XMLmind XSL
Utility.

Out of the box, in addition to DocBook and XHTML documents,
XMLmind XSL Utility now allows to convert DITA 1.1 documents
to production-quality XHTML 1.0, XHTML 1.1, HTML 4.1,
Java[tm] Help, HTML Help, Eclipse Help, PDF, PostScript®,
RTF (can be opened in Word 2000+), WordprocessingML (can be
opened in Word 2003+), Office Open XML (.docx, can be opened
in Word 2007+), OpenOffice (.odt, can be opened in
OpenOffice.org 2+).
_____________________________________________

More information:
http://www.xmlmind.com/foconverter/changes.html

--
XMLmind FO Converter Information List
xfc-announce@...
http://www.xmlmind.com/mailman/listinfo/xfc-announce

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

[ANN] Release of XMLmind XML Editor v4.5.1

2009-11-27T01:04:18Z

XMLmind XML Editor Personal Edition v4.5.1 can be downloaded from
http://www.xmlmind.com/xmleditor/download.shtml

Professional Edition users, please upgrade using this form:
http://www.xmlmind.com/store/download.php

(The above form is usually accessed through
http://www.xmlmind.com/xmleditor/upgrade.html.)
_____________________________________________

XMLmind XML Editor v4.5.1 (November 26, 2009):

* New submenu "View > Display Images" allows to
display images as thumbnails, as bounding boxes
or normally. The selected mode may be used as a
default.

* Thanks to XMLmind DITA Converter 1.1.0, DITA
documents can now be converted to Eclipse
Help.

* Among several other functions, new menu item
"Options > Customize Configuration >
Preprocessing Options" makes it easy specifying
a DITA conditional processing profile (a
.ditaval file) from within XXE.
_____________________________________________

More information:
http://www.xmlmind.com/xmleditor/changes.html

--
XMLmind XML Editor Support List
xmleditor-support@...
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...

Re: RFE 2791288: add quote to corpauthor and gui elements

2009-11-23T07:39:32Z

Norman Walsh <ndw@...> writes:
> My current thinking is that we should treat the inlines in groups. If
> you're going to allow some elements of a group, you might just as well
> allow all the elements.
[...]
> I think the natural proposal at this point is to say that we should
> allow the publishing inlines (and trademark) into the ubiquituos
> inlnes.

At the November 2009 telcon, I took an action to produce a
customization layer that implements this proposal. Please find it
attached, along with an example document that outlines the scope of
the changes imposed by this proposal.

More ubiquitous inlines

More ubiquitous inlines

Under this proposal, all of the “publishing inlines” and trademark are added to the set of “ubiquitous inlines”. This will extend the content models of all of the following elements:

`abbrev`	`database`	`keycap`	`postcode`
`accel`	`edition`	`keycode`	`productname`
`acronym`	`email`	`keysym`	`productnumber`
`address`	`emphasis`	`label`	`property`
`application`	`envar`	`lineage`	`publishername`
`arg`	`errorcode`	`lineannotation`	`refmiscinfo`
`artpagenums`	`errorname`	`literal`	`releaseinfo`
`attribution`	`errortext`	`manvolnum`	`remark`
`authorinitials`	`errortype`	`markup`	`returnvalue`
`bibliocoverage`	`exceptionname`	`mathphrase`	`revnumber`
`biblioid`	`fax`	`methodname`	`revremark`
`bibliomisc`	`filename`	`modifier`	`seriesvolnums`
`bibliomset`	`firstname`	`mousebutton`	`shortaffil`
`bibliorelation`	`funcdef`	`msgaud`	`state`
`bibliosource`	`funcparams`	`msglevel`	`street`
`citebiblioid`	`function`	`msgorig`	`subscript`
`city`	`givenname`	`option`	`superscript`
`classname`	`guibutton`	`optional`	`surname`
`code`	`guiicon`	`orgname`	`symbol`
`command`	`guilabel`	`otheraddr`	`tag`
`confdates`	`guimenu`	`othername`	`token`
`confnum`	`guimenuitem`	`package`	`trademark`
`confsponsor`	`guisubmenu`	`pagenums`	`type`
`conftitle`	`hardware`	`paramdef`	`uri`
`constant`	`holder`	`parameter`	`varname`
`contractnum`	`honorific`	`personname`	`volumenum`
`contractsponsor`	`interfacename`	`phone`	`wordasword`
`contrib`	`issuenum`	`phrase`	`year`
`country`	`jobtitle`	`pob`

In addition to inlinemediaobject, remark, subscript, superscript, the linking inlines, and alt, these elements would now also allow abbrev, acronym, trademark, date, emphasis, footnote and footnoteref, foreignphrase, phrase, quote, wordasword, firstterm, glossterm, and coref.

In the particular case of emphasis, foreignphrase, phrase, quote, firstterm, and glossterm only a limited form of each element would be allowed. A quote, for example, in this context would also have a content model limited to the new definition of “ubiquitious inlines”.

The new schema will allow things like: An application and filename.xml.

Be seeing you,
norm

--
Norman Walsh <ndw@...> | A compromise is the art of
http://www.oasis-open.org/docbook/ | dividing a cake in such a way that
Chair, DocBook Technical Committee | everyone believes he has the
| biggest piece.--Ludwig Erhard

moreubiq.rnc (1K) Download Attachment
moreubiq-test.xml (7K) Download Attachment
attachment2 (191 bytes) Download Attachment

DocBook Technical Committee Meeting Minutes: 18 November 2009

2009-11-19T09:59:42Z

DocBook Technical Committee Meeting Minutes: 18 November 2009
=============================================================

The DocBook Technical Committee met on Wednesday, 18 November 2009 at
01:00p EDT (10:00a PDT, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
022:30p India+) for 60 minutes.

1. Roll call

Present: Patricia Gee, Paul Grosso, Dick Hamilton,
Scott Hudson, Gershon Joseph, Jirka Kosek, Larry Rowland,
Bob Stayton, Norm Walsh. We have a quorum.

Absent: Chris Chung, Jim Earley, Keith Falhgren, Nancy Harrison,
Corey Leong, Dave Pawson, John Pederson, Pine Zhang

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

3. Next meeting: 16 December 2009

4. Review of the agenda.

Add item 11a regarding DocBook website maintenance.

5. Review of open action items

a. Norm to put the new backwards compatibility policy in the spec.
COMPLETED.

b. Norm to put the new backwards compatibility policy in the
reference documentation.
COMPLETED.

c. Norm to take a look at the inlines and make a proposal
regarding RFE 2791288.
COMPLETED.

d. Norm to reply to RFE 2820947 (transclusion) with the
committee's concerns (see the minutes).
COMPLETED.

e. Gershon to develop a reltable example.
CONTINUED.

6. DocBook 5.0 standards celebration.

DocBook 5.0 was approved as an OASIS Standard. Congratulations
to all involved. [Pop goes the virtual champagne cork]

7. New edition of DocBook: The Definitive Guide

Dick reports that they are close to doing a technical review,
and he will solicit technical reviewers.

8. Publishing Subcommittee report.

Scott reports that they are still having problems deriving a
DTD from the RelaxNG for the publishing schema.
This technical glitch is holding up the process, and he
may have to resort to creating it by hand.

9. eLearning Subcommittee report.

Scott is organizing an initial meeting for 8 December at
10am EST. They will meet the 2nd Tuesday of each month.

10. DocBook assembly schema.

No further changes have been suggested. Members said they
would try out the prototype stylesheets that Bob provided
that convert between a DocBook document and an assembly
with topics.

ACTION: Larry will publish an updated schema with last month's
changes.

Norm suggested that we make available both full and simplified
versions. He is concerned that the details of the full
version will overwhelm those getting started who need
just basic assembly. It may be separate schemas, or
just documentation and examples.

ACTION: Norm to prepare a proposal for full and simplified
assembly versions.

Bob proposed adding a relatedlink element to DocBook 5. [2]
This could complement related links managed at the
assembly level. Members were generally favorable, but
no action was taken yet.

Bob suggested organizing a separate discussion of
linking in modular DocBook, and several members
expressed interest.

ACTION: Bob to organize a meeting to discuss linking
in modular DocBook.

11. topic element (RFE #2820190).

No further discussion at this time.

11a. DocBook websites.
We have received feedback on the docbook mailing lists
that the number and organization of DocBook websites is
a bit confusing.

ACTION: Norm to develop a proposal for maintaining
the DocBook websites.

12. Review of Requests for Enhancement

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

http://sourceforge.net/tracker/index.php?func=detail&;
group_id=21935&atid=384107&aid=XXXX

RFEs to revisit for 6.0
1907003 biblioid content model too broad

RFEs to be considered
1679665 Add better support for modular documentation

This is covered under agenda item 10.

2770858 Add limited emphasis to ubiquitous inlines
2791288 add quote to corpauthor and gui elements

Norm looked at these two items together. He agrees that since
quote characters are permitted everywhere, the quote element
should also since it can generate quote characters suitable
to each locale. Norm suggested allowing the elements defined
in this DocBook RelaxNG pattern to appear almost everywhere:

db.publishing.inlines =
(db.abbrev
| db.acronym
| db.date
| db.emphasis
| db.footnote
| db.footnoteref
| db.foreignphrase
| db.phrase
| db.quote
| db.subscript
| db.superscript
| db.wordasword)
| db.glossary.inlines
| db.coref

He suggests using other alternate patterns as needed to prevent
nested use of inappropriate elements. There were no
objections.

ACTION: Norm to develop schema changes for discussion at
the next meeting.

2820190 add a topic element

Pending.

2820947 Ability to transclude text

At the August 2009 meeting [3], the committee suggested that
this feature be developed as an XML standard rather than a DocBook
feature. Members now don't feel this is likely to solve the
problems users have expressed. Members have suggested that
XInclude is not sufficient, conref is too complicated, but the
needs persist.

ACTION: Norm to develop a list of use cases and requirements
for transclusion.

ACTION: Bob to add agenda item for this RFE to next meeting.

2821653 indexterms in footnotes

Bob had reported that indexterms in footnotes work in XSLT.
We thought we approved allowing indexterms in footnotes at
the last meeting, but it was not recorded in the minutes,
so it is considered not approved yet. We will reconsider
at the next meeting. Paul suggested that this needs
better documentation.

ACTION: Norm to better document indexterm placement.

-----

[1] http://lists.oasis-open.org/archives/docbook-tc/200910/msg00022.html
[2] http://lists.oasis-open.org/archives/docbook-tc/200911/msg00003.html
[3] http://lists.oasis-open.org/archives/docbook-tc/200908/msg00004.html

Bob Stayton
Sagehill Enterprises
bobs@...

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@...
For additional commands, e-mail: docbook-help@...