rfc/dtd/rfc2629.dds

#?SuikaWikiConfig/2.0

DocumentType:
  @Name: Markup Language for IETF RFCs
  @Version: (RFC 2629)
  @ID: rfc2629
  @BaseURI:
    http://suika.fam.cx/gate/cvs/*checkout*/markup/rfc/dtd/
  
  @Namespace:
    @@UsePrefix: 0
  
  @Copyright: Wakaba <w@suika.fam.cx>
  @RCSDate: $Date: 2003/10/23 23:25:33 $

Driver:
  @ModuleSet:
    @@Name: Markup Language for IETF RFCs
    @@ID: rfc2629
    @@BaseURI:
      module/
    @@Namespace:
      @@@Name:
        urn:x-suika-fam-cx:markup:ietf:rfc:2629:
      @@@DefaultPrefix: rfc
      @@@UsePrefix: -1
    @@Default: 1
  
  @QNameModule:
    @@ID:
      rfc2629:qname
  
  @DatatypeModule:
    @@ID:
      rfc2629:datatype
  @NotationModule:
    @@ID:
      rfc2629:notation
  
  @AttributeModule:
    @@ID:
      rfc2629:attribs
  
  @Module:
    @@ID:
      rfc2629:blkstruct
    @@Description: Block structural module
  @Module:
    @@ID:
      rfc2629:figure
    @@Description: Figure module
  @Module:
    @@ID:
      rfc2629:metainfo
    @@Description: Metainformational module
  @Module:
    @@ID:
      rfc2629:reference
    @@Description: Reference and hyperlink module
  @Module:
    @@ID:
      rfc2629:struct
    @@Description: Document structure module
  
  @GeneralEntity:
    @@Name: rfc.number
    @@EntityValue: XXXX
    @@Description:
      General entity "rfc.number"
      \
      If you use this entity, you should define this entity with your RFC issued
      number in the internal subset of DOCTYPE declaration of your RFC document.

Model:
  
  @Class:
    @@Name: figure
    @@Content: figure
  
  @Class:
    @@Name: t-figure
    @@Content: | $figure
    @@Description:
      RFC 2629-bis says that although RFC 2629 allows the figure element to
      be nested within the t element, authors are strongly encouraged to
      avoid this usage.
  
  @Class:
    @@Name: hyperlink
    @@Content: xref | eref
  
  @Class:
    @@Name: list
    @@Content: list
  
  @Class:
    @@Name: inline
    @@Content:
        $hyperlink
  
  @Class:
    @@Name: blockcontent.extra
    @@Content: 
  @Class:
    @@Name: blockcontent
    @@Content: $blockcontent.extra
  
  @Class:
    @@Name: block
    @@Content:
        t
      | figure
      | section
  
  @Class:
    @@Name: misc
    @@Content:
        iref
  
  
  @Class:
    @@Name: metaterm.content
    @@Content: ($CTEXT.datatype)
    @@Description: Terminal element representing a meta property
  
  @Class:
    @@Name: rfc-header.extra
    @@Content: 
  @Class:
    @@Name: rfc-header
    @@Content:
      front
      $rfc-header.extra
  
  @Class:
    @@Name: front-title.extra
    @@Content:
  @Class:
    @@Name: front-title
    @@Content:
      title
      $front-title.extra
  
  @Class:
    @@Name:
      :Misc.extra
    @@Content: 
  @Class:
    @@Name:
      :Misc.class
    @@Content:
      $misc
      $:Misc.extra
    @@Description:
      neither block nor inline, and can
      essentially be used anywhere in the document body
  
  @Class:
    @@Name:
      :Inline.extra
    @@Content: 
  @Class:
    @@Name:
      :Inline.class
    @@Content:
      $inline
      $:Inline.extra
    @@Description: includes all inline elements
  @Class:
    @@Name: 
      :Inline.mix
    @@Content:
      $:Inline.class
      $:Misc.class
    @@Description: all inline elements, including %Misc.class;
  
  @Class:
    @@Name:
      :Block.extra
    @@Content: 
  @Class:
    @@Name:
      :Block.class
    @@Content:
      $block
      $:Block.extra
    @@Description: includes all block elements
  @Class:
    @@Name: 
      :Block.mix
    @@Content:
      $:Block.class
      $:Misc.class
    @@Description: includes all block elements plus %Misc.class;
  
  @Class:
    @@Name:
      :Flow.mix
    @@Content:
        $:Block.class
      | $:Inline.class
      $:Misc.class
