/[volute]/trunk/projects/dm/vo-dml/models/ds/DatasetMetadata-1.0.vo-dml.xml
ViewVC logotype

Contents of /trunk/projects/dm/vo-dml/models/ds/DatasetMetadata-1.0.vo-dml.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 3222 - (show annotations)
Mon Jan 11 21:00:07 2016 UTC (4 years, 10 months ago) by mdittmar
File MIME type: text/xml
File size: 52329 byte(s)
merge MCD and GL from previous; fix bug in modelprefix template of xslt script; integrate updates to STC prototype
1 <?xml version="1.0" encoding="UTF-8"?>
2 <vo-dml:model xmlns:vo-dml="http://www.ivoa.net/xml/VODML/v1.0">
3 <name>ds</name>
4 <description>
5 This document provides a data model describing the structure and content of generic Dataset metadata for the IVOA. This is a high-level model which is to be referenced and extended by other models describing specific types of Datasets and Data products. In this document, we specify the generic Dataset, as well as an ObservationDataset model which covers the class of Datasets which are derived from an Observation. At the time of this writing, there is no formal Observation-Experiment model for the IVOA, so we include a hypothetical Observation-Experiment model to serve as a placeholder.
6
7 </description>
8 <title>IVOA Dataset Metadata Model</title>
9 <author>Mark Cresitello-Dittmar, Francois Bonnarel, Omar Laurino, Gerard Lemson, Mireille Louys, Arnold Rots, Doug Tody, and the IVOA Data Model Working Group.</author>
10 <version>1.0</version>
11 <previousVersion>0.x</previousVersion>
12 <lastModified>2016-01-11T15:54:31</lastModified>
13 <import>
14 <name>ivoa</name>
15 <url>http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/ivoa/IVOA.vo-dml.xml</url>
16 <documentationURL>http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/ivoa/IVOA.html</documentationURL>
17 </import>
18 <import>
19 <name>char</name>
20 <url>http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/characterization/Characterization.vo-dml.xml</url>
21 <documentationURL>http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/characterization/Characterization.html</documentationURL>
22 </import>
23 <import>
24 <name>stc</name>
25 <url>http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/STC2/prototype/STCPrototype-2.0.vo-dml.xml</url>
26 <documentationURL>http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/STC2/prototype/STCPrototype-2.0.html</documentationURL>
27 </import>
28
29 <package>
30 <vodml-id>experiment</vodml-id>
31 <name>experiment</name>
32 <description>
33 The Observation Experiment model refers to several elements related to an Observation and its configuration. As of the time of this writing, there is no IVOA recommendation for a general Observation data model. The Provenance data model, in progress, will define the pattern for describing the relation between actions and results, and how to record these in datasets. In lieu of these standards, this document defines a straw-man Observation model.
34
35 The Observation is modeled as a type of 'Experiment', with some basic structure defined to provide metadata about the observation target and configuration. The product, or 'result' of the Observation is zero or more ObsDataset objects. This pattern is inspired by, and compatible with the Simulation Data Model, where a 'Simulation' can be considered another form of 'Experiment' or perhaps even another form of 'Observation'.
36
37 </description>
38 <objectType>
39 <vodml-id>experiment.Bandpass</vodml-id>
40 <name>Bandpass</name>
41 <description>
42 Describes the spectral range of the observation. The value may be expressed in terms
43 of general spectral bands, or specific bandpass names. If multiple bands are covered, the value
44 may be a comma delimited combination of appropriate bands. If expressed as general bands,
45 the value(s) must be selected from the enumerated set given by the SpectralBand type. There is
46 no controlled vocabulary for bandpass names as the list is too long to enumerate. Effort should
47 be made to use highly recognized bandpass names (eg: "U","V","B","R","I", "H-alpha").
48 This field corresponds to both the Coverage.Spectral and Coverage.Spectral.Bandpass fields of
49 the Resource Metadata document.
50
51 </description>
52 <extends>
53 <vodml-ref>ds:experiment.ObservingElement</vodml-ref>
54 </extends>
55 </objectType>
56
57 <objectType>
58 <vodml-id>experiment.Observation</vodml-id>
59 <name>Observation</name>
60 <description>
61
62 </description>
63 <attribute>
64 <vodml-id>experiment.Observation.observationID</vodml-id>
65 <name>observationID</name>
66 <description>
67 Internal ID determined by the data provide to uniquely identify the observation within the institution or entity performing the observation.
68
69 </description>
70 <datatype>
71 <vodml-ref>ivoa:string</vodml-ref>
72 </datatype>
73 <multiplicity>
74 <minOccurs>1</minOccurs>
75 <maxOccurs>1</maxOccurs>
76 </multiplicity>
77 </attribute>
78 <collection>
79 <vodml-id>experiment.Observation.target</vodml-id>
80 <name>target</name>
81 <description>
82 The target of the observation. The content of this object may vary greatly depending on the goals and nature of the observation. For example the 'target' could be a galaxy, stellar object, planet, or calibration source. As such, we allow the BaseTarget class here, and permit users to define and use more content rich flavors according to their needs.
83
84 </description>
85 <datatype>
86 <vodml-ref>ds:experiment.BaseTarget</vodml-ref>
87 </datatype>
88 <multiplicity>
89 <minOccurs>1</minOccurs>
90 <maxOccurs>1</maxOccurs>
91 </multiplicity>
92 </collection>
93 <collection>
94 <vodml-id>experiment.Observation.obsConfig</vodml-id>
95 <name>obsConfig</name>
96 <description>
97 Observation configuration metadata, provides information about who, where, and how the observation was conducted.
98
99 </description>
100 <datatype>
101 <vodml-ref>ds:experiment.ObsConfig</vodml-ref>
102 </datatype>
103 <multiplicity>
104 <minOccurs>1</minOccurs>
105 <maxOccurs>1</maxOccurs>
106 </multiplicity>
107 </collection>
108 <collection>
109 <vodml-id>experiment.Observation.proposal</vodml-id>
110 <name>proposal</name>
111 <description>
112 Identifies any proposal related to the observation. This field may be used to gather all observations and products related to a particular proposal.
113
114 </description>
115 <datatype>
116 <vodml-ref>ds:experiment.Proposal</vodml-ref>
117 </datatype>
118 <multiplicity>
119 <minOccurs>0</minOccurs>
120 <maxOccurs>1</maxOccurs>
121 </multiplicity>
122 </collection>
123 <collection>
124 <vodml-id>experiment.Observation.result</vodml-id>
125 <name>result</name>
126 <description>
127 The result of an observation is zero or more Observation Datasets.
128
129 </description>
130 <datatype>
131 <vodml-ref>ds:dataset.ObsDataset</vodml-ref>
132 </datatype>
133 <multiplicity>
134 <minOccurs>0</minOccurs>
135 <maxOccurs>-1</maxOccurs>
136 </multiplicity>
137 </collection>
138 </objectType>
139
140 <objectType>
141 <vodml-id>experiment.Proposal</vodml-id>
142 <name>Proposal</name>
143 <description>
144 Metadata related to the proposal or document which spawned the observation.
145
146 </description>
147 <attribute>
148 <vodml-id>experiment.Proposal.identifier</vodml-id>
149 <name>identifier</name>
150 <description>
151 Tag used to uniquely identify a particular proposal within the institution or entity.
152
153 </description>
154 <datatype>
155 <vodml-ref>ivoa:string</vodml-ref>
156 </datatype>
157 <multiplicity>
158 <minOccurs>1</minOccurs>
159 <maxOccurs>1</maxOccurs>
160 </multiplicity>
161 </attribute>
162 </objectType>
163
164 <objectType abstract="true">
165 <vodml-id>experiment.ObservingElement</vodml-id>
166 <name>ObservingElement</name>
167 <description>
168 Abstract base class for defining observation parameters. Each subclass of ObservationElement pertains to a particular 'domain' of the observation setup, e.g. the Facility, or the Instrument, and may have additional structure to provide all relevant metadata in that domain.
169
170 </description>
171 <attribute>
172 <vodml-id>experiment.ObservingElement.name</vodml-id>
173 <name>name</name>
174 <description>
175 The name attribute identifies the particular instance of the ObservingElement. e.g. the Facility name.
176
177 </description>
178 <datatype>
179 <vodml-ref>ivoa:string</vodml-ref>
180 </datatype>
181 <multiplicity>
182 <minOccurs>1</minOccurs>
183 <maxOccurs>1</maxOccurs>
184 </multiplicity>
185 </attribute>
186 </objectType>
187
188 <objectType>
189 <vodml-id>experiment.Instrument</vodml-id>
190 <name>Instrument</name>
191 <description>
192 Identifies the instrument used to create the data. (RM:Collection.Instrument) This can
193 be a specific instrument name, general type or something else, such as a program in the case of
194 theoretical data. We restrict this field to a single value.
195
196 </description>
197 <extends>
198 <vodml-ref>ds:experiment.ObservingElement</vodml-ref>
199 </extends>
200 </objectType>
201
202 <objectType>
203 <vodml-id>experiment.Target</vodml-id>
204 <name>Target</name>
205 <description>
206 General purpose Target object.
207 </description>
208 <extends>
209 <vodml-ref>ds:experiment.BaseTarget</vodml-ref>
210 </extends>
211 <attribute>
212 <vodml-id>experiment.Target.objectClass</vodml-id>
213 <name>objectClass</name>
214 <description>
215 General classification or type of the target. This field supports the discovery of data pertaining to a common class. e.g. "Star", "Galaxy", "AGN". At the time of this writing, there is no IVOA recommended vocabulary for this field. The SIMBAD and NED databases use defined vocabularies for astronomical object classifications which may serve as the basis for such.
216 </description>
217 <datatype>
218 <vodml-ref>ivoa:string</vodml-ref>
219 </datatype>
220 <multiplicity>
221 <minOccurs>0</minOccurs>
222 <maxOccurs>1</maxOccurs>
223 </multiplicity>
224 </attribute>
225 </objectType>
226
227 <objectType abstract="true">
228 <vodml-id>experiment.BaseTarget</vodml-id>
229 <name>BaseTarget</name>
230 <description>
231 Abstract base class for the Target object tree. The target object provides identifying metadata related to the subject or goal of the experiment. For an Observational experiment, this would typically be an astronomical object. The BaseTarget class defines high-level identifying information, and must be extended for particular classes of Target which may define additional characteristics.
232
233 </description>
234 <attribute>
235 <vodml-id>experiment.BaseTarget.name</vodml-id>
236 <name>name</name>
237 <description>
238 The target name. The primary purpose of this field is to provide the user with a recognizable identity of the particular subject or goal. However, since this may be a query-able field in data discovery protocols, care should be taken to use values which follow conventions for the domain appropriate for the data. For an astronomical object, this may be a name suitable for use within a domain-specific resolution service. Simulated data might also use this sort of name (if simulating a particular object), or a more generic term such as "G2V star".
239
240 </description>
241 <datatype>
242 <vodml-ref>ivoa:string</vodml-ref>
243 </datatype>
244 <multiplicity>
245 <minOccurs>1</minOccurs>
246 <maxOccurs>1</maxOccurs>
247 </multiplicity>
248 </attribute>
249 <attribute>
250 <vodml-id>experiment.BaseTarget.description</vodml-id>
251 <name>description</name>
252 <description>
253 Free form description of target.
254
255 </description>
256 <datatype>
257 <vodml-ref>ivoa:string</vodml-ref>
258 </datatype>
259 <multiplicity>
260 <minOccurs>0</minOccurs>
261 <maxOccurs>1</maxOccurs>
262 </multiplicity>
263 </attribute>
264 <attribute>
265 <vodml-id>experiment.BaseTarget.position</vodml-id>
266 <name>position</name>
267 <description>
268 This field provides the spatial location of the target. The value is an STC Position object which supports all required dimensionality and coordinate frame specification needs. In the context of an Astronomical Target, this field gives the nominal RA and Dec location for the target. For example, the catalog position of the source.
269
270 </description>
271 <datatype>
272 <vodml-ref>stc:Position</vodml-ref>
273 </datatype>
274 <multiplicity>
275 <minOccurs>0</minOccurs>
276 <maxOccurs>1</maxOccurs>
277 </multiplicity>
278 </attribute>
279 </objectType>
280
281 <objectType>
282 <vodml-id>experiment.AstroTarget</vodml-id>
283 <name>AstroTarget</name>
284 <description>
285 Extension of BaseTarget specialized for astronomical objects. The AstroTarget defines additional astronomical properties of the target.
286 </description>
287 <extends>
288 <vodml-ref>ds:experiment.BaseTarget</vodml-ref>
289 </extends>
290 <attribute>
291 <vodml-id>experiment.AstroTarget.objectClass</vodml-id>
292 <name>objectClass</name>
293 <description>
294 General classification or type of the target. This field supports the discovery of data pertaining to a common class. e.g. "Star", "Galaxy", "AGN". At the time of this writing, there is no IVOA recommended vocabulary for this field. The SIMBAD and NED databases use defined vocabularies for astronomical object classifications which may serve as the basis for such.
295
296 </description>
297 <datatype>
298 <vodml-ref>ivoa:string</vodml-ref>
299 </datatype>
300 <multiplicity>
301 <minOccurs>0</minOccurs>
302 <maxOccurs>1</maxOccurs>
303 </multiplicity>
304 </attribute>
305 <attribute>
306 <vodml-id>experiment.AstroTarget.spectralClass</vodml-id>
307 <name>spectralClass</name>
308 <description>
309 Spectral class of the object. As with objectClass, there is no IVOA recommended vocabulary for specifying the spectral class of an object. There is an IVOA Note on the subject entitled "An encoding system to represent stellar spectral classes in archival databases and catalogs", describing an encoding system which has been adopted by the MAST archive.
310
311 </description>
312 <datatype>
313 <vodml-ref>ivoa:string</vodml-ref>
314 </datatype>
315 <multiplicity>
316 <minOccurs>0</minOccurs>
317 <maxOccurs>1</maxOccurs>
318 </multiplicity>
319 </attribute>
320 <attribute>
321 <vodml-id>experiment.AstroTarget.redshift</vodml-id>
322 <name>redshift</name>
323 <description>
324 This field gives the canonical redshift of the astronomical object. It is normally used to store the cosmological redshift of extragalactic objects, although it may also be used to store the observed redshift of Galactic sources if that information is felt by the data provider to be useful.
325
326 </description>
327 <datatype>
328 <vodml-ref>ivoa:real</vodml-ref>
329 </datatype>
330 <multiplicity>
331 <minOccurs>0</minOccurs>
332 <maxOccurs>1</maxOccurs>
333 </multiplicity>
334 </attribute>
335 <attribute>
336 <vodml-id>experiment.AstroTarget.varAmpl</vodml-id>
337 <name>varAmpl</name>
338 <description>
339 Canonical variability amplitude attributed to the target.
340
341 </description>
342 <datatype>
343 <vodml-ref>ivoa:real</vodml-ref>
344 </datatype>
345 <multiplicity>
346 <minOccurs>0</minOccurs>
347 <maxOccurs>1</maxOccurs>
348 </multiplicity>
349 </attribute>
350 </objectType>
351
352 <objectType>
353 <vodml-id>experiment.Facility</vodml-id>
354 <name>Facility</name>
355 <description>
356 Name of the facility performing the observation.
357
358 </description>
359 <extends>
360 <vodml-ref>ds:experiment.ObservingElement</vodml-ref>
361 </extends>
362 </objectType>
363
364 <objectType>
365 <vodml-id>experiment.DataSource</vodml-id>
366 <name>DataSource</name>
367 <description>
368 Describes the original source of the data in a very general fashion. In other words, "What sort of observation originally generated the data?" Suggested values include:
369 * survey: Survey data typically covers some region of observational parameter space with as complete as possible coverage within that region.
370 * pointed: Pointed data of a particular object or field.
371 * theory: Theory data, generated based on a theoretical model.
372 * artificial: Artificial, or simulated data. Similar to 'theory', but not necessarily based on a theoretical model.
373 * custom: Custom data, as part of a specific research project.
374
375 </description>
376 <extends>
377 <vodml-ref>ds:experiment.ObservingElement</vodml-ref>
378 </extends>
379 </objectType>
380
381 <objectType>
382 <vodml-id>experiment.ObsConfig</vodml-id>
383 <name>ObsConfig</name>
384 <description>
385 ObsConfig is a simple container object for all Observation Configuration metadata. It is modeled as a simple list of observing elements. Each ObservingElement provides metadata describing a particular domain of the observation setup. For example, the Facility performing the observation, the Instrument being used, etc.
386
387 </description>
388 <collection>
389 <vodml-id>experiment.ObsConfig.observingElement</vodml-id>
390 <name>observingElement</name>
391 <description>
392 Collection of zero or more ObservingElements which define observation parameters.
393 </description>
394 <datatype>
395 <vodml-ref>ds:experiment.ObservingElement</vodml-ref>
396 </datatype>
397 <multiplicity>
398 <minOccurs>0</minOccurs>
399 <maxOccurs>-1</maxOccurs>
400 </multiplicity>
401 </collection>
402 </objectType>
403
404 </package>
405
406
407
408 <package>
409 <vodml-id>dataset</vodml-id>
410 <name>dataset</name>
411 <description>
412 Dataset Metadata package
413 </description>
414 <enumeration>
415 <vodml-id>dataset.DataProductType</vodml-id>
416 <name>DataProductType</name>
417 <description>
418 Enumeration identifying the high level classification of a data product.
419 </description>
420 <literal>
421 <vodml-id>dataset.DataProductType.cube</vodml-id>
422 <name>cube</name>
423 <description>
424 A multidimensional astronomical image of three (3) or more axes.
425
426 </description>
427 </literal>
428 <literal>
429 <vodml-id>dataset.DataProductType.image</vodml-id>
430 <name>image</name>
431 <description>
432 A two (2) dimensional astronomical image.
433 </description>
434 </literal>
435 <literal>
436 <vodml-id>dataset.DataProductType.photometry</vodml-id>
437 <name>photometry</name>
438 <description>
439 Dataset with spectral coverage with irregular gaps.
440
441 </description>
442 </literal>
443 <literal>
444 <vodml-id>dataset.DataProductType.spectrum</vodml-id>
445 <name>spectrum</name>
446 <description>
447 Dataset where spectral coverage is the primary attribute, in contiguous bins. e.g. a 1D spectrum or a long slit spectrum.
448
449 </description>
450 </literal>
451 <literal>
452 <vodml-id>dataset.DataProductType.timeseries</vodml-id>
453 <name>timeseries</name>
454 <description>
455 Dataset presenting some quantity varying as a function of time. A light curve is a typical example of a timeseries dataset.
456 </description>
457 </literal>
458 <literal>
459 <vodml-id>dataset.DataProductType.sed</vodml-id>
460 <name>sed</name>
461 <description>
462 A spectral energy distribution, an advanced data product often produced by combining data from multiple observations.
463 </description>
464 </literal>
465 <literal>
466 <vodml-id>dataset.DataProductType.visibility</vodml-id>
467 <name>visibility</name>
468 <description>
469 A visibility (radio) dataset. Typically this is instrumental data, and is often a complex object containing multiple files or other substructures. A visibility dataset may contain data with spatial, spectral, time, and polarization information for each measured visibility.
470 </description>
471 </literal>
472 <literal>
473 <vodml-id>dataset.DataProductType.event</vodml-id>
474 <name>event</name>
475 <description>
476 An event counting dataset (e.g. X-ray). An event dataset may contain data with spatial, spectral, and time information for each measured event.
477 </description>
478 </literal>
479 <literal>
480 <vodml-id>dataset.DataProductType.catalog</vodml-id>
481 <name>catalog</name>
482 <description>
483 A catalog.
484
485 </description>
486 </literal>
487 </enumeration>
488
489 <enumeration>
490 <vodml-id>dataset.CreationType</vodml-id>
491 <name>CreationType</name>
492 <description>
493 Enumeration of dataset creation types.
494 </description>
495 <literal>
496 <vodml-id>dataset.CreationType.archival</vodml-id>
497 <name>archival</name>
498 <description>
499 Indicates that it is one of a collection of datasets generated in a systematic, homogeneous way and is stored statically (or at least versioned). It will be possible to regenerate this dataset at a later date. The remaining types imply on-the-fly manipulation.
500 </description>
501 </literal>
502 <literal>
503 <vodml-id>dataset.CreationType.cutout</vodml-id>
504 <name>cutout</name>
505 <description>
506 Indicates that the dataset was created "on-the-fly", by subsetting, but not by modifying values.
507
508 </description>
509 </literal>
510 <literal>
511 <vodml-id>dataset.CreationType.filtered</vodml-id>
512 <name>filtered</name>
513 <description>
514 May involve excluding data prior to binning into samples, also "on-the-fly"
515
516 </description>
517 </literal>
518 <literal>
519 <vodml-id>dataset.CreationType.mosaic</vodml-id>
520 <name>mosaic</name>
521 <description>
522 Combines multiple original datasets "on-the-fly"
523 </description>
524 </literal>
525 <literal>
526 <vodml-id>dataset.CreationType.spectral extraction</vodml-id>
527 <name>spectral extraction</name>
528 <description>
529 Has been extracted, for example, from a spectral data cube.
530
531 </description>
532 </literal>
533 <literal>
534 <vodml-id>dataset.CreationType.catalog extraction</vodml-id>
535 <name>catalog extraction</name>
536 <description>
537 Has been extracted from a catalog.
538 </description>
539 </literal>
540 </enumeration>
541
542 <enumeration>
543 <vodml-id>dataset.RightsType</vodml-id>
544 <name>RightsType</name>
545 <description>
546 Enumeration of access rights levels.
547
548 </description>
549 <literal>
550 <vodml-id>dataset.RightsType.public</vodml-id>
551 <name>public</name>
552 <description>
553 unrestricted, public access is allowed, without authentication.
554 </description>
555 </literal>
556 <literal>
557 <vodml-id>dataset.RightsType.proprietary</vodml-id>
558 <name>proprietary</name>
559 <description>
560 only proprietary access is allowed with authentication.
561
562 </description>
563 </literal>
564 <literal>
565 <vodml-id>dataset.RightsType.secure</vodml-id>
566 <name>secure</name>
567 <description>
568 authenticated, public access is allowed.
569 </description>
570 </literal>
571 </enumeration>
572
573 <enumeration>
574 <vodml-id>dataset.SpectralBandType</vodml-id>
575 <name>SpectralBandType</name>
576 <description>
577 TODO : Missing description : please, update your UML model asap.
578 </description>
579 <literal>
580 <vodml-id>dataset.SpectralBandType.Radio</vodml-id>
581 <name>Radio</name>
582 <description>
583 λ ≥ 10 mm; ν ≤ 30 GHz
584 </description>
585 </literal>
586 <literal>
587 <vodml-id>dataset.SpectralBandType.Millimeter</vodml-id>
588 <name>Millimeter</name>
589 <description>
590 0.1 mm ≤ λ ≤ 10 mm; 3000 GHz ≥ ν ≥ 30 GHz
591
592 </description>
593 </literal>
594 <literal>
595 <vodml-id>dataset.SpectralBandType.Infrared</vodml-id>
596 <name>Infrared</name>
597 <description>
598 1 μ ≤ λ ≤ 100 μ
599 </description>
600 </literal>
601 <literal>
602 <vodml-id>dataset.SpectralBandType.Optical</vodml-id>
603 <name>Optical</name>
604 <description>
605 0.3 μ ≤ λ ≤ 1 μ
606
607 </description>
608 </literal>
609 <literal>
610 <vodml-id>dataset.SpectralBandType.Ultraviolet</vodml-id>
611 <name>Ultraviolet</name>
612 <description>
613 100 Å ≤ λ ≤ 3000 Å; 1.2 eV ≤ E ≤ 120 eV
614
615 </description>
616 </literal>
617 <literal>
618 <vodml-id>dataset.SpectralBandType.X-ray</vodml-id>
619 <name>X-ray</name>
620 <description>
621 0.1 Å ≤ λ ≤ 100 Å; 0.12 keV ≤ E ≤ 120 keV
622
623 </description>
624 </literal>
625 <literal>
626 <vodml-id>dataset.SpectralBandType.Gamma-ray</vodml-id>
627 <name>Gamma-ray</name>
628 <description>
629 E ≥ 120keV
630 </description>
631 </literal>
632 </enumeration>
633
634 <objectType>
635 <vodml-id>dataset.DataModel</vodml-id>
636 <name>DataModel</name>
637 <description>
638 This object provides specific information regarding the data model and version thereof that a dataset represents. This information is primarily an aide to (de)serialization of the dataset. As such, it would better be defined by serialization conventions. In lieu of such conventions, we include this object and representative serialization examples for the primary file formats VOTable and FITS.
639
640 </description>
641 <attribute>
642 <vodml-id>dataset.DataModel.name</vodml-id>
643 <name>name</name>
644 <description>
645 Formatted string providing the name and version of the model document. The format speficication is "[name]-[version].[subversion]". Each derived model should specifically state the appropriate string for this field.
646
647 </description>
648 <datatype>
649 <vodml-ref>ivoa:string</vodml-ref>
650 </datatype>
651 <multiplicity>
652 <minOccurs>1</minOccurs>
653 <maxOccurs>1</maxOccurs>
654 </multiplicity>
655 </attribute>
656 <attribute>
657 <vodml-id>dataset.DataModel.prefix</vodml-id>
658 <name>prefix</name>
659 <description>
660 Prefix string used in UType string for elements associated with the model. For IVOA standard models, this will be a predetermined string (e.g. 'stc' or 'spec'). Extended, or user defined content can specify a unique prefix for their own content.
661
662 </description>
663 <datatype>
664 <vodml-ref>ivoa:string</vodml-ref>
665 </datatype>
666 <multiplicity>
667 <minOccurs>0</minOccurs>
668 <maxOccurs>1</maxOccurs>
669 </multiplicity>
670 </attribute>
671 <attribute>
672 <vodml-id>dataset.DataModel.URL</vodml-id>
673 <name>URL</name>
674 <description>
675 URL pointer to the XML schema associated with the model.
676
677 </description>
678 <datatype>
679 <vodml-ref>ivoa:anyURI</vodml-ref>
680 </datatype>
681 <multiplicity>
682 <minOccurs>0</minOccurs>
683 <maxOccurs>1</maxOccurs>
684 </multiplicity>
685 </attribute>
686 </objectType>
687
688 <objectType abstract="true">
689 <vodml-id>dataset.Dataset</vodml-id>
690 <name>Dataset</name>
691 <description>
692 Abstract object for the generic IVOA Dataset. It is intended to be useful for any type of data. Specific dataset models should extend this object, providing detailed definitions and additional content as appropriate for that type of dataset.
693
694 </description>
695 <attribute>
696 <vodml-id>dataset.Dataset.dataProductType</vodml-id>
697 <name>dataProductType</name>
698 <description>
699 Describes the high level scientific classification of the data content. Values are restricted to the DataProductType enumeration set and convey the general idea of the content and organization of
700 a dataset.
701
702 </description>
703 <datatype>
704 <vodml-ref>ds:dataset.DataProductType</vodml-ref>
705 </datatype>
706 <multiplicity>
707 <minOccurs>1</minOccurs>
708 <maxOccurs>1</maxOccurs>
709 </multiplicity>
710 </attribute>
711 <attribute>
712 <vodml-id>dataset.Dataset.dataProductSubtype</vodml-id>
713 <name>dataProductSubtype</name>
714 <description>
715 Secondary type classification for the dataset. This field is intended to precisely specify the scientific nature of the data product, possibly in terms relevant only to a specific archive or data collection. For example, dataProductType='image' could have associated dataProductSubtype="src.image", "bkg.image", "PixelMask", etc. Values are unrestricted strings.
716
717 </description>
718 <datatype>
719 <vodml-ref>ivoa:string</vodml-ref>
720 </datatype>
721 <multiplicity>
722 <minOccurs>0</minOccurs>
723 <maxOccurs>1</maxOccurs>
724 </multiplicity>
725 </attribute>
726 <collection>
727 <vodml-id>dataset.Dataset.curation</vodml-id>
728 <name>curation</name>
729 <description>
730 Provides metadata related to the entity responsible for the curation of the dataset.
731
732 </description>
733 <datatype>
734 <vodml-ref>ds:dataset.Curation</vodml-ref>
735 </datatype>
736 <multiplicity>
737 <minOccurs>1</minOccurs>
738 <maxOccurs>1</maxOccurs>
739 </multiplicity>
740 </collection>
741 <collection>
742 <vodml-id>dataset.Dataset.dataID</vodml-id>
743 <name>dataID</name>
744 <description>
745 DataID provides high level identification metadata for the dataset itself, and any associations with various collections.
746 </description>
747 <datatype>
748 <vodml-ref>ds:dataset.DataID</vodml-ref>
749 </datatype>
750 <multiplicity>
751 <minOccurs>1</minOccurs>
752 <maxOccurs>1</maxOccurs>
753 </multiplicity>
754 </collection>
755 </objectType>
756
757 <objectType>
758 <vodml-id>dataset.DataID</vodml-id>
759 <name>DataID</name>
760 <description>
761 The Data Identification object (DataID) stores the dataset identifiers and its membership within larger collections.
762 The Dataset IDs in this object must comply with the syntax for dataset identifiers defined in the "IVOA Identifiers" document, including the use of 'stop' characters to identify specific datasets that are not individually in the registry. e.g., ivo://example.net/aservice?2013/5/2342.
763 Much of the content of this object is assembled from various definitions in the IVAO Resource Metadata document. Here, we provide a brief description of each field for easy reference, along with a notation of its mapping to the Resource Metadata document (RM:field), where the reader may find more detailed information.
764
765 </description>
766 <attribute>
767 <vodml-id>dataset.DataID.title</vodml-id>
768 <name>title</name>
769 <description>
770 A free form string giving a title for the dataset. (RM:Identity.Title)
771 </description>
772 <datatype>
773 <vodml-ref>ivoa:string</vodml-ref>
774 </datatype>
775 <multiplicity>
776 <minOccurs>1</minOccurs>
777 <maxOccurs>1</maxOccurs>
778 </multiplicity>
779 </attribute>
780 <attribute>
781 <vodml-id>dataset.DataID.datasetID</vodml-id>
782 <name>datasetID</name>
783 <description>
784 If the dataset is registered with an external 'global index service' such as ADS, the publisher may include that identifier here. This provides a common, persistent identifier for the dataset, and possible access point to follow for information on publications and other related datasets. Note: the same dataset published at more than one location would have different Curation.publisherDID values, but the same DataID.datasetID. eg: "ivo://ADS/Sa.CXO?obsid=1234", "ivo://ADS/sh.hut#ngc4151_141"
785
786 </description>
787 <datatype>
788 <vodml-ref>ivoa:anyURI</vodml-ref>
789 </datatype>
790 <multiplicity>
791 <minOccurs>0</minOccurs>
792 <maxOccurs>1</maxOccurs>
793 </multiplicity>
794 </attribute>
795 <attribute>
796 <vodml-id>dataset.DataID.creatorDID</vodml-id>
797 <name>creatorDID</name>
798 <description>
799 The dataset identifier assigned by the creator. Here, the authority-id of the identifier must be that of the creator. It is used to identify the original exposure of the dataset in an archive, and will remain static regardless of where the dataset is published. The creator ID will not necessarily change even if the VO object in question is a cutout or is otherwise further processed.
800
801 </description>
802 <datatype>
803 <vodml-ref>ivoa:anyURI</vodml-ref>
804 </datatype>
805 <multiplicity>
806 <minOccurs>0</minOccurs>
807 <maxOccurs>1</maxOccurs>
808 </multiplicity>
809 </attribute>
810 <attribute>
811 <vodml-id>dataset.DataID.date</vodml-id>
812 <name>date</name>
813 <description>
814 Data processing or creation date (RM:Curation.Date).
815 </description>
816 <datatype>
817 <vodml-ref>ivoa:datetime</vodml-ref>
818 </datatype>
819 <multiplicity>
820 <minOccurs>0</minOccurs>
821 <maxOccurs>1</maxOccurs>
822 </multiplicity>
823 </attribute>
824 <attribute>
825 <vodml-id>dataset.DataID.creator</vodml-id>
826 <name>creator</name>
827 <description>
828 A free form string giving the name of the institution or entity which created the dataset. (RM:Curation.Creator)
829
830 </description>
831 <datatype>
832 <vodml-ref>ivoa:string</vodml-ref>
833 </datatype>
834 <multiplicity>
835 <minOccurs>0</minOccurs>
836 <maxOccurs>1</maxOccurs>
837 </multiplicity>
838 </attribute>
839 <attribute>
840 <vodml-id>dataset.DataID.collection</vodml-id>
841 <name>collection</name>
842 <description>
843 The dataset is associated with zero or more Collections (instrument name, survey name, etc.) . Each instance is a free form string of a particular collection tag. The values are generally defined by the creating entity and indicate some degree of compatibility with other data sharing the same Collection properties. Examples: "WFC", "Sloan", "BFS Spectrograph", "MSX Galactic Plane Survey".
844
845 </description>
846 <datatype>
847 <vodml-ref>ivoa:string</vodml-ref>
848 </datatype>
849 <multiplicity>
850 <minOccurs>0</minOccurs>
851 <maxOccurs>-1</maxOccurs>
852 </multiplicity>
853 </attribute>
854 <attribute>
855 <vodml-id>dataset.DataID.version</vodml-id>
856 <name>version</name>
857 <description>
858 Version assigned by the creator, reflecting the production version of the dataset. This value should only be changed by the creator, upon the new release of a dataset. There are no format restrictions or specifications on the versioning scheme.
859
860 </description>
861 <datatype>
862 <vodml-ref>ivoa:string</vodml-ref>
863 </datatype>
864 <multiplicity>
865 <minOccurs>0</minOccurs>
866 <maxOccurs>1</maxOccurs>
867 </multiplicity>
868 </attribute>
869 <attribute>
870 <vodml-id>dataset.DataID.creationType</vodml-id>
871 <name>creationType</name>
872 <description>
873 The dataset creation type describes the nature or genre of the content. (RM:General.Type).
874 </description>
875 <datatype>
876 <vodml-ref>ds:dataset.CreationType</vodml-ref>
877 </datatype>
878 <multiplicity>
879 <minOccurs>0</minOccurs>
880 <maxOccurs>1</maxOccurs>
881 </multiplicity>
882 </attribute>
883 <attribute>
884 <vodml-id>dataset.DataID.logo</vodml-id>
885 <name>logo</name>
886 <description>
887 URL pointer to a graphical logo associated with the creator of the document content. (RM:Curation.Creator.Logo)
888 </description>
889 <datatype>
890 <vodml-ref>ivoa:anyURI</vodml-ref>
891 </datatype>
892 <multiplicity>
893 <minOccurs>0</minOccurs>
894 <maxOccurs>1</maxOccurs>
895 </multiplicity>
896 </attribute>
897 <attribute>
898 <vodml-id>dataset.DataID.contributor</vodml-id>
899 <name>contributor</name>
900 <description>
901 Persons or entities who contributed to the generation of the scientific content of the dataset. Users of the dataset should include these in subsequent credits and acknowledgements. Each instance identifies an entity, formatted to the desired acknowledgment expression. (RM:Curation.Contributor)
902
903 </description>
904 <datatype>
905 <vodml-ref>ivoa:string</vodml-ref>
906 </datatype>
907 <multiplicity>
908 <minOccurs>0</minOccurs>
909 <maxOccurs>-1</maxOccurs>
910 </multiplicity>
911 </attribute>
912 <attribute>
913 <vodml-id>dataset.DataID.observationID</vodml-id>
914 <name>observationID</name>
915 <description>
916 Internal ID determined by the data provider to identify the observation from which the dataset was produced.
917
918 </description>
919 <datatype>
920 <vodml-ref>ivoa:string</vodml-ref>
921 </datatype>
922 <multiplicity>
923 <minOccurs>0</minOccurs>
924 <maxOccurs>1</maxOccurs>
925 </multiplicity>
926 </attribute>
927 </objectType>
928
929 <objectType>
930 <vodml-id>dataset.Curation</vodml-id>
931 <name>Curation</name>
932 <description>
933 The Curation object provides information about the entity responsible for the support of the dataset content. It is assembled from definitions provided by the IVOA standard document, "Resource Metadata for the Virtual Observatory; Version 1.12" (Resource Metadata). Here, we provide a brief description of each field for easy reference, along with a notation of its mapping to the Resource Metadata document (RM:field), where the reader may find more detailed information.
934 </description>
935 <attribute>
936 <vodml-id>dataset.Curation.publisher</vodml-id>
937 <name>publisher</name>
938 <description>
939 Common name for the entity making the data available. (RM:Curation.Publisher)
940
941 </description>
942 <datatype>
943 <vodml-ref>ivoa:string</vodml-ref>
944 </datatype>
945 <multiplicity>
946 <minOccurs>1</minOccurs>
947 <maxOccurs>1</maxOccurs>
948 </multiplicity>
949 </attribute>
950 <attribute>
951 <vodml-id>dataset.Curation.publisherID</vodml-id>
952 <name>publisherID</name>
953 <description>
954 IVOA resource identifier associated with the publisher and registered with an IVOA compliant registry (eg: ivo://mast.stsci.edu). Values are to be expressed using the syntax described in "IVOA Identifiers". (RM:Curation.PublisherID)
955
956 </description>
957 <datatype>
958 <vodml-ref>ivoa:anyURI</vodml-ref>
959 </datatype>
960 <multiplicity>
961 <minOccurs>0</minOccurs>
962 <maxOccurs>1</maxOccurs>
963 </multiplicity>
964 </attribute>
965 <attribute>
966 <vodml-id>dataset.Curation.publisherDID</vodml-id>
967 <name>publisherDID</name>
968 <description>
969 IVOA dataset identifier assigned by the publisher to uniquely identify the dataset within its holdings. Typically, the basis of this identifier will be the publisher ID. However, if the publisherchooses to use a 'global index service' such as ADS to obtain persistent identifiers for their datasets, rather than generate their own, that identifier should be used both here and for DataID.datasetID. Note: this model also defines a creator dataset ID (DataID.creatorDID), these will differ if the publishing entity is not the creator of the dataset. Values are to be expressed as dataset identifiers using the syntax described in "IVOA Identifiers"
970 </description>
971 <datatype>
972 <vodml-ref>ivoa:anyURI</vodml-ref>
973 </datatype>
974 <multiplicity>
975 <minOccurs>0</minOccurs>
976 <maxOccurs>1</maxOccurs>
977 </multiplicity>
978 </attribute>
979 <attribute>
980 <vodml-id>dataset.Curation.version</vodml-id>
981 <name>version</name>
982 <description>
983 Version of the curated dataset, assigned by the publisher. This is an independent versioning from DataID.version that allows the publisher to track changes to the high level dataset metadata (e.g. curation metadata, identifiers, etc.) without effecting the creator defined dataset version. The value may be based on the DataID.version (e.g. by adding a sub-version extension), or an independent versioning. There are no format restrictions on the value. (RM:Curation.Version)
984
985 </description>
986 <datatype>
987 <vodml-ref>ivoa:string</vodml-ref>
988 </datatype>
989 <multiplicity>
990 <minOccurs>0</minOccurs>
991 <maxOccurs>1</maxOccurs>
992 </multiplicity>
993 </attribute>
994 <attribute>
995 <vodml-id>dataset.Curation.rights</vodml-id>
996 <name>rights</name>
997 <description>
998 Indicates the access privileges to the content. (RM:Collection.Rights)
999
1000 </description>
1001 <datatype>
1002 <vodml-ref>ds:dataset.RightsType</vodml-ref>
1003 </datatype>
1004 <multiplicity>
1005 <minOccurs>0</minOccurs>
1006 <maxOccurs>1</maxOccurs>
1007 </multiplicity>
1008 </attribute>
1009 <attribute>
1010 <vodml-id>dataset.Curation.releaseDate</vodml-id>
1011 <name>releaseDate</name>
1012 <description>
1013 Date the curated dataset was last modified. (RM:Curation.Date)
1014 </description>
1015 <datatype>
1016 <vodml-ref>ivoa:datetime</vodml-ref>
1017 </datatype>
1018 <multiplicity>
1019 <minOccurs>0</minOccurs>
1020 <maxOccurs>1</maxOccurs>
1021 </multiplicity>
1022 </attribute>
1023 <attribute>
1024 <vodml-id>dataset.Curation.reference</vodml-id>
1025 <name>reference</name>
1026 <description>
1027 Zero or more bibliographic or documentation references associated with the dataset. Each instance provides a single forward link to a major publication which references the dataset. Values should be expressed as a URL, or bibcode (discernible as a 19 character string beginning with 4 digits). Free text references are allowed, but discouraged. (RM:General.Source)
1028
1029 </description>
1030 <datatype>
1031 <vodml-ref>ivoa:string</vodml-ref>
1032 </datatype>
1033 <multiplicity>
1034 <minOccurs>0</minOccurs>
1035 <maxOccurs>-1</maxOccurs>
1036 </multiplicity>
1037 </attribute>
1038 <collection>
1039 <vodml-id>dataset.Curation.contact</vodml-id>
1040 <name>contact</name>
1041 <description>
1042 Contact information of the person/entity responsible for the content of the dataset. We recommend using a generic 'helpdesk' type contact rather than individuals whose information may more easily become obsolete. (RM:Curation.Contact)
1043
1044 </description>
1045 <datatype>
1046 <vodml-ref>ds:dataset.Contact</vodml-ref>
1047 </datatype>
1048 <multiplicity>
1049 <minOccurs>0</minOccurs>
1050 <maxOccurs>1</maxOccurs>
1051 </multiplicity>
1052 </collection>
1053 </objectType>
1054
1055 <objectType>
1056 <vodml-id>dataset.Contact</vodml-id>
1057 <name>Contact</name>
1058 <description>
1059 Contact information for a person or entity.
1060 </description>
1061 <attribute>
1062 <vodml-id>dataset.Contact.name</vodml-id>
1063 <name>name</name>
1064 <description>
1065 Name of the contact or entity. (RM:Contact.Name)
1066
1067 </description>
1068 <datatype>
1069 <vodml-ref>ivoa:string</vodml-ref>
1070 </datatype>
1071 <multiplicity>
1072 <minOccurs>1</minOccurs>
1073 <maxOccurs>1</maxOccurs>
1074 </multiplicity>
1075 </attribute>
1076 <attribute>
1077 <vodml-id>dataset.Contact.email</vodml-id>
1078 <name>email</name>
1079 <description>
1080 E-mail address of the contact. (RM:Contact.Email)
1081 </description>
1082 <datatype>
1083 <vodml-ref>ivoa:string</vodml-ref>
1084 </datatype>
1085 <multiplicity>
1086 <minOccurs>0</minOccurs>
1087 <maxOccurs>1</maxOccurs>
1088 </multiplicity>
1089 </attribute>
1090 </objectType>
1091
1092 <objectType>
1093 <vodml-id>dataset.Characterisation</vodml-id>
1094 <name>Characterisation</name>
1095 <description>
1096 This Characterisation object is a direct extension of the Characterisation object from the IVOA Characterisation Data Model Standard. This provides a local object which may be contained in a 'composition' relation to other objects of this model (specifically ObsDataset). This object may be extended and/or modified by specific Dataset models as needed.
1097 Characterisation provides a broad scale description of the coordinate space occupied by the dataset in each of the axis domains. This includes axes not directly represented in the dataset 'data', for example, the Time axis of a 2D special image. As such, there is a strong correlation between Characterisation and Data objects. In some cases, the values may be directly derived from the Data, in others, they provide supporting metadata about the broader domain. For example, the Accuracy fields in Characterisation represent typical accuracy for the dataset, while those within Data provide per-data-point errors.
1098 </description>
1099 <extends>
1100 <vodml-ref>char:Char</vodml-ref>
1101 </extends>
1102 </objectType>
1103
1104 <objectType>
1105 <vodml-id>dataset.Derived</vodml-id>
1106 <name>Derived</name>
1107 <description>
1108 The Derived (short for Derived Data) object holds derived information obtained by evaluating or analyzing the contents of the dataset. The specific content of this object is strongly dependent on the specific type of dataset, so we provide a generic model which may be specialized in other models to define elements appropriate for that type of dataset.
1109
1110 The primary purpose of this object is to provide a common framework in which specific information may be placed to aid in discovery and filtering of datasets in various access protocols.
1111
1112 </description>
1113 <collection>
1114 <vodml-id>dataset.Derived.derivedElement</vodml-id>
1115 <name>derivedElement</name>
1116 <description>
1117 Collection of zero or more DerivedElement objects, each of which provides a specific quantity obtained by analyzing the dataset content.
1118
1119 </description>
1120 <datatype>
1121 <vodml-ref>ds:dataset.DerivedElement</vodml-ref>
1122 </datatype>
1123 <multiplicity>
1124 <minOccurs>0</minOccurs>
1125 <maxOccurs>-1</maxOccurs>
1126 </multiplicity>
1127 </collection>
1128 </objectType>
1129
1130 <objectType abstract="true">
1131 <vodml-id>dataset.ObsDataset</vodml-id>
1132 <name>ObsDataset</name>
1133 <description>
1134 Abstract object extending Dataset with metadata relevant to datasets derived from Observations.
1135
1136 </description>
1137 <extends>
1138 <vodml-ref>ds:dataset.Dataset</vodml-ref>
1139 </extends>
1140 <attribute>
1141 <vodml-id>dataset.ObsDataset.calibLevel</vodml-id>
1142 <name>calibLevel</name>
1143 <description>
1144 High level classification for the calibration level of the particular dataset as a whole. The calibration level concept conveys to the user information on how much data reduction/processing has been applied to the data. It is up to the data providers to consider how to map their own internal classification to the scale defined here.
1145 Scale:
1146 * 0 - Raw instrumental data, in a proprietary or internal data-provider defined format.
1147 * 1 - Instrumental data in a standard format (FITS, VOTable, etc )
1148 * 2 - Calibrated, science ready data with the instrument signature removed.
1149 * 3 - Enhanced data products like mosaics, resampled or drizzled images, or heavily processed survey fields. Level 3 data products may represent the combination of data from multiple primary observations.
1150
1151 </description>
1152 <datatype>
1153 <vodml-ref>ivoa:integer</vodml-ref>
1154 </datatype>
1155 <multiplicity>
1156 <minOccurs>0</minOccurs>
1157 <maxOccurs>1</maxOccurs>
1158 </multiplicity>
1159 </attribute>
1160 <collection>
1161 <vodml-id>dataset.ObsDataset.characterisation</vodml-id>
1162 <name>characterisation</name>
1163 <description>
1164 Characterisation provides a 'characteristic' view of the coordinate space for the dataset as a whole.
1165 </description>
1166 <datatype>
1167 <vodml-ref>ds:dataset.Characterisation</vodml-ref>
1168 </datatype>
1169 <multiplicity>
1170 <minOccurs>1</minOccurs>
1171 <maxOccurs>1</maxOccurs>
1172 </multiplicity>
1173 </collection>
1174 <collection>
1175 <vodml-id>dataset.ObsDataset.derived</vodml-id>
1176 <name>derived</name>
1177 <description>
1178 Provides a high level summary of certain properties of the dataset. Its primary purpose is to support high level filtering of datasets during data discovery.
1179
1180 </description>
1181 <datatype>
1182 <vodml-ref>ds:dataset.Derived</vodml-ref>
1183 </datatype>
1184 <multiplicity>
1185 <minOccurs>0</minOccurs>
1186 <maxOccurs>1</maxOccurs>
1187 </multiplicity>
1188 </collection>
1189 <reference>
1190 <vodml-id>dataset.ObsDataset.target</vodml-id>
1191 <name>target</name>
1192 <description>
1193 Reference to a BaseTarget object from Observation. Provides metadata describing the target of the observation.
1194 </description>
1195 <datatype>
1196 <vodml-ref>ds:experiment.BaseTarget</vodml-ref>
1197 </datatype>
1198 <multiplicity>
1199 <minOccurs>1</minOccurs>
1200 <maxOccurs>1</maxOccurs>
1201 </multiplicity>
1202 </reference>
1203 <reference>
1204 <vodml-id>dataset.ObsDataset.proposal</vodml-id>
1205 <name>proposal</name>
1206 <description>
1207 Reference to Proposal object from Observation. This object provides metadata identifying any proposal related to the observation which produced the dataset.
1208 </description>
1209 <datatype>
1210 <vodml-ref>ds:experiment.Proposal</vodml-ref>
1211 </datatype>
1212 <multiplicity>
1213 <minOccurs>0</minOccurs>
1214 <maxOccurs>1</maxOccurs>
1215 </multiplicity>
1216 </reference>
1217 <reference>
1218 <vodml-id>dataset.ObsDataset.obsConfig</vodml-id>
1219 <name>obsConfig</name>
1220 <description>
1221 Reference to ObsConfig object from Observation. This object provides some high-level metadata related to the observation configuration.
1222 </description>
1223 <datatype>
1224 <vodml-ref>ds:experiment.ObsConfig</vodml-ref>
1225 </datatype>
1226 <multiplicity>
1227 <minOccurs>0</minOccurs>
1228 <maxOccurs>1</maxOccurs>
1229 </multiplicity>
1230 </reference>
1231 <reference>
1232 <vodml-id>dataset.ObsDataset.coordSys</vodml-id>
1233 <name>coordSys</name>
1234 <description>
1235 Zero or more references to coordinate system defintions associated with the dataset. Since multiple data products may contibute to the content of a dataset, this element provides convenient, high-level access to definitions which may be distributed among lower-level objects.
1236
1237 </description>
1238 <datatype>
1239 <vodml-ref>stc:AstroCoordSystem</vodml-ref>
1240 </datatype>
1241 <multiplicity>
1242 <minOccurs>0</minOccurs>
1243 <maxOccurs>-1</maxOccurs>
1244 </multiplicity>
1245 </reference>
1246 </objectType>
1247
1248 <objectType abstract="true">
1249 <vodml-id>dataset.DerivedElement</vodml-id>
1250 <name>DerivedElement</name>
1251 <description>
1252 Abstract base for defining derived data elements. Typically, models for specific data products would extend this object to define various elements appropriate for that model. For example, the Spectrum model could define signal-to-noise ratio (SNR), or TimeSeries could define period, or variability. We put no restriction on the DerivedElement content since the result could be a simple value or a complex object. However, it is recommended that extensions be simple and compact in keeping with the primary intent of use in data discovery.
1253
1254 </description>
1255 </objectType>
1256
1257 <objectType>
1258 <vodml-id>dataset.DerivedScalar</vodml-id>
1259 <name>DerivedScalar</name>
1260 <description>
1261 Simple extension of DerivedElement class which can serve many use cases. Usages of this object in other models to define specific elements should explicitly define the element name, and the process by which the value is determined.
1262
1263 </description>
1264 <extends>
1265 <vodml-ref>ds:dataset.DerivedElement</vodml-ref>
1266 </extends>
1267 <attribute>
1268 <vodml-id>dataset.DerivedScalar.name</vodml-id>
1269 <name>name</name>
1270 <description>
1271 Name identifying the derived element.
1272 </description>
1273 <datatype>
1274 <vodml-ref>ivoa:string</vodml-ref>
1275 </datatype>
1276 <multiplicity>
1277 <minOccurs>1</minOccurs>
1278 <maxOccurs>1</maxOccurs>
1279 </multiplicity>
1280 </attribute>
1281 <attribute>
1282 <vodml-id>dataset.DerivedScalar.value</vodml-id>
1283 <name>value</name>
1284 <description>
1285 Value of the derived element.
1286
1287 </description>
1288 <datatype>
1289 <vodml-ref>ivoa:quantity.Quantity</vodml-ref>
1290 </datatype>
1291 <multiplicity>
1292 <minOccurs>1</minOccurs>
1293 <maxOccurs>1</maxOccurs>
1294 </multiplicity>
1295 </attribute>
1296 </objectType>
1297
1298 </package>
1299
1300 </vo-dml:model>

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