ViewVC logotype

Contents of /trunk/projects/theory/snapdm/xsd/simdb/experiment.xsd

Parent Directory Parent Directory | Revision Log Revision Log

Revision 500 - (show annotations)
Fri May 16 04:44:38 2008 UTC (12 years, 6 months ago) by gerard.lemson
File size: 27136 byte(s)
latest generated versions of the schemas
1 <?xml version="1.0" encoding="UTF-8"?>
2 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
3 xmlns="http://www.ivoa.net/xml/SNAP/v0.1/simdb/experiment"
4 xmlns:base="http://www.ivoa.net/xml/dm/base/v0.1"
5 xmlns:p5="http://www.ivoa.net/xml/SNAP/v0.1/simdb"
6 xmlns:p2="http://www.ivoa.net/xml/SNAP/v0.1/simdb/protocol"
7 xmlns:p6="http://www.ivoa.net/xml/SNAP/v0.1/simdb/object"
8 targetNamespace="http://www.ivoa.net/xml/SNAP/v0.1/simdb/experiment">
9 <xsd:annotation>
10 <xsd:documentation>Generated from UML-&gt;XMI-&gt;intermediate-&gt;XSD.</xsd:documentation>
11 </xsd:annotation>
12 <xsd:import namespace="http://www.ivoa.net/xml/SNAP/v0.1/simdb"
13 schemaLocation="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/xsd/simdb.xsd"/>
14 <xsd:import namespace="http://www.ivoa.net/xml/SNAP/v0.1/simdb/protocol"
15 schemaLocation="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/xsd/simdb/protocol.xsd"/>
16 <xsd:import namespace="http://www.ivoa.net/xml/SNAP/v0.1/simdb/object"
17 schemaLocation="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/xsd/simdb/object.xsd"/>
18 <xsd:import namespace="http://www.ivoa.net/xml/dm/base/v0.1"
19 schemaLocation="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/xsd/base.xsd"/>
20 <xsd:complexType name="Simulation">
21 <xsd:annotation>
22 <xsd:documentation>This class represents the basic simulations from which eventually all SNAP data products are derived. It extends SNAPExperiment by adding descriptions of the physical processes that were simulated</xsd:documentation>
23 <xsd:appinfo>xmiid=_12_1_8e0028f_1173260098343_801274_269</xsd:appinfo>
24 </xsd:annotation>
25 <xsd:complexContent>
26 <xsd:extension base="Experiment">
27 <xsd:sequence>
28 <xsd:element name="executionTime" type="xsd:dateTime" minOccurs="0"/>
29 <xsd:element name="appliedPhysics" type="AppliedPhysics" maxOccurs="unbounded"/>
30 </xsd:sequence>
31 </xsd:extension>
32 </xsd:complexContent>
33 </xsd:complexType>
35 <xsd:complexType name="Characterisation">
36 <xsd:annotation>
37 <xsd:documentation>This class represents the characterisation of a property of an object in a given object collection. It represents both a priori and a posteriori characterisations. With a priori characterisation we indicate possible and/or nominal [?] values the variable may take, it defines the possible range of values of the property. In contrast, an a posteriori characterisation of a property in an object collection provides summarising, likely statistical, information on the values that were actually taken up (observed, simulated) by the objects in the collection.
38 The a priori characterisation is most similar, in fact a generalisation of the Characterisation model of the IVOA Data Model working group [3].
40 In the current model we stick to simple (numerical) quantities for characterising a collection of objects. For example the equivalent value of a support from [3] is absent, as it is not terribly useful for discovery and querying, even more so of course for concepts equivalent to sensitivity.
41 [TBD How relevant is it for simulations? Examples if we require it for the actual meta data specification, for example for usages beyond query and discovery.]
43 TODO currently the characterisation is restricted to numericalobservables, generalisation comes later.</xsd:documentation>
44 <xsd:appinfo>xmiid=_12_1_8e0028f_1173261097203_650221_811</xsd:appinfo>
45 </xsd:annotation>
46 <xsd:sequence>
47 <xsd:element name="value" type="p5:Quantity" minOccurs="0"/>
48 <xsd:element name="type" type="CharacterisationType" minOccurs="0"/>
49 <xsd:element name="aPriori" type="xsd:boolean" minOccurs="0"/>
50 <xsd:element name="axis" type="base:Reference">
51 <xsd:annotation>
52 <xsd:appinfo>xmiidref=_12_1_8e0028f_1173260158109_378937_365</xsd:appinfo>
53 </xsd:annotation>
54 </xsd:element>
55 </xsd:sequence>
56 </xsd:complexType>
58 <xsd:complexType name="ObjectCollection">
59 <xsd:annotation>
60 <xsd:documentation>We assume that a single SNAPResult can consist of collections of objects (ObjectType). For example some simulations can produce both dark matter, stellar and gas particles, together building up the whole target objects. Each of these sets of particles is in general separately characterised and the ObjectCollection class provides an anchor for this. They may also be separately stored</xsd:documentation>
61 <xsd:appinfo>xmiid=_12_1_8e0028f_1173261164953_285409_884</xsd:appinfo>
62 </xsd:annotation>
63 <xsd:sequence>
64 <xsd:element name="numberOfObjects" type="xsd:int" minOccurs="0"/>
65 <xsd:element name="characterisation" type="Characterisation" minOccurs="0"
66 maxOccurs="unbounded"/>
67 <xsd:element name="objectType" type="base:Reference">
68 <xsd:annotation>
69 <xsd:appinfo>xmiidref=_12_1_1_8e0028f_1178640418734_24506_1505</xsd:appinfo>
70 </xsd:annotation>
71 </xsd:element>
72 </xsd:sequence>
73 </xsd:complexType>
75 <xsd:complexType name="Experiment" abstract="true">
76 <xsd:annotation>
77 <xsd:documentation>Base class of objects that can be described by, queried by, discovered by the SNAP protocol.
78 It included simulations of spatial systems and their "level-1" derived data products.
80 The base class for those kinds of experiments that can produce representations of a part of the universe.</xsd:documentation>
81 <xsd:appinfo>xmiid=_12_1_8e0028f_1175592662265_484162_263</xsd:appinfo>
82 </xsd:annotation>
83 <xsd:complexContent>
84 <xsd:extension base="p5:Resource">
85 <xsd:sequence>
86 <xsd:element name="targetObject" type="TargetObjectType" minOccurs="0" maxOccurs="unbounded"/>
87 <xsd:element name="snapshot" type="Snapshot" minOccurs="0" maxOccurs="unbounded"/>
88 <xsd:element name="service" type="WebService" minOccurs="0" maxOccurs="unbounded"/>
89 <xsd:element name="algorithm" type="Algorithm" minOccurs="0" maxOccurs="unbounded"/>
90 <xsd:element name="targetProcess" type="TargetProcess" minOccurs="0" maxOccurs="unbounded"/>
91 <xsd:element name="parameter" type="ParameterSetting" minOccurs="0" maxOccurs="unbounded"/>
92 <xsd:element name="inputData" type="InputDataset" minOccurs="0" maxOccurs="unbounded"/>
93 <xsd:element name="representationObject" type="ExperimentRepresentationObject"
94 maxOccurs="unbounded"/>
95 <xsd:element name="protocol" type="base:Reference">
96 <xsd:annotation>
97 <xsd:appinfo>xmiidref=_12_1_8e0028f_1175789188406_755001_115</xsd:appinfo>
98 </xsd:annotation>
99 </xsd:element>
100 </xsd:sequence>
101 </xsd:extension>
102 </xsd:complexContent>
103 </xsd:complexType>
105 <xsd:complexType name="Snapshot">
106 <xsd:annotation>
107 <xsd:documentation>This class represents a part of the universe at a particular point in time, or possibly a more general sub-volume of space-time, for example a light-cone. We realise this does not represent all possible outputs of simulations. For example some simulations of dense (collisional) stellar systems produce orbits of the individual particles, at individual output times . In general though those results can be used to produce snapshots as well (Peter Teuben, private communication). Hence for the current version of the model we propose the use of Snapshot results of simulations and other SNAPResults as well, the only exception being light-cones through cosmological simulations</xsd:documentation>
108 <xsd:appinfo>xmiid=_12_1_8e0028f_1175592736546_383422_309</xsd:appinfo>
109 </xsd:annotation>
110 <xsd:sequence>
111 <xsd:element name="publisherDID" type="xsd:string"/>
112 <xsd:element name="time" type="p5:Quantity"/>
113 <xsd:element name="spatialSizePhysical" type="p5:Quantity" minOccurs="0"/>
114 <xsd:element name="objectCollection" type="ObjectCollection" maxOccurs="unbounded"/>
115 </xsd:sequence>
116 </xsd:complexType>
118 <xsd:complexType name="ClusterDetection">
119 <xsd:annotation>
120 <xsd:documentation>Represents the creation of a Snapshot consisting of a catalogues of groups of objects extracted form the input Snapshot. Those can be particles, but also grid cells</xsd:documentation>
121 <xsd:appinfo>xmiid=_12_1_8e0028f_1175595880687_132606_426</xsd:appinfo>
122 </xsd:annotation>
123 <xsd:complexContent>
124 <xsd:extension base="PostProcessing"/>
125 </xsd:complexContent>
126 </xsd:complexType>
128 <xsd:complexType name="Algorithm">
129 <xsd:annotation>
130 <xsd:documentation>Represents the numerical algorithm representing a physical process in the simulator code</xsd:documentation>
131 <xsd:appinfo>xmiid=_12_1_8e0028f_1175674070859_180053_115</xsd:appinfo>
132 </xsd:annotation>
133 <xsd:sequence>
134 <xsd:element name="name" type="xsd:string"/>
135 <xsd:element name="description" type="xsd:string" minOccurs="0"/>
136 <xsd:element name="label" type="xsd:string" minOccurs="0"/>
137 </xsd:sequence>
138 </xsd:complexType>
140 <xsd:complexType name="Visualisation">
141 <xsd:annotation>
142 <xsd:documentation>Represents the creation of a 2-dimensional image-like representation of the universe from a three dimensional one. This can be done for example by projection, slicing. Any (set of) variables can be used. Important is (?) that the spatial dimensions are properly transferred to the new data product.
143 Note that this is not the same as applying a virtual telescope where some model is made of the photon streams/fluxes originating from the simulated object. It is merely a small representation of the underlying observables. In that sense the product is a representation of a part of the universe
144 </xsd:documentation>
145 <xsd:appinfo>xmiid=_12_1_8e0028f_1175774347859_5102_267</xsd:appinfo>
146 </xsd:annotation>
147 <xsd:complexContent>
148 <xsd:extension base="PostProcessing"/>
149 </xsd:complexContent>
150 </xsd:complexType>
152 <xsd:complexType name="PostProcessing" abstract="true">
153 <xsd:annotation>
154 <xsd:documentation>Represents a SNAPExperiment that acts on a pre-existing Snapshot to produce another Snapshot. In standard terminology this produces Level 1 data products (this is true whether the original Snapshot was a Level 0 products or already a Level 1 product)</xsd:documentation>
155 <xsd:appinfo>xmiid=_12_1_8e0028f_1175776635250_448091_386</xsd:appinfo>
156 </xsd:annotation>
157 <xsd:complexContent>
158 <xsd:extension base="Experiment">
159 <xsd:sequence>
160 <xsd:element name="primaryExperiment" type="base:Reference" minOccurs="0">
161 <xsd:annotation>
162 <xsd:appinfo>xmiidref=_12_1_8e0028f_1175592662265_484162_263</xsd:appinfo>
163 </xsd:annotation>
164 </xsd:element>
165 </xsd:sequence>
166 </xsd:extension>
167 </xsd:complexContent>
168 </xsd:complexType>
170 <xsd:complexType name="InputDataset">
171 <xsd:annotation>
172 <xsd:documentation>Associates a snapshot to a SNAPPostprocessing experiment. The associated snapshot is assumed to have been the target of the post-processing</xsd:documentation>
173 <xsd:appinfo>xmiid=_12_1_8e0028f_1175776701562_299478_435</xsd:appinfo>
174 </xsd:annotation>
175 <xsd:sequence>
176 <xsd:element name="snapshot" type="base:Reference">
177 <xsd:annotation>
178 <xsd:appinfo>xmiidref=_12_1_8e0028f_1175592736546_383422_309</xsd:appinfo>
179 </xsd:annotation>
180 </xsd:element>
181 </xsd:sequence>
182 </xsd:complexType>
184 <xsd:complexType name="WebService">
185 <xsd:annotation>
186 <xsd:documentation>This class represents a web service that can be used to access the results of an Experiment.
187 The web service is represented by a base URL and a service type. The type may be a standard to be developed by the SimDAP specification, or a simple custom service. In the latter case the base URL should point to a web page that presents further details.</xsd:documentation>
188 <xsd:appinfo>xmiid=_12_1_1_8e0028f_1178634214328_979805_732</xsd:appinfo>
189 </xsd:annotation>
190 <xsd:sequence>
191 <xsd:element name="baseURL" type="xsd:string"/>
192 <xsd:element name="description" type="xsd:string" minOccurs="0"/>
193 <xsd:element name="type" type="ServiceType"/>
194 </xsd:sequence>
195 </xsd:complexType>
197 <xsd:complexType name="TargetProcess">
198 <xsd:annotation>
199 <xsd:documentation>This class represents the fact that some simulations are run to investigate physical processes, rather than simulation specific objects or systems. Instances of this class can be used to describe this. For example one may study "turbulence", or "gravitational cluster" or "galaxy formation".</xsd:documentation>
200 <xsd:appinfo>xmiid=_12_1_2_213004e4_1193927417218_156887_401</xsd:appinfo>
201 </xsd:annotation>
202 <xsd:complexContent>
203 <xsd:extension base="p6:ObjectType">
204 <xsd:sequence>
205 <xsd:element name="astroJournalSubject" type="xsd:string" minOccurs="0"/>
206 </xsd:sequence>
207 </xsd:extension>
208 </xsd:complexContent>
209 </xsd:complexType>
211 <xsd:complexType name="ParameterSetting" abstract="true">
212 <xsd:annotation>
213 <xsd:documentation>To run an Experiments, one usually needs to assign values to parameters defined on the corresponding Protocol. This class makes the association between the Experiment and the parameters. Parameters can have many different types and so the type of the value can in general not be pre-assigned, as base class Value coiuld be used, but for usability purposes we decided to sub class this class instead to deal with numeric and all other parameters.</xsd:documentation>
214 <xsd:appinfo>xmiid=_12_1_2_213004e4_1195984162343_63311_299</xsd:appinfo>
215 </xsd:annotation>
216 <xsd:sequence>
217 <xsd:element name="inputParameter" type="base:Reference" minOccurs="0">
218 <xsd:annotation>
219 <xsd:appinfo>xmiidref=_12_1_8e0028f_1173260612156_632863_688</xsd:appinfo>
220 </xsd:annotation>
221 </xsd:element>
222 </xsd:sequence>
223 </xsd:complexType>
225 <xsd:complexType name="AppliedPhysics">
226 <xsd:annotation>
227 <xsd:documentation>Many simulation codes allow one to turn on or off modules corresponding to different physics. This class is aan association betwene the Simulation and the Physics available on a certaion protocol.</xsd:documentation>
228 <xsd:appinfo>xmiid=_14_0_8e0028f_1202819493156_452128_1609</xsd:appinfo>
229 </xsd:annotation>
230 <xsd:sequence>
231 <xsd:element name="physics" type="base:Reference">
232 <xsd:annotation>
233 <xsd:appinfo>xmiidref=_12_1_8e0028f_1173262198953_752563_1200</xsd:appinfo>
234 </xsd:annotation>
235 </xsd:element>
236 </xsd:sequence>
237 </xsd:complexType>
239 <xsd:complexType name="SubvolumeExtraction">
240 <xsd:annotation>
241 <xsd:documentation>Represents the extraction of a subvolume from an existing Snapshot</xsd:documentation>
242 <xsd:appinfo>xmiid=_12_1_8e0028f_1175599204640_374973_516</xsd:appinfo>
243 </xsd:annotation>
244 <xsd:complexContent>
245 <xsd:extension base="PostProcessing"/>
246 </xsd:complexContent>
247 </xsd:complexType>
249 <xsd:complexType name="ExperimentRepresentationObject">
250 <xsd:annotation>
251 <xsd:documentation>Protocols often allow one to choose which representation object types one wants to use in an experiment. For example, SPH codes may have dark matter particles, gass particles, star particles. A given experiment may not require all. This class associates the experiment to the actual representation object types that are used.</xsd:documentation>
252 <xsd:appinfo>xmiid=_12_1_8e0028f_1208963843859_164887_244</xsd:appinfo>
253 </xsd:annotation>
254 <xsd:sequence>
255 <xsd:element name="property" type="ExperimentProperty" minOccurs="0" maxOccurs="unbounded"/>
256 <xsd:element name="type" type="base:Reference">
257 <xsd:annotation>
258 <xsd:appinfo>xmiidref=_12_1_8e0028f_1173260105000_913974_289</xsd:appinfo>
259 </xsd:annotation>
260 </xsd:element>
261 </xsd:sequence>
262 </xsd:complexType>
264 <xsd:complexType name="ExperimentProperty">
265 <xsd:annotation>
266 <xsd:documentation>Apart form allowing a user the freedom to choose between available representation object types, Protocols may also allow one to choose from available properties on the selected object.
267 This class represents such a choice.</xsd:documentation>
268 <xsd:appinfo>xmiid=_12_1_8e0028f_1208963945515_646605_471</xsd:appinfo>
269 </xsd:annotation>
270 <xsd:sequence>
271 <xsd:element name="property" type="base:Reference">
272 <xsd:annotation>
273 <xsd:appinfo>xmiidref=_12_1_8e0028f_1173260158109_378937_365</xsd:appinfo>
274 </xsd:annotation>
275 </xsd:element>
276 </xsd:sequence>
277 </xsd:complexType>
279 <xsd:complexType name="TargetObjectType">
280 <xsd:annotation>
281 <xsd:documentation>This class represents the actual system that is being simulated. Instances of this object should correspond to physical objects and/or systems. They should be the answer to queries such as, “what does this simulation simulate?”</xsd:documentation>
282 <xsd:appinfo>xmiid=_12_1_8e0028f_1175527967546_211274_169</xsd:appinfo>
283 </xsd:annotation>
284 <xsd:complexContent>
285 <xsd:extension base="p6:ObjectType">
286 <xsd:sequence>
287 <xsd:element name="multiplicity" type="p5:Cardinality" minOccurs="0"/>
288 <xsd:element name="identityName" type="xsd:string" minOccurs="0"/>
289 <xsd:element name="label" type="xsd:string" minOccurs="0"/>
290 </xsd:sequence>
291 </xsd:extension>
292 </xsd:complexContent>
293 </xsd:complexType>
295 <xsd:complexType name="CompositeExperiment">
296 <xsd:annotation>
297 <xsd:documentation>A CompositeExperiment is a group of experiments run together in a kind of workflow or pipeline mode. They have their own protocol, consiting of sub protocols for the child experiments.</xsd:documentation>
298 <xsd:appinfo>xmiid=_12_1_8e0028f_1209037435156_352640_267</xsd:appinfo>
299 </xsd:annotation>
300 <xsd:complexContent>
301 <xsd:extension base="Experiment">
302 <xsd:sequence>
303 <xsd:element name="child" type="ChildExperiment" maxOccurs="unbounded"/>
304 </xsd:sequence>
305 </xsd:extension>
306 </xsd:complexContent>
307 </xsd:complexType>
309 <xsd:complexType name="CompositeProtocol">
310 <xsd:annotation>
311 <xsd:documentation>This class embodies a composition of othe rprotocols to work together as a protocol for a single (composite) experiment. It can be seen as embodying a workflow or pipeline, but is not modeled as a graph, only an agggregation of separately described protocols thusfar.</xsd:documentation>
312 <xsd:appinfo>xmiid=_12_1_8e0028f_1209037627390_53284_333</xsd:appinfo>
313 </xsd:annotation>
314 <xsd:complexContent>
315 <xsd:extension base="p2:Protocol">
316 <xsd:sequence>
317 <xsd:element name="child" type="ChildProtocol" maxOccurs="unbounded"/>
318 </xsd:sequence>
319 </xsd:extension>
320 </xsd:complexContent>
321 </xsd:complexType>
323 <xsd:complexType name="ChildExperiment">
324 <xsd:annotation>
325 <xsd:documentation>Association class to indictae the experiments making up a composite experiment.</xsd:documentation>
326 <xsd:appinfo>xmiid=_12_1_8e0028f_1209038083546_352136_491</xsd:appinfo>
327 </xsd:annotation>
328 <xsd:sequence>
329 <xsd:element name="experiment" type="base:Reference">
330 <xsd:annotation>
331 <xsd:appinfo>xmiidref=_12_1_8e0028f_1175592662265_484162_263</xsd:appinfo>
332 </xsd:annotation>
333 </xsd:element>
334 </xsd:sequence>
335 </xsd:complexType>
337 <xsd:complexType name="ChildProtocol">
338 <xsd:annotation>
339 <xsd:documentation>Association class representing a protocol that is used by a composite protocol.</xsd:documentation>
340 <xsd:appinfo>xmiid=_12_1_8e0028f_1209038149156_959482_630</xsd:appinfo>
341 </xsd:annotation>
342 <xsd:sequence>
343 <xsd:element name="protocol" type="base:Reference">
344 <xsd:annotation>
345 <xsd:appinfo>xmiidref=_12_1_8e0028f_1175789188406_755001_115</xsd:appinfo>
346 </xsd:annotation>
347 </xsd:element>
348 </xsd:sequence>
349 </xsd:complexType>
351 <xsd:complexType name="GenericParameterSetting">
352 <xsd:annotation>
353 <xsd:documentation>Represents a parametr setting for non-numeric parameters. The value is therefore a simple string.</xsd:documentation>
354 <xsd:appinfo>xmiid=_12_1_8e0028f_1209397657343_412857_223</xsd:appinfo>
355 </xsd:annotation>
356 <xsd:complexContent>
357 <xsd:extension base="ParameterSetting">
358 <xsd:sequence>
359 <xsd:element name="value" type="xsd:string"/>
360 </xsd:sequence>
361 </xsd:extension>
362 </xsd:complexContent>
363 </xsd:complexType>
365 <xsd:complexType name="NumericParameterSetting">
366 <xsd:annotation>
367 <xsd:documentation>Represents the setting of a numerical parameter. We alllow a free unit in the value.
368 TODO decide whether we want/require this freedom of unit!</xsd:documentation>
369 <xsd:appinfo>xmiid=_12_1_8e0028f_1209397707921_986976_272</xsd:appinfo>
370 </xsd:annotation>
371 <xsd:complexContent>
372 <xsd:extension base="ParameterSetting">
373 <xsd:sequence>
374 <xsd:element name="value" type="p5:Quantity"/>
375 </xsd:sequence>
376 </xsd:extension>
377 </xsd:complexContent>
378 </xsd:complexType>
380 <xsd:simpleType name="ServiceType">
381 <xsd:annotation>
382 <xsd:documentation>This enumeration indicates a list of possible service types that can be applied to snapshots of a given simulation. The contents of this enumeration will be decided evenatually by a SimDAP protocol specification, though 'custom' is always available and not specified in SimDAP.</xsd:documentation>
383 <xsd:appinfo>xmiid=_12_1_1_8e0028f_1178636199937_418371_870</xsd:appinfo>
384 </xsd:annotation>
385 <xsd:restriction base="xsd:string">
386 <xsd:enumeration value="download">
387 <xsd:annotation>
388 <xsd:documentation>Represents a service that allows one to download a snapshot.</xsd:documentation>
389 </xsd:annotation>
390 </xsd:enumeration>
391 <xsd:enumeration value="cutout">
392 <xsd:annotation>
393 <xsd:documentation>Represents a SimDAP service that defines a cut-out operation on an existing snapshot.</xsd:documentation>
394 </xsd:annotation>
395 </xsd:enumeration>
396 <xsd:enumeration value="gridding">
397 <xsd:annotation>
398 <xsd:documentation>Represents a SimDAP service that defines a (re)gridding operation on an existing snapshot.
399 NB This may be have to be renamed depending on SimDAP standard.</xsd:documentation>
400 </xsd:annotation>
401 </xsd:enumeration>
402 <xsd:enumeration value="clusterfinder">
403 <xsd:annotation>
404 <xsd:documentation>Represents a SimDAP service that defines a cluster-finder operation on an existing snapshot, supposedly of an N-body simulation.
405 NB This may be have to be renamed depending on SimDAP standard.</xsd:documentation>
406 </xsd:annotation>
407 </xsd:enumeration>
408 <xsd:enumeration value="visualisation">
409 <xsd:annotation>
410 <xsd:documentation>Represents a SimDAP service that defines a visualisation operation on an existing snapshot, producing a 2 dimensional grid.
411 NB This may be have to be renamed depending on SimDAP standard.</xsd:documentation>
412 </xsd:annotation>
413 </xsd:enumeration>
414 <xsd:enumeration value="custom">
415 <xsd:annotation>
416 <xsd:documentation>Thie represents a general, unspecified online operation on a simulation. It may be of any kind, no restriction on interface.</xsd:documentation>
417 </xsd:annotation>
418 </xsd:enumeration>
419 </xsd:restriction>
420 </xsd:simpleType>
422 <xsd:simpleType name="CharacterisationType">
423 <xsd:annotation>
424 <xsd:documentation>This enumeration lists possible ways to characterise a collection of Property-s in a snapshot. The literals in this enumeration in general correspond to the result of a statistical operation on this collection (when a posteriori) or on the corresponding operation on the a priori probability distribtion (assuming this can be defined) of its values.
426 TBD May need to be turned into an ontology, i.e. the values are not defined in this model, but in an external set of reference data.</xsd:documentation>
427 <xsd:appinfo>xmiid=_12_1_2_213004e4_1207894335531_849311_215</xsd:appinfo>
428 </xsd:annotation>
429 <xsd:restriction base="xsd:string">
430 <xsd:enumeration value="nominal">
431 <xsd:annotation>
432 <xsd:documentation>A typical value, as judged by the publisher of the snapshots.
433 May not correspond to a predefined statistical operation such as mean or mode.</xsd:documentation>
434 </xsd:annotation>
435 </xsd:enumeration>
436 <xsd:enumeration value="min">
437 <xsd:annotation>
438 <xsd:documentation>Represents the minimum ('possible' if a priori, 'attained' if a osteriori) value for the characterised property.</xsd:documentation>
439 </xsd:annotation>
440 </xsd:enumeration>
441 <xsd:enumeration value="max">
442 <xsd:annotation>
443 <xsd:documentation>Represents the maximum ('possible' if a priori, 'attained' if a osteriori) value for the characterised property.</xsd:documentation>
444 </xsd:annotation>
445 </xsd:enumeration>
446 <xsd:enumeration value="mean">
447 <xsd:annotation>
448 <xsd:documentation>Represents the mean ('expected' if a priori, 'attained' if a posteriori) value for the characterised property.</xsd:documentation>
449 </xsd:annotation>
450 </xsd:enumeration>
451 <xsd:enumeration value="stdev">
452 <xsd:annotation>
453 <xsd:documentation>Represents the expected/attained standard deviation for the characterised property.</xsd:documentation>
454 </xsd:annotation>
455 </xsd:enumeration>
456 </xsd:restriction>
457 </xsd:simpleType>
459 </xsd:schema>

ViewVC Help
Powered by ViewVC 1.1.26