HTML versions of CD-04

["Gilbert Pilz" <Gilbert.Pilz@bea.com>]

So here's a fun little experiment:

1.) Go to http://docs.oasis-open.org/templates and download "OASIS
Specification Template v2-0.ott".

2.) From your desktop open the above template (this assumes you have OO
2.0 installed). This will create a new .odt document with appropriate
boiler-plate etc. Scroll to the bottom of the document and notice how
the appendix section titles are in 18-point, bold, blue Arial with the
word "Appendix" pre-pended.

3.) Save this new document as HTML (for best results configure OO to
render to HTML 3.2).

4.) Open the resulting HTML document with a browser and scroll to the
bottom of the document. Notice how the appendix section numbers are in a
normal-looking (not large, not bold, black) font without the word
"Appendix".

I've attached a copy of the HTML that is generated from the above
process.

I'm not saying that OASIS is responsible for OO's bugs. On the other
hand, if we are going to be required to produce HTML, it would be
helpful if the templates that we are provided with produced documents
that rendered properly to HTML.

- gp

[Specification Title vX.X]

[Stage], [DD Month YYYY]

Document identifier:

[document identifier as per OASIS Artifact Naming Guidelines]

OASIS identifier:

[OASIS document number]

Location:

Persistent: [persistent location]

This Version: [location of this version]

Previous Version: [location of previous version]

Technical Committee:

OASIS [official name of technical committee] TC

Chair(s):

[Chair name]

[Chair name]

Editor(s):

[Editor name]

[Editor name]

Subject / Keywords:

[Comma-separated keyword listing]

OASIS Conceptual Model Topic Area:

[Topic Area]

Related Work:

This specification replaces or supercedes:

• [specification replaced by this standard]

• [specification replaced by this standard]

This specification is related to:

• [related specifications]

• [related specifications]

Abstract:

[Summary of the technical purpose of the document.]

Status:

This document was last revised or approved by the [TC name | membership of OASIS] on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at www.oasis-open.org/committees/[short name].

For 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 Technical Committee web page (www.oasis-open.org/committees/[TC short name]ipr.php.

The non-normative errata page for this specification is located at www.oasis-open.org/committees/[TC short name].



Notices

Copyright © OASIS Open 2005. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

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 section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, 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 OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

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' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on 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 implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.



Table of Contents

1 Introduction 5

1.1 Terminology 5

1.2 Normative References 5

1.3 Non-normative References 5

2 [Section Title] 6

1 Introduction

[All text is normative unless otherwise indicated.]

1.1 Terminology

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be interpreted as described in IETF RFC 2119 .

1.2 Normative References

[RFC 2119] S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. IETF RFC 2119, March 1997. http://www.ietf.org/rfc/rfc2119.txt.

[Reference] [reference citation]

1.3 Non-normative References

[Reference] [reference citation]

[Reference] [reference citation]

2 [Section Title]

1. Acknowledgments

The following individuals have participated in the creation of this specification and are gratefully acknowledged

Participants:

• [Participant name, affiliation | Individual member]
• [Participant name, affiliation | Individual member]
• [Participant name, affiliation | Individual member]



2. Revision History

[optional; should not be included in OASIS standards]

3. Non-Normative Text

[document identifier goes here] [dd Month yyyy]
Copyright © OASIS Open 2005. All Rights Reserved. Page 10 of 10

Sample_from_template_html_m59b2c745.gif