22 |
|
|
23 |
\editor{Markus Demleitner} |
\editor{Markus Demleitner} |
24 |
|
|
25 |
|
\previousversion[https://ivoa.net/documents/SimpleDALRegExt/20200424/]{ |
26 |
|
WD-20200424} |
27 |
\previousversion[http://ivoa.net/documents/SimpleDALRegExt/20200212/]{ |
\previousversion[http://ivoa.net/documents/SimpleDALRegExt/20200212/]{ |
28 |
WD-20200212} |
WD-20200212} |
29 |
\previousversion[http://ivoa.net/documents/SimpleDALRegExt/20170530/]{ |
\previousversion[http://ivoa.net/documents/SimpleDALRegExt/20170530/]{ |
83 |
in specification in case of conflicts. |
in specification in case of conflicts. |
84 |
Note that the schema files in the IVOA repository can change |
Note that the schema files in the IVOA repository can change |
85 |
over time according to the |
over time according to the |
86 |
rules laid down in \citet{note:schemaversioning}. |
rules laid down in \citet{2018ivoa.spec.0529H}. |
87 |
|
|
88 |
Reference to specific elements and types defined in the VOResource |
Reference to specific elements and types defined in the VOResource |
89 |
schema include the namespaces prefix, \xmlel{vr:}, as in |
schema include the namespaces prefix, \xmlel{vr:}, as in |
187 |
\label{fig:archdiag} |
\label{fig:archdiag} |
188 |
\end{figure} |
\end{figure} |
189 |
|
|
190 |
The IVOA Architecture \citep{note:VOARCH} provides a high-level view of how IVOA |
The IVOA Architecture \citep{2010ivoa.rept.1123A} provides a high-level view of how IVOA |
191 |
standards work together to connect users and applications with |
standards work together to connect users and applications with |
192 |
providers of data and services, as depicted in the diagram in |
providers of data and services, as depicted in the diagram in |
193 |
Fig.~\ref{fig:archdiag}. |
Fig.~\ref{fig:archdiag}. |
2219 |
|
|
2220 |
\section{Change History} |
\section{Change History} |
2221 |
|
|
2222 |
|
\subsection{Changes from WD-2020-04-24} |
2223 |
|
|
2224 |
|
Editorial changes only. |
2225 |
|
|
2226 |
\subsection{Changes from WD-2020-02-12} |
\subsection{Changes from WD-2020-02-12} |
2227 |
|
|
2228 |
\begin{itemize} |
\begin{itemize} |
2309 |
were updated to match that specified in the XSDs (i.e. to include a |
were updated to match that specified in the XSDs (i.e. to include a |
2310 |
``v'' preceding the version field). |
``v'' preceding the version field). |
2311 |
\item Several capability metadata with types xs:int and xs:float were |
\item Several capability metadata with types xs:int and xs:float were |
2312 |
changed to xs:positiveInterger xs:double to allow for larger/more |
changed to xs:positive\-Integer xs:double to allow for larger/more |
2313 |
precise numbers. |
precise numbers. |
2314 |
\item Capability metadata that indicated maximum allowed values (e.g. |
\item Capability metadata that indicated maximum allowed values (e.g. |
2315 |
<maxRecords>, <maxImageSize>, etc.) were made optional to avoid |
<maxRecords>, <maxImageSize>, etc.) were made optional to avoid |
2316 |
large, meaningless numbers from being provided. Now not specifying |
large, meaningless numbers from being provided. Now not specifying |
2317 |
a value is the preferred way to indicate that no upper limit |
a value is the preferred way to indicate that no upper limit |
2318 |
applies. |
applies. |
2319 |
\item Semantic definition of <sia:maxImageExtent> clarified to |
\item Semantic definition of sia:maxImageExtent clarified to |
2320 |
differentiate it from <sia:maxQueryRegionSize> |
differentiate it from sia:max\-QueryRegionSize |
2321 |
\item The type for <sia:maxImageSize> was changed to xs:positiveInteger, |
\item The type for <sia:maxImageSize> was changed to xs:positiveInteger, |
2322 |
a single number that represents the length of a side in pixels. The |
a single number that represents the length of a side in pixels. The |
2323 |
sia:ImageSize type (no longer needed) was dropped. |
sia:ImageSize type (no longer needed) was dropped. |