[Volute] r5280 - in trunk/projects/dm/STC/Coords/doc: . diagrams

Volute commit messages volutecommits at g-vo.org
Wed Dec 12 23:03:12 CET 2018


Author: mdittmar
Date: Wed Dec 12 23:03:12 2018
New Revision: 5280

Log:
corrects margins, ivoa diagram; adds internal references for types

Modified:
   trunk/projects/dm/STC/Coords/doc/Coordinates.tex
   trunk/projects/dm/STC/Coords/doc/WD-Coords-1.0.pdf
   trunk/projects/dm/STC/Coords/doc/body.tex
   trunk/projects/dm/STC/Coords/doc/diagrams/ivoa_types.png
   trunk/projects/dm/STC/Coords/doc/ivoa_types.tex

Modified: trunk/projects/dm/STC/Coords/doc/Coordinates.tex
==============================================================================
--- trunk/projects/dm/STC/Coords/doc/Coordinates.tex	Wed Dec 12 23:01:10 2018	(r5279)
+++ trunk/projects/dm/STC/Coords/doc/Coordinates.tex	Wed Dec 12 23:03:12 2018	(r5280)
@@ -1,4 +1,5 @@
 \documentclass[11pt,a4paper]{ivoa}
+\usepackage[margin=4.25cm]{geometry} 
 \input tthdefs
 \setcounter{tocdepth}{2}
 
@@ -18,7 +19,6 @@
 % \previousversion[????URL????]{????Funny Label????}
 \previousversion{This is the first public release}
        
-
 \begin{document}
 \begin{abstract}
   In creating version 2 of the Space-Time Coordinate Metadata for the Virtual Observatory (STC) Data Model \citep{std:STC}, it was decided to split the content into various component models which focus on particular aspects of the previous model scope.  
@@ -51,6 +51,7 @@
 infrastructure that enable VO applications.
 
 
+\newgeometry{left=1.0in,right=1.0in,bottom=1.0in}
 \section{Introduction}
 
 \subsection{Motivation}
@@ -76,15 +77,15 @@
 \end{enumerate}
 
 \subsection{Context and Scope}
