[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Changes to PubSubJ deliverable
Bernard, Apologies for the delay in getting the suggested corrections to you! I have attached a document with the suggested corrections as well as the OASIS document that I used as the template for the corrections. (Particular thanks to Mary Nisikawa for the new document name. Errors in the implementation of that name and other "corrections" should be charged to yours truly.) Note that some of the formatting in the Word document is highly defective! Apologies, hurried and more concerned about the content than the presentation. (Perhaps Vivian could help with the niceties of Word, which I use as rather powerful scratch pad more than anything else.) On the document name, the OASIS guidelines are found at: http://www.oasis-open.org/spectools/docs/chairs-filenaming-02.html Mary Nisikawa suggested: > pubsubj-pt1-1.0-cs.pdf (html etc.) which I used for the attached document. Other changes: *Title* OASIS Published Subjects Technical Committee Recommendation, 2003-06-24 became: OASIS Published Subjects Technical Committee Specification, 2003-06-24 *Document identifier* Document identifier: 2003-06-26-00002.000.doc became: Document identifier: pubsubj-pt1-1.0-cs.doc *Status* Status: Committee Recommendation became: Status: Committee Specification The erratta page for this specification is at http://www.oasis-open.org/apps/org/workgroup/tm-pubsubj/ *Revision* Revision: $Id: pubsubj-gentle-intro.htm,v 1.13 2003/06/24 09:09:30 pepper Exp $ became: (move to end and provide revision history, just left marker for it since I don't have the proper content) *Table of Contents* I don't use Word often enough to revise the TOC. Need to delete 4. References and put that content under the References section (note addition of square brackets) in the Appendixes section. I added the Committee members from the OASIS pages and pasted in the boiler-plate from the example HTML page which I am attaching to this post. Appendixes A. Committee Members (Non-Normative) B. Notices C. Intellectual Property Rights D. Revision History References Should be online most of the coming weekend. Note that I am leaving for the UK on the 17th of July and returning to the US on the 26th of July. Should have relatively reliable email access during that time. Leaving for Montreal on the 31st of July and hope to see one and all at the ISO meetings on the 1st of August! Hope everyone is having a great day! Patrick -- Patrick Durusau Director of Research and Development Society of Biblical Literature Patrick.Durusau@sbl-site.org Chair, V1 - Text Processing: Office and Publishing Systems Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model Topic Maps: Human, not artificial, intelligence at work!Title: {Document Title}
Working Draft 03, {date}
Copyright © 2002 OASIS Open, Inc. All Rights Reserved. Table of Contents
AppendixesThe key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this document are to be interpreted as described in [RFC 2119]. {This section is provided to explain and demonstrate the DocBook markup for OASIS specifications. It is important to use the markup provided in the template consistently and to avoid adding new elements or using raw formatting.} {Delete this entire section when using this sample document to begin a new specification.} The role of DocBook is to identify the semantic elements of your document; to say what things are, not how they should be formatted. When DocBook is transformed to HTML for rendering, CSS is used to provide most of the visual styling information. For transformation to print, the styling is controlled more closely by the XSLT stylesheet. OASIS specifications are DocBook articles. Each article must have introductory metadata and may contain any number of section elements followed optionally by appendix, glossary, bibliography, and index elements. A specification can be divided into sections with the section element. Sections are recursive. Section numbering is provided by the stylesheet, authors should not insert section numbers manually. DocBook provides several list styles:
For schema and other code examples, use the programlisting element: 1234567890123456789012345678901234567890123456789012345678901234567890 1 2 3 4 5 6 <simpleType name="DecisionType"> <restriction base="string"> <enumeration value="Permit"/> <enumeration value="Deny"/> <enumeration value="Indeterminate"/> </restriction> </simpleType> For small, non-normative code fragments, screen is appropriate: A small code example To format code examples so that they will be highlighted more distinctly in the presentation, use informalexample: 1234567890123456789012345678901234567890123456789012345678901234567890 1 2 3 4 5 6 <simpleType name="DecisionType"> <restriction base="string"> <enumeration value="Permit"/> <enumeration value="Deny"/> <enumeration value="Indeterminate"/> </restriction> </simpleType> Alternatively, to create formal figures or examples, with numbers and titles, use figure or example, respectively. DocBook provides a whole host of inline elements, many of which may be appropriate for your specification. Consider, in particular, computeroutput, emphasis, literal, markup, phrase, quote, replaceable, sgmltag, sgmltag, userinput. Within an article, the articleinfo element provides a wrapper for metadata. Each of the required metadata elements should be encoded as follows:
A. Committee Members (Non-Normative)The following individuals were members of the committee during the formulation of this document:
B. NoticesCopyright © The Organization for the Advancement of Structured Information Standards [OASIS] 2001, 2002. 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. C. 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 {technical-committee} web page (http://www.oasis-open.org/committees/{technical-committee}) D. Revision History
Normative[RFC 2119] S. Bradner. RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. IETF (Internet Engineering Task Force). 1997. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]