rfc/dtd/rfc2629.dds

#?SuikaWikiConfig/2.0

DocumentType:
  @Name: Markup Language for IETF RFCs
  @Version: (RFC 2629)
  @Description:
    This is a XML based markup language for IETF RFC documents.
  @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/30 07:06:48 $

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