-
Notifications
You must be signed in to change notification settings - Fork 21
/
HowToUse.html
332 lines (285 loc) · 8.22 KB
/
HowToUse.html
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
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
<TITLE>USER'S GUIDE FOR MSV XML GENERATOR</TITLE>
<style>
.title
{
text-align:center;
font-weight:bold;
}
PRE
{
background-color: rgb(240,240,240);
}
</style>
</HEAD>
<BODY>
<P ALIGN=center><B>
USER'S GUIDE FOR MSV XML GENERATOR<BR>
<P>
MSV XML Generator is a tool to generate XML instances from various kinds of schemas.
</P>
<H1>Contents of This Document</H1>
<OL>
<LI><A href="#quick">Quick Start</A>
<LI><A href="#root">Specifying the Root Element</A>
<LI><A href="#example">Providing Examples</A>
<LI><A href="#size">Controlling the Size of Documents</A>
<LI><A href="#error">Generating Invalid Documents</A>
<!-- <LI><A href="#custom">Writing Code to Customize Behavior</A> -->
</OL>
<H1><A name="quick">Quick Start</A></H1>
<P>
To generate a valid instance from a RELAX grammar, enter the following command:
</P>
<PRE>
$ java -jar xmlgen.jar myGrammar.rxg
</PRE>
<P>
To generate 100 valid instances from a TREX pattern, enter the command:
</P>
<PRE>
$ java -jar xmlgen.jar -n 100 myPattern.trex out$.xml
</PRE>
<P>
This will create out00.xml, out01.xml, ... out99.xml.
</P>
<P>
XML Generator is also capable of generating invalid instances.
The following example generates one instance(<code>invalid.xml</code>)
from a W3C XML Schema(<code>mine.xsd</code>).
The generated file is usually almost valid.
</P>
<PRE>
$ java -jar xmlgen.jar -error 1/100 mine.xsd invalid.xml
</PRE>
<P>
The next example also generates an invalid instance. But this time
the generated instance is almost completely wrong.
</P>
<PRE>
$ java -jar xmlgen.jar -error 1/2 mine.xsd terrible.xml
</PRE>
<A name="root">
<H1>Specifying the Root Element</H1></A>
<P>
With schema languages like XML Schema, the generator cannot tell what element should be used as the root element. Therefore, by default it picks one randomly. The "-root" option allows you to change this behavior by telling the generator to use a specific element.
</P><P>
To generate XML files that start with a <code>foo</code> element of the namespace <code>http://my.name.space/</code>, specify:
</P>
<PRE>
$ java -jar xmlgen.jar mine.xsd -root {http://my.name.space/}foo
</PRE>
<P>
If you are not using XML namespaces, you say
</P>
<PRE>
$ java -jar xmlgen.jar mine.xsd -root {}foo
</PRE>
<A name="example">
<H1>Providing Examples</H1></A>
<P>
Due to the expressiveness of W3C XML Schema Part 2, sometimes it is difficult
to generate a string that satisfies a given datatype, especially when the type is derived with
many facets.
</P>
<P>
If this is the case, XML Generator reports the following error and stops.
</P>
<PRE>
unable to generate value for this datatype: XXXX
</PRE>
<P>
You can provide example instances to avoid this problem. If you have a valid instance
<code>abc.xml</code> that conforms to <code>joe.trex</code>,
then enter the following command:
</P>
<PRE>
$ java -jar xmlgen.jar joe.trex <b>-example abc.xml</b>
</PRE>
<P>
XML Generator will read that file and extract literals found in it. Those literals
are then used to generate instances.
The "-example" option can be used more than once to provide additional examples.
</P>
<PRE>
$ java -jar xmlgen.jar joe.trex -example ex1.xml -example ex2.xml
</PRE>
<H1><A NAME="intro">Controlling the Size of Documents</A></H1>
<P>
The size of generated documents can be controlled with two parameters:
cut-back depth and width.
</P>
<P>
Cut-back depth decides how deep a document can be. Once the depth exceeds this value,
the generator is switched to "cut back" mode. In this mode, the generator skips any optional
expressions (like <code>'?'</code> or <code>'*'</code> in a DTD) and tries to stop
further generation.
Therefore if the cut-back depth is set to a bigger value,
generated documents tend to be big.
</P>
<P>
Width decides how many times repeatable items are repeated.
If you set this value to 5, then
<code>'*'</code> will be repeated from 0 to 5 times (uniformly distributed),
and <code>'+'</code> will be repeated from 1 to 6 times (uniformly distributed).
Therefore if width is set to a bigger value, generated documents tend to be also big.
</P>
<P>
Depending on the schema used,
the correlation between the size of generated documents and these parameters
varies.
So you may need to tune these parameters through trial-and-error.
</P>
<H1><A NAME="error">Generating Invalid Documents</A></H1>
<P>
Generator is capable of generating invalid instances.
In this mode, generator randomly inserts errors into the document.
Errors are made by manipulating the document according to several predefined patterns.
</P>
<P>
You can control the probability of each pattern,
or you can set all probabilities to the same value with the "-error" option.
</P>
<P>
Probabilities are set by a fractional number "m/n".
"2/100" indicates probability of 2%.
</P>
<P>
The following sub-sections enumerates each pattern and command line option to control the probability.
</P>
<H3>Greedy Choice</H3>
<P>
A "greedy choice" error is one that selects more than one choice at a time.
</P>
<PRE><XMP>
Schema:
<choice>
<element name="A"> .... </element>
<element name="B"> .... </element>
</choice>
Instance:
<A> ... </A>
<B> ... </B>
</XMP></PRE>
<P>
This probability can be controlled through the "-error-greedyChoice" option.
</P>
<H3>Missing Attribute</H3>
<P>
A "missing attribute" error is made by intentionally skipping a required attribute.
This probability can be controlled through the "-error-missingAttribute" option.
</P>
<PRE><XMP>
Schema:
<element name="foo">
<attribute name="bar">
...
</element>
Instance:
<foo>
...
</foo>
</XMP></PRE>
<H3>Missing Element</H3>
<P>
A "missing element" error is made by intentionally skipping a required element.
This probability can be controlled through the "-error-missingElement" option.
</P>
<H3>Mutated Attribute</H3>
<P>
A "mutated attribute" error is made by intentionally replacing an attribute
by another completely irrelevant attribute.
This probability can be controlled through the "-error-mutatedAttribute" option.
</P>
<PRE><XMP>
Schema:
<element name="foo">
<attribute name="bar">
...
</element>
...
<attribute name="zoo" />
Instance:
<foo zoo="...">
...
</foo>
</XMP></PRE>
<H3>Mutated Element</H3>
<P>
A "mutated element" error is made by intentionally replacing an element
by another completely irrelevant element.
This probability can be controlled through the "-error-mutatedElement" option.
</P>
<H3>Sequence Error</H3>
<P>
A "sequence error" is made by swapping the order of items of a sequence.
This probability can be controlled through the "-error-sequenceError" option.
</P>
<PRE><XMP>
Schema:
<sequence>
<element name="foo"/>
<element name="bar"/>
</sequence>
Instance:
<bar/>
<foo/>
</XMP></PRE>
<H3>Slip-in Attribute</H3>
<P>
A "slip-in attribute" error is made by adding an irrelevant attribute to an element.
This probability can be controlled through the "-error-slipinAttribute" option.
</P>
<PRE><XMP>
Schema:
<element name="foo"/>
<attribute name="a"/>
...
</element>
Instance:
<foo a="..." xyz="...">
...
</foo>
</XMP></PRE>
<H3>Slip-in Element</H3>
<P>
A "slip-in element" error is the element counterpart of the "slip-in attribute" error.
This probability can be controlled through the "-error-slipinElement" option.
</P>
<H3>Missing '+'</H3>
<P>
A "missing plus" error is made by not generating a
non-optional repeatable item.
This probability can be controlled through the "-error-missingPlus" option.
</P>
<PRE><XMP>
Schema:
<!ELEMENT foo (a,b+,c)>
Instance:
<foo>
<a/><c/>
</foo>
</XMP></PRE>
<H3>Attribute Name Typo</H3>
<P>
An "attribute name typo" error is made by modifying several characters of
an attribute name.
This probability can be controlled through the "-error-attributeNameTypo" option.
</P>
<PRE><XMP>
Schema:
<!ATTLIST foo bar CDATA #IMPLIED>
Instance:
<foo bbr="..." />
</XMP></PRE>
<H3>Element Name Typo</H3>
<P>
An "element name typo" error is the element version of the "attribute name typo" error.
It is made by modifying several characters of an element name.
This probability can be controlled through the "-error-elementNameTypo" option.
</P>
</BODY>
</HTML>