-This document is a result from updating the \href{http://www.ivoa.net/documents/latest/STC.html}{Space-Time Coordinate Metadata for the Virtual Observatory} (STC) \citep{std:STC} model for use in VO-DML compliant models. That model provides metadata describing Space-Time, related, and other Coordinates. These metadata are to be used for specifying coordinate-related information for datasets, catalogs, and queries.
+This document results from updating the \href{http://www.ivoa.net/documents/latest/STC.html}{Space-Time Coordinate Metadata for the Virtual Observatory} (STC) \citep{std:STC} model for use in VO-DML compliant models. That model provides metadata describing Space-Time, related, and other Coordinates. These metadata are to be used for specifying coordinate-related information for datasets, catalogs, and queries.
 
-The update and revision of the STC model has sub-divided the content into component models, each covering a portion of the scope of the parent model.  This has allowed for a better description of the relations between the various components, allows for independent development of the component models, and creates smaller, more digestible content for users.
+The update and revision of the STC model has sub-divided the content into component models, each covering a portion of the scope of the parent model.  This allows for a better description of the relations between the various components, allows for independent development of the component models, and creates smaller, more digestible content for users.
 
 This document describes the Coordinates model which provides the metadata describing:
 \begin{itemize}
 \item the basic model for constructing coordinate frames and for collecting them in coordinate systems
 \item the general model for specifying coordinate values
-\item simple, concrete, domain specific coordinate types for the most common use cases.
+\item simple, concrete, domain-specific coordinate types for the most common use cases.
 \end{itemize}
 
 \pagebreak

Modified: trunk/projects/dm/STC/Coords/doc/WD-Coords-1.0.pdf
==============================================================================
Binary file (source and/or target). No diff available.

Modified: trunk/projects/dm/STC/Coords/doc/body.tex
==============================================================================
--- trunk/projects/dm/STC/Coords/doc/body.tex	Wed Dec 12 23:01:10 2018	(r5279)
+++ trunk/projects/dm/STC/Coords/doc/body.tex	Wed Dec 12 23:03:12 2018	(r5280)
@@ -19,7 +19,7 @@
 
 \pagebreak
 \section{Model: coords }
-
+  
   % INSERT FIGURE HERE
   \begin{figure}[h]
   \begin{center}
@@ -36,8 +36,8 @@
 
     \subsubsection{CoordSpace.axis}
       \textbf{vodml-id: CoordSpace.axis} \newline
-      \textbf{type: coords:Axis} \newline
-      \textbf{multiplicity: 1..*} \newline
+      \textbf{type: \hyperref[sect:Axis]{coords:Axis}} \newline
+      \textbf{multiplicity: 1..*} \newline 
       Describes an axis of the coordinate space.
 
   \subsection{Axis (Abstract)}
@@ -46,8 +46,8 @@
 
     \subsubsection{Axis.name}
       \textbf{vodml-id: Axis.name} \newline
-      \textbf{type: ivoa:string} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:string}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Freeform string, provides the name or label for the axis.
 
   \subsection{ContinuousAxis}
@@ -56,20 +56,20 @@
 
     \subsubsection{ContinuousAxis.domainMin}
       \textbf{vodml-id: ContinuousAxis.domainMin} \newline
-      \textbf{type: ivoa:Quantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:Quantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Minimum extent of the axis domain space. If not provided, the domain space is considered to have no lower bound (-INFINITY).
 
     \subsubsection{ContinuousAxis.domainMax}
       \textbf{vodml-id: ContinuousAxis.domainMax} \newline
-      \textbf{type: ivoa:Quantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:Quantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Maximum extent of the axis domain space. If not provided, the domain space is considered to have no upper bound (+INFINITY).
 
     \subsubsection{ContinuousAxis.cyclic}
       \textbf{vodml-id: ContinuousAxis.cyclic} \newline
-      \textbf{type: ivoa:boolean} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:boolean}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Flag indicating if the axis is cyclic in nature. If not provided, it is assumed to be FALSE.
 
   \subsection{BinnedAxis}
@@ -78,8 +78,8 @@
 
     \subsubsection{BinnedAxis.length}
       \textbf{vodml-id: BinnedAxis.length} \newline
-      \textbf{type: ivoa:nonnegativeInteger} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:nonnegativeInteger}} \newline
+      \textbf{multiplicity: 1} \newline 
       The length, or number of bins, along the axis.
 
   \subsection{DiscreteSetAxis}
@@ -113,14 +113,14 @@
 
     \subsubsection{GenericCoordFrame.refPosition}
       \textbf{vodml-id: GenericCoordFrame.refPosition} \newline
-      \textbf{type: coords:domain.space.RefLocation} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.space.RefLocation]{coords:domain.space.RefLocation}} \newline
+      \textbf{multiplicity: 1} \newline 
       Spatial location in phase space (position and velocity) at which the observed value is considered to have been taken. This will typically be given by a standard reference position, but we allow for custom locations as well.
 
     \subsubsection{GenericCoordFrame.planetaryEphem}
       \textbf{vodml-id: GenericCoordFrame.planetaryEphem} \newline
-      \textbf{type: ivoa:string} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:string}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       A planetary ephemeris MAY be provided, and SHOULD be provided whenever appropriate, to indicate which solar system ephemeris was used. If needed, but not provided, it is assumed to be "DE405"
 
   \subsection{Coordinate (Abstract)}
@@ -129,8 +129,8 @@
 
     \subsubsection{Coordinate.frame}
       \textbf{vodml-id: Coordinate.frame} \newline
-      \textbf{type: coords:CoordFrame} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:CoordFrame]{coords:CoordFrame}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Provided additional metadata relevant to interpreting the coordinate value. For example, the spatial reference position, or time scale.
 
   \subsection{CoordValue (Abstract)}
@@ -139,8 +139,8 @@
 
     \subsubsection{CoordValue.axis}
       \textbf{vodml-id: CoordValue.axis} \newline
