forked from ivoa/mapping-vodml
-
Notifications
You must be signed in to change notification settings - Fork 0
/
metadata.yaml
136 lines (134 loc) · 3.95 KB
/
metadata.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
---
title: Mapping Data Models to VOTable
name: MappingDMtoVOTable
version: '1.0-201506xx'
# supported types: WD, PR, NOTE, REC, DERR
# custom types may be provided by creating files
# in `style/messages`, following the examples.
type: WD
date: '2016-08-30'
dateCode: '20160830'
author:
- name: Gerard Lemson
url: http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/GerardLemson
- name: Omar Laurino
url: http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/OmarLaurino
- name: Patrick Dowler
- name: Markus Demleitner
- name: Matthew Graham
- name: Jesus Salgado
editor:
- name: Omar Laurino
- name: Gerard Lemson
group: Data Models
previousVersion:
- ver: xx
url: http://www.ivoa.net/documents/xx
abstract: |
Data providers and curators provide a great deal of metadata with their data
files: this metadata is invaluable for users and for Virtual Observatory
software developers. In order to be interoperable, the metadata must refer
to common Data Models. This specification defines a scheme for annotating
VOTable instances in a standard, consistent, interoperable fashion, so that
each piece of metadata can unambiguously refer to the correct Data Model
element it expresses, assuming there is a suitable data model.
With this specification, data providers can
unambiguously and completely represent Data Model instances in the VOTable
format, and clients can build *faithful* representations of such instances.
The mapping is operated through opaque, portable strings.
references:
- id: vodml
type: article
author:
- family: Lemson
given: Gerard
title: 'VO - DML: a consistent modeling language for IVOA data models'
issued:
year: 2015
month: 10
day: 10
URL: 'http://www.ivoa.net/documents/VODML/20151010/index.html'
- id: usages
type: article
author:
- family: Graham
given: Matthew
title: 'UTypes: current usages and practices in the IVOA'
issued:
year: 2013
month: 2
day: 13
URL: 'http://www.ivoa.net/documents/Notes/UTypesUsage/index.html'
- id: fits
type: article
author:
- family: Thomas
given: Brian
- family: Jenness
given: Tim
- family: Economou
given: Frossie
title: "Learning from FITS: Limitations in use in modern astronomical research"
issued:
year: 2015
month: 09
journal: "Astronomy and Computing"
URL: "http://adsabs.harvard.edu/abs/2015A%26C....12..133T"
- id: votable
type: article
author:
- family: Ochsenbein
given: Francois
title: 'VOTable Format Definition'
issued:
year: 1900
month: xxxx
day: xxxx
URL: 'http://www.ivoa.net/documents/xxxx'
- id: simdm
title: 'Simulation DM spec'
issued:
year: 1900
- id: chardm
title: 'Characterization DM spec'
issued:
year: 1900
- id: spectrumdm
title: 'Spectrum DM spec'
issued:
year: 1900
- id: stcdm
title: 'STC spec'
issued:
year: 1900
- id: orm
title: 'ORM mapping tools: Hibernate, JPA spec'
issued:
year: 1900
- id: ucd
title: 'UCDs'
issued:
year: 1900
- id: stc_in_vot
title: 'STC in VOTable note'
issued:
year: 1900
- id: skos
title: 'PR on use of SKOS vocabularies in IVOA'
issued:
year: 1900
- id: ids
title: 'IVOA Identifiers'
issued:
year: 1900
- id: vourp
title: 'VOURP'
issued:
year: 1900
- id: ivoid
title: 'IVOA Identifiers'
issued:
year: 1900
link-citations: true
linkReferences: true
---