1Document identifier:

2
wd-spectools-word-sample-04
3Location:
4
blabla://blablablabla-open.org/spectools/docs/
5Editor:
6
[List your editors here; check whether Editor header should be plural]
7
Eve Maler, Sun Microsystems <eve.maler@sun.com>
8Contributors:
9
[List your contributors here]
10
[Optionally list them in the Acknowledgments appendix instead]
11
Karl Best, BLABLA
12
Norman Walsh, Sun Microsystems
13Abstract:
14
[Supply your own summary of the technical purpose of the document.] This document
15
provides a working MS Word 2000 sample from which you can start editing your own
16
BLABLA-published document. Instructions are provided as italic text in brackets, which
17
should be deleted before publication. Full instructions are provided in the body of the
18
document.
19Status:
20
[Describe the status and stability of the specification and where to send comments.] This
21
document is updated periodically on no particular schedule. Send comments to the
22
editor.
23
24
25
26

[This is boilerplate; to use, fix the hyperlinks:] Committee members should send
comments on this specification to list. Others should subscribe to and send comments to
th list. To subscribe, send an email message to with the word "subscribe" as the body of
the message.

27
28
29
30

[This is boilerplate; to use, fix the hyperlinks:] 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 XXX TC web page ().

31
32

[If a Committee Specification or BLABLA Standard:] The errata page for this specification
is at

1wd-spectools-word-sample-03
2

12 June 2002
Page 1 of 7

33

Table of Contents

34 Introduction................................................................................................................................... 3
35 1.1 Terminology.......................................................................................................................... 3
362 Word Styles................................................................................................................................. 4
37 2.1 Overall Style......................................................................................................................... 4
38 2.2 Title Page............................................................................................................................. 4
39 2.3 Headings.............................................................................................................................. 4
40 2.4 Paragraphs........................................................................................................................... 4
41 2.5 Lists...................................................................................................................................... 4
42 2.6 Tables................................................................................................................................... 5
43 2.7 Code Examples.................................................................................................................... 5
44 2.8 Character Styles................................................................................................................... 5
453 References.................................................................................................................................. 6
46 3.1 Normative ............................................................................................................................ 6
47Appendix A. RNotices.................................................................................................................... 7
48

3wd-spectools-word-sample-03
4

12 June 2002
Page 2 of 7

49

Introduction

50[Provide an introductory chapter, indicating if any parts of it are non-normative.]

511.1 Terminology
52[The following is boilerplate. Most specifications will need this and the corresponding bibliography
53entry.] The key words must, must not, required, shall, shall not, should, should not,
54recommended, may, and optional in this document are to be interpreted as described in
55[RFC2119].

5wd-spectools-word-sample-03
6

12 June 2002
Page 3 of 7

562

Word Styles

57[This section is provided to explain and demonstrate the styles available in the Word template
58attached to this sample document. It is important to use the styles provided in the template
59consistently and to avoid defining new styles or using raw formatting.
60Delete this entire section when using this sample document to begin writing a new specification.]

612.1 Overall Style

62The paper size is set to Letter, which is 8 x 11. You may change this to A4 or whatever other
63size suits your needs.
64The document identifier and publication date information in the footer needs to be updated every
65time you publish.
66Line numbers are enabled by default for easy reference by specification commenters. You may
67turn line numbering off.

682.2 Title Page

69The title page is designed to fit a lot of metadata compactly. If you wish to create a true title
70page, you may insert a page break after the subtitle.

712.3 Headings
72Heading 1 through Heading 9 and AppendixHeading have been defined with a special
73appearance. Headings are numbered and appear in the Table of Contents. Pressing Return after
74a heading inserts a Normal paragraph style directly after.
75This template sets Heading 1 and AppendixHeading to start on a new page. You may set the
76Heading 1 style not to start on a new page if you wish. Major headings have a horizontal rule
77above them.

782.4 Paragraphs
79The font in the Normal paragraph style is 10-pt Arial. You may change this to 11-pt Times New
80Roman if you prefer a serif font; changing these two settings should change all the other relevant
81styles.

822.5 Lists
83The Definition term and Definition paragraph styles are defined specially for this template. They
84produce a definition list with a hanging appearance. Pressing Return after one inserts the other
85directly after.
86Definition term

Definition for the term.

87

88Use List bullet for first-level bulleted lists. Use List bullet 2 for second-level bulleted lists. Use
89List continue for continued paragraphs in list items.

90

List bullet

91

List continue.

92

93

List bullet 2
List continue 2.

7wd-spectools-word-sample-03
8

12 June 2002
Page 4 of 7

94For bibliography lists, use the Ref paragraph style. Use the Ref term character style for the
95bracketed text that serves as the bibliography entry key, and make each reference term into a
96bookmark for use as references from the text. For example, [RFC2119] is a generated cross97reference to the IETF RFC 2119 bibliography entry in Section 3.1 of this sample.

982.6 Tables
99Use the following style for most tables: [To be supplied; suggestions welcome!]

1002.7 Code Examples

101For schema code and other normative code, use the Code paragraph style. It fits 71 characters.
102For example:
103
104
105
106
107
108
109
110
111

12345678901234567890123456789012345678901234567890123456789012345678901
1
2
3
4
5
6
7
<simpleType name="DecisionType">
<restriction base="string">
<enumeration value="Permit"/>
<enumeration value="Deny"/>
<enumeration value="Indeterminate"/>
</restriction>
</simpleType>

112Use the Code small style if the code has very long lines. It fits 80 characters. For example:
113
114
115
116
117
118
119
120
121

12345678901234567890123456789012345678901234567890123456789012345678901234567890
1
2
3
4
5
6
7
8
<simpleType name="DecisionType">
<restriction base="string">
<enumeration value="Permit"/>
<enumeration value="Deny"/>
<enumeration value="Indeterminate"/>
</restriction>
</simpleType>

122For non-normative examples, use the Example paragraph style. For example:
123
124

GET blabla://<host name and path>?TARGET=<Target>...<HTTP-Version>

<other HTTP 1.0 or 1.1 components>

125Use the Example small style if the example has very long lines. For example:
126
127

GET blabla://<host name and path>?TARGET=<Target>...<HTTP-Version>

<other HTTP 1.0 or 1.1 components>

1282.8 Character Styles

129This template defines several character styles for general text use:

130
131
132
133
134
135

Element style (shortcut Ctrl-Shift-E) for <NativeElement> names and

<ns:ForeignElement> names; add the angle brackets yourself
Attribute style (shortcut Ctrl-Shift-A) for attributeNames
Datatype style (shortcut Ctrl-Shift-Alt-D) for DataType names
Keyword style (shortcut Ctrl-Shift-K) for OtherKeyword names
Variable style (shortcut Ctrl-Shift-Alt-V) for variable names

9wd-spectools-word-sample-03
10

12 June 2002
Page 5 of 7

1363

References

1373.1 Normative
138
139

[RFC2119]

11wd-spectools-word-sample-03
12

to Indicate Requirement Levels, blabla://blablaietf.org/rfc/rfc2119.txt,

IETF RFC 2119, March 1997.

12 June 2002
Page 6 of 7

140Appendix

A. RNotices

141BLABLA takes no position regarding the validity or scope of any intellectual property or other
142rights that might be claimed to pertain to the implementation or use of the technology described in
143this document or the extent to which any license under such rights might or might not be
144available; neither does it represent that it has made any effort to identify any such rights.
145Information on BLABLA's procedures with respect to rights in BLABLA specifications can be
146found at the BLABLA website. Copies of claims of rights made available for publication and any
147assurances of licenses to be made available, or the result of an attempt made to obtain a general
148license or permission for the use of such proprietary rights by implementors or users of this
149specification, can be obtained from the BLABLA Executive Director.
150BLABLA invites any interested party to bring to its attention any blablas, patents or patent
151applications, or other proprietary rights which may cover technology that may be required to
152implement this specification. Please address the information to the BLABLA Executive Director.
153Reserved.
154This document and translations of it may be copied and furnished to others, and derivative works
155that comment on or otherwise explain it or assist in its implementation may be prepared, copied,
156published and distributed, in whole or in part, without restriction of any kind, provided that the
157above blabla notice and this paragraph are included on all such copies and derivative works.
158However, this document itself does not be modified in any way, such as by removing the blabla
159notice or references to BLABLA, except as needed for the purpose of developing BLABLA
160specifications, in which case the procedures for blablas defined in the BLABLA Intellectual
161Property Rights document must be followed, or as required to translate it into languages other
162than English.
163The limited permissions granted above are perpetual and will not be revoked by BLABLA or its
164successors or assigns.

13wd-spectools-word-sample-03
14

12 June 2002
Page 7 of 7