[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: DocBook V4.5
/ Mary McRae <marypmcrae@gmail.com> was heard to say: | Hi Norm, | | Exactly :-) I was wondering what happened to your submission | yesterday! I just blew it, my bad. | I'll note it for 15 Mar - I don't expect there will be | any problems getting 5 OASIS member organizations to certify that | they're using the spec! Uh. No. :-) I've tweaked the formatting of the specification a little bit in an attempt to comply with the Artifact Standard Identification Scheme for Metadata 1.0. Can you take a look and see if you think the TC Administrator would approve of my document ;-)Title: The DocBook Document Type
The DocBook Document TypeCommittee Specification, 16 February 2006
Copyright © 2001, 2002, 2003, 2004, 2005, 2006 The Organization for the Advancement of Structured Information Standards [OASIS]. All Rights Reserved. Table of ContentsAppendixesDocBook 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.5 release is a maintainance release. It introduces no backwards-incompatible changes. All valid DocBook 4.4 documents are also valid DocBook 4.5 documents. The Committee decided to produce a DocBook V4.5, incorporating a few recent backwards-compatible changes, in order to publish DocBook as a Committee Draft and eventually as an OASIS Standard through the new process. 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. It is also available in RELAX NG and W3C XML Schema formats. The DocBook site is mirrored on http://docbook.org/. There are no technical changes in this release. There are no technical changes in this release. There are no backwards-incompatible changes in this release. Each of the changes made between DocBook V4.5b1 and DocBook V4.5CR1 is summarized here. For complete details, consult the individual RFEs and the meeting minutes. There are no technical changes in DocBook V4.5CR1. There are no backwards-incompatible changes in this release. Each of the changes made between DocBook V4.4 and DocBook V4.5b1 is summarized here. For complete details, consult the individual RFEs and the meeting minutes.
XML validation technologies have evolved rapidly in the last few years. The Technical Committee is exploring the possibility of using RELAX NG as the principal validation technology for DocBook V5.0. The move to RELAX NG will also cause some one time backward-incompatible changes which are not listed in this specifcation. A. The DocBook Media TypeThis appendix registers a new MIME media type, "
For documents labeled as " B. OASIS DocBook Technical Committee (Non-Normative)The following individuals were members of the committee during the formulation of this Committee Specification:
C. NoticesCopyright © The Organization for the Advancement of Structured Information Standards [OASIS] 2001, 2002, 2003, 2004, 2005, 2006. 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 whether 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, et. al., editors. Extensible Markup Language (XML) 1.0 (Third Edition). World Wide Web Consortium, 04 Feb 2004. [RFC 2119] IETF (Internet Engineering Task Force). RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. 1997. [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. |
Be seeing you, norm P.S. Sorry for the dup, I forgot to send it to Mary the first time around. -- Norman Walsh <ndw@nwalsh.com> | Clearness is so eminently one of http://www.oasis-open.org/docbook/ | the characteristics of truth that Chair, DocBook Technical Committee | often it even passes for truth | itself.-- Joubert
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]