From 4d24c86b9f21334e82fd8ca95583a6f446755137 Mon Sep 17 00:00:00 2001 From: Mireille Louys Date: Wed, 7 May 2025 14:03:17 +0200 Subject: [PATCH] typo corrections in biblio references --- ObsCore.tex | 93 +++++++++++++++++++++++++++-------------------------- obscore.bib | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 135 insertions(+), 46 deletions(-) create mode 100644 obscore.bib diff --git a/ObsCore.tex b/ObsCore.tex index a4f2397..8f6c780 100644 --- a/ObsCore.tex +++ b/ObsCore.tex @@ -18,12 +18,12 @@ {Fran\c{c}ois Bonnarel} \author{Alberto Micol} -\editor{Mireille Louys} -\editor{Doug Tody} -\editor[http://www.ivoa.net/twiki/bin/view/IVOA/PatrickDowler]{Patrick Dowler} -\editor{Daniel Durand} + \editor{Mireille Louys} + \editor{Doug Tody} + \editor[http://www.ivoa.net/twiki/bin/view/IVOA/PatrickDowler]{Patrick Dowler} + \editor{Daniel Durand} -% \previousversion[????URL????]{????Concise Document Label????} +% \previousversion[????URL????]{ObsCore} \previousversion[http://www.ivoa.net/Documents/ObsCore/20161004/PR-ObsCore-v1.1-20161004.pdf]{R-ObsCore-v1.1-20161004.pdf} \previousversion[https://www.ivoa.net/documents/ObsCore/20111028/REC-ObsCore-v1.0-20111028.pdf]{REC-ObsCore-v1.0-20111028.pdf} @@ -47,7 +47,7 @@ reference to more complete data models such as Characterisation DM, Spectrum DM or Simple Spectral Line Data Model (SSLDM). -ObsCore shares a large set of common concepts with DataSet Metadata Data Model \cite{CITATIONCre16l1036} which binds +ObsCore shares a large set of common concepts with DataSet Metadata Data Model \citep{wd:DatasetDM} which binds together most of the data model concepts from the above models in a comprehensive and more general frame work. This current specification on the contrary provides guidelines for implementing these concepts using the TAP protocol @@ -96,13 +96,13 @@ \section{Introduction} The ObsCore data model is focused on describing the core metadata common to most data products distributed for astronomical observations.~ It is the common basis that helps to search and discover datasets across various VO compatible archives via a customized TAP protocol: ObsTAP. ObsCore also provides the core data model for discovery and -description of specific types of astronomical data (e.g., images and spectra) via the ``typed'' VO data access +description of specific types of astronomical data (e.g., images and spectra) via the 'typed' VO data access protocols. These type-specific protocols may extend ObsCore to more fully describe specific types of data, but the intent is that all VO data access protocols share the same core description of the data. In order to take into account the pixelated data such as images, data cubes, and time series as well, this version makes explicit the nature and length of the dataset axes as defined in the Characterisation data model -\cite{CITATIONIVO07l1036}. These allow covering the requirements for axes length (as a number of bins) expressed in +\citep{2008ivoa.spec.0325L}. These allow covering the requirements for axes length (as a number of bins) expressed in added uses-cases in Appendix A, sections A.3 for data cubes, A.4 for time series, A.5 for event lists. In addition it corrects a few errors in the description of data model items found in version 1.0. @@ -140,7 +140,7 @@ \subsection{Second building block: the Table Access Protocol (TAP)} tables. TAP allows a client to (step 1) browse through the various tables and columns (names, units, etc.) in an archive to collect the information necessary to pose a query, then (step 2) actually perform a table query. The Table Access Protocol (TAP) specification was developed and reached recommendation status in March 2010 -\cite{CITATIONTAPl1036}. +\citep{2010ivoa.spec.0327D}. \subsection{The goal of this effort} Building on the work done on data models and TAP, it becomes possible to define a standard service protocol to expose @@ -231,9 +231,9 @@ \subsection{The goal of this effort} launched at the first Data Model WG meeting held in Cambridge, UK at the IVOA meeting in May 2003. The first Observation data model was sketched out relying on some key concepts: Dataset, Identification, Curation, physical Characterisation and Provenance (either instrumental or software). A description of the early stages of this -development can be found in \cite{CITATIONCharDM2007l1036} (Observation IVOA note). Some of these concepts have already -been elaborated in existing data models, namely the Spectrum data model \cite{CITATIONJon07l1036} for general items -such as dataset identification and curation, and the Characterisation data model \cite{CITATIONIVO07l1036a} for the +development can be found in \citep{IVOANote:DMObservation} (Observation IVOA note). Some of these concepts have already +been elaborated in existing data models, namely the Spectrum data model \citep{2011ivoa.spec.1120M} for general items +such as dataset identification and curation, and the Characterisation data model \citep{2008ivoa.spec.0325L} for the description of the physical axes and properties of an observation, such as coverage, resolution, sampling, and accuracy. The Core Components data model reuses the relevant elements from those models. Generalization of the observational model to support data from theoretical models (e.g., synthetic spectra) is possible but is not addressed @@ -296,8 +296,8 @@ \subsection{The goal of this effort} describe time metadata. Details on the ObsCoreDM axes definitions are available in the Characterisation data model standard document -\cite{CITATIONIVO07l1036a}. The hypertext documentation of the model is available on the IVOA web site under the -ObsCore wiki page http://www.ivoa.net/internal/IVOA/ObsDMCoreComponents/ . +\citep{2008ivoa.spec.0325L}. The hypertext documentation of the model is available on the IVOA web site under the +ObsCore wiki page \url{http://www.ivoa.net/internal/IVOA/ObsDMCoreComponents/} . \subsection[Main Concepts of the ObsCore Data Model]{Main Concepts of the ObsCore Data Model} The ObsCore data model is the result of the analysis of the data discovery use cases introduced in Chapter 2. Two sets @@ -358,7 +358,7 @@ \subsection{Specific Data Model Elements} In order to support the global data discoverability and accessibility requirements, some new concepts previously not covered by any other data model have to be introduced. This section describes those, which are: the data product type, a classification of the various levels of calibration and processing applied to the data, the file content and format -enriched and extended from the concept described in the SSA protocol\cite{CITATIONTod2012l1036}. In addition, a +enriched and extended from the concept described in the SSA protocol\citep{2012ivoa.spec.0210T}. In addition, a clarification of how the terms Observation and Data Product are used in the ObsTAP context is provided as well as a discussion for composed products. @@ -571,7 +571,7 @@ \section{Implementation of ObsCore in a TAP Service} ivoa.ObsCore & instrument\_name & adql:VARCHAR & & \\\hline \end{longtable} %\end{center} -\label{bkm:Ref286578377}Table T4. List of the minimal set of data model fields to +\label{tab:4}Table T4. List of the minimal set of data model fields to implement for an ObsTAP service. See tables of Appendix C for the full description of the TAP\_SCHEMA.columns table. %\end{table} @@ -649,7 +649,7 @@ \subsection{Observation Identifier (obs\_id)} Values in the obs\_id column must not be NULL. \subsection{Publisher Dataset Identifier (obs\_publisher\_did)} -The obs\_publisher\_did column contains the IVOA dataset identifier \cite{CITATIONPla07l1036} for the published data +The obs\_publisher\_did column contains the IVOA dataset identifier \citep{2007ivoa.spec.0314P} for the published data product. This value must be unique within the namespace controlled by the dataset publisher (data center). The value will also be globally unique since each publisher has a unique IVOA registered publisher ID. The same dataset may however have more than one publisher dataset identifier if it is published in more than one location; the creator DID, @@ -668,7 +668,7 @@ \subsection{Access URL (access\_url)} forced to store it statically in the database). More details are given on the use of CLOB data types for the TAP SCHEMA in the TAP Standard document -\cite{CITATIONTAPl1036}, section 2.5 Table upload. +\citep{2010ivoa.spec.0327D}, section 2.5 Table upload. Access URLs are not guaranteed to remain valid and unchanged indefinitely. To access a specific data product after a period of time (e.g., days or weeks) a query should be performed (e.g., using obs\_publisher\_did) to obtain a fresh @@ -679,7 +679,7 @@ \subsection{Access Format (access\_format)} data model field is important both for data discovery and for the client to evaluate whether it will be able to actually use the data product if downloaded. -MIME types are often used to specify file formats in existing protocols such as HTTP\cite{CITATIONIntl1036}. However +MIME types are often used to specify file formats in existing protocols such as HTTP \citep{std:MIME_types}. However when dealing with astronomical observations as in ObsTAP services, more information about the format of the data is required than can be specified by conventional MIME types. For instance we might want to distinguish between various formats like multi-extension FITS (e.g. for CCD mosaic instruments or MUSE IFU data), or ASDM (e.g. for ALMA or other @@ -728,7 +728,7 @@ \subsection{Access Format (access\_format)} application/x-votable+xml; content=datalink & datalink & A datalink response containing links to data sets or services attached to the current dataset\\\hline \end{tabular} %\end{center} -\label{bkm:Ref286578377}Table T5: TODO: label from orig doc +\label{tab:5}Table T5: TODO: label from orig doc %\end{table} The value of access\_format should be a MIME type, either a standard MIME type, an extended MIME type from the above table, or a new custom MIME type defined by the data provider. The short names suggested here are not used directly by @@ -740,7 +740,7 @@ \subsection{Access Format (access\_format)} Observational datasets consisting of multiple instrument-specific files may be exposed in formats like application/x-directory, application/x-tar or application/x-tar-gzip. Details of the package content and how to access -inner data products are described in the IVOA Data Link specification\cite{CITATIONPat15l1036}. See the example +inner data products are described in the IVOA Data Link specification \citep{2015ivoa.spec.0617D}. See the example presented in section \ref{bkm:Ref303703299} . Compression is inherent in some file formats, e.g., ZIP or JPEG. In other formats it is optional and is indicated by @@ -790,7 +790,7 @@ \subsection{Spatial Coverage (s\_region)} We specify the data type as adql:VARCHAR so that users can specify spatial queries using a single column and in a limited number of ways. If implemented in TAP 1.0, and included in the select list of the query, the output is always -an STC-S string as described in \cite{CITATIONTAPl1036} [section 6]. In the WHERE clause, the s\_region column can be +an STC-S string as described in \citep{2010ivoa.spec.0327D} [section 6]. In the WHERE clause, the s\_region column can be used with the ADQL geometry functions (INTERSECTS, CONTAINS) to specify conditions; the service will generally have to translate these into native SQL that enforces the same conditions or a suitable approximation. Implementers may approximate the spatial query conditions by translating the INTERSECTS and CONTAINS function calls in the query. @@ -861,7 +861,7 @@ \subsection{Polarization states (pol\_states)} See section \ref{bkm:Ref482802717} for details. \subsection{Observable Axis Description (o\_ucd)} -The o\_ucd column specifies a UCD \cite{CITATIONPre07l1036} describing the nature of the observable within the data +The o\_ucd column specifies a UCD \citep{2007ivoa.spec.0402P} describing the nature of the observable within the data product. The observable is the measured quantity, for a sampled dataset, such as for example photon counts or flux density stored in the pixel value within an image. Often for optical astronomical images the value would be phot.count; for fully flux calibrated data a value such as phot.flux.density (usually specified in Jy) would be used. Any valid UCD @@ -895,7 +895,7 @@ \subsection{Axes lengths (s\_xel1, s\_xel2, em\_xel, t\_xel, pol\_xel)} \subsection{Additional Columns} \label{bkm:Ref421295535}\label{bkm:Ref421297012}Service providers may include additional columns in the ivoa.ObsCore table to expose additional metadata. These columns must be described in the TAP\_SCHEMA.columns table and in the output -from the VOSI-tables resource \cite{CITATIONVOSI2010l1036}. Users may access these columns by examining the column +from the VOSI-tables resource \citep{2011ivoa.spec.0531G}. Users may access these columns by examining the column metadata for individual services and then using them explicitly in queries or by selecting all columns in the query (e.g. ``select * from ivoa.ObsCore ...'' in an ADQL query). In order to provide homogeneity in the keywords used as optional fields, we recommend where possible to use the items defined in the full data model (Appendix B) and flagged @@ -904,7 +904,7 @@ \subsection{Additional Columns} \section{Registering an ObsTAP Service} \label{sec:obstap-register}The standard identifier for this version of the ObsCore model now follows the IVOA Identifiers -v2.0 specification \cite{CITATIONDem16l1036} and should be ivo://ivoa.net/std/ObsCore\#core-1.1 +v2.0 specification \citep{2016ivoa.spec.0523D} and should be ivo://ivoa.net/std/ObsCore\#core-1.1 The ObsCore data model will be registered using this identifier in the StandardsRegExt (standards registry extension) definition. @@ -913,7 +913,7 @@ \section{Registering an ObsTAP Service} all services that accept ObsCore queries. This can be done in any registry by using the keyword ``ObsCore'' to describe the service. In addition, fine-grained registries may include the complete VODataService table set description. -The TAPRegExt (Table Access Protocol registry extension) \cite{CITATIONDem15l1036} provides a mechanism (the +The TAPRegExt (Table Access Protocol registry extension) \citep{2012ivoa.spec.0827D} provides a mechanism (the `dataModel' element) to list one or more data models that are supported by a TAP service. The data model support uses the ivo standard identifier (above). One or more `dataModel' elements may be included as child elements of the {}`capability' element describing the TAP service which is the `capability' element with the following attributes: @@ -940,6 +940,7 @@ \section{Registering an ObsTAP Service} available and contains all the mandatory columns\footnote{ Additional columns with optional ObsCore Utypes, Utypes from other data models, or no Utypes at all are allowed}. + \section{Changes from Previous Versions} Errata on REC 2017 May 09: @@ -993,7 +994,7 @@ \section{Changes from Previous Versions} % NOTE: IVOA recommendations must be cited from docrepo rather than ivoabib % (REC entries there are for legacy documents only) -\bibliography{ivoatex/ivoabib,ivoatex/docrepo} +\bibliography{ivoatex/docrepo, ivoatex/ivoabib, obscore} \appendix \section{Use Cases in detail} @@ -1006,7 +1007,7 @@ \section{Use Cases in detail} below. Please note that for most science cases, a full TAP implementation is required for them to work as well as STC regions -support. \cite{CITATIONSTCl1036} +support. \citep{2009ivoa.rept.1030R} Some of the use-cases listed by the committee require advanced functionalities like ``search by type'', ``query from an input list'', and have not been fully developed here. @@ -1616,7 +1617,7 @@ \section{ObsCore Data Model Detailed Description} \subsection{Observation Information} This class is a place holder that gathers all metadata relative to an observed and distributed dataset. It points to -existing classes of Spectrum DM and types from VODataService \cite{CITATIONVodatal1036} . +existing classes of Spectrum DM and types from VODataService \citep{2010ivoa.spec.1202P} . \subsubsection{Data Product Type (dataproduct\_type)} The model defines a data product type attribute for the Observation Class. It is the type of the observation product @@ -1711,14 +1712,14 @@ \subsubsection{Collection name (obs\_collection)} \subsubsection{Creation date (obs\_creation\_date)} The date when the dataset was created. This is a time stamp, adopting the VO format regularly used in protocols and -defined in DALI \cite{CITATIONPat13l1036} section 3.1.2 , i.e a restriction of the ISO 8601 format without the Z tag , +defined in DALI \citep{2013ivoa.spec.1129D} section 3.1.2 , i.e a restriction of the ISO 8601 format without the Z tag , as defined in FITS standard.(``YYYY-MM-DDThh:mm:ss''). \subsubsection{Creator name (obs\_creator\_name)} The name of the institution or entity which created the dataset. \subsubsection{Dataset Creator Identifier (obs\_creator\_did)} -IVOA dataset identifier given by its creator. See definition in the SpectrumDM specification \cite{CITATIONJon07l1036} +IVOA dataset identifier given by its creator. See definition in the SpectrumDM specification \citep{2007ivoa.spec.1029M} \subsection{Curation metadata} The Curation class inherits from the Spectrum data model and VOResource concepts too. The various attributes for @@ -1729,7 +1730,7 @@ \subsubsection{Publisher Dataset ID (obs\_publisher\_did)} identifier given by the creator of the dataset. (new reduction, new calibration, etc..). The corresponding Utype mapped from the Spectrum DM is Curation.PublisherDID and relates to the same definition. -This field contains the IVOA dataset identifier \cite{CITATIONPla07l1036} for the published data product. This value +This field contains the IVOA dataset identifier \citep{2007ivoa.spec.0314P} for the published data product. This value must be unique within the namespace controlled by the dataset publisher (data center). It will also be globally unique since each publisher has a unique registered publisher ID. The same dataset may however have more than one publisher dataset identifier if it is published in more than one location (the creator DID, if defined for the given dataset, @@ -1740,11 +1741,11 @@ \subsubsection{Publisher Identifier (publisher\_id)} \subsubsection{Bibliographic Reference (bib\_reference)} URL or bibcode for documentation. This is a forward link to major publications which reference the dataset. This is -re-used from the SSA definition. See \cite{CITATIONTod2012l1036a} in section 4.2.5.6 about Curation Metadata. +re-used from the SSA definition. See \citep{2012ivoa.spec.0210T} in section 4.2.5.6 about Curation Metadata. \subsubsection{Data Rights (data\_rights)} This parameter allows mentioning the availability of a dataset. Possible values are: public, secure, or proprietary as -stated in the VODataService recommendation\cite{CITATIONVodatal1036}. +stated in the VODataService recommendation\citep{2010ivoa.spec.1202P}. \subsubsection{Release Date (obs\_release\_date)} This is a new attribute added to the original Curation class inherited from the Spectrum Data Model. @@ -1756,7 +1757,7 @@ \subsubsection{Release Date (obs\_release\_date)} \subsection{Data Access} The data format as well as the URL to access the dataset is provided by the Access Class inherited from the SSA Utype -list \cite{CITATIONTod2012l1036a}. Also included is an attribute for the estimated size of the data file. +list \citep{2012ivoa.spec.0210T}. Also included is an attribute for the estimated size of the data file. \subsubsection{Access Reference (access\_url)} This item (Access.Reference) contains a URL that can be used to download the data product (as a file of some sort). @@ -1782,7 +1783,7 @@ \subsection{Description of physical axes: Characterisation classes} As mentioned in the use-cases, selection criteria for an observation depend on the physical axes contained in the dataset especially the position, band, time, and the type of observed quantity that we call ``observable'' in the data model. The observable axis can cover various types of flux but also velocity, etc. Such a description was tackled in -the IVOA Characterisation data model \cite{CITATIONIVO07l1036} from which we re-use mainly the first and second levels +the IVOA Characterisation data model \citep{2008ivoa.spec.0325L} from which we re-use mainly the first and second levels of details except for the spatial coverage where the support region (level 3) is used too. \subsubsection{Spatial axis} @@ -1807,7 +1808,7 @@ \subsubsection{Spatial axis} \item Coordinate system \end{itemize} The coordinate system defined in the Characterisation DM is based on the STC:Coordsys class. The model in principle -supports all kind of coordinate systems defined in the STC reference list \cite{CITATIONSTCl1036}. However, the ObsTAP +supports all kind of coordinate systems defined in the STC reference list \citep{2009ivoa.rept.1030R}. However, the ObsTAP implementation of the model mandates that queries expressed in ICRS should be supported in an ObsTAP service. This allows a general query to be sent to multiple archives or data centers, but requires some interpretation /conversion of coordinates at the server side. Still this is efficient for the large data discovery strategy we need to provide. Data @@ -1826,7 +1827,7 @@ \subsubsection{Spatial axis} whose short names in the ObsCore table are s\_ra and s\_dec. We assume that ObsTAP implements these coordinates in the ICRS system. -Using other coordinate systems as defined in STC \cite{CITATIONSTCl1036} and re-used in the Characterisation DM can be +Using other coordinate systems as defined in STC \citep{2009ivoa.rept.1030R} and re-used in the Characterisation DM can be considered in client applications in charge of the coordinate translations. \paragraph{The covered region} @@ -1899,7 +1900,7 @@ \subsubsection{Spectral axis} The data model distinguishes the various flavors of this axis using the UCD attached to it, Char.SpectralAxis.ucd named as em\_ucd in ObsTAP optional fields. Possible values for this UCD are defined in the Spectrum DM -\cite{CITATIONJon07l1036} in section 4.1. +\citep{2011ivoa.spec.1120M} in section 4.1. Depending on the UCD used to specify the axis, the ObsCore model allows to describe the spectral coordinates in a relevant unit, corresponding to the spectral quantity, and specified in the model in Char.SpectralAxis.unit (em\_unit) @@ -2019,13 +2020,13 @@ \subsubsection{Nature of the observed quantity (o\_ucd)} more general axis: the ``observable axis'' that can be either flux or any other quantity, the nature of which is specified by the UCD attached to this axis. -The possible UCD values are part of the UCD1+ vocabulary \cite{CITATIONPre07l1036} . One can find simple flux classes +The possible UCD values are part of the UCD1+ vocabulary \citep{2007ivoa.spec.0402P} . One can find simple flux classes like: phot.flux, phot.flux.density, phot.count, phot.mag, or more complex combinations such as: phot.flux.density;phys.polarization.stokes Various possibilities have been gathered at the following URL: -http://www.ivoa.net/internal/IVOA/ObsTap/ListForObservable25Oct2010.pdf +\url{http://www.ivoa.net/internal/IVOA/ObsTap/ListForObservable25Oct2010.pdf} which provides a (non-exhaustive) list of possible triplets (observable name, UCD, units) for various observables data providers may want to describe in their archive. The units used to encode values of the Observable quantity are @@ -2036,7 +2037,7 @@ \subsubsection{Calibration status on observable (Flux or other) (o\_calib\_statu This describes the calibration applied on the Flux observed (or other observable quantity). It is a string to be selected in \{absolute, relative, normalized, any\} as defined in the SSA specification -\cite{CITATIONTod2012l1036a} in section 4.1.2.10. +\citep{2012ivoa.spec.0210T} in section 4.1.2.10. This list can be extended or updated for instance using an extension mechanism similar to the definition of new UCDs in the IVOA process, following the feedback from implementations of ObsTAP services. @@ -2059,7 +2060,7 @@ \subsubsection{List of polarization states (pol\_states)} In the Obs/TAP implementation the column name is pol\_states.It is a mandatory field with NULL value allowed if no polarization applies. Otherwise it contains a list of polarization labels inspired from the FITS specification. See -Table 7 in FITS WCS Paper 1 \cite{CITATIONGrel1036} . Labels are combined using symbols from the \{I Q U V RR LL RL LR +Table 7 in FITS WCS Paper 1 \citep{2002A&A...395.1061G} . Labels are combined using symbols from the \{I Q U V RR LL RL LR XX YY XY YX POLI POLA\} set and separated by a / character. A leading / character must start the list and a trailing / character must end it. It should be ordered following the above list, compatible with the FITS list table for polarization definition. @@ -2076,7 +2077,7 @@ \subsubsection{List of polarization states (pol\_states)} selects only datasets containing Y polarization state. -See A. Richards IVOA Note for the context of polarization data\cite{CITATIONRic10l1036}. +See A. Richards 's IVOA Note \citep{IVOANote:Polarisation} for the context of polarization data . \subsubsection{Number of polarization elements (pol\_xel)} pol\_xel specifies the number of different polarization states present in the data. Its Utype in the Obscore DM is @@ -2115,7 +2116,7 @@ \subsection{Provenance} \subsubsection{Facility (facility\_name)} The Facility class codes information about the observatory or facility used to collect the data. In this model we define one attribute of Utype Provenance.ObsConfig.facility.name which re-uses the Facility concept defined in the -VODataService specification\cite{CITATIONVodatal1036}. +VODataService specification \citep{2010ivoa.spec.1202P}. For combined observations stemming from multiple facilities the name may contain a list of comma separated strings, or the word {\textquotedbl}Many{\textquotedbl}; if the list is too long, as defined in the VODataservice specification. @@ -2189,7 +2190,7 @@ \subsection{Implementing a package of multiple data products} \item For classes referencing one other class, we use the name of the reference or role, and not the one of the pointed class. \end{itemize} -The meaning of the various columns corresponds to the definitions of the TAP IVOA standard \cite{CITATIONTAPl1036}. See +The meaning of the various columns corresponds to the definitions of the TAP IVOA standard \citep{2010ivoa.spec.0327D}. See section 2.6.3 for the description of columns attributes. As a reminder, the last three columns are implementation oriented: diff --git a/obscore.bib b/obscore.bib new file mode 100644 index 0000000..d68ef10 --- /dev/null +++ b/obscore.bib @@ -0,0 +1,88 @@ +% not in docrepo.bib +% http://www.iana.org/assignments/media-types/ + +@Misc{std:MIME_types, + author = {The Internet Assigned Numbers Authority}, + title = {MIME Media Types}, + howpublished = {IANA standard}, + organization = {{IANA}}, + url = {http://www.iana.org/assignments/media-types/}, + year = 2007 +} + +@Misc{IVOANote:Polarisation, + author = {A, M. S. Richards and F. Bonnarel}, + title = {Note on the description of polarization data +Version 1.0}, + howpublished = {IVOA Note}, + organization = {{IVOA}}, + url = {https://ivoa.net/documents/Notes/Polarization/20100203/}, + month = Feb, + year = 2010 +} +@Misc{IVOANote:Characterisation2, + author = { F. Bonnarel and I.Chilingarian and al.}, + title = {Characterisation DM: Complements and new features. Observation quality and variability - complex datasets, Version 1.0}, + howpublished = {IVOA Working Draft}, + organization = {{IVOA}}, + url = {https://ivoa.net/documents/Characterisation2/20121029/index.html}, + month = Oct, + year = 2012 +} +@Misc{wd:DatasetDM, + author = { F. Bonnarel and O. Laurino and G. Lemsonand M.Louys,and A. Rots and D.Tody and the IVOA Data Model Working}, + title = {IVOA Dataset Metadata Model, Version 1.0}, + howpublished = {IVOA Working Draft}, + organization = {{IVOA}}, + url = {https://www.ivoa.net/documents/DatasetDM/20160317/WD-DatasetDM-1.0-20160317.pdfl}, + month = Mar, + year = 2016 +} + +@Misc{IVOANote:DMObservation, + author = { J. McDowell and al.}, + title = {Data Model for Observation Version 1.0}, + howpublished = {IVOA Note}, + organization = {{IVOA}}, + url = {https://ivoa.net/documents/latest/DMObs.htmll}, + month = Apr, + year = 2005 +} + +@ARTICLE{2002A&A...395.1061G, + author = {{Greisen}, E.~W. and {Calabretta}, M.~R.}, + title = "{Representations of world coordinates in FITS}", + journal = {Astronomy and Astrophysics}, + keywords = {methods: data analysis, techniques: image processing, astronomical data bases: miscellaneous, Astrophysics}, + year = 2002, + month = dec, + volume = {395}, + pages = {1061-1075}, + doi = {10.1051/0004-6361:20021326}, +archivePrefix = {arXiv}, + eprint = {astro-ph/0207407}, + primaryClass = {astro-ph}, + adsurl = {https://ui.adsabs.harvard.edu/abs/2002A&A...395.1061G}, + adsnote = {Provided by the SAO/NASA Astrophysics Data System} +} + +@Misc{IVOANote:PhotometryVotable, + author = {S. Derrière}, + title = {Providing photometric data measurements description +in votables}, + howpublished = {IVOA Note}, + organization = {{IVOA}}, + url = {https://wiki.ivoa.net/internal/IVOA/PhotometryDataModel/NOTE-PPDMDesc-0.1-20101202.pdf }, + month = Apr, + year = 2010 +} +@Misc{IVOANote:ObservableUCD, + author = {M.Louys and F. Bonnarel}, + title = {List of UCD for observable quantities}, + howpublished = {Tech. report}, + organization = {{IVOA wiki }}, + url = {https://wiki.ivoa.net/internal/IVOA/ObsTap/ListForObservable25Oct2010.pdf }, + year = 2010 +} + +