-      \textbf{type: coords:Axis} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:Axis]{coords:Axis}} \newline
+      \textbf{multiplicity: 1} \newline 
       Reference to the particular axis of the coordinate space along which this value is given. eg: the X axis of a 3D CARTESIAN coordinate space.
 
   \subsection{PhysicalCoordValue}
@@ -153,8 +153,8 @@
 
     \subsubsection{PhysicalCoordValue.cval}
       \textbf{vodml-id: PhysicalCoordValue.cval} \newline
-      \textbf{type: ivoa:Quantity} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:Quantity}} \newline
+      \textbf{multiplicity: 1} \newline 
       This coordinate MUST contain a value expressed as an ivoa:Quantity.
 
   \subsection{BinnedCoordValue}
@@ -167,8 +167,8 @@
 
     \subsubsection{BinnedCoordValue.cval}
       \textbf{vodml-id: BinnedCoordValue.cval} \newline
-      \textbf{type: ivoa:integer} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:integer}} \newline
+      \textbf{multiplicity: 1} \newline 
       The binned coordinate value, expressed as an integer. eg: bin number, pixel index.
 
   \subsection{CompositeCoordinate (Abstract)}
@@ -177,8 +177,8 @@
 
     \subsubsection{CompositeCoordinate.cmpt}
       \textbf{vodml-id: CompositeCoordinate.cmpt} \newline
-      \textbf{type: coords:CoordValue} \newline
-      \textbf{multiplicity: 1..*} \newline
+      \textbf{type: \hyperref[sect:CoordValue]{coords:CoordValue}} \newline
+      \textbf{multiplicity: 1..*} \newline 
       Component member of the composite coordinate.
 
   \subsection{CompositeCoord1D}
@@ -212,8 +212,8 @@
 
     \subsubsection{AstroCoordSystem.coordFrame}
       \textbf{vodml-id: AstroCoordSystem.coordFrame} \newline
-      \textbf{type: coords:CoordFrame} \newline
-      \textbf{multiplicity: 0..*} \newline
+      \textbf{type: \hyperref[sect:CoordFrame]{coords:CoordFrame}} \newline
+      \textbf{multiplicity: 0..*} \newline 
       Frame specification for some domain of the coordinate space.
 
 \pagebreak
@@ -243,17 +243,17 @@
   This package provides specialized content for the Pixel domain. The Pixel coordinate space is defined as a 'virtual' binned space, with no physical meaning. The axes in this space provide integer indexes into that space.
 
   \subsection{PixelCoordSystem}
-  \label{sect:PixelCoordSystem}
+  \label{sect:domain.pixel.PixelCoordSystem}
     The PixelCoordSystem provides a complete description of the pixel coordinate space. It SHALL contain one PixelSpace instance describing each pixel axis.
 
     \subsubsection{PixelCoordSystem.pixelSpace}
       \textbf{vodml-id: domain.pixel.PixelCoordSystem.pixelSpace} \newline
-      \textbf{type: coords:domain.pixel.PixelSpace} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.pixel.PixelSpace]{coords:domain.pixel.PixelSpace}} \newline
+      \textbf{multiplicity: 1} \newline 
       The pixel space completely defines the pixel coordinate axes. Each axis MUST be defined as a BinnedAxis type.
 
   \subsection{PixelSpace}
-  \label{sect:PixelSpace}
+  \label{sect:domain.pixel.PixelSpace}
     A PixelSpace SHALL include one or more BinnedAxis objects describing the pixel coordinate space. A handedness value MAY be provided to specify the relative orientation of the axes.
 
     \noindent \textbf{subset} \newline
@@ -262,12 +262,12 @@
 
     \subsubsection{PixelSpace.handedness}
       \textbf{vodml-id: domain.pixel.PixelSpace.handedness} \newline
-      \textbf{type: coords:Handedness} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:Handedness]{coords:Handedness}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Specifies the handedness of the coordinate space.
 
   \subsection{PixelIndex}
