[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Minutes from 14/15 June 2000
Here are the minutes from the meeting in Paris. If no one posts an
objection before next week, I'll post them to the website.
<webpage id="min20000614">
<config param="rcsdate" value="$Date: 2000/02/15 21:44:58 $"/>
<config param="filename" value="min20000614.html"/>
<config param="dir" value="meetings"/>
<head>
<title>DocBook TC Minutes, 14/15 June 2000</title>
<summary>Meeting minutes</summary>
</head>
<sect1>
<title>Summary</title>
<para>These notes summarize the DocBook Technical Committee (TC) meeting that
took place in Paris on 14 and 15 June 2000 as part of the OASIS meetings
colocated with XML Europe '00.</para>
</sect1>
<sect1><title>14 June</title>
<sect2>
<title>Present</title>
<itemizedlist>
<listitem><para>Terry Allen</para></listitem>
<listitem><para>Dennis Evans</para></listitem>
<listitem><para>Eduardo Gutentag</para></listitem>
<listitem><para>Norman Walsh (Chair)</para></listitem>
</itemizedlist>
</sect2>
<sect2>
<title>Agenda</title>
<itemizedlist>
<listitem><para>Review and approve DocBook 4.1 changes</para></listitem>
<listitem><para>Review RFEs</para></listitem>
<listitem><para>Discuss parameter entity reorganization</para></listitem>
<listitem><para>Discuss XML Schema</para></listitem>
</itemizedlist>
<sect3>
<title>Review and approve DocBook V4.1</title>
<para>Moved: we approve V4.1 with the minor changes previously
outlined: fixing FPIs, comments, and the version number in the
catalog.</para>
<para>The motion was adopted without objection.</para>
<para>If 4.1 contains errors, let's make it possible to fix them without
a teleconference or face-to-face meeting:</para>
<para>Moved: we agree that future versions of 4.x can be released by the editor
without formal vote, provided that members of the docbook-tc mailing list
are given 5 business days to raise objections and no such objections are
raised.</para>
<para>The motion was adopted without objection.</para>
</sect3>
<sect3>
<title>New RFEs</title>
<variablelist>
<varlistentry><term>Issue 117: Add support for DOI in meta</term>
<listitem><para>
We see that DOI will not be the only object identifier.
We will add biblioid and citebiblioid with a class attribute. The
legal values of this attribute will be: urn, doi, isbn, issn, pubnumber.
The elements isbn, issn, and pubnumber are deprecated. FU that we will
remove them in 6.0.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 120: Add macro element for marking up macros in programming languages</term>
<listitem><para>Macro already exists as a class of systemitem. See
<link linkend="action200006">action items</link>; we need a design principal
for when to add new inlines or new class attributes.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 121: Add markup for signals</term>
<listitem><para>
Need more info. What other sorts of things are like this. Rather than
adding new inlines for signal specifically, we'd like to come up with
an element that was more general and add class values. Perhaps "Event"
and "EventHandler"?
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 122: Add markup for troubleshooting</term>
<listitem><para>
Rejected: this seems to be too application specific. Suggest Procedure
with role and possibly other inline markup or a local extension.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 123: Add markup to support specifications</term>
<listitem><para>
Rejected: we consider this is out-of-scope for DocBook, but he should
consider RosettaNet which is doing product spec sheets and similar
sorts of things.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 124: Add markup for hostnames and other host identifiers</term>
<listitem><para>
We already have a class on systemitem for systename. We suggest that these
are further useful class values for systemitem but do not warrant a unique
element name. We'll add the following class attributes to systemitem:
domainname, fqdomainname, ipaddress, netmask, etheraddress. We consider
hostname already covered by systemname.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 125: Add markup for usernames</term>
<listitem><para>Username already exists as a class of systemitem.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 126: Allow SimpleSect in Section</term>
<listitem><para>We will add SimpleSect to the end of Section.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 127: Add 'dissertation' to list of article classes</term>
<listitem><para>Yes.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 128: Better support for typing and linking in funcdef</term>
<listitem><para>
We'll add type to the content model of funcdef and paramdef to allow
authors to specify that types are in fact types. Linking will be handled
by XLink in some future version.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 129: Support easier installation</term>
<listitem><para>
The committee welcomes such efforts, but is unwilling to undertake the
issue directly. There's too much variability across platforms.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 130: Add inline markup for protocols, FS types, and partitions</term>
<listitem><para>
Protocol is another example of a case where we need to consider the design
more carefully (what other things are like protocols); in the meantime use
literal, phrase, or some other markup with a role attribute.
</para>
<para>
We'll add 'filesystem' to the class attribute of systemitem.
</para>
<para>
We'll add 'partition' to the class attribute of filename.
</para></listitem>
</varlistentry>
<varlistentry><term>Issue 131: Simplify citerefentry markup</term>
<listitem><para>Considered and rejected.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<sect3><title>Discuss parameter entity reorganization</title>
<para>Discussion continues.</para>
</sect3>
<sect3><title>Discuss XML Schema</title>
<para>Discussion continues.</para>
</sect3>
</sect2>
</sect1>
<sect1><title>15 June</title>
<sect2>
<title>Present</title>
<itemizedlist>
<listitem><para>Terry Allen</para></listitem>
<listitem><para>Dennis Evans</para></listitem>
<listitem><para>Norman Walsh (Chair)</para></listitem>
</itemizedlist>
</sect2>
<sect2>
<title>Agenda</title>
<itemizedlist>
<listitem><para>Review and approve DocBook 4.1 changes</para></listitem>
<listitem><para>Review RFEs</para></listitem>
<listitem><para>Discuss parameter entity reorganization</para></listitem>
<listitem><para>Discuss XML Schema</para></listitem>
</itemizedlist>
<sect3><title>Discuss parameter entity reorganization</title>
<para>Discussion continues.</para>
</sect3>
<sect3><title>Discuss XML Schema</title>
<para>Discussion continues.</para>
</sect3>
</sect2>
</sect1>
<sect1 id="action200006"><title>Action Items</title>
<itemizedlist>
<listitem><para>norm: Remind list about EBNF. If there's no comment in
1 month, we'll just close the issue.
</para></listitem>
<listitem><para>norm: Remind list about coregion. If no one expresses
need, we'll just close the issue.
</para></listitem>
<listitem><para>Dennis: survey the landscape of technical inlines and
propose a design principal.
</para></listitem>
</itemizedlist>
</sect1>
</webpage>
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | The laws of conscience, which we
http://www.oasis-open.org/docbook/ | pretend to be derived from nature,
Chair, DocBook Technical Committee | proceed from custom.--Montaigne
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC