|
|
|
DocBook TC
Minutes, 07/08 Mar 1999 |
|
|
These notes summarize the DocBook
Technical Committee (TC) meeting that took
place in San Jose on 07 and 08 Mar 1999 as
part of the OASIS meetings colocated with
XTech'99.
-
Discuss XML migration
-
Review of RFEs
-
Discuss 4.0 to make sure we've
identified all the
backwards incompatible changes we
want for 5.0
-
Better support for other
computer languages (funcsynopsis
and inlines)
-
Additional inlines for Linux
community
-
Revisit use of %nav.class;
in book components and sections
-
Review ToC/LoT apparatus, should
LoT become ListOfTitles? Should TOC
persist?
-
Marginal graphics
The TC has decided that DocBook v5.0
will be XML compatible. We will not rename
DocBook and the only change made to the FPI
will be the version number (we will not add
“XML” to the FPI).
We will add a README file that explains
the hardest issues, such as tag omission,
inclusions, exclusions, etc.
As a result of the preceding RFEs, the
changes described below will be made.
-
A new effectivity attribute, Condition
will be added to the common
attributes. (17)
-
The elements in the %nav.class
; parameter entity will be
allowed at the component and
section levels. (38)
-
The content model of components
and sections will be made loose, as
the content model of book was made
loose in 3.1. (38)
-
The class values
devicefile and
libraryfile will be added
to Filename.
(65)
-
The class values
username,
groupname , and
library will be added to
SystemItem .
(65)
-
A SideBarInfo
element will be added to SideBar.
(81)
-
The values Journal,
Series, Set, and
Manuscript will be added
to PubWork
attribute of CiteTitle.
(85)
-
The attribute values
xmlpi (for <?pitarget
?>) and emptytag (for
<foo/>) will be added to the
Class
attribute of SgmlTag
-
Parameter entities will be added
to allow a customization layer to
remove the dbcent.mod and
dbnotn.mod
modules. (88)
-
CO will be
added to the content models of Synopsis and
LiteralLayout.
(92)
-
The content model of MsgText will
be reduced to a mixture that is
equivalent to the current %
example.mix;. (37)
-
The full CALS table model will
be replaced with the OASIS Exchange
Table model. (80)
-
Title will
be removed from %
bibliocomponent.mix;. The
title in a bibliographic entry is
properly a citation and not a
title, so the appropriate markup is
CiteTitle .
CiteTitle
was added to %
bibliocomponent.mix; in
DocBook 3.1. (83)
-
The content model of CiteTitle
will be reduced to %title.char.mix;.
(84)
-
The Class
attribute on ProductName
will be made #IMPLIED.
(89)
-
The Synopsis
element will be removed from %para.char.mix;.
(91)
-
ErrorName
will be defined to be the name for
an ErrorCode
(ENOENT). ErrorCode
will be defined to be the
alphanumeric code for the error
(-2). ErrorType
remains the classification of the
error. ErrorText
will be added to hold the text of
an error message. (94)
As a result of the preceding RFEs, the
changes described below will be made as
soon as the details can be worked out.
-
The content model of ToC will be
simplified. The semantic of a ToC is
that it only contains entries for
the elements that are its peers and
descendants of its peers. The
semantic of an empty ToC is that
it is a location where an
automatically generated table of
contents is to appear. (97)
Perhaps:
<!ELEMENT ToC - O ((%bookcomponent.title.content;)?,
(%component.mix;)*, (ToCDiv* | ToCEntry*))
%ndxterm.exclusion;>
<!ATTLIST ToC
%pagenum.attrib;
%common.attrib;
%toc.role.attrib;
%local.toc.attrib;>
<!ELEMENT ToCDiv - O ((%sect.title.content;)?,((%tocdivcomponent.mix;)*,
ToCEntry+))>
<!ATTLIST ToCDiv
%linkend.attrib; --to element that this entry represents--
%pagenum.attrib;
%common.attrib;
%toc.role.attrib;
%local.toc.attrib;>
<!ELEMENT ToCEntry - - ((%para.char.mix;)+,ToCEntry*)>
<!ATTLIST ToCEntry
%linkend.attrib; --to element that this entry represents--
%pagenum.attrib;
%common.attrib;
%tocentry.role.attrib;
%local.tocentry.attrib;>
-
FuncSynopsis
will be extended to provide support
for modern programming
languages.
-
Additional inlines will be added
to provide support for modern
programming languages.
-
Look at DOM WG's IDL model for
ideas about extending FuncSynopsis.
-
Formulate proposal for new inlines
(RFE 96).
-
Find out more about IETM forms
(RFE 93).
-
Fix documentation for KeyCap.
(Norm)
-
Cleanup *Info contents
and add an RFE for it. (Terry)
-
Ask list about renaming ToC and LoT to
TableOfContents
and ListOfTitles,
respectively.
|
|
|
|