OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [docbook-tc] Charter Revision

I've attached a revised charter draft that makes the
changes suggested by Gershon and Norm.

OASIS does not use camel case, though the connection
between OASIS, DocBook and camels is intriguing:). I
probably fat fingered the camel case after typing
DocBook so many times.


Managing Writers: A Real World Guide to Managing Technical Documentation

> -----Original Message-----
> From: Norman Walsh [mailto:ndw@nwalsh.com] 
> Sent: Wednesday, January 21, 2009 10:42 AM
> To: docbook-tc@lists.oasis-open.org
> Subject: Re: [docbook-tc] Charter Revision
> "Gershon Joseph (gerjosep)" <gerjosep@cisco.com> writes:
> > I'm not sure about limited the sentence to "supports". Maybe the
> > following is better:
> > The TC's deliverables currently include the XML DocBook schema, a
> > simplified authoring subset, and a variant for the 
> publishing industry.
> That sounds good.
> Editorially, does OASIS refer to subcommittees as "SubCommittee"s?
> Camel case looks a little odd there to my eyes.
>                                         Be seeing you,
>                                           norm
> -- 
> Norman Walsh <ndw@nwalsh.com>      | It costs a great deal to be
> http://www.oasis-open.org/docbook/ | reasonable; it costs
> Chair, DocBook Technical Committee | youth.--Madame de la Fayette
Title: OASIS DocBook Technical Committee Charter

The charter for this TC is as follows.


OASIS DocBook Technical Committee.

Statement of Purpose

Almost all computer hardware and software developed around the world needs some documentation. For the most part, this documentation has a similar structure and a large core of common idioms. The community benefits from having a standard, open, interchangeable vocabulary in which to write this documentation. DocBook has been, and will continue to be, designed to satisfy this requirement. For more than a decade, DocBook has provided a structured markup vocabulary for just this purpose.

DocBook is now widely used in both commercial and Open Source environments including Debian, Fedora, FreeBSD, GNOME, Hewlett-Packard, IBM Linux Technology Center, KDE, Linux Documentation Project, Mandriva, PHP, Red Hat, SUSE, Subversion, and Sun Microsystems, to name just a few.

The OASIS DocBook Technical Committee is chartered to develop and maintain the DocBook family of specifications and to continue to support its ever growing user base. The TC currently supports the XML DocBook schema, a simplified authoring subset, and a variant for the publishing industry.

The normative version of the DocBook Version 5.0 schema will be delivered using the RelaxNG schema language with additional constraints specified in Schematron. The Technical Committee may support other schema languages as appropriate, and may develop additional modules and derived document types.

Scope of Work

The TC is engaged in evolving the suite of DocBook specifications. The scope of DocBook is computer hardware and software documentation. Broadly, this includes both print and online tutorial and reference documentation as well as online help, user guides, exercises and other ancillary forms of documentation.

This effort will deliver on the following goals:

Most requests for enhancement that are not motivated by a requirement in computer hardware or software documentation are considered out of scope for the committee. However, the committee may address needs in related domains through extensions or variants, and may commission sub-committees to focus on related domains. It is not a goal of the Technical Committee to expand the scope of DocBook to include additional, unrelated problem domains.

The OASIS DocBook Publishers Subcommittee develops and maintains official variants of DocBook to support the publishing industry.

List of Deliverables

The TC expects to update the DocBook family of specifications to reflect issues and enhancements adopted by the TC. Our current timeline for this evolution is:

Q4 2008

Q1 2009

Q3 2009

Additional documents may also be produced at the Committee's discretion. The TC's intent is to pursue OASIS Standard status for major DocBook revisions.


The primary audience for the final output of this TC is structured documentation system architects, implementers, authors, publishers, and users.

Language of the TC

All business of the TC will be conducted in English.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]