-  \label{sect:PixelIndex}
+  \label{sect:domain.pixel.PixelIndex}
     A coordinate value in the pixel domain. A 1-dimensional pixel index. There is no frame in the pixel domain, so no frame reference is allowed.
 
     \noindent \textbf{constraint} \newline
@@ -287,77 +287,77 @@
   This package provides specialized content for the Space domain. The spatial domain requires a Space Frame, giving the reference frame (orientation) and reference position (origin). We also define here a set of simplified spatial coordinate types for the most common cases.
 
   \subsection{SpaceFrame}
-  \label{sect:SpaceFrame}
+  \label{sect:domain.space.SpaceFrame}
     A Space Frame is specified by its Reference Frame (currently only standard reference frames are allowed), and a Reference Position. An equinox MUST be provided for pre-ICRS reference frames. A planetary ephemeris MAY be provided if relevant; if not provided, it is assumed to be "DE 405".
 
     \subsubsection{SpaceFrame.refPosition}
       \textbf{vodml-id: domain.space.SpaceFrame.refPosition} \newline
-      \textbf{type: coords:domain.space.RefLocation} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.space.RefLocation]{coords:domain.space.RefLocation}} \newline
+      \textbf{multiplicity: 1} \newline 
       The spatial location at which the coordinates are considered to have been determined. We support both standard and custom reference positions.
 
     \subsubsection{SpaceFrame.spaceRefFrame}
       \textbf{vodml-id: domain.space.SpaceFrame.spaceRefFrame} \newline
-      \textbf{type: ivoa:string} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:string}} \newline
       \textbf{vocabulary: https://ivoa.net/vocabularies/coords/SpaceRefFrame} \newline
       \textbf{multiplicity: 1} \newline
       The spatial reference frame. Values MUST be selected from the controlled vocabulary at the given URL.
 
     \subsubsection{SpaceFrame.equinox}
       \textbf{vodml-id: domain.space.SpaceFrame.equinox} \newline
-      \textbf{type: coords:domain.space.Epoch} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:domain.space.Epoch]{coords:domain.space.Epoch}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Reference date for the frame, required for pre-ICRS reference frames.
 
     \subsubsection{SpaceFrame.planetaryEphem}
       \textbf{vodml-id: domain.space.SpaceFrame.planetaryEphem} \newline
-      \textbf{type: ivoa:string} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:string}} \newline
+      \textbf{multiplicity: 1} \newline 
       Ephemeris file for solar system objects SHOULD be specified whenever relevant.
 
   \subsection{Epoch}
-  \label{sect:Epoch}
+  \label{sect:domain.space.Epoch}
   We define epoch as a primitive data type with the expected form "<type><year>" where type = "J" or "B" for Julian or Besselian respectively, and year is expressed as a decimal year. eg: "B1950", "J2000.0"
 
   \subsection{RefLocation (Abstract)}
-  \label{sect:RefLocation}
+  \label{sect:domain.space.RefLocation}
     RefLocation defines the origin of the spatial coordinate space. This location is represented either by a standard reference position (which absolute location in phase space is known by definition), or a specified point in another Spatial frame. This object is used as the origin of the SpaceFrame here, but also to specify the Spatial Reference Position (refPosition) associated with other domain Frames. For example, in the Time domain, the Spatial Reference Position indicates that the 'time' values are the time that the 'event' occured at that location, which might be different from the detector location.
 
   \subsection{StdRefLocation}
-  \label{sect:StdRefLocation}
+  \label{sect:domain.space.StdRefLocation}
     An absolute a-priori known location in phase space (position and velocity). Values are selected from the StdRefPosition vocabulary. Considering that the GEOCENTER is really the only place for which we know the absolute location at all times, all other locations require the specification of a planetary ephemeris. LSR[KD] are red for spectral and reshift frames. TOPOCENTER (location of the observer) is special in that it assumes that the observing location is available through other means (e.g. a geographic location or an orbit ephemeris). RELOCATABLE is available for simulations. UNKNOWN should only be used if absolutely necessary.
 
     \subsubsection{StdRefLocation.position}
       \textbf{vodml-id: domain.space.StdRefLocation.position} \newline