1	wakaba	1.1	#?SuikaWikiConfig/2.0
2
3			DocumentType:
4			@Name: Markup Language for IETF RFCs
5			@Version: (RFC 2629)
6			@ID: rfc2629
7			@BaseURI:
8			http://suika.fam.cx/gate/cvs/checkout/markup/rfc/dtd/
9
10			@Namespace:
11			@@UsePrefix: 0
12
13			@Copyright: Wakaba <w@suika.fam.cx>
14	wakaba	1.2	@RCSDate: $Date: 2003/10/23 23:25:33 $
15	wakaba	1.1
16			Driver:
17			@ModuleSet:
18			@@Name: Markup Language for IETF RFCs
19			@@ID: rfc2629
20			@@BaseURI:
21			module/
22			@@Namespace:
23			@@@Name:
24			urn:x-suika-fam-cx:markup:ietf:rfc:2629:
25			@@@DefaultPrefix: rfc
26			@@@UsePrefix: -1
27			@@Default: 1
28
29			@QNameModule:
30			@@ID:
31			rfc2629:qname
32
33			@DatatypeModule:
34			@@ID:
35			rfc2629:datatype
36			@NotationModule:
37			@@ID:
38			rfc2629:notation
39
40			@AttributeModule:
41			@@ID:
42			rfc2629:attribs
43
44			@Module:
45			@@ID:
46			rfc2629:blkstruct
47			@@Description: Block structural module
48			@Module:
49			@@ID:
50			rfc2629:figure
51			@@Description: Figure module
52			@Module:
53			@@ID:
54			rfc2629:metainfo
55			@@Description: Metainformational module
56			@Module:
57			@@ID:
58			rfc2629:reference
59			@@Description: Reference and hyperlink module
60			@Module:
61			@@ID:
62			rfc2629:struct
63			@@Description: Document structure module
64
65			@GeneralEntity:
66			@@Name: rfc.number
67			@@EntityValue: XXXX
68			@@Description:
69			General entity "rfc.number"
70			\
71			If you use this entity, you should define this entity with your RFC issued
72			number in the internal subset of DOCTYPE declaration of your RFC document.
73
74			Model:
75
76			@Class:
77			@@Name: figure
78			@@Content: figure
79	wakaba	1.2
80			@Class:
81			@@Name: t-figure
82			@@Content: \| $figure
83			@@Description:
84			RFC 2629-bis says that although RFC 2629 allows the figure element to
85			be nested within the t element, authors are strongly encouraged to
86			avoid this usage.
87	wakaba	1.1
88			@Class:
89			@@Name: hyperlink
90			@@Content: xref \| eref
91
92			@Class:
93			@@Name: list
94			@@Content: list
95
96			@Class:
97			@@Name: inline
98			@@Content:
99			$hyperlink
100
101			@Class:
102			@@Name: blockcontent.extra
103			@@Content:
104			@Class:
105			@@Name: blockcontent
106			@@Content: $blockcontent.extra
107
108			@Class:
109			@@Name: block
110			@@Content:
111			t
112			\| figure
113			\| section
114
115			@Class:
116			@@Name: misc
117			@@Content:
118			iref
119
120
121			@Class:
122			@@Name: metaterm.content
123			@@Content: ($CTEXT.datatype)
124			@@Description: Terminal element representing a meta property
125
126			@Class:
127			@@Name: rfc-header.extra
128			@@Content:
129			@Class:
130			@@Name: rfc-header
131			@@Content:
132			front
133			$rfc-header.extra
134
135			@Class:
136			@@Name: front-title.extra
137			@@Content:
138			@Class:
139			@@Name: front-title
140			@@Content:
141			title
142			$front-title.extra
143
144			@Class:
145			@@Name:
146			:Misc.extra
147			@@Content:
148			@Class:
149			@@Name:
150			:Misc.class
151			@@Content:
152			$misc
153			$:Misc.extra
154			@@Description:
155			neither block nor inline, and can
156			essentially be used anywhere in the document body
157
158			@Class:
159			@@Name:
160			:Inline.extra
161			@@Content:
162			@Class:
163			@@Name:
164			:Inline.class
165			@@Content:
166			$inline
167			$:Inline.extra
168			@@Description: includes all inline elements
169			@Class:
170			@@Name:
171			:Inline.mix
172			@@Content:
173			$:Inline.class
174			$:Misc.class
175			@@Description: all inline elements, including %Misc.class;
176
177			@Class:
178			@@Name:
179			:Block.extra
180			@@Content:
181			@Class:
182			@@Name:
183			:Block.class
184			@@Content:
185			$block
186			$:Block.extra
187			@@Description: includes all block elements
188			@Class:
189			@@Name:
190			:Block.mix
191			@@Content:
192			$:Block.class
193			$:Misc.class
194			@@Description: includes all block elements plus %Misc.class;
195
196			@Class:
197			@@Name:
198			:Flow.mix
199			@@Content:
200			$:Block.class
201			\| $:Inline.class
202			$:Misc.class