source: fedd/fedd_types.xsd @ 159a447

axis_examplecompt_changesinfo-opsversion-1.30version-2.00version-3.01version-3.02
Last change on this file since 159a447 was d81971a, checked in by Ted Faber <faber@…>, 16 years ago

checkpoint of the resource management stuff

  • Property mode set to 100644
File size: 22.3 KB
Line 
1<?xml version="1.0"?>
2<xsd:schema targetNamespace="http://www.isi.edu/faber/fedd_types"
3  xmlns:tns="http://www.isi.edu/faber/fedd_types"
4  xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"
5  xmlns="http://www.w3.org/2000/10/XMLSchema">
6
7  <xsd:complexType name="IDType">
8    <xsd:annotation>
9      <xsd:documentation>
10        An ID is an identifier for a principal, service, or object.  This type
11        is currently polymorphic o allow different implementations of type,
12        though running code primarily uses localnames and fedids.
13      </xsd:documentation>
14    </xsd:annotation>
15    <xsd:choice>
16      <xsd:element name="uuid" type="xsd:base64Binary"/>
17      <xsd:element name="fedid" type="xsd:base64Binary"/>
18      <xsd:element name="uri" type="xsd:string"/>
19      <xsd:element name="localname" type="xsd:string"/>
20      <xsd:element name="kerberosUsername" type="xsd:string"/>
21    </xsd:choice>
22  </xsd:complexType>
23
24  <xsd:complexType name="nodeType">
25    <xsd:annotation>
26      <xsd:documentation>
27        A node from an Emulab.  It may have 0 or more images or hardware
28        types associated with it.  As this description is used for
29        acquiring access to the testbed in question, multiple images or
30        types are considered options.  Specifying multiple image names
31        indicates that the requester is looking for support for any of
32        them.
33      </xsd:documentation>
34    </xsd:annotation>
35    <xsd:sequence>
36      <xsd:element name="image" type="xsd:string" minOccurs="0"
37        maxOccurs="unbounded"/>
38      <xsd:element name="hardware" type="xsd:string" minOccurs="0"
39        maxOccurs="unbounded"/>
40    </xsd:sequence>
41    <xsd:attribute name="count" type="xsd:int" use="optional"/>
42  </xsd:complexType>
43
44  <xsd:simpleType name="kindType">
45    <xsd:annotation>
46      <xsd:documentation>
47        An indication of how requested networking capacity is measured.
48        This will undoubtably expand.
49      </xsd:documentation>
50    </xsd:annotation>
51    <xsd:restriction base="xsd:string">
52      <xsd:enumeration value="max"/>
53      <xsd:enumeration value="average"/>
54    </xsd:restriction>
55  </xsd:simpleType>
56
57  <xsd:complexType name="capacityType">
58    <xsd:annotation>
59      <xsd:documentation>
60        A strawman network capacity description for access negotiation.
61        This will come to include more and more interesting parameters.
62      </xsd:documentation>
63    </xsd:annotation>
64    <xsd:sequence>
65      <xsd:element name="rate" type="xsd:double"/>
66      <xsd:element name="kind" type="tns:kindType"/>
67    </xsd:sequence>
68  </xsd:complexType>
69
70  <xsd:complexType name="accessType">
71    <xsd:annotation>
72      <xsd:documentation>
73        This captures an access credential that will be used to access
74        resources.  These are certificates or public keys.  The type is
75        used to designate the key to which access should be bound, or on
76        a reply has been bound.  Dynamic credentials where new keys have
77        been created may also be passed in this kind of field.
78      </xsd:documentation>
79    </xsd:annotation>
80    <xsd:choice>
81      <xsd:element name="X509" type="xsd:base64Binary"/>
82      <xsd:element name="sshPubkey" type="xsd:base64Binary"/>
83      <xsd:element name="pgpPubkey" type="xsd:base64Binary"/>
84    </xsd:choice>
85  </xsd:complexType>
86
87  <xsd:simpleType name="userRole">
88    <xsd:annotation>
89      <xsd:documentation>
90        This defines the role the user/account is playing in the
91        federated experiment.  An account being accessed by the
92        federation system to create the experiment is in the
93        experimentCreation role and the accounts that experimenters will
94        use to access local testbed services (e.g., rebooting a local
95        node) are serviceAccess roles.
96      </xsd:documentation>
97    </xsd:annotation>
98    <xsd:restriction base="xsd:string">
99      <xsd:enumeration value="serviceAccess"/>
100      <xsd:enumeration value="experimentCreation"/>
101    </xsd:restriction>
102  </xsd:simpleType>
103
104
105  <xsd:complexType name="userType">
106    <xsd:annotation>
107      <xsd:documentation>
108        The definition of a user principal.  It includes the
109        identification of the user as an ID type, the access credential(s)
110        that the user will use, and the role of the user, if any.
111        Multiple access keys may be used, and it is also possible for
112        the user to be anonymous.  Though it is possible to specify a
113        user without ID, access, or role, it is difficult to imagine
114        such a user being useful.
115      </xsd:documentation>
116    </xsd:annotation>
117    <xsd:sequence>
118      <xsd:element name="userID" type="tns:IDType" minOccurs="0"
119        maxOccurs="1"/>
120      <xsd:element name="access" type="tns:accessType" minOccurs="0"
121        maxOccurs="unbounded"/>
122      <xsd:element name="role" type="tns:userRole" minOccurs="0" maxOccurs="1"/>
123    </xsd:sequence>
124  </xsd:complexType>
125
126  <xsd:complexType name="fedAttrType">
127    <xsd:annotation>
128      <xsd:documentation>
129        A general attribute/value pair for passing federation parameters and
130        preferences.  Anything encodable in XML is allowed.  This is a
131        point for customization and extension.
132      </xsd:documentation>
133    </xsd:annotation>
134    <xsd:sequence>
135      <xsd:element name="attribute" type="xsd:string"/>
136      <xsd:element name="value" type="xsd:string"/>
137    </xsd:sequence>
138  </xsd:complexType>
139
140
141  <xsd:complexType name="resourcesType">
142    <xsd:annotation>
143      <xsd:documentation>
144        The estimate of resources a requester is looking for, or the
145        response of a testbed indicating what it can provide.  This is
146        something of a placeholder for a full resource specification,
147        and alternative encodings are likely to be imported.
148      </xsd:documentation>
149    </xsd:annotation>
150    <xsd:sequence>
151      <xsd:element name="node" type="tns:nodeType" minOccurs="0"
152        maxOccurs="unbounded" />
153      <xsd:element name="capacity" type="tns:capacityType" minOccurs="0"
154        maxOccurs="unbounded"/>
155    </xsd:sequence>
156  </xsd:complexType>
157
158  <xsd:complexType name="mapType">
159    <xsd:annotation>
160      <xsd:documentation>
161        Explicit translation of testbed attribute in a federated experiment
162        description to the URI at which the controlling federation
163        system can be reached.  Used in a creation request.
164
165        This type allows tools to encode experiments in familiar local
166        names for experimenters while providing remote federation
167        systems the information to map the local name into a service
168        location.
169      </xsd:documentation>
170    </xsd:annotation>
171    <xsd:sequence>
172      <xsd:element name="testbed" type="tns:IDType"/>
173      <xsd:element name="uri" type="xsd:string"/>
174    </xsd:sequence>
175  </xsd:complexType>
176
177
178  <xsd:complexType name="projectType">
179    <xsd:annotation>
180      <xsd:documentation>
181        A description of the project used to access a testbed.  Includes
182        the testbed being accessed, the project name (often a local
183        name, scoped by the testbed), and any users who have been
184        granted access or for whom access is being requested.
185      </xsd:documentation>
186    </xsd:annotation>
187    <xsd:sequence>
188      <xsd:element name="testbed" type="tns:IDType" minOccurs="0"
189        maxOccurs="1"/>
190      <xsd:element name="name" type="tns:IDType" minOccurs="0" maxOccurs="1"/>
191      <xsd:element name="user" type="tns:userType" minOccurs="0"
192        maxOccurs="unbounded"/>
193    </xsd:sequence>
194  </xsd:complexType>
195
196  <xsd:complexType name="emulabType">
197    <xsd:annotation>
198      <xsd:documentation>
199        A description of an Emulab sufficient for the federation system
200        to create a sub experiment on it.  Note that fedAttrs provide an
201        extension mechanism by which testbeds may communicate additional
202        information and preferences to federation systems that
203        understand it.
204      </xsd:documentation>
205    </xsd:annotation>
206    <xsd:sequence>
207      <xsd:element name="project" type="tns:projectType"/>
208      <xsd:element name="domain" type="xsd:string"/>
209      <xsd:element name="boss" type="xsd:string"/>
210      <xsd:element name="ops" type="xsd:string"/>
211      <xsd:element name="fileServer" type="xsd:string"/>
212      <xsd:element name="eventServer" type="xsd:string"/>
213      <xsd:element name="fedAttr" type="tns:fedAttrType" minOccurs="0"
214        maxOccurs="unbounded"/>
215    </xsd:sequence>
216  </xsd:complexType>
217
218  <xsd:complexType name="federatedExperimentType">
219    <xsd:annotation>
220      <xsd:documentation>
221        Naming and Emulab instantiation information about a federant.
222        This is returned by various informational requests and as part
223        of a successful creation message.
224      </xsd:documentation>
225    </xsd:annotation>
226    <xsd:sequence>
227      <xsd:element name="name" type="tns:IDType" minOccurs="1" 
228        maxOccurs="unbounded"/>
229      <xsd:element name="emulab" type="tns:emulabType"/>
230      <xsd:element name="master" type="xsd:boolean"/>
231    </xsd:sequence>
232  </xsd:complexType>
233
234
235  <xsd:complexType name="vtoponodeType">
236    <xsd:annotation>
237      <xsd:documentation>
238        Node in the virtual topology of a federated experiment (Emulab
239        legacy).  The fields are the local hostname and the IP addresses
240        of the experimental interfaces(colon-separated).
241      </xsd:documentation>
242    </xsd:annotation>
243    <xsd:sequence>
244      <xsd:element name="vname" type="xsd:string"/>
245      <xsd:element name="ips" type="xsd:string"/>
246    </xsd:sequence>
247  </xsd:complexType>
248
249  <xsd:complexType name="vtopolanType">
250    <xsd:annotation>
251      <xsd:documentation>
252        LAN in the virtual topology of a federated experiment (Emulab legacy).
253        The fields are the name of the LAN/link (vname) the node that
254        this description applies to (vnode), the IP of the connection,
255        and performance information.
256      </xsd:documentation>
257    </xsd:annotation>
258    <xsd:sequence>
259      <xsd:element name="vname" type="xsd:string"/>
260      <xsd:element name="vnode" type="xsd:string"/>
261      <xsd:element name="ip" type="xsd:string"/>
262      <xsd:element name="bandwidth" type="xsd:int"/>
263      <xsd:element name="delay" type="xsd:float"/>
264      <xsd:element name="member" type="xsd:string"/>
265    </xsd:sequence>
266  </xsd:complexType>
267
268  <xsd:complexType name="vtopoType">
269    <xsd:annotation>
270      <xsd:documentation>
271        The virtual topology of a federated experiment (Emulab legacy).
272      </xsd:documentation>
273    </xsd:annotation>
274    <xsd:sequence>
275      <xsd:element name="node" type="tns:vtoponodeType" minOccurs="0" 
276        maxOccurs="unbounded" />
277      <xsd:element name="lan" type="tns:vtopolanType" minOccurs="0"
278        maxOccurs="unbounded"/>
279    </xsd:sequence>
280  </xsd:complexType>
281
282  <xsd:complexType name="visnodeType">
283    <xsd:annotation>
284      <xsd:documentation>
285        Node in the visualization of a federated experiment (Emulab
286        legacy).  Fields include the local hostname of the node, x,y
287        coordinates in a 2-dimensional representation, and whether the
288        node in the visualization is a host or a LAN.
289      </xsd:documentation>
290    </xsd:annotation>
291    <xsd:sequence>
292      <xsd:element name="name" type="xsd:string"/>
293      <xsd:element name="x" type="xsd:int"/>
294      <xsd:element name="y" type="xsd:int"/>
295      <xsd:element name="type" type="xsd:string"/>
296    </xsd:sequence>
297  </xsd:complexType>
298
299  <xsd:complexType name="visType">
300    <xsd:annotation>
301      <xsd:documentation>
302        The visualization of a federated experiment (Emulab legacy)
303      </xsd:documentation>
304    </xsd:annotation>
305    <xsd:sequence>
306      <xsd:element name="node" type="tns:visnodeType" minOccurs="0"
307        maxOccurs="unbounded"/>
308    </xsd:sequence>
309  </xsd:complexType>
310
311  <xsd:complexType name="projectAllocType">
312    <xsd:annotation>
313      <xsd:documentation>
314        The information needed to create a dynamic project, specifically
315        a project description and the resources in needs access to.
316        This is used by an internal fedd interface.
317      </xsd:documentation>
318    </xsd:annotation>
319    <xsd:sequence>
320      <xsd:element name="project" type="tns:projectType"/>
321      <xsd:element name="resources" type="tns:resourcesType" 
322        minOccurs="0" maxOccurs="1"/>
323    </xsd:sequence>
324  </xsd:complexType>
325
326  <xsd:complexType name="projectAllocResponseType">
327    <xsd:annotation>
328      <xsd:documentation>
329        The description of a dynamically created project, used by an
330        internal fedd interface.
331      </xsd:documentation>
332    </xsd:annotation>
333    <xsd:sequence>
334      <xsd:element name="project" type="tns:projectType"/>
335    </xsd:sequence>
336  </xsd:complexType>
337
338  <xsd:complexType name="experimentDescriptionType">
339    <xsd:annotation>
340      <xsd:documentation>
341        The description of the federated experiment, in extended ns2.
342      </xsd:documentation>
343    </xsd:annotation>
344    <xsd:choice>
345      <xsd:element name="ns2description" type="xsd:base64Binary"/>
346    </xsd:choice>
347  </xsd:complexType>
348
349  <xsd:complexType name="requestType">
350    <xsd:annotation>
351      <xsd:documentation>
352        Request for access to a testbed.  It includes the testbed from
353        which resources are being requested (a single service may
354        provide access to many), the user or project requesting access
355        (a testbed making the request will leave both empty), the
356        resources needed, the access keys to be used in the subsequent
357        instantiation and service use, an allocation ID to identify this
358        access in later requests, and scheduling information.
359      </xsd:documentation>
360    </xsd:annotation>
361    <xsd:sequence>
362      <xsd:element name="destinationTestbed" type="tns:IDType"
363        minOccurs="0" maxOccurs="1" />
364      <xsd:choice>
365        <xsd:element name="project" type="tns:projectType" minOccurs="0" 
366          maxOccurs="1"/>
367        <xsd:element name="user" type="tns:userType" minOccurs="0"
368          maxOccurs="unbounded"/>
369      </xsd:choice>
370      <xsd:element name="resources" type="tns:resourcesType" minOccurs="0" 
371        maxOccurs="1"/>
372      <xsd:element name="createAccess" type="tns:accessType" minOccurs="1" 
373        maxOccurs="unbounded"/>
374      <xsd:element name="serviceAccess" type="tns:accessType" minOccurs="1" 
375        maxOccurs="unbounded"/>
376      <xsd:element name="allocID" type="tns:IDType"/>
377      <xsd:element name="when" type="xsd:dateTime" minOccurs="0" maxOccurs="1"/>
378      <xsd:element name="until" type="xsd:dateTime" minOccurs="0" 
379        maxOccurs="1"/>
380    </xsd:sequence>
381  </xsd:complexType>
382
383  <xsd:complexType name="responseType">
384    <xsd:annotation>
385      <xsd:documentation>
386        Response to an access request.  Includes the allocation, the
387        information needed to access creation and experiment services
388        and scheduling information.
389      </xsd:documentation>
390    </xsd:annotation>
391    <xsd:sequence>
392      <xsd:element name="allocID" type="tns:IDType"/>
393      <xsd:element name="emulab" type="tns:emulabType"/>
394      <xsd:element name="when" type="xsd:dateTime" minOccurs="0" maxOccurs="1"/>
395      <xsd:element name="until" type="xsd:dateTime" minOccurs="0" 
396        maxOccurs="1"/>
397    </xsd:sequence>
398  </xsd:complexType>
399
400  <xsd:complexType name="releaseRequestType">
401    <xsd:annotation>
402      <xsd:documentation>
403        A request to release the access rights allocated by an earlier
404        RequestAccess call.
405      </xsd:documentation>
406    </xsd:annotation>
407    <xsd:sequence>
408      <xsd:element name="allocID" type="tns:IDType"/>
409    </xsd:sequence>
410  </xsd:complexType>
411
412  <xsd:complexType name="releaseResponseType">
413    <xsd:annotation>
414      <xsd:documentation>
415        Indication that the access has been terminated.
416      </xsd:documentation>
417    </xsd:annotation>
418    <xsd:sequence>
419      <xsd:element name="allocID" type="tns:IDType"/>
420    </xsd:sequence>
421  </xsd:complexType>
422
423  <xsd:complexType name="createRequestType">
424    <xsd:annotation>
425      <xsd:documentation>
426        A request to embed a federated experiment across testbeds.  Non-
427        standard local names for testbeds are included in the
428        testbedmap, the user making the request, the experiment
429        description, master testbed, and a suggested experiment name are
430        included.  More than one name can be suggested, either as
431        synonyms (a fedid and a localname) or as choices (multiple
432        localnames).
433      </xsd:documentation>
434    </xsd:annotation>
435    <xsd:sequence>
436      <xsd:element name="testbedmap" type="tns:mapType" minOccurs="0"
437        maxOccurs="unbounded"/>
438      <xsd:element name="user" type="tns:userType" minOccurs="1"
439        maxOccurs="unbounded"/>
440      <xsd:element name="experimentdescription" 
441        type="tns:experimentDescriptionType"/>
442      <xsd:element name="master" type="xsd:string"/>
443      <xsd:element name="experimentID" type="tns:IDType" minOccurs="0" 
444        maxOccurs="1"/>
445    </xsd:sequence>
446  </xsd:complexType>
447
448  <xsd:complexType name="createResponseType">
449    <xsd:annotation>
450      <xsd:documentation>
451        The reply to a successful creation request.  Includes the
452        information about federants hosting sub-experiments for service
453        access as well as virtual topology and visualization
454        information.  All that information is relative to the requester.
455        ExperimentAccess includes credentials with which one can access
456        the experiment.  These may include a public key necessary to
457        prove possession of the credential and should be treated with
458        care.
459      </xsd:documentation>
460    </xsd:annotation>
461    <xsd:sequence>
462      <xsd:element name="federant" type="tns:federatedExperimentType" 
463        minOccurs="1" maxOccurs="unbounded"/>
464      <xsd:element name="vtopo" type="tns:vtopoType" minOccurs="0"
465        maxOccurs="1"/>
466      <xsd:element name="vis" type="tns:visType" minOccurs="0"
467        maxOccurs="1"/>
468      <xsd:element name="experimentID" type="tns:IDType" minOccurs="1"
469        maxOccurs="unbounded"/>
470      <xsd:element name="experimentAccess" type="tns:accessType" minOccurs="0"
471        maxOccurs="1"/>
472    </xsd:sequence>
473  </xsd:complexType>
474
475  <xsd:complexType name="vtopoRequestType">
476    <xsd:annotation>
477      <xsd:documentation>
478        Request for an existing experiment's virtual topology.
479        Different information may be returned based on the user's rights
480        to see the topology.
481      </xsd:documentation>
482    </xsd:annotation>
483    <xsd:sequence>
484      <xsd:element name="experiment" type="tns:IDType"/>
485    </xsd:sequence>
486  </xsd:complexType>
487
488  <xsd:complexType name="vtopoResponseType">
489    <xsd:annotation>
490      <xsd:documentation>
491        The response to a topology request.  Different information may
492        be returned based on the user's rights to see the topology.
493      </xsd:documentation>
494    </xsd:annotation>
495    <xsd:sequence>
496      <xsd:element name="experiment" type="tns:IDType"/>
497      <xsd:element name="vtopo" type="tns:vtopoType"/>
498    </xsd:sequence>
499  </xsd:complexType>
500
501
502  <xsd:complexType name="visRequestType">
503    <xsd:annotation>
504      <xsd:documentation>
505        Request for an existing experiment's visualization.  This is
506        largely a compatibility service.  Different information may be
507        returned based on the user's rights to see the topology.
508      </xsd:documentation>
509    </xsd:annotation>
510    <xsd:sequence>
511      <xsd:element name="experiment" type="tns:IDType"/>
512    </xsd:sequence>
513  </xsd:complexType>
514
515  <xsd:complexType name="visResponseType">
516    <xsd:annotation>
517      <xsd:documentation>
518        An existing experiment's visualization.  This is largely a
519        compatibility service.  Different information may be returned
520        based on the user's rights to see the topology.
521      </xsd:documentation>
522    </xsd:annotation>
523    <xsd:sequence>
524      <xsd:element name="experiment" type="tns:IDType"/>
525      <xsd:element name="vis" type="tns:visType"/>
526    </xsd:sequence>
527  </xsd:complexType>
528
529  <xsd:complexType name="infoRequestType">
530    <xsd:annotation>
531      <xsd:documentation>
532        A combined topology, visualalization, and federant request.
533        Different information may be returned based on the user's rights
534        to see the topology.  </xsd:documentation>
535    </xsd:annotation>
536    <xsd:sequence>
537      <xsd:element name="experiment" type="tns:IDType"/>
538    </xsd:sequence>
539  </xsd:complexType>
540
541  <xsd:complexType name="infoResponseType">
542    <xsd:annotation>
543      <xsd:documentation>
544        Information on an instantiated experiment.  A createResponse
545        without the secret information.  Different information may be
546        returned based on the user's rights to see the topology.
547      </xsd:documentation>
548    </xsd:annotation>
549    <xsd:sequence>
550      <xsd:element name="federant" type="tns:federatedExperimentType" 
551        minOccurs="1" maxOccurs="unbounded"/>
552      <xsd:element name="vtopo" type="tns:vtopoType" minOccurs="0"
553        maxOccurs="1"/>
554      <xsd:element name="vis" type="tns:visType" minOccurs="0"
555        maxOccurs="1"/>
556      <xsd:element name="experimentID" type="tns:IDType" minOccurs="1"
557        maxOccurs="unbounded"/>
558    </xsd:sequence>
559  </xsd:complexType>
560
561  <xsd:complexType name="terminateRequestType">
562    <xsd:annotation>
563      <xsd:documentation>
564        Request to terminate an experiment.
565      </xsd:documentation>
566    </xsd:annotation>
567    <xsd:sequence>
568      <xsd:element name="experiment" type="tns:IDType"/>
569    </xsd:sequence>
570  </xsd:complexType>
571
572  <xsd:complexType name="terminateResponseType">
573    <xsd:annotation>
574      <xsd:documentation>
575        Indication that the experiment has been terminated.
576      </xsd:documentation>
577    </xsd:annotation>
578    <xsd:sequence>
579      <xsd:element name="experiment" type="tns:IDType"/>
580    </xsd:sequence>
581  </xsd:complexType>
582
583  <xsd:complexType name="ns2SplitRequestType">
584    <xsd:annotation>
585      <xsd:documentation>
586        Request to run the CEDL splitter remotely.  This is primarily an
587        internal interface.
588      </xsd:documentation>
589    </xsd:annotation>
590    <xsd:sequence>
591      <xsd:element name="description" type="tns:experimentDescriptionType"/>
592      <xsd:element name="master" type="xsd:string"/>
593      <xsd:element name="include_fedkit" type="xsd:bool"/>
594    </xsd:sequence>
595  </xsd:complexType>
596
597  <xsd:complexType name="ns2SplitResponseType">
598    <xsd:annotation>
599      <xsd:documentation>
600        Remote splitter output.  Also an internal interface
601      </xsd:documentation>
602    </xsd:annotation>
603    <xsd:sequence>
604      <xsd:element name="output" type="xsd:base64Binary"/>
605    </xsd:sequence>
606  </xsd:complexType>
607
608
609  <xsd:complexType name="faultType">
610    <xsd:annotation>
611      <xsd:documentation>
612        Indication that a service has failed.  The code values are
613
614          1 access denied
615          2 proxy error
616          3 badly formed request
617          4 server configuration error
618          5 internal error
619          6 partial instantiation
620          7 federant error
621
622        Errstr contains the text above corresponding to the code.  Code
623        is always present.  Desc provides additional human-readable data
624        about the error.
625      </xsd:documentation>
626    </xsd:annotation>
627    <xsd:sequence>
628      <xsd:element name="code" type="xsd:int">
629        <xsd:restriction>
630          <xsd:enumeration value="1"/>  <!-- access denied -->
631          <xsd:enumeration value="2"/>  <!-- proxy error -->
632          <xsd:enumeration value="3"/>  <!-- badly formed request -->
633          <xsd:enumeration value="4"/>  <!-- server configuration error -->
634          <xsd:enumeration value="5"/>  <!-- internal error -->
635          <xsd:enumeration value="6"/>  <!-- partial instantiation -->
636          <xsd:enumeration value="7"/>  <!-- federant error -->
637        </xsd:restriction>
638      </xsd:element>
639      <xsd:element name="errstr" minOccurs="0" maxOccurs="1" type="xsd:string">
640      </xsd:element>
641      <xsd:element name="desc" type="xsd:string"/>
642    </xsd:sequence>
643  </xsd:complexType>
644</xsd:schema>
Note: See TracBrowser for help on using the repository browser.