-      \textbf{type: ivoa:string} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:string}} \newline
       \textbf{vocabulary: https://ivoa.net/vocabularies/coords/ReferencePosition} \newline
       \textbf{multiplicity: 1} \newline
       Standard reference location. Values MUST be selected from the controlled vocabulary at the given URL.
 
   \subsection{CustomRefLocation}
-  \label{sect:CustomRefLocation}
+  \label{sect:domain.space.CustomRefLocation}
     A custom reference location in phase space (position and velocity). Position and velocity are given as coordinates with an associated SpaceFrame. An epoch MAY be provided to further refine the location.
 
     \subsubsection{CustomRefLocation.epoch}
       \textbf{vodml-id: domain.space.CustomRefLocation.epoch} \newline
-      \textbf{type: coords:domain.space.Epoch} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:domain.space.Epoch]{coords:domain.space.Epoch}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Epoch for the reference location.
 
     \subsubsection{CustomRefLocation.position}
       \textbf{vodml-id: domain.space.CustomRefLocation.position} \newline
-      \textbf{type: coords:CompositeCoordinate} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:CompositeCoordinate]{coords:CompositeCoordinate}} \newline
+      \textbf{multiplicity: 1} \newline 
       The spatial coordinates of the reference location.
 
     \subsubsection{CustomRefLocation.velocity}
       \textbf{vodml-id: domain.space.CustomRefLocation.velocity} \newline
-      \textbf{type: coords:CompositeCoordinate} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:CompositeCoordinate]{coords:CompositeCoordinate}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       The velocity of the reference location.
 
   \subsection{SpaceCoord (Abstract)}
-  \label{sect:SpaceCoord}
+  \label{sect:domain.space.SpaceCoord}
     Abstract head of a set of specialized spatial coordinate types which cover the most commonly used cases. The definitions of these 'shortcut' types include a complete description of the associated coordinate space in which they reside, thereby reducing the need to include 'boilerplate' content. It is expected that these coordinates will be used in the vast majority of cases.
 
     \noindent \textbf{subset} \newline
@@ -365,113 +365,113 @@
     \indent   \textbf{type: coords:domain.space.SpaceFrame} \newline
 
   \subsection{CartesianCoord}
-  \label{sect:CartesianCoord}
+  \label{sect:domain.space.CartesianCoord}
     A spatial location in a standard 3D Cartesian coordinate space (see: \ref{sect:Cartesian} ). All axes are optional, users need only supply values for relevant axes.
 
     \subsubsection{CartesianCoord.x}
       \textbf{vodml-id: domain.space.CartesianCoord.x} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Coordinate value along the 'X' axis.
 
     \subsubsection{CartesianCoord.y}
       \textbf{vodml-id: domain.space.CartesianCoord.y} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Coordinate value along the 'Y' axis.
 
     \subsubsection{CartesianCoord.z}
       \textbf{vodml-id: domain.space.CartesianCoord.z} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Coordinate value along the 'Z' axis.
 
   \subsection{EclipticCoord}
-  \label{sect:EclipticCoord}
+  \label{sect:domain.space.EclipticCoord}
     A spatial location in a spherical Ecliptic coordinate space (see: \ref{sect:Spherical} ). The associated SpaceFrame MUST represent an Ecliptic frame.
 
     \subsubsection{EclipticCoord.elong}
       \textbf{vodml-id: domain.space.EclipticCoord.elong} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Longitude axis.
 
     \subsubsection{EclipticCoord.elat}
       \textbf{vodml-id: domain.space.EclipticCoord.elat} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Latitude axis.
 
     \subsubsection{EclipticCoord.r}
       \textbf{vodml-id: domain.space.EclipticCoord.r} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Radial axis.
 
   \subsection{EquatorialCoord}
-  \label{sect:EquatorialCoord}
+  \label{sect:domain.space.EquatorialCoord}
     A spatial location in a spherical Equatorial coordinate space (see: \ref{sect:Spherical} ). The associated SpaceFrame MUST represent an Equatorial frame.
 
     \subsubsection{EquatorialCoord.ra}
       \textbf{vodml-id: domain.space.EquatorialCoord.ra} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Longitude axis, (Right Ascension)
 
     \subsubsection{EquatorialCoord.dec}
       \textbf{vodml-id: domain.space.EquatorialCoord.dec} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Latitude axis, (Declination)
 
     \subsubsection{EquatorialCoord.r}
       \textbf{vodml-id: domain.space.EquatorialCoord.r} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the radial axis, (Distance)
 
   \subsection{GalacticCoord}
-  \label{sect:GalacticCoord}
+  \label{sect:domain.space.GalacticCoord}
     A spatial location in a spherical Galactic coordinate space (see: \ref{sect:Spherical} ). The associated SpaceFrame MUST represent a Galactic frame.
 
     \subsubsection{GalacticCoord.l}
       \textbf{vodml-id: domain.space.GalacticCoord.l} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Longitude axis.
 
     \subsubsection{GalacticCoord.b}
       \textbf{vodml-id: domain.space.GalacticCoord.b} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Latitude axis.
 
     \subsubsection{GalacticCoord.r}
       \textbf{vodml-id: domain.space.GalacticCoord.r} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Radial axis.
 
   \subsection{LongLatCoord}
-  \label{sect:LongLatCoord}
+  \label{sect:domain.space.LongLatCoord}
     A spatial location in a Generic Spherical coordinate space (see: \ref{sect:Spherical} ).
 
     \subsubsection{LongLatCoord.long}
       \textbf{vodml-id: domain.space.LongLatCoord.long} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Longitude axis.
 
     \subsubsection{LongLatCoord.lat}
       \textbf{vodml-id: domain.space.LongLatCoord.lat} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Latitude axis.
 
     \subsubsection{LongLatCoord.r}
       \textbf{vodml-id: domain.space.LongLatCoord.r} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       Value along the Radial axis.
 
 \pagebreak
@@ -517,30 +517,30 @@
   \end{enumerate}
 
   \subsection{TimeFrame}
-  \label{sect:TimeFrame}
+  \label{sect:domain.time.TimeFrame}
     A TimeFrame SHALL include a time scale and reference position. It MAY also include a reference direction.
 
     \subsubsection{TimeFrame.refPosition}
       \textbf{vodml-id: domain.time.TimeFrame.refPosition} \newline
-      \textbf{type: coords:domain.space.RefLocation} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.space.RefLocation]{coords:domain.space.RefLocation}} \newline
+      \textbf{multiplicity: 1} \newline 
       The spatial location at which the coordinate is considered to have been taken from.
 
     \subsubsection{TimeFrame.timescale}
       \textbf{vodml-id: domain.time.TimeFrame.timescale} \newline
-      \textbf{type: ivoa:string} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:string}} \newline
       \textbf{vocabulary: https://ivoa.net/vocabularies/coords/TimeScale} \newline
       \textbf{multiplicity: 1} \newline
       The time scale sets the reference frame. The value MUST be selected from the controlled vocabulary at the given URL.
 
     \subsubsection{TimeFrame.refDirection}
       \textbf{vodml-id: domain.time.TimeFrame.refDirection} \newline
-      \textbf{type: coords:domain.space.RefLocation} \newline
-      \textbf{multiplicity: 0..1} \newline
+      \textbf{type: \hyperref[sect:domain.space.RefLocation]{coords:domain.space.RefLocation}} \newline
+      \textbf{multiplicity: 0..1} \newline 
       The reference direction is needed if the time stamps are transformed to a time frame with a different reference position. In those situations, the solar system ephemeris also comes into play.
 
   \subsection{TimeStamp (Abstract)}
-  \label{sect:TimeStamp}
+  \label{sect:domain.time.TimeStamp}
     This is the abstract basis for a set of simple time domain coordinates which is expected to accommodate the vast majority of use cases. All TimeStamps, by definition, refer to the axis of a standard 1-D coordinate space, with domainMin|Max of +/-Infinity. As such, there is no 'axis' reference on TimeStamps. All TimeStamps SHOULD refer to an appropriate TimeFrame.
 
     \noindent \textbf{subset} \newline
@@ -548,53 +548,53 @@
     \indent   \textbf{type: coords:domain.time.TimeFrame} \newline
 
   \subsection{TimeInstant (Abstract)}
-  \label{sect:TimeInstant}
+  \label{sect:domain.time.TimeInstant}
     TimeStamps which specify a specific instant in time.
 
   \subsection{ISOTime}
-  \label{sect:ISOTime}
+  \label{sect:domain.time.ISOTime}
     An instant in time expressed with structure in representation defined by the ISO-8601 standard within the restrictions imposed by the IVOA.
 
     \subsubsection{ISOTime.date}
       \textbf{vodml-id: domain.time.ISOTime.date} \newline
-      \textbf{type: ivoa:datetime} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:datetime}} \newline
+      \textbf{multiplicity: 1} \newline 
       The ISOTime coordinate value.
 
   \subsection{JD}
-  \label{sect:JD}
+  \label{sect:domain.time.JD}
     A time stamp expressed in Julian days. Note that JD does not properly specify a time stamp unless it is related to a time scale and reference position. Precision can easily become an issue with JD, as the numbers tend to be large.
 
     \subsubsection{JD.date}
       \textbf{vodml-id: domain.time.JD.date} \newline
-      \textbf{type: ivoa:real} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:real}} \newline
+      \textbf{multiplicity: 1} \newline 
       The JD coordinate value. JD dates are dimensionless, with implied units in days.
 
   \subsection{MJD}
-  \label{sect:MJD}
+  \label{sect:domain.time.MJD}
     A time stamp expressed in Modified Julian Days. T(MJD) = T(JD) - 2440000.5.
 
     \subsubsection{MJD.date}
       \textbf{vodml-id: domain.time.MJD.date} \newline
-      \textbf{type: ivoa:real} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:real}} \newline
+      \textbf{multiplicity: 1} \newline 
       The MJD coordinate value. MJD dates are dimensionless, with implied units in days.
 
   \subsection{TimeOffset}
-  \label{sect:TimeOffset}
+  \label{sect:domain.time.TimeOffset}
     Time is given as an offset from a specific point in time (time0).
 
     \subsubsection{TimeOffset.time}
       \textbf{vodml-id: domain.time.TimeOffset.time} \newline
-      \textbf{type: ivoa:RealQuantity} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline
+      \textbf{multiplicity: 1} \newline 
       The TimeOffset coordinate value.
 
     \subsubsection{TimeOffset.time0}
       \textbf{vodml-id: domain.time.TimeOffset.time0} \newline
-      \textbf{type: coords:domain.time.TimeInstant} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.time.TimeInstant]{coords:domain.time.TimeInstant}} \newline
+      \textbf{multiplicity: 1} \newline 
       The reference time from which the offset is calculated. This MUST be given as a TimeInstant (e.g.: JD, MJD, ISOTime).
 
 \pagebreak
@@ -611,7 +611,7 @@
   This package provides specialized content for the Polarization domain. This domain provides a concrete example of a Discrete coordinate space. The coordinates in this domain are given by enumerated lists of the various polarization types.
 
   \subsection{PolCoordValue (Abstract)}
-  \label{sect:PolCoordValue}
+  \label{sect:domain.polarization.PolCoordValue}
     Abstract head of the polarization coordinate types. Here we constrain the coordinate value to refer to a discrete axis type.
 
     \noindent \textbf{subset} \newline
@@ -622,47 +622,47 @@
     \indent    \textbf{detail: PolCoordValue.PolCoordValue.frame:CoordFrame[0] }\newline
 
   \subsection{PolStokes}
-  \label{sect:PolStokes}
+  \label{sect:domain.polarization.PolStokes}
     Coordinate for Stokes Polarization type
 
     \subsubsection{PolStokes.cval}
       \textbf{vodml-id: domain.polarization.PolStokes.cval} \newline
-      \textbf{type: coords:domain.polarization.PolStokesEnum} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.polarization.PolStokesEnum]{coords:domain.polarization.PolStokesEnum}} \newline
+      \textbf{multiplicity: 1} \newline 
       The coordinate value MUST be from the PolStokesEnum enumerated set.
 
   \subsection{PolCircular}
-  \label{sect:PolCircular}
+  \label{sect:domain.polarization.PolCircular}
     Coordinate for Circular Polarization type
 
     \subsubsection{PolCircular.cval}
       \textbf{vodml-id: domain.polarization.PolCircular.cval} \newline
-      \textbf{type: coords:domain.polarization.PolCircularEnum} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.polarization.PolCircularEnum]{coords:domain.polarization.PolCircularEnum}} \newline
+      \textbf{multiplicity: 1} \newline 
       The coordinate value MUST be from the PolCircularEnum enumerated set.
 
   \subsection{PolLinear}
-  \label{sect:PolLinear}
+  \label{sect:domain.polarization.PolLinear}
     Coordinate for LinearPolarization type
 
     \subsubsection{PolLinear.cval}
       \textbf{vodml-id: domain.polarization.PolLinear.cval} \newline
-      \textbf{type: coords:domain.polarization.PolLinearEnum} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.polarization.PolLinearEnum]{coords:domain.polarization.PolLinearEnum}} \newline
+      \textbf{multiplicity: 1} \newline 
       The coordinate value MUST be from the PolLinearEnum enumerated set.
 
   \subsection{PolVector}
-  \label{sect:PolVector}
+  \label{sect:domain.polarization.PolVector}
     Coordinate for Vector Polarization type
 
     \subsubsection{PolVector.cval}
       \textbf{vodml-id: domain.polarization.PolVector.cval} \newline
-      \textbf{type: coords:domain.polarization.PolVectorEnum} \newline
-      \textbf{multiplicity: 1} \newline
+      \textbf{type: \hyperref[sect:domain.polarization.PolVectorEnum]{coords:domain.polarization.PolVectorEnum}} \newline
+      \textbf{multiplicity: 1} \newline 
       The coordinate value MUST be from the PolVectorEnum enumerated set.
 
   \subsection{PolStokesEnum}
-  \label{sect:PolStokesEnum}
+  \label{sect:domain.polarization.PolStokesEnum}
 
   Stokes Polarization states
 
@@ -679,7 +679,7 @@
   \normalsize
 
   \subsection{PolCircularEnum}
-  \label{sect:PolCircularEnum}
+  \label{sect:domain.polarization.PolCircularEnum}
 
   Circular Polarization states
 
@@ -696,7 +696,7 @@
   \normalsize
 
   \subsection{PolLinearEnum}
-  \label{sect:PolLinearEnum}
+  \label{sect:domain.polarization.PolLinearEnum}
 
   Linear Polarization states
 
@@ -713,7 +713,7 @@
   \normalsize
 
   \subsection{PolVectorEnum}
-  \label{sect:PolVectorEnum}
+  \label{sect:domain.polarization.PolVectorEnum}
 
   Vector Polarization states
 

Modified: trunk/projects/dm/STC/Coords/doc/diagrams/ivoa_types.png
==============================================================================
Binary file (source and/or target). No diff available.

Modified: trunk/projects/dm/STC/Coords/doc/ivoa_types.tex
==============================================================================
--- trunk/projects/dm/STC/Coords/doc/ivoa_types.tex	Wed Dec 12 23:01:10 2018	(r5279)
+++ trunk/projects/dm/STC/Coords/doc/ivoa_types.tex	Wed Dec 12 23:03:12 2018	(r5280)
@@ -22,11 +22,6 @@
 quantities. This standard reconciles common practices and current standards for use within the
 IVOA community.
 
-  \subsubsection{UCDs}
-  \label{sect:UCDs}
-  This model requires any ucd field to comply with syntax defined in ”An IVOA Standard for Unified
-Content Descriptors” \citep{2005ivoa.spec.0819D}.
-
   \subsubsection{Dates}
   \label{sect:Dates}
   The 'datetime' datatype is for expressing date-time values. The string representation of a


More information about the Volutecommits mailing list