From e024f979181f348fe9386b37831a9b3f5c2fc4b6 Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:46:11 +0000 Subject: [PATCH 1/9] Missing 'a' --- DALI.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DALI.tex b/DALI.tex index a73d579..3de1598 100644 --- a/DALI.tex +++ b/DALI.tex @@ -859,7 +859,7 @@ \subsection{MOC} The value is the ascii serialisation of a MOC specified in \citet{2022ivoa.spec.0727F} section 4.3.2 and may be a one- or two-dimension (spatial) MOC. -Note: explicit time MOC and space-time MOC xtypes may be added in future version. +Note: explicit time MOC and space-time MOC xtypes may be added in a future version. \subsection{Multi-Polygon} Multi-polygon values serialised in VOTable or service parameters must have the From a789348720abede6e8a00517004f4f19a98bce4c Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 12:23:12 +0000 Subject: [PATCH 2/9] Remove incorrect backslash Escaping backslash is not required in \verb environment, and shows up in both PDF and HTML output. --- DALI.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DALI.tex b/DALI.tex index 3de1598..84ca169 100644 --- a/DALI.tex +++ b/DALI.tex @@ -1393,7 +1393,7 @@ \subsubsection{Overflow} \label{sec:response-overflow} If an overflow occurs (for example, result exceeds MAXREC) and the output format is VOTable, the service must include an \xmlel{INFO} element in the \xmlel{RESOURCE} -with \verb|name="QUERY\_STATUS"| and the \verb|value="OVERFLOW"|. If the initial +with \verb|name="QUERY_STATUS"| and the \verb|value="OVERFLOW"|. If the initial \xmlel{INFO} element (above) specified the overflow, no further elements are needed, e.g.: From 3f5de8b13076fa4f75215b79ca7e223fe15d010b Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:27:22 +0000 Subject: [PATCH 3/9] Replace "and or" with "or" Arguably it should be replaced instead by "and/or" or maybe "and". --- DALI.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DALI.tex b/DALI.tex index 84ca169..7c01488 100644 --- a/DALI.tex +++ b/DALI.tex @@ -709,7 +709,7 @@ \subsection{Intervals} \verb|datatype="long"|, \verb|arraysize="2"|, \verb|xtype="interval"|. Interval values serialised in VOTable (\xmlel{FIELD}) or service parameters -(\xmlel{PARAM}) with this xtype may include additional metadata like minimum and +(\xmlel{PARAM}) with this xtype may include additional metadata like minimum or maximum value. These are specified using the standard scalar \verb|MIN| and \verb|MAX| child elements to describe the (minimum) lower bound and (maximum) upper bound of interval(s) respectively. From ab041f15b902fc9f609e957701c33886ea80925f Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:26:29 +0000 Subject: [PATCH 4/9] add some \noindents as required Improves PDF formatting. --- DALI.tex | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/DALI.tex b/DALI.tex index 7c01488..bb4a30d 100644 --- a/DALI.tex +++ b/DALI.tex @@ -92,6 +92,7 @@ \subsection{Example Usage of the DALI Specification} to a specified registry extension schema \end{itemize} +\noindent and would have to define the registry extension schema to be used to register services and to implement the VOSI-capabilities resource. Most of the service specification would be in defining the semantics (possibly controllable via @@ -377,6 +378,7 @@ \subsection{DALI-examples} \end{lstlisting} +\noindent would imply that the name of the example \texttt{x} is \nolinkurl{http://object-resolver.edu/M42} rather than just ``Messier 42''. Full RDFa offers the \xmlel{content} attribute to allow correct @@ -626,7 +628,8 @@ \subsection{Timestamp} YYYY-MM-DD['T'hh:mm:ss[.SSS]] \end{verbatim} -where the T is a character separating the date and time components. The time +\noindent +where the T is a character separating the date and time components. The time component is optional, in which case the T separator is not used. Fractions of a second are permitted but not required. For example: @@ -636,6 +639,7 @@ \subsection{Timestamp} 2002-03-04 \end{verbatim} +\noindent are all legal date or date plus time values. Astronomical values never include a time zone indicator. However, values that are civil in nature (e.g. when some processing was completed, when some record @@ -646,6 +650,7 @@ \subsection{Timestamp} YYYY-MM-DD['T'hh:mm:ss[.SSS]['Z']] \end{verbatim} +\noindent where the optional Z character indicates the value is UTC. For example: \begin{verbatim} @@ -653,6 +658,7 @@ \subsection{Timestamp} 2000-01-02T15:20:30Z \end{verbatim} +\noindent are valid civil time values. In cases where time values may be expressed using Julian Date (JD) or Modified Julian Date (MJD), these follow the rules for double precision numbers above and may have additional metadata as @@ -797,6 +803,7 @@ \subsection{Range} 10.0 11.0 20.0 21.0 \end{verbatim} +\noindent includes values from 10 to 11 (coordinate1) and from 20 to 21 (coordinate2). Valid coordinate value limits are specified by \verb|xtype="point"| above. @@ -1145,6 +1152,7 @@ \subsubsection{UPLOAD} UPLOAD=table1,http://example.com/t1 \end{verbatim} +\noindent would define an input named table1 at the given URI. Resource names must be simple strings made up of alphabetic, numeric, and the underscore characters only and must start with an alphabetic character. From d2173c37eab01c66b51e7f8a606d0bff990018df Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:29:00 +0000 Subject: [PATCH 5/9] Note arraysize may be definite for xtype=hms/dms For xtypes hms and dms follow the practice in the rest of the document of noting that arraysize="*" can be replaced with definite values if known. --- DALI.tex | 3 +++ 1 file changed, 3 insertions(+) diff --git a/DALI.tex b/DALI.tex index bb4a30d..efcedf5 100644 --- a/DALI.tex +++ b/DALI.tex @@ -729,6 +729,9 @@ \subsection{Sexagesimal Coordinates} \item declination: \verb|datatype="char"| \verb|arraysize="*"| \verb|xtype="dms"| \end{itemize} +\noindent +(the arraysize may also be a fixed length or variable length with limit). + For \verb|xtype="hms"|, the values are serialised as hours:minutes:seconds where hours and minutes are integer values and seconds is a real value. For \verb|xtype="dms"|, the values are serialised as degrees:minutes:seconds where degrees and minutes are integer From b22651068d2258384af36b0763ec0584b5ec13d7 Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:05:03 +0000 Subject: [PATCH 6/9] update VOSI-* text for consistency with revised policy Change the text in the VOSI-availability and VOSI-capabilities sections to match the revised policy about required VOSI services from the table in Section 2. --- DALI.tex | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/DALI.tex b/DALI.tex index efcedf5..f0856d5 100644 --- a/DALI.tex +++ b/DALI.tex @@ -490,8 +490,9 @@ \subsection{Availability: VOSI-availability} VOSI-availability \citep{2017ivoa.spec.0524G} defines a simple web resource that reports on the current ability of the service to perform. -All DAL services must implement the VOSI-availability resource and provide a description -of this capability in the VOSI-capabilities document. The VOSI-availability resource is +If the VOSI-availability resource is implemented a description +of this capability must be provided in the VOSI-capabilities document. +The VOSI-availability resource is intended to respond with a dynamically generated document describing the current state of the service operation, e.g.: @@ -513,7 +514,7 @@ \subsection{Capabilities: VOSI-capabilities} VOSI-capabilities should describe all the resources exposed by the service, including which standards each resource implements. -All DAL services must implement the /capabilities resource. The following +All registered DAL services must implement the /capabilities resource. The following capabilities document shows the three VOSI resources and a TAP base resource: \begin{lstlisting}[language=XML,basicstyle=\footnotesize] From d13d180c3329df50c1a3b1e9932a2d9010da33dc Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:08:54 +0000 Subject: [PATCH 7/9] Remove availability declaration from capabilities example Remove the stanza declaring the VOSI-availability from the VOSI-capabilities example. The example wasn't wrong, since availability may still optionally be present and declared, but the majority of new services will probably not include availability, and the example is more compact without it. You could also do something similar in section 1.2. --- DALI.tex | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/DALI.tex b/DALI.tex index f0856d5..8d46e47 100644 --- a/DALI.tex +++ b/DALI.tex @@ -515,7 +515,8 @@ \subsection{Capabilities: VOSI-capabilities} including which standards each resource implements. All registered DAL services must implement the /capabilities resource. The following -capabilities document shows the three VOSI resources and a TAP base resource: +capabilities document shows the capabilities and tables VOSI resources +and a TAP base resource: \begin{lstlisting}[language=XML,basicstyle=\footnotesize] @@ -532,14 +533,6 @@ \subsection{Capabilities: VOSI-capabilities} - - - - http://example.com/tap/availability - - - - From a08af17ee490978b670d8a4ce14fddbd5947cee3 Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:42:13 +0000 Subject: [PATCH 8/9] Tidy deprecation text concerning polygons Replace the text "not allowed (highly discouraged?)" [I presume a marker for an editorial decision to be made later] with "highly discouraged". You could go the other way and write "not allowed" instead, but IMO highly discouraged is good enough. --- DALI.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DALI.tex b/DALI.tex index 8d46e47..beb2ee3 100644 --- a/DALI.tex +++ b/DALI.tex @@ -830,7 +830,7 @@ \subsection{Polygon} latitude ...) with an even number of values and at least three (3) points (six (6) numeric values). A polygon is always implicitly closed: there is an implied edge from the last point back to the first point; explicitly including the first point at the end is -not allowed (highly discouraged?) because it creates an edge of length 0 that has +highly discouraged because it creates an edge of length 0 that has negative side effects on some polygon computations. For example: \begin{verbatim} From 241557f7b1b3bd75bba03e97da3fffa80bc9e65c Mon Sep 17 00:00:00 2001 From: Mark Taylor Date: Mon, 18 Mar 2024 11:52:11 +0000 Subject: [PATCH 9/9] Clarifications to MAXREC/overflow Add "where possible" to the MAXREC section in acknowledgement of the fact that not all output formats support overflow flagging. Add a crossreference from the Overflow section back to the MAXREC section. --- DALI.tex | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/DALI.tex b/DALI.tex index beb2ee3..6b49286 100644 --- a/DALI.tex +++ b/DALI.tex @@ -1126,7 +1126,7 @@ \subsubsection{MAXREC} enforce a limit on the value of MAXREC that is smaller than the value in the request. If the size of the result exceeds the resulting limit, the service must only return the requested number of rows. If the result set is truncated in this -fashion, it must include an overflow indicator as specified in Section \ref{sec:response-overflow}. +fashion, it must include an overflow indicator where possible as specified in Section \ref{sec:response-overflow}. The service must support the special value of MAXREC=0. This value indicates that, in the event of an otherwise valid request, a valid response be returned @@ -1427,7 +1427,8 @@ \subsubsection{Overflow} \verb|text/tab-separated-values| do not support indicating overflow. In general, services may truncate the output results when reaching a limit. A default or -user-specified value of the MAXREC parameter is a common mechanism that causes truncation +user-specified value of the MAXREC parameter defined in Section \ref{sec:MAXREC} +is a common mechanism that causes truncation of results, but service providers may also impose limits in services that do not use MAXREC and indicate that the limit was reached with the overflow indicator.