RFC2629testcases J. F. Reschke 
 greenbytes 
 January 2005 


Test cases for RFC2629 formatting


Table of Contents


1. Lists

1.1 hanging list

Name:
timeout
Namespace:
DAV:
Purpose:
The timeout associated with a lock
Value:
TimeType ;Defined in section 9.8

1.2 numbered list

A numbered list:

  1. one
  2. two
  3. three

1.3 ordered list (letters)

An ordered list using letters:

  1. one
  2. two
  3. three
  4. one
  5. two
  6. three
  7. one
  8. two
  9. three
  10. one
  11. two
  12. three
  13. one
  14. two
  15. three
  16. one
  17. two
  18. three
  19. one
  20. two
  21. three
  22. one
  23. two
  24. three
  25. one
  26. two
  27. three
  28. one
  29. two
  30. three

1.4 no explicit counters

Example for numbered list with user-defined-format:

R1:
R1
R2:
R2

Another list:

S1:
S1
S2:
S2

Next list should continue counting R's:

R3:
R3
R4:
R4

Same with character-based numbering:

c-a:
c-a
c-b:
c-b

1.5 with explicit counters

A few requirements:

R1:
req R1
R2:
req R2

More requirements:

R3:
req R3
R4:
req R4

A few rules:

R1:
rule R1
R2:
rule R2
R3:
rule R3

Explicit counter with name matching it's format string:

c-c:
c-c
c-d:
c-d

Same, without counter:

c-e:
c-e
c-f:
c-f

1.6 Nested list

  1. One
  2. Two
    1. 17
    2. 42
  3. Three

1.7 list without style

One
Two
Three

2. spanx

This is default.

This is emph(asized).

This is strong.

This is verb(atim).

Here is a carriage return inside a spanx element.


3. Tables

The list of valid keywords are:

keyworddefaultmeaningnot aligned
strict no try to enforce the ID-nits conventions and DTD validity 
iprnotified no include boilerplate from Section 10.4(d) of [RFC2026] bb bb 
compact no when producing a txt/nroff file, try to conserve vertical whitespace ccc ccc ccc 
subcompact compact if compact is "yes", then setting this to "no" will make things a little less compact dddd dddd dddd dddd 
needLines n/a an integer hint indicating how many contiguous lines are needed at this point in the output eeeee eeeee eeeee eeeee eeeee 

Remember, that as with everything else in XML, keywords and values are case-sensitive.


4. Figures

with preamble, no title...

  +--+
  |  |
  +--+
  +--+
  |  |
  +--+

with postamble and title...

Figure 1: another figure

The figure above has the title "another figure".


5. References

5.1 xref with no content

We are in Section 5.

5.2 xref with no content

Section 5 is the parent section.

5.3 xref with no auto-formatting

So far we have sections 1 ("Lists") through 5 ("References").

5.4 eref with no content

See also <http://greenbytes.de/tech/webdav>. Here's another one that is quite long: <http://greenbytes.de/tech/webdav/draft-reschke-rfc3744bis-issues.html#5.7_inherited-acl-set-protected>. Does it break properly?

5.5 eref with content

See also greenbytes WebDAV resources.


6. Paragraph formatting

This is the first sentence of the paragraph. This is the second sentence of the paragraph (with two leading blanks). Here's another sentence that was started on a separate line in the input file.

This is the second paragraph.


7. Sections

7.1 Subsection with TOC entry

7.2 Subsection without TOC entry

7.2.1 Sub-subsection with TOC entry


8. Comments

This line contains a few comments. [rfc.comment.1] This line contains a few comments. [comment1] This line contains a few comments. [comment2] This line contains a few comments. [rfc.comment.2] This line contains a few comments.


9. Artwork width

This should fit (69 characters plus three spaces of indentation in text output).

012345678901234567890123456789012345678901234567890123456789012345678

This shouldn't.

0123456789012345678901234567890123456789012345678901234567890123456789

10. Extensions

These are tests for extensions done in rfc2629.xslt. Do not expect them to work out-of-the-box in xml2rfc.

10.1 Markup in figure/artwork

Internal References: a test reference to [RFC2396]

External References: a test reference to <http://xml.resource.org>

a test index entry inside a figure

Styling: <spanx> inside artwork

11. Blank Lines

Just a forced
line break.

One

blank line.

Seven







blank lines.

12. References

[RFC2026]Bradner, S., “The Internet Standards Process -- Revision 3”, BCP 9, RFC 2026, October 1996.
[RFC2396]Berners-Lee, T., Fielding, R.T., and L. Masinter, “Uniform Resource Identifiers (URI): Generic Syntax”, RFC 2396, August 1998.
This RFC will soon be updated, check <http://cvs.apache.org/viewcvs.cgi/*checkout*/ietf-uri/rev-2002/rfc2396bis.html> for the latest draft.
The issues list is at <http://cvs.apache.org/viewcvs.cgi/*checkout*/ietf-uri/rev-2002/issues.html>.

Editorial Comments

[rfc.comment.1]
No anchor, source given. --JRE
[comment1]
Anchor given, no source.
[comment2]
Both specified. --JRE
[rfc.comment.2]
No anchor, no source.

Author's Address

Julian F. Reschkegreenbytes GmbHSalzmannstrasse 152Muenster, NW 48159GermanyPhone: +49 251 2807760Fax: +49 251 2807761EMail: URI: http://greenbytes.de/tech/webdav/

Index

<