/[volute]/trunk/projects/theory/snapdm/output/SNAP_SimulationDM_types.xsd
ViewVC logotype

Contents of /trunk/projects/theory/snapdm/output/SNAP_SimulationDM_types.xsd

Parent Directory Parent Directory | Revision Log Revision Log


Revision 67 - (show annotations)
Wed Feb 20 19:39:48 2008 UTC (12 years, 9 months ago) by richard.p.wagner
File size: 49096 byte(s)
Initial creation and import of the theory data model.
1 <?xml version="1.0" encoding="UTF-8"?>
2 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
3 targetNamespace="http://www.ivoa.net/xml/theory/SNAPSimulation_types/v0.1"
4 xmlns="http://www.ivoa.net/xml/theory/SNAPSimulation_types/v0.1"
5 xmlns:ont="http://www.ivoa.net/xml/theory/SNAPOntology/v0.1"
6 xmlns:res="http://www.ivoa.net/xml/VOResource/v1.0">
7 <!-- xmlns:ivo="http://www.ivoa.net/xml/VOIdentifier/v1.1"-->
8 <xsd:annotation>
9 <xsd:documentation>
10 This document presents a mapping of the SNAP data model
11 developed by the theory interest group. That model is a
12 proposal to the DM working group for modelling a subset of
13 astrophysical simulations. Those simulation
14
15
16 This mapping is performed as much as possible (i.e. modulo
17 mistakes, typos, out-of-synchs) according to the
18 prescription for mapping UML data model to XML Schema
19 presented in
20 http://www.ivoa.net/internal/IVOA/VOResource010RevNotes/ModelBasedSchema.ppt
21 and described in the SNAP Data model document in [LINK].
22
23 </xsd:documentation>
24 </xsd:annotation>
25 <xsd:annotation>
26 <xsd:documentation>
27 History of this document: 2007-09-09: First semi complete
28 mapping of the data model. 2007-09-12: After upload as
29 attachements to SNAP simulation data model page, updated the
30 schemaImports. Note that it would be good to have a proper
31 location for the IVOA Identifier schema.
32
33 </xsd:documentation>
34 </xsd:annotation>
35
36 <!--
37 <xsd:import
38 namespace="http://www.ivoa.net/xml/theory/SNAPOntology/v0.1"
39 schemaLocation="http://www.ivoa.net/internal/IVOA/IVOATheorySimulationDatamodel/SNAP_ontology.xsd" />
40 <xsd:import namespace="http://www.ivoa.net/xml/VOIdentifier/v1.1"
41 schemaLocation="http://www.ivoa.net/internal/IVOA/IVOATheorySimulationDatamodel/IVOAIdentifiers.xsd" />
42 <xsd:import namespace="http://www.ivoa.net/xml/VOResource/v1.0"
43 schemaLocation="http://www.ivoa.net/xml/VOResource/v1.0" />
44 -->
45
46 <xsd:import namespace="http://www.ivoa.net/xml/theory/SNAPOntology/v0.1" schemaLocation="./SNAP_ontology.xsd" />
47 <!-- <xsd:import namespace="http://www.ivoa.net/xml/VOIdentifier/v1.1" schemaLocation="./IVOAIdentifiers.xsd" /> -->
48 <xsd:import namespace="http://www.ivoa.net/xml/VOResource/v1.0" schemaLocation="./VOResource-v1.0.xsd" />
49 <!-- -->
50 <xsd:complexType name="SNAPResource" abstract="true">
51 <xsd:annotation>
52 <xsd:documentation>
53 This is a thin copy of the Registry Resource model's Resource
54 that borrowes some of its elements. It *is not* a Registry Resource though.
55 In particular we want to refine the content model here.
56 Using a restriction of the res:Resource leads to problems, as we'd like
57 to extend the Resource at the same time.
58 Hence we create a new type.
59 </xsd:documentation>
60 </xsd:annotation>
61 <xsd:sequence>
62 <xsd:element name="identifier" type="res:IdentifierURI"/>
63 <xsd:element name="publisherDID" type="res:IdentifierURI">
64 <xsd:annotation>
65 <xsd:documentation>
66 Publisher-designated ID. The ID by which
67 this SNAP resource is known to its
68 archive and the services applicable to
69 it. Will be used to add to the baseurl
70 of anyservice that is applicable to it.
71 </xsd:documentation>
72 </xsd:annotation>
73 </xsd:element>
74 <xsd:element name="title" type="xsd:token"/>
75 <xsd:element name="shortName" type="res:ShortName" minOccurs="0"/>
76 <xsd:element name="description" type="xsd:string" minOccurs="0"/>
77 <xsd:element name="referenceURL" type="xsd:anyURI" minOccurs="0"/>
78 <xsd:element name="publicationURI" type="xsd:anyURI" minOccurs="0">
79 <xsd:annotation>
80 <xsd:documentation>
81 A URI to a publication describing this
82 experiment. TBD higher maxOccurs
83 necessary?
84 </xsd:documentation>
85 </xsd:annotation>
86 </xsd:element>
87 <xsd:element name="curation" type="res:Curation"/>
88 </xsd:sequence>
89 <xsd:attribute name="created" type="xsd:dateTime" use="required">
90 <xsd:annotation>
91 <xsd:documentation>
92 The UTC date and time this resource metadata description
93 was created.
94 </xsd:documentation>
95 <xsd:documentation>
96 This timestamp must not be in the future. This time is
97 not required to be accurate; it should be at least
98 accurate to the day. Any insignificant time fields
99 should be set to zero.
100 </xsd:documentation>
101 </xsd:annotation>
102 </xsd:attribute>
103
104 <xsd:attribute name="updated" type="xsd:dateTime" use="required">
105 <xsd:annotation>
106 <xsd:documentation>
107 The UTC date this resource metadata description was last updated.
108 </xsd:documentation>
109 <xsd:documentation>
110 This timestamp must not be in the future. This time is
111 not required to be accurate; it should be at least
112 accurate to the day. Any insignificant time fields
113 should be set to zero.
114 </xsd:documentation>
115 </xsd:annotation>
116 </xsd:attribute>
117
118 <xsd:attribute name="status" use="required">
119 <xsd:annotation>
120 <xsd:documentation>
121 a tag indicating whether this resource is believed to be still
122 actively maintained.
123 </xsd:documentation>
124 </xsd:annotation>
125 <xsd:simpleType>
126 <xsd:restriction base="xsd:string">
127 <xsd:enumeration value="active">
128 <xsd:annotation>
129 <xsd:documentation>
130 resource is believed to be currently maintained, and its
131 description is up to date (default).
132 </xsd:documentation>
133 </xsd:annotation>
134 </xsd:enumeration>
135 <xsd:enumeration value="inactive">
136 <xsd:annotation>
137 <xsd:documentation>
138 resource is apparently not being maintained at the present.
139 </xsd:documentation>
140 </xsd:annotation>
141 </xsd:enumeration>
142 <xsd:enumeration value="deleted">
143 <xsd:annotation>
144 <xsd:documentation>
145 resource publisher has explicitly deleted the resource.
146 </xsd:documentation>
147 </xsd:annotation>
148 </xsd:enumeration>
149 </xsd:restriction>
150 </xsd:simpleType>
151 </xsd:attribute>
152 </xsd:complexType>
153 <!--
154 <xsd:complexType name="SNAPResource" abstract="true">
155 <xsd:annotation>
156 <xsd:documentation>
157 </xsd:documentation>
158 </xsd:annotation>
159 <xsd:complexContent>
160 <xsd:extension base="res:Resource">
161 <xsd:sequence>
162 <xsd:element name="publicationURI" type="xsd:anyURI"
163 minOccurs="0">
164 <xsd:annotation>
165 <xsd:documentation>
166 A URI to a publication describing this
167 experiment. TBD higher maxOccurs
168 necessary?
169 </xsd:documentation>
170 </xsd:annotation>
171 </xsd:element>
172 </xsd:sequence>
173 </xsd:extension>
174 </xsd:complexContent>
175 </xsd:complexType>
176 -->
177 <xsd:complexType name="SNAPProtocol" abstract="true">
178 <xsd:annotation>
179 <xsd:documentation>
180 A protocol for running SNAP experiments.
181 </xsd:documentation>
182 </xsd:annotation>
183 <xsd:complexContent>
184 <xsd:extension base="SNAPResource">
185 <xsd:annotation>
186 <xsd:documentation>
187 A SNAPProtocol is a Resource in the sence of the
188 Resource model.
189 </xsd:documentation>
190 </xsd:annotation>
191 <xsd:sequence>
192 <xsd:element name="code" type="xsd:anyURI"
193 minOccurs="0">
194 <xsd:annotation>
195 <xsd:documentation>
196 URL where the source code can be
197 retrieved.
198 </xsd:documentation>
199 </xsd:annotation>
200 </xsd:element>
201 <xsd:element name="version" type="xsd:string">
202 </xsd:element>
203 <xsd:element name="inputParameter" type="InputParameter" minOccurs="0" maxOccurs="unbounded"/>
204 <xsd:element name="parameterGroup" type="ParameterGroup" minOccurs="0" maxOccurs="unbounded"/>
205 </xsd:sequence>
206 </xsd:extension>
207 </xsd:complexContent>
208 </xsd:complexType>
209
210 <xsd:complexType name="GenericSNAPProtocol" >
211 <xsd:annotation>
212 <xsd:documentation>
213 A protocol for running SNAP experiments.
214 </xsd:documentation>
215 </xsd:annotation>
216 <xsd:complexContent>
217 <xsd:extension base="SNAPProtocol">
218 </xsd:extension>
219 </xsd:complexContent>
220 </xsd:complexType>
221
222 <!-- SNAP Experiments and sub types -->
223 <xsd:complexType name="SNAPExperiment" abstract="true">
224 <xsd:annotation>
225 <xsd:documentation>
226 The fundamental root entity of the SNAP model. The SNAP
227 model represents experiments that produce snapshots of
228 the universe. This is the base type of a set of more
229 specialised types such as Simulation, GroupFinder etc.
230 </xsd:documentation>
231 </xsd:annotation>
232 <xsd:complexContent>
233 <xsd:extension base="SNAPResource">
234 <xsd:annotation>
235 <xsd:documentation>
236 A SNAPProtocol is a Resource in the sence of the
237 Resource model.
238 </xsd:documentation>
239 </xsd:annotation>
240 <xsd:sequence>
241 <xsd:element name="protocol" type="res:IdentifierURI">
242 <xsd:annotation>
243 <xsd:documentation>
244 The protocol according to which this
245 experiment was executed.
246 </xsd:documentation>
247 </xsd:annotation>
248 </xsd:element>
249 <xsd:element name="snapshot" type="Snapshot"
250 minOccurs="0" maxOccurs="unbounded">
251 <xsd:annotation>
252 <xsd:documentation>
253 The collection of snapshots representing
254 the result of this experiment.
255 </xsd:documentation>
256 </xsd:annotation>
257 </xsd:element>
258 <!--
259 <xsd:element name="ownedBy" type="Party"
260 minOccurs="1" maxOccurs="unbounded">
261 <xsd:annotation>
262 <xsd:documentation>
263 Curation metadata indicating who owns
264 this SNAP experiment.
265 </xsd:documentation>
266 </xsd:annotation>
267 </xsd:element>
268 -->
269 <xsd:element name="targetObject"
270 type="TargetObjectType" minOccurs="0" maxOccurs="unbounded">
271 <xsd:annotation>
272 <xsd:documentation>
273 Indication of the type of object that is
274 being produced in this experiment.
275 </xsd:documentation>
276 </xsd:annotation>
277 </xsd:element>
278 <xsd:element name="targetProcess"
279 type="TargetProcess" minOccurs="0" maxOccurs="unbounded">
280 <xsd:annotation>
281 <xsd:documentation>
282 Indication of the type of process that represented
283 and/or studied in this experiment.
284 </xsd:documentation>
285 </xsd:annotation>
286 </xsd:element>
287 <xsd:element name="representationObjectType"
288 type="RepresentationObjectType" minOccurs="0"
289 maxOccurs="unbounded">
290 <xsd:annotation>
291 <xsd:documentation>
292 The type of object that is being used as
293 fundamental building block in the
294 experiment for representing the
295 simulated world. Examples are particles
296 for N-body simulations, mesh cells for
297 mesh simulations etc.
298 </xsd:documentation>
299 </xsd:annotation>
300 </xsd:element>
301 <xsd:element name="numericalAlgorithm" type="NumericalAlgorithm" minOccurs="0" maxOccurs="unbounded">
302 <xsd:annotation>
303 <xsd:documentation>
304 The numerical algorithms(s) used in the experiment.
305 </xsd:documentation>
306 </xsd:annotation>
307 </xsd:element>
308
309 <xsd:element name="parameter" type="ParameterSetting"
310 minOccurs="0" maxOccurs="unbounded">
311 <xsd:annotation>
312 <xsd:documentation>
313 Parameter definitions and values used in
314 the running of this experiment.
315 </xsd:documentation>
316 </xsd:annotation>
317 </xsd:element>
318 <xsd:element name="applicableWebservice" type="SNAPWebservice" minOccurs="0" maxOccurs="unbounded">
319 <xsd:annotation>
320 <xsd:documentation>
321 A web service that provides access to this SNAP experiment's results in some form.
322 </xsd:documentation>
323 </xsd:annotation>
324 </xsd:element>
325 </xsd:sequence>
326 </xsd:extension>
327 </xsd:complexContent>
328 </xsd:complexType>
329
330 <xsd:complexType name="Snapshot">
331 <xsd:annotation>
332 <xsd:documentation>
333 A representation of a subset of space-time. Currently
334 modelled to support constant-time, space-like slices
335 only.
336 </xsd:documentation>
337 </xsd:annotation>
338 <xsd:sequence>
339 <xsd:element name="publisherDID"
340 type="res:IdentifierURI">
341 <xsd:annotation>
342 <xsd:documentation>
343 An identifier specified by the publisher of this
344 experiment. This is the identifier by which IVOA
345 registered (SNAP)services will recognize this
346 particular snapshot. TBD We could have this as a
347 suffix to the SNAPExperiment's publisherDID.
348 </xsd:documentation>
349 </xsd:annotation>
350 </xsd:element>
351 <xsd:element name="spatialSizePhysical" type="Quantity">
352 <xsd:annotation>
353 <xsd:documentation>
354 The physical (i.e. not comoving for example)
355 size of the snapshot. TBD Need to come up with a
356 way to specify this for multi-dimensional
357 volumes. Use Quantity as a place holder datatype
358 for such instances.
359 </xsd:documentation>
360 </xsd:annotation>
361 </xsd:element>
362 <xsd:element name="simulationTimestamp" type="Quantity">
363 <xsd:annotation>
364 <xsd:documentation>
365 The simulation timestamp for this snapshot. Its
366 datatype (Quantity) is a place-holder for a
367 proper way of representing simulation
368 timestamps.
369 </xsd:documentation>
370 </xsd:annotation>
371 </xsd:element>
372 <xsd:element name="objectCollection" type="ObjectCollection" minOccurs="0" maxOccurs="unbounded"/>
373 </xsd:sequence>
374 </xsd:complexType>
375
376 <xsd:complexType name="ObjectType" abstract="true">
377 <xsd:annotation>
378 <xsd:documentation>
379 The base class representing objects with properties. For
380 a subject such as simulations where we can not
381 pre-define the objects that play a role we need a method
382 for publishers to define custom objects.
383 </xsd:documentation>
384 </xsd:annotation>
385 <xsd:sequence>
386 <xsd:element name="name" type="xsd:string">
387 <xsd:annotation>
388 <xsd:documentation>
389 The name by which this object type is referred
390 to in the containing experiment.
391 </xsd:documentation>
392 </xsd:annotation>
393 </xsd:element>
394 <xsd:element name="description" type="xsd:string">
395 <xsd:annotation>
396 <xsd:documentation>
397 A plain text short description of this object
398 type.
399 </xsd:documentation>
400 </xsd:annotation>
401 </xsd:element>
402 <xsd:element name="property" type="Property" minOccurs="0"
403 maxOccurs="unbounded">
404 <xsd:annotation>
405 <xsd:documentation>
406 Collection of properties. There must be at least
407 1, other wise the objects is irrelevant.
408 </xsd:documentation>
409 </xsd:annotation>
410 </xsd:element>
411 <xsd:element name="childObject" type="ChildObject" minOccurs="0" maxOccurs="unbounded">
412 <xsd:annotation>
413 <xsd:documentation>
414 Thtough a collection of ChildObject-s, a hierarchy of objects can be represented.
415 </xsd:documentation>
416 </xsd:annotation>
417 </xsd:element>
418 <xsd:element name="propertyGroup" type="PropertyGroup" minOccurs="0"
419 maxOccurs="unbounded">
420 <xsd:annotation>
421 <xsd:documentation>
422 Collection of property groups.
423 </xsd:documentation>
424 </xsd:annotation>
425 </xsd:element>
426 </xsd:sequence>
427 <xsd:attribute name="ID" type="xsd:ID">
428 <xsd:annotation>
429 <xsd:documentation>
430 Identifier to be used for references to this objects
431 within the document itself.
432 </xsd:documentation>
433 </xsd:annotation>
434 </xsd:attribute>
435 </xsd:complexType>
436
437 <xsd:complexType name="ChildObject">
438 <xsd:annotation>
439 <xsd:documentation>
440 Represents an association of one (parent) object type to another (child).
441 It allows one to build hierarchies of complexer object types.
442 Example: Galaxy built from disk, bulge and dark halo.
443 </xsd:documentation>
444 </xsd:annotation>
445 <xsd:sequence>
446 <xsd:element name="cardinality" type="Cardinality" default="1">
447 <xsd:annotation>
448 <xsd:documentation>
449 Indicates the multiplicity of the child object collection on the parent.
450 </xsd:documentation>
451 </xsd:annotation>
452 </xsd:element>
453 <xsd:element name="name" type="xsd:string">
454 <xsd:annotation>
455 <xsd:documentation>
456 The name of this child collection on the parent.
457 </xsd:documentation>
458 </xsd:annotation>
459 </xsd:element>
460 <xsd:element name="description" type="xsd:string">
461 <xsd:annotation>
462 <xsd:documentation>
463 Documents the relationship between parent and child object.
464 </xsd:documentation>
465 </xsd:annotation>
466 </xsd:element>
467 </xsd:sequence>
468 <xsd:attribute name="objectRef" type="xsd:IDREF" use="required">
469 <xsd:annotation>
470 <xsd:documentation>
471 Reference to the ObjectType that is the child of the parent ObjectType
472 containing this ChildObject. This child object type must be defined
473 in this same XML document, therefore we can use the ID/IDREF serialisation
474 of the corresponding UML reference.
475
476 </xsd:documentation>
477 </xsd:annotation>
478 </xsd:attribute>
479 </xsd:complexType>
480
481 <xsd:complexType name="TargetObjectType">
482 <xsd:complexContent>
483 <xsd:extension base="ObjectType">
484 <xsd:sequence>
485 <!-- -->
486 <!-- <xsd:element name="label" type="ont:AstroObject" minOccurs="0">
487 <xsd:annotation>
488 <xsd:documentation>
489 The label in the ontology of
490 AstroObjects [TBD add link]
491 </xsd:documentation>
492 </xsd:annotation>
493 </xsd:element>
494 -->
495 <xsd:element name="astroJournalSubject"
496 type="ont:AstroJournalKeyword" minOccurs="0">
497 <xsd:annotation>
498 <xsd:documentation>
499 The label in the "ontology" of subject
500 keywords in the major astronomical
501 journals.
502 </xsd:documentation>
503 </xsd:annotation>
504 </xsd:element>
505 <xsd:element name="multiplicity" type="xsd:integer"
506 minOccurs="0">
507 <xsd:annotation>
508 <xsd:documentation>
509 Indication, not necessarily exact, how
510 many objects of this object type are
511 around in the simulation.
512 </xsd:documentation>
513 </xsd:annotation>
514 </xsd:element>
515 <xsd:element name="identifiedObject"
516 type="xsd:string" minOccurs="0">
517 <xsd:annotation>
518 <xsd:documentation>
519 This element allows one to indicate that
520 a specific, identified, real-world
521 object is being represented by this
522 SNAPExperiment. For example, if an exact
523 simulation of a particular object, say
524 the Magellanic-Stream was performed,
525 this element allows one to say so.
526 </xsd:documentation>
527 </xsd:annotation>
528 </xsd:element>
529 </xsd:sequence>
530 </xsd:extension>
531 </xsd:complexContent>
532 </xsd:complexType>
533
534 <xsd:complexType name="RepresentationObjectType">
535 <xsd:complexContent>
536 <xsd:extension base="ObjectType">
537 <xsd:sequence>
538 <xsd:element name="label"
539 type="ont:SNAPRepresentationObject">
540 <xsd:annotation>
541 <xsd:documentation>
542 Label indicating what kind of
543 representation object this is by
544 referring to a standard list
545 ("ontology") of possible object types.
546 </xsd:documentation>
547 </xsd:annotation>
548 </xsd:element>
549 <!--
550 <xsd:element name="astroObject"
551 type="ont:AstroObject" minOccurs="0">
552 <xsd:annotation>
553 <xsd:documentation>
554 Some representation objects may have
555 astronomical meaning (as opposed to say
556 "mesh cell"). Examples are for example
557 if a globular cluster is modeled with an
558 n-body point particle representing a
559 complete star. In this case an extra
560 label can be provided indicating what
561 kind of physical object is represented.
562 It is especially relevant for various post-processing results
563 such as halo finders, or for example semi-analytical galaxy formation routines.
564 </xsd:documentation>
565 </xsd:annotation>
566 </xsd:element>
567 -->
568 <xsd:element name="astroObject"
569 type="ont:AstroJournalKeyword" minOccurs="0">
570 <xsd:annotation>
571 <xsd:documentation>
572 Some representation objects may have
573 astronomical meaning (as opposed to say
574 "mesh cell"). Examples are for example
575 if a globular cluster is modeled with an
576 n-body point particle representing a
577 complete star. In this case an extra
578 label can be provided indicating what
579 kind of physical object is represented.
580 It is especially relevant for various post-processing results
581 such as halo finders, or for example semi-analytical galaxy formation routines.
582 </xsd:documentation>
583 </xsd:annotation>
584 </xsd:element>
585 </xsd:sequence>
586 </xsd:extension>
587 </xsd:complexContent>
588 </xsd:complexType>
589
590 <xsd:complexType name="Property">
591 <xsd:annotation>
592 <xsd:documentation>
593 A property that an object can have.
594 </xsd:documentation>
595 </xsd:annotation>
596 <xsd:sequence>
597 <xsd:element name="name" type="xsd:string">
598 <xsd:annotation>
599 <xsd:documentation>
600 The name by which this property is known in the
601 experiment.
602 </xsd:documentation>
603 </xsd:annotation>
604 </xsd:element>
605 <xsd:element name="datatype" type="Datatype">
606 <xsd:annotation>
607 <xsd:documentation>
608 The datatype of this property in the experiment.
609 As the latter is software based, the datatype is
610 a software datatype. Distinctions are therefore
611 drawn between (real*4/4byte) floats and
612 (real*8/8 byte) doubles etc.
613 </xsd:documentation>
614 </xsd:annotation>
615 </xsd:element>
616 <xsd:element name="cardinality" type="Cardinality" >
617 <xsd:annotation>
618 <xsd:documentation>
619 The cardinality of this property in the
620 experiment.
621 </xsd:documentation>
622 </xsd:annotation>
623 </xsd:element>
624 <xsd:element name="ucd" type="ont:UCD" minOccurs="0">
625 <xsd:annotation>
626 <xsd:documentation>
627 A labvel assigned to this property to provide
628 its meaning in the IVOA standard UCD system.
629 </xsd:documentation>
630 </xsd:annotation>
631 </xsd:element>
632 <xsd:element name="description" type="xsd:string" minOccurs="0">
633 <xsd:annotation>
634 <xsd:documentation>
635 A short description of this property.
636 </xsd:documentation>
637 </xsd:annotation>
638 </xsd:element>
639 </xsd:sequence>
640 <xsd:attribute name="ID" type="xsd:ID"></xsd:attribute>
641 </xsd:complexType>
642
643 <xsd:complexType name="PropertyGroup">
644 <xsd:annotation>
645 <xsd:documentation>
646 Represents a grouping of properties on an object type.
647 Is mainly useful for presentation purposes.
648 Is not meant to represent an object hierarchy, for that purpose
649 one should use the ChildObject hierarchy.
650 </xsd:documentation>
651 </xsd:annotation>
652 <xsd:sequence>
653 <xsd:element name="name" type="xsd:string"/>
654 <xsd:element name="description" type="xsd:string" minOccurs="0"/>
655 <xsd:element name="member" type="PropertyGroupMember" maxOccurs="unbounded">
656 <xsd:annotation>
657 <xsd:documentation>
658 Reference to a Property that is contained in this group.
659 </xsd:documentation>
660 </xsd:annotation>
661 </xsd:element>
662 </xsd:sequence>
663 </xsd:complexType>
664
665 <xsd:complexType name="PropertyGroupMember">
666 <xsd:annotation>
667 <xsd:documentation>
668 Represents a member in a PropertyGroup.
669 </xsd:documentation>
670 </xsd:annotation>
671 <xsd:sequence>
672 <xsd:element name="rank" type="xsd:int" minOccurs="0">
673 <xsd:annotation>
674 <xsd:documentation>
675 Rank of the member property in the group.
676 </xsd:documentation>
677 </xsd:annotation>
678 </xsd:element>
679 </xsd:sequence>
680 <xsd:attribute name="propertyRef" type="xsd:IDREF" use="required">
681 <xsd:annotation>
682 <xsd:documentation>
683 As all the properties are supposed to be defined in the same document with the
684 group, we can use an ID/IDREF serialisation of the corresponding UML reference.
685 </xsd:documentation>
686 </xsd:annotation>
687 </xsd:attribute>
688 </xsd:complexType>
689
690 <xsd:complexType name="TargetProcess">
691 <xsd:annotation>
692 <xsd:documentation>
693 A process that plays a role in an experiment, either as an object of study in
694 itself, or because it is part of the simulated processes.
695 </xsd:documentation>
696 </xsd:annotation>
697 <xsd:sequence>
698 <xsd:element name="name" type="xsd:string"/>
699 <xsd:element name="description" type="xsd:string" minOccurs="0"/>
700 <!--
701 <xsd:element name="label" type="ont:PhysicalProcess" minOccurs="0"/>
702 -->
703 <xsd:element name="astroJournalSubject" type="ont:AstroJournalKeyword" minOccurs="0">
704 <xsd:annotation>
705 <xsd:documentation>
706 Maybe maxOccurs=unbounded?
707 </xsd:documentation>
708 </xsd:annotation>
709 </xsd:element>
710 </xsd:sequence>
711 </xsd:complexType>
712
713 <xsd:complexType name="ParameterSetting">
714 <xsd:annotation>
715 <xsd:documentation>A parameter setting. It should suffice to only give name
716 and value, where the name is contrained to be an input parameter
717 name on a protocol. Could use a referencing IVO-ID then ...
718 TBD!
719 </xsd:documentation>
720 </xsd:annotation>
721 <xsd:sequence>
722 <xsd:element name="name" type="xsd:string">
723 <xsd:annotation>
724 <xsd:documentation>
725 The name by which this parameter is used in the
726 experiment.
727 </xsd:documentation>
728 </xsd:annotation>
729 </xsd:element>
730 <xsd:element name="datatype" type="Datatype" minOccurs="0">
731 <xsd:annotation>
732 <xsd:documentation>
733 The datatype of this parameter. As this is a
734 software experiment, the datatypes are software
735 datatypes.
736 </xsd:documentation>
737 </xsd:annotation>
738 </xsd:element>
739 <xsd:element name="cardinality" type="Cardinality" minOccurs="0">
740 <xsd:annotation>
741 <xsd:documentation>
742 The cardinality of this parameter.
743 </xsd:documentation>
744 </xsd:annotation>
745 </xsd:element>
746 <xsd:element name="label" type="ont:UCD" minOccurs="0">
747 <xsd:annotation>
748 <xsd:documentation></xsd:documentation>
749 </xsd:annotation>
750 </xsd:element>
751 <xsd:element name="value" type="Value">
752 <xsd:annotation>
753 <xsd:documentation>
754 The value given to this parameter. TBD Could
755 specify its datatype as anyType, but prefer we
756 handle it ourself.
757 </xsd:documentation>
758 </xsd:annotation>
759 </xsd:element>
760 <xsd:element name="description" type="xsd:string" minOccurs="0">
761 <xsd:annotation>
762 <xsd:documentation>
763 A short description of this parameter.
764 </xsd:documentation>
765 </xsd:annotation>
766 </xsd:element>
767 </xsd:sequence>
768 </xsd:complexType>
769
770 <xsd:complexType name="InputParameter">
771 <xsd:annotation>
772 <xsd:documentation>A parameter definition of a protocol</xsd:documentation>
773 </xsd:annotation>
774 <xsd:sequence>
775 <xsd:element name="name" type="xsd:string">
776 <xsd:annotation>
777 <xsd:documentation>
778 The name by which this parameter is referred to in the protocol.
779 </xsd:documentation>
780 </xsd:annotation>
781 </xsd:element>
782 <xsd:element name="datatype" type="Datatype" minOccurs="0">
783 <xsd:annotation>
784 <xsd:documentation>
785 The datatype of this parameter. As this is a
786 software protocol, the datatypes are software
787 datatypes.
788 </xsd:documentation>
789 </xsd:annotation>
790 </xsd:element>
791 <xsd:element name="cardinality" type="Cardinality" minOccurs="0">
792 <xsd:annotation>
793 <xsd:documentation>
794 The cardinality of this parameter.
795 </xsd:documentation>
796 </xsd:annotation>
797 </xsd:element>
798 <xsd:element name="label" type="ont:UCD" minOccurs="0">
799 <xsd:annotation>
800 <xsd:documentation></xsd:documentation>
801 </xsd:annotation>
802 </xsd:element>
803 <xsd:element name="description" type="xsd:string" minOccurs="0">
804 <xsd:annotation>
805 <xsd:documentation>
806 A short description of this parameter.
807 </xsd:documentation>
808 </xsd:annotation>
809 </xsd:element>
810 </xsd:sequence>
811 </xsd:complexType>
812
813 <xsd:complexType name="ParameterGroup">
814 <xsd:annotation>
815 <xsd:documentation>
816 Represents a grouping of properties on an object type.
817 Is mainly useful for presentation purposes.
818 Is not meant to represent an object hierarchy, for that purpose
819 one should use the ChildObject hierarchy.
820 </xsd:documentation>
821 </xsd:annotation>
822 <xsd:sequence>
823 <xsd:element name="name" type="xsd:string"/>
824 <xsd:element name="description" type="xsd:string" minOccurs="0"/>
825 <xsd:element name="member" type="ParameterGroupMember" maxOccurs="unbounded">
826 <xsd:annotation>
827 <xsd:documentation>
828 Reference to an InputParameter that is contained in this group.
829 </xsd:documentation>
830 </xsd:annotation>
831 </xsd:element>
832 </xsd:sequence>
833 </xsd:complexType>
834
835 <xsd:complexType name="ParameterGroupMember">
836 <xsd:annotation>
837 <xsd:documentation>
838 Represents a member in a ParameterGroup.
839 </xsd:documentation>
840 </xsd:annotation>
841 <xsd:sequence>
842 <xsd:element name="rank" type="xsd:int" minOccurs="0"/>
843 </xsd:sequence>
844 <xsd:attribute name="parameterRef" type="xsd:IDREF" use="required">
845 <xsd:annotation>
846 <xsd:documentation>
847 As all these parameters are supposed to be defined in the same document with the
848 group, we can use an ID/IDREF serialisation of the corresponding UML reference.
849 </xsd:documentation>
850 </xsd:annotation>
851 </xsd:attribute>
852 </xsd:complexType>
853
854 <xsd:complexType name="ObjectCollection">
855 <xsd:annotation>
856 <xsd:documentation>
857 Represents a collection of fundamental data objects
858 representing the world. Though the data themselves are
859 not represented in the meta-data model, this type holds
860 on to metadata about the collections.
861 </xsd:documentation>
862 </xsd:annotation>
863 <xsd:sequence>
864 <xsd:element name="numberOfObjects" type="xsd:int">
865 <xsd:annotation>
866 <xsd:documentation>
867 The number of objects in this collection.
868 </xsd:documentation>
869 </xsd:annotation>
870 </xsd:element>
871 <xsd:element name="characterisation" type="Characterisation"
872 minOccurs="0" maxOccurs="unbounded">
873 <xsd:annotation>
874 <xsd:documentation>
875 Collection of objects characterising the objects
876 in this collection by giving summaries of the
877 various properties of the objects in the
878 collection.
879 </xsd:documentation>
880 </xsd:annotation>
881 </xsd:element>
882 </xsd:sequence>
883 <xsd:attribute name="objectType" type="xsd:IDREF">
884 <xsd:annotation>
885 <xsd:documentation>
886 The reference to the object type of the objects
887 stored in this collection. As this object type
888 will be defined in the same document an IDREF to
889 its ID can be used.
890 </xsd:documentation>
891 </xsd:annotation>
892 </xsd:attribute>
893 </xsd:complexType>
894
895 <xsd:complexType name="Characterisation">
896 <xsd:annotation>
897 <xsd:documentation>
898 Represents means of characterising collections of
899 objects, more in particular a particular property of the
900 objects in the collection. This can be done both by
901 specifying possible values this property can take (a
902 priori characterisation) and by characterising the
903 values actually taken up by the properties in the
904 collection (a posteriori characterisation). [TBD This is
905 applicable to numerical properties (having Quantity-s as
906 value) only.]
907 </xsd:documentation>
908 </xsd:annotation>
909 <xsd:sequence>
910 <xsd:element name="lowerBound" type="Quantity"
911 minOccurs="0">
912 <xsd:annotation>
913 <xsd:documentation>
914 The lowest value the characterised property can
915 possibly take in the containing collection. This
916 is an "a priori" characterisation.
917 </xsd:documentation>
918 </xsd:annotation>
919 </xsd:element>
920 <xsd:element name="upperBound" type="Quantity"
921 minOccurs="0">
922 <xsd:annotation>
923 <xsd:documentation>
924 The highest value the characterised property can
925 possibly take in the containing collection. This
926 is an "a priori" characterisation.
927 </xsd:documentation>
928 </xsd:annotation>
929 </xsd:element>
930 <xsd:element name="nominalValue" type="Quantity"
931 minOccurs="0">
932 <xsd:annotation>
933 <xsd:documentation>
934 The typical value the characterised property
935 takes in the containing collection. Can be
936 thought of as the location element in the
937 Characterisaiton data model. This is an "a
938 priori" characterisation.
939 </xsd:documentation>
940 </xsd:annotation>
941 </xsd:element>
942 <xsd:element name="min" type="Quantity" minOccurs="0">
943 <xsd:annotation>
944 <xsd:documentation>
945 The lowest value of the characterised property
946 actually taken by an object in the containing
947 collection. This is an "a posteriori"
948 characterisation.
949 </xsd:documentation>
950 </xsd:annotation>
951 </xsd:element>
952 <xsd:element name="max" type="Quantity" minOccurs="0">
953 <xsd:annotation>
954 <xsd:documentation>
955 The largest value of the characterised property
956 actually taken by an object in the containing
957 collection. This is an "a posteriori"
958 characterisation.
959 </xsd:documentation>
960 </xsd:annotation>
961 </xsd:element>
962 <xsd:element name="mean" type="Quantity" minOccurs="0">
963 <xsd:annotation>
964 <xsd:documentation>
965 The mean value of the characterised property
966 over the containing collection. This is an "a
967 posteriori" characterisation.
968 </xsd:documentation>
969 </xsd:annotation>
970 </xsd:element>
971 <xsd:element name="standardDeviation" type="Quantity"
972 minOccurs="0">
973 <xsd:annotation>
974 <xsd:documentation>
975 The standard deviation of the characterised
976 property over the containing collection. This is
977 an "a posteriori" characterisation.
978 </xsd:documentation>
979 </xsd:annotation>
980 </xsd:element>
981 </xsd:sequence>
982 <xsd:attribute name="property" type="xsd:IDREF">
983 <xsd:annotation>
984 <xsd:documentation>
985 Reference to the actual property that is being
986 characterised by this object. Reference is to
987 the ID attribute of the Propertry type. We can
988 use an ID/IDREF implementation as the referenced
989 element will have to be in the same document as
990 the referring element, for they both belong to
991 the same root element, which is a
992 SNAPExperiment.
993 </xsd:documentation>
994 </xsd:annotation>
995 </xsd:attribute>
996 </xsd:complexType>
997
998
999 <xsd:complexType name="SNAPWebservice">
1000 <xsd:annotation>
1001 <xsd:documentation>
1002 A webservice that can be used to do something with the
1003 results of this SNAP experiment. Examples of this are
1004 some standard services like cut-out, projection etc. An
1005 API can be defined for all of these that can be derived
1006 from the base service which accepts the publisherDID-s
1007 for the SNAPExperiment and a Snapshot.
1008 </xsd:documentation>
1009 </xsd:annotation>
1010 <xsd:sequence>
1011 <xsd:element name="ivoID" type="res:IdentifierURI" minOccurs="0">
1012 <xsd:annotation>
1013 <xsd:documentation>
1014 The IVO compatible (see ...) identifier with which the service is registered.
1015 May be null in case the servie is not registered.
1016 </xsd:documentation>
1017 </xsd:annotation>
1018 </xsd:element>
1019 <xsd:element name="baseURL" type="xsd:anyURI">
1020 <xsd:annotation>
1021 <xsd:documentation>
1022 The base URL from which the complete HTTP GET
1023 can be built for standard SNAP services, or
1024 which leads to a web page from which the web
1025 application can be started for custom services.
1026 </xsd:documentation>
1027 </xsd:annotation>
1028 </xsd:element>
1029 <xsd:element name="documentationURL" type="xsd:anyURI">
1030 <xsd:annotation>
1031 <xsd:documentation>
1032 The base URL where one can reach information
1033 about the web service.
1034 </xsd:documentation>
1035 </xsd:annotation>
1036 </xsd:element>
1037 <xsd:element name="description" type="xsd:string">
1038 <xsd:annotation>
1039 <xsd:documentation>
1040 A short description of the service.
1041 </xsd:documentation>
1042 </xsd:annotation>
1043 </xsd:element>
1044 <xsd:element name="type" type="SNAPServiceType">
1045 <xsd:annotation>
1046 <xsd:documentation>
1047 Label indicating whether this is a standard type
1048 SNAP service, or a custom one.
1049 </xsd:documentation>
1050 </xsd:annotation>
1051 </xsd:element>
1052 </xsd:sequence>
1053 </xsd:complexType>
1054
1055 <!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
1056 <!-- SNAP experiments and protocols -->
1057 <!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
1058 <xsd:complexType name="SNAPSimulator">
1059 <xsd:annotation>
1060 <xsd:documentation>
1061 A simulator protocol producing snapshots of the
1062 universe.
1063 </xsd:documentation>
1064 </xsd:annotation>
1065 <xsd:complexContent>
1066 <xsd:extension base="SNAPProtocol">
1067 <xsd:sequence>
1068 <xsd:element name="physics" type="PhysicsEquation" minOccurs="0" maxOccurs="unbounded"/>
1069 </xsd:sequence>
1070 </xsd:extension>
1071 </xsd:complexContent>
1072 </xsd:complexType>
1073
1074 <xsd:complexType name="GenericSNAPExperiment">
1075 <xsd:annotation>
1076 <xsd:documentation>
1077 A protocol for running SNAP experiments.
1078 </xsd:documentation>
1079 </xsd:annotation>
1080 <xsd:complexContent>
1081 <xsd:extension base="SNAPExperiment">
1082 </xsd:extension>
1083 </xsd:complexContent>
1084 </xsd:complexType>
1085
1086 <xsd:complexType name="SNAPSimulation">
1087 <xsd:annotation>
1088 <xsd:documentation>
1089 Represents an original SNAP simulation. Corresponds to
1090 the "Level-0" data products. Important for its
1091 description are the physcial processes that are being
1092 modeled and the numerical algorithms
1093 </xsd:documentation>
1094 </xsd:annotation>
1095 <xsd:complexContent>
1096 <xsd:extension base="SNAPExperiment">
1097 <xsd:sequence>
1098 <xsd:element name="physics" type="PhysicsEquation"
1099 minOccurs="0" maxOccurs="unbounded">
1100 <xsd:annotation>
1101 <xsd:documentation>
1102 The physical processes used in this
1103 simulation.
1104 </xsd:documentation>
1105 </xsd:annotation>
1106 </xsd:element>
1107 </xsd:sequence>
1108 </xsd:extension>
1109 </xsd:complexContent>
1110 </xsd:complexType>
1111
1112 <xsd:complexType name="PhysicsEquation">
1113 <xsd:annotation>
1114 <xsd:documentation>
1115 Represents meta-data regarding physical processes used
1116 in simulators. An instance of this object corresponds to an exact evolution
1117 equation.
1118 </xsd:documentation>
1119 </xsd:annotation>
1120 <xsd:sequence>
1121 <xsd:element name="name" type="xsd:string">
1122 <xsd:annotation>
1123 <xsd:documentation>
1124 Name by which the publisher refers to this algoruthm in the experiment.
1125 </xsd:documentation>
1126 </xsd:annotation>
1127 </xsd:element>
1128 <xsd:element name="description" type="xsd:string">
1129 <xsd:annotation>
1130 <xsd:documentation>
1131 Short description of the algorithm.
1132 </xsd:documentation>
1133 </xsd:annotation>
1134 </xsd:element>
1135 <xsd:element name="texForm" type="xsd:string" minOccurs="0">
1136 <xsd:annotation>
1137 <xsd:documentation>
1138 The (evolution) equation in TeX form.
1139 </xsd:documentation>
1140 </xsd:annotation>
1141 </xsd:element>
1142 </xsd:sequence>
1143 </xsd:complexType>
1144
1145 <xsd:complexType name="NumericalAlgorithm">
1146 <xsd:annotation>
1147 <xsd:documentation>
1148 Represents a numerical algorithm for modelling physical
1149 processes in a simulation.
1150 </xsd:documentation>
1151 </xsd:annotation>
1152 <xsd:sequence>
1153 <xsd:element name="name" type="xsd:string">
1154 <xsd:annotation>
1155 <xsd:documentation>
1156 Name by which the publisher refers to this algoruthm in the experiment.
1157 </xsd:documentation>
1158 </xsd:annotation>
1159 </xsd:element>
1160 <xsd:element name="description" type="xsd:string" minOccurs="0">
1161 <xsd:annotation>
1162 <xsd:documentation>
1163 Short description of the algorithm.
1164 </xsd:documentation>
1165 </xsd:annotation>
1166 </xsd:element>
1167 <xsd:element name="documentationURL" type="xsd:anyURI" minOccurs="0">
1168 <xsd:annotation>
1169 <xsd:documentation>
1170 URL to a document describing this algorithm in more detail.
1171 </xsd:documentation>
1172 </xsd:annotation>
1173 </xsd:element>
1174 <xsd:element name="label" type="ont:Numerics" minOccurs="0">
1175 <xsd:annotation>
1176 <xsd:documentation>
1177 An "ontological" label, indicating the type of numerical algorithm that is used.
1178 </xsd:documentation>
1179 </xsd:annotation>
1180 </xsd:element>
1181 </xsd:sequence>
1182 </xsd:complexType>
1183
1184 <xsd:complexType name="AnnotatedSNAPResource">
1185 <xsd:sequence>
1186 <xsd:element name="resourceIVOID" type="res:IdentifierURI"/>
1187 <xsd:element name="annotation" type="xsd:string" minOccurs="0"/>
1188 </xsd:sequence>
1189 </xsd:complexType>
1190 <xsd:complexType name="SNAPProject">
1191 <xsd:annotation>
1192 <xsd:documentation>
1193 An aggregation of annotated SNAPResource-s that together
1194 form a project.
1195 </xsd:documentation>
1196 </xsd:annotation>
1197 <xsd:complexContent>
1198 <xsd:extension base="res:Resource">
1199 <xsd:sequence>
1200 <xsd:element name="snapResource" type="AnnotatedSNAPResource" maxOccurs="unbounded"/>
1201 </xsd:sequence>
1202 </xsd:extension>
1203 </xsd:complexContent>
1204 </xsd:complexType>
1205
1206
1207 <!-- classes dealing with parties (organisations, persons, collaborations, ...) -->
1208 <xsd:complexType name="Party" abstract="true">
1209 <xsd:annotation>
1210 <xsd:documentation>
1211 Represents a party that can play a role in the context
1212 of this model. A party can be a person or an
1213 organisation.
1214 </xsd:documentation>
1215 <xsd:documentation>
1216 Currently this type is not used, all this type of information is represented
1217 by the Curation on SNAPResource.
1218 </xsd:documentation>
1219 </xsd:annotation>
1220 <xsd:sequence>
1221
1222 </xsd:sequence>
1223 </xsd:complexType>
1224
1225 <!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
1226 <!-- value types -->
1227 <!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
1228
1229 <xsd:complexType name="Value" >
1230 <xsd:annotation>
1231 <xsd:documentation>
1232 Represents a value-type. properties and parameters have
1233 such values.
1234 </xsd:documentation>
1235 </xsd:annotation>
1236 <xsd:simpleContent>
1237 <xsd:extension base="xsd:string"/>
1238 </xsd:simpleContent>
1239 </xsd:complexType>
1240
1241 <xsd:complexType name="Quantity">
1242 <xsd:annotation>
1243 <xsd:documentation>
1244 Represents a numerical value type.
1245 </xsd:documentation>
1246 </xsd:annotation>
1247 <xsd:simpleContent>
1248 <xsd:extension base="Value">
1249 <xsd:attribute name="unit" type="xsd:string"
1250 use="optional">
1251 <xsd:annotation>
1252 <xsd:documentation>
1253 The unit (if applicable) of this
1254 quantity.
1255 </xsd:documentation>
1256 </xsd:annotation>
1257 </xsd:attribute>
1258 </xsd:extension>
1259 </xsd:simpleContent>
1260 </xsd:complexType>
1261
1262 <xsd:simpleType name="Datatype">
1263 <xsd:annotation>
1264 <xsd:documentation>
1265 List of primitive datatypes that a parameter can have.
1266 These are software datatypes (i.e. float and double iso
1267 only real).
1268 </xsd:documentation>
1269 </xsd:annotation>
1270 <xsd:restriction base="xsd:string">
1271 <xsd:enumeration value="boolean" />
1272 <xsd:enumeration value="complex" />
1273 <xsd:enumeration value="datetime" />
1274 <xsd:enumeration value="double" />
1275 <xsd:enumeration value="float" />
1276 <xsd:enumeration value="int" />
1277 <xsd:enumeration value="long" />
1278 <xsd:enumeration value="rational" />
1279 <xsd:enumeration value="short" />
1280 <xsd:enumeration value="string" />
1281 </xsd:restriction>
1282 </xsd:simpleType>
1283
1284 <xsd:simpleType name="Cardinality">
1285 <xsd:annotation>
1286 <xsd:documentation>
1287 List of valid values for indicating the cardinality of a
1288 property. Values have usual meaning.
1289 </xsd:documentation>
1290 </xsd:annotation>
1291 <xsd:restriction base="xsd:string">
1292 <xsd:enumeration value="0..1" />
1293 <xsd:enumeration value="1" />
1294 <xsd:enumeration value="0..*" />
1295 <xsd:enumeration value="1..*" />
1296 </xsd:restriction>
1297 </xsd:simpleType>
1298
1299 <xsd:simpleType name="SNAPServiceType">
1300 <xsd:annotation>
1301 <xsd:documentation>
1302 Defines a number of standard services that can deal with
1303 SNAP results.
1304 </xsd:documentation>
1305 </xsd:annotation>
1306 <xsd:restriction base="xsd:string">
1307 <xsd:enumeration value="download">
1308 <xsd:annotation>
1309 <xsd:documentation>
1310 A simple download service. To be defined what
1311 parameters belong to this.
1312 </xsd:documentation>
1313 </xsd:annotation>
1314 </xsd:enumeration>
1315 <xsd:enumeration value="cutout">
1316 <xsd:annotation>
1317 <xsd:documentation>
1318 A service thta produces a spatial cut-out of a
1319 snapshot. This can be of a nbumber of shapes:
1320 sphere, box, maybe more general. To be defined
1321 what parameters belong to this.
1322 </xsd:documentation>
1323 </xsd:annotation>
1324 </xsd:enumeration>
1325 <xsd:enumeration value="gridding">
1326 <xsd:annotation>
1327 <xsd:documentation>
1328 Create a mesh-like representation of an existing
1329 snapshot. The latter may consist of particles,
1330 but the service can also do a regridding of an
1331 existing mesh. To be defined what parameters
1332 belong to this.
1333 </xsd:documentation>
1334 </xsd:annotation>
1335 </xsd:enumeration>
1336 <xsd:enumeration value="clusterfinder">
1337 <xsd:annotation>
1338 <xsd:documentation>
1339 Identify clusters in a snapshot. Can be done
1340 both for mesh-like and for n-body simulations.
1341 To be defined what parameters belong to this.
1342 </xsd:documentation>
1343 </xsd:annotation>
1344 </xsd:enumeration>
1345 <xsd:enumeration value="visualisation">
1346 <xsd:annotation>
1347 <xsd:documentation>
1348 A service to create a visualisation, i.e. 2D
1349 image of a snapshot. To be defined what
1350 parameters belong to this.
1351 </xsd:documentation>
1352 </xsd:annotation>
1353 </xsd:enumeration>
1354 <xsd:enumeration value="custom">
1355 <xsd:annotation>
1356 <xsd:documentation>
1357 A custom service.
1358 </xsd:documentation>
1359 </xsd:annotation>
1360 </xsd:enumeration>
1361 </xsd:restriction>
1362 </xsd:simpleType>
1363
1364 </xsd:schema>

msdemlei@ari.uni-heidelberg.de
ViewVC Help
Powered by ViewVC 1.1.26