mirror of https://github.com/moparisthebest/xeps
Use of definition list for glossary, best practice on table usage and reminder on PDF publications.
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@4102 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Tobias Markmann
parent
3b7b75503a
commit
732073d306
11
xep-0143.xml
11
xep-0143.xml
|
|
@ -11,6 +11,7 @@
|
|||
&LEGALNOTICE;
|
||||
<number>0143</number>
|
||||
<status>Active</status>
|
||||
<interim/>
|
||||
<type>Procedural</type>
|
||||
<sig>Standards</sig>
|
||||
<approver>Council</approver>
|
||||
|
|
@ -21,6 +22,12 @@
|
|||
<supersededby/>
|
||||
<shortname>N/A</shortname>
|
||||
&stpeter;
|
||||
<revision>
|
||||
<version>1.1rc1</version>
|
||||
<date>2010-02-12</date>
|
||||
<initials>tm</initials>
|
||||
<remark><p>Use of definition list for glossary, best practice on table usage and reminder on PDF publications.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>1.0</version>
|
||||
<date>2004-12-09</date>
|
||||
|
|
@ -109,8 +116,9 @@
|
|||
<p>Aside from the metadata in the <header/> element (see above), a XEP file is a series of sections, arranged in a hierarchy (<section1/> is a top-level section, within which you can nest <section2/> sections, and so on down to <section4/>). The title of a section is captured in the 'topic' attribute. You should also include an 'anchor' attribute so that you can link to page fragments from within your document. The allowable elements within a section element probably look familiar from XHTML: <p/> for paragraphs, <ol/> and <ul/> for ordered and unordered lists, and so on.</p>
|
||||
<p>The <example/> and <code/> elements are used to show protocol snippets; the <example/> element SHOULD possess a 'caption' attribute that describes the example, whereas the <code/> element does not. Define an XML CDATA section within both of these elements so that you do not need to escape the '<' and '>' characters in your sample XML stanzas, since this makes life much easier for author and editor alike (see the markup in existing XEP specifications).</p>
|
||||
<p>The <p/> and <li/> elements can also contain more markup that is familiar from XHTML, such as the <img/> element. Note that hyperlinks are of the form <link url='foo'>bar</link> rather than <a href='foo'>bar</a>; the reasons for this are lost in the mists of time and it is too late to change it now, so you'll just have to adjust. If needed, you can also use inline structural and presentational markup such as <em/>, <strong/>, <tt/>, <cite/>, and <span/> within the <p/> and <li/> elements. </p>
|
||||
<p>You may also include tables (these are helpful for listing error codes and such). The <table/> element SHOULD possess a 'caption' attribute that describes the table's contents. Standard XHTML table structure applies (<tr/> defines a row, which contains <th/> elements for header rows and <td/> elements for data rows), and the 'colspan' and 'rowspan' attributes are also available if you need them. Table presentation (such as cellpadding and cellspacing) is handled by the XSLT and CSS stylesheets.</p>
|
||||
<p>You may also include tables (these are helpful for listing error codes and such). The <table/> element SHOULD possess a 'caption' attribute that describes the table's contents. Standard XHTML table structure applies (<tr/> defines a row, which contains <th/> elements for header rows and <td/> elements for data rows), and the 'colspan' and 'rowspan' attributes are also available if you need them. Table presentation (such as cellpadding and cellspacing) is handled by the XSLT and CSS stylesheets. However keep in mind that tables weren't mend to display huge amount of text.</p>
|
||||
<p>In fact, the xep.xsl file performs all sorts of magic in converting your XML file into HTML, including creation of the front matter, table of contents, section numbering, notes, and revision history. Feel free to submit patches for this file, but do not commit your modified version to source control.</p>
|
||||
<p>While HTML being the primary publishing format for XEPs, the XSF Editor also publishes XEPs in form of PDF since 2010. Keeping that in mind you should try to avoid tables with too much columns which require more width available on paper.</p>
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='The Sections of a XEP Document' anchor='sections'>
|
||||
|
|
@ -130,6 +138,7 @@
|
|||
</section2>
|
||||
<section2 topic='Glossary' anchor='sections-glossary'>
|
||||
<p>If your XEP document uses terms that may not be familiar to the reader, please define them in a glossary.</p>
|
||||
<p>The preferred layout for a glossary is a definition list using the HTML <dl>-tag.</p>
|
||||
</section2>
|
||||
<section2 topic='Use Cases' anchor='sections-usecases'>
|
||||
<p>It is recommended that document authors structure their proposals according to the use cases that the proposal will address. <note>A good introduction to use cases may be found at <<link url="http://www.pols.co.uk/usecasezone/">http://www.pols.co.uk/usecasezone/</link>>.</note> We have found that use cases force authors to focus on functionality rather than "protocol for the sake of protocol". It is also helpful to sort use cases by actor, as is done in &xep0045;, for example. Include one subsection for each use case.</p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue