[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Committee Spec
/ Norman Walsh <ndw@nwalsh.com> was heard to say: | Here's the spec. I have the impression that not everyone has read it, | or perhaps even knew it existed. I'll delay posting 4.3 for a few more | days until I see if there are any comments. | | In particular, we should probably have discussed the MIME type | appendix. Easier to read if I attach it, huh?Title: The DocBook Document Type
Committee Specification 4.3, 17 Mar 2004
Copyright © 2001, 2002, 2003, 2004 The Organization for the Advancement of Structured Information Standards [OASIS]. All Rights Reserved. Table of Contents
AppendixesDocBook is general purpose XML and SGML document type particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications). The DocBook Technical Committee maintains the DocBook schema. DocBook is officially available as a Document Type Definition (DTD) for both XML and SGML. It is unofficially available in other forms as well. The Version 4.3 release is a maintainance release. It introduces no backwards-incompatible changes. All valid DocBook 4.2 documents are also valid DocBook 4.3 documents. The DocBook Technical Committee welcomes bug reports and requests for enhancement (RFEs) from the user community. The current list of outstanding requests is available through the SourceForge tracker interface. This is also the preferred mechanism for submitting new requests. Old RFEs, from a previous legacy tracking system, are archived for reference. The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this Committee Specification are to be interpreted as described in [RFC 2119]. Note that for reasons of style, these words are not capitalized in this document. The DocBook document type is distributed for XML and SGML from the DocBook site at OASIS. DocBook is also available from the mirror on http://docbook.org/. There are no substantive changes in this release. This is the official Committee Specification. There are no backwards-incompatible changes in this release.
There are no backwards-incompatible changes in this release.
There are no backwards-incompatible changes in this release. Per the decision at the 19 Nov 2003 Technical Committee meeting, DocBook V4.3b5 is republished as DocBook V4.3CR1 (Candidate Release 1). There have been no technical changes since V4.3b5. There are no backwards-incompatible changes in this release. Each of the changes made between DocBook V4.2b4 and DocBook XML V4.3b5 is summarized here. For complete details, consult the individual RFEs and the meeting minutes. There are no backwards-incompatible changes in this release. Each of the changes made between DocBook V4.2b3 and DocBook XML V4.3b4 is summarized here. For complete details, consult the individual RFEs and the meeting minutes.
There are no backwards-incompatible changes in this release. Each of the changes made between DocBook V4.2b2 and DocBook XML V4.3b3 is summarized here. For complete details, consult the individual RFEs and the meeting minutes.
There are no backwards-incompatible changes in this release. Each of the changes made between DocBook V4.2 and DocBook XML V4.3b2 is summarized here. For complete details, consult the individual RFEs and the meeting minutes. There was no public beta 1 release.
This is a beta release by the editor. It has no normative status and may contain bugs. The following backwards-incompatible changes were announced in DocBook V4.0, the DocBook Technical Committee expects to incorporate them into DocBook V5.0. Each of the changes proposed is summarized here. For complete details, consult the individual RFEs and the meeting minutes.
The DocBook Technical Committee expects to announce the following backwards-incompatible changes in DocBook V5.0, for eventual incorporation into DocBook V6.0. Each of the changes proposed is summarized here. For complete details, consult the individual RFEs and the meeting minutes.
A. The DocBook Media TypeThis appendix registers a new MIME media type, "application/docbook+xml".
B. OASIS DocBook Technical Committee (Non-Normative)The following individuals were members of the committee during the formulation of this Committee Specification:
[RFC 3023] IETF (Internet Engineering Task Force). RFC 3023: XML Media Types. M. Murata, S. St. Laurent, D. Kohn. 2001. [DocBook: TDG] Norman Walsh and Leonard Meullner. DocBook: The Definitive Guide. O’Reilly & Associates, 1999. C. NoticesCopyright © The Organization for the Advancement of Structured Information Standards [OASIS] 2001, 2002, 2003, 2004. All Rights Reserved. OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director. OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS has been notified of intellectual property rights claimed in regard to some or all of the contents of this specification. For more information consult the online list of claimed rights. D. Intellectual Property RightsFor information on wether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the DocBook web page (http://www.oasis-open.org/committees/docbook/) E. Revision History
Normative[SGML] JTC 1, SC 34. ISO 8879:1986 Information processing -- Text and office systems -- Standard Generalized Markup Language (SGML). 1986. [XML] Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, and Eve Maler, editors. Extensible Markup Language (XML) 1.0 Second Edition. World Wide Web Consortium, 2000. [RFC 2119] IETF (Internet Engineering Task Force). RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. 1997. |
Be seeing you, norm -- Norman Walsh <ndw@nwalsh.com> | Everything should be made as http://www.oasis-open.org/docbook/ | simple as possible, but no simpler. Chair, DocBook Technical Committee |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]