File: README.xml

package info (click to toggle)
docbook-jrefentry 1.1.0-1
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k, lenny, sarge, squeeze
  • size: 108 kB
  • ctags: 9
  • sloc: xml: 236; makefile: 32; sh: 4
file content (179 lines) | stat: -rw-r--r-- 5,123 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
<!DOCTYPE article
  PUBLIC "-//OASIS//DTD Simplified DocBook XML V4.1.2.5//EN"
  "http://www.oasis-open.org/docbook/xml/simple/4.1.2.5/sdocbook.dtd">
<article>
<artheader><title>README for the JRefEntry DTD V1.1</title>
<copyright><year>2000</year><year>2001</year>
<holder>Norman Walsh</holder></copyright>
<legalnotice>
<para>Java and JavaDoc are registered trademarks of
Sun Microsystems, Inc.</para>
</legalnotice>
</artheader>

<para>This is a customization of the DocBook RefEntry model. The
purpose of this customization is to mirror the order and nature
of structured comment tags in JavaDoc documentation.</para>

<section><title>Overview</title>

<para>JavaDoc comments for a consist of a purpose followed by a
description followed by additional, optional tags. This structure
is modelled by JRefEntry as follows:</para>

<informaltable>
<tgroup cols="2" pgwide="1">
<thead>
<row>
  <entry>JavaDoc tag</entry>
  <entry>JRefEntry element</entry>
</row>
</thead>
<tbody>
<row>
  <entry><emphasis>purpose</emphasis> (contextual)</entry>
  <entry><sgmltag>refpurpose</sgmltag></entry>
</row>
<row>
  <entry><emphasis>description</emphasis> (contextual)</entry>
  <entry><sgmltag>refdescription</sgmltag></entry>
</row>
<row>
  <entry>@author</entry>
  <entry><sgmltag>refauthor</sgmltag></entry>
</row>
<row>
  <entry>@version</entry>
  <entry><sgmltag>refversion</sgmltag></entry>
</row>
<row>
  <entry>@param</entry>
  <entry><sgmltag>refparameter</sgmltag></entry>
</row>
<row>
  <entry>@return</entry>
  <entry><sgmltag>refreturn</sgmltag></entry>
</row>
<row>
  <entry>@exception</entry>
  <entry><sgmltag>refexception</sgmltag></entry>
</row>
<row>
  <entry>@throws (alternate for @exception)</entry>
  <entry><sgmltag>refthrows</sgmltag> (alternate for <sgmltag>refexception</sgmltag>)</entry>
</row>
<row>
  <entry>@see</entry>
  <entry><sgmltag>refsee</sgmltag></entry>
</row>
<row>
  <entry>@since</entry>
  <entry><sgmltag>refsince</sgmltag></entry>
</row>
<row>
  <entry>@serial</entry>
  <entry><sgmltag>refserial</sgmltag></entry>
</row>
<row>
  <entry>@deprecated</entry>
  <entry><sgmltag>refdeprecated</sgmltag></entry>
</row>
</tbody>
</tgroup>
</informaltable>

<para>Within sections that would normally be repeated (e.g., @param),
use a <sgmltag>variablelist</sgmltag> for each individual item. To break
the items into groups, use separate lists.</para>

<note>
<para>The content models of each of these special sections are
designed so that the could easily be mapped to a normal DocBook
<sgmltag>refentry</sgmltag>. For example,
<sgmltag class="starttag">refdescription</sgmltag>
could easily be mapped to
<literal><![CDATA[<refsect1><title>Description</title>]]></literal>.</para>
</note>

</section>
<section><title>Manifest</title>

<variablelist>
<varlistentry><term>README</term>
<listitem>
<para>This readme file.</para>
</listitem>
</varlistentry>
<varlistentry><term>jrefentry.dtd</term>
<listitem>
<para>The JRefEntry DTD. It is built on top of the XML version of
DocBook V4.0.</para>
</listitem>
</varlistentry>
</variablelist>

</section>
<section><title>Installation</title>

<para>Place the files in this distribution somewhere on your machine.  Adjust
your catalog(s) if appropriate (XML tools frequently do not support 
catalogs, so this may be irrelevant for you).</para>

<para>Please use the following formal public identifier to identify this
DTD:</para>

<programlisting>
  -//Norman Walsh//DTD JRefEntry V1.0//EN
</programlisting>

<para>For example, to write a JRefEntry document, you might use
this DOCTYPE declaration:</para>

<programlisting>
<![CDATA[<!DOCTYPE refentry
          PUBLIC "-//Norman Walsh//DTD JRefEntry V1.0//EN"
                 "http://nwalsh.com/docbook/jrefentry/1.0/jrefentry.dtd">
]]></programlisting>

</section>

<section><title>Copyright</title>

<literallayout>
JRefEntry DTD V1.0
Copyright &copy; 2000 Norman Walsh
http://nwalsh.com/docbook/jrefentry/
</literallayout>

<para>You may distribute this DTD under the same terms as DocBook.</para>

<para>Please direct all questions and comments about this DTD to
Norman Walsh, <email>ndw@nwalsh.com</email>.</para>

<para>This DTD is based on DocBook XML V4.1.2 from OASIS.</para>

<para>For more information about the DocBook DTD, see
<ulink url="http://www.oasis-open.org/docbook/">http://www.oasis-open.org/docbook/</ulink>.</para>

</section>
<section><title>Warranty</title>

<para>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT.  IN NO EVENT SHALL NORMAN WALSH OR ANY OTHER
CONTRIBUTOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.</para>

</section>
<section><title>Contacting the Author</title>

<para>This DTD is maintained by the DocBook Open Repository team on
<ulink url="http://sourceforge.net/projects/docbook/">SourceForge</ulink>.
</para>

</section>
</article>