Skip to content

Adjustments to section Role in the VO Architecture #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pdowler merged 3 commits into from
Sep 19, 2025
Merged

Adjustments to section Role in the VO Architecture #57

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3105e37
remove obsolete paragraph
mbtaylor May 12, 2025
160b876
Meas and Coords are now REC
mbtaylor May 12, 2025
002a60b
reference some DALI-using standards in the Role section
mbtaylor May 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 13 additions & 16 deletions DALI.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,33 +46,30 @@ \subsection{Role within the VO Architecture}

\begin{figure}
\centering

% Get the architecture diagram from the TCG chair
% http://wiki.ivoa.net/twiki/bin/view/IVOA/IvoaTCG
% If they give you a PDF, for now dumb it down to a png by
% convert -antialias -density 72x72 archdiag.pdf archdiag.png
% Oh -- Notes don't need this; you'd have to remove archdiag.png
% from FIGURES in the Makefile, too.

\includegraphics[width=0.9\textwidth]{role_diagram.pdf}
\caption{Architecture diagram for this document}
\label{fig:archdiag}
\end{figure}

Astronomical coordinate values accepted and returned by DAL services use a
string representation of the Space-Time Coordinates \citep{2007ivoa.spec.1030R} data
model. The
concrete DAL service specification defines whether the returned resources are
serializations of a particular standard data model. For preserving backwards
compatibility or to enable service-specific use cases, the concrete DAL service
specification may explicitly specify the use of ad-hoc Utypes.

A registry extension schema, usually extending VODataService \citep{2021ivoa.spec.1102D},
may be used to
describe the capabilities of a DAL service. This schema is used within the
VOSI-capabilities \citep{2017ivoa.spec.0524G} resource and in registry records for the
service.

The intention of DALI is to promote consistency of behaviour
between services in the DAL family where appropriate.
Standards such as
ConeSearch \citep{2008ivoa.specQ0222P},
SIA \citep{2015ivoa.spec.1223D},
SSA \citep{2012ivoa.spec.0210T} and
TAP \citep{2019ivoa.spec.0927D}
fall into this category,
but the details of compliance are the responsibility of those
specific standards, and may not in all cases conform exactly
to the recommendations here, for instance in the case of ConeSearch 1.03
because the text predates DALI.

\subsection{Example Usage of the DALI Specification}
The DALI specification defines common elements that make up Data Access Layer
(DAL) services. DAL service specifications will refer to the sections in this
Expand Down
Binary file modified role_diagram.pdf
View file
Open in desktop
Binary file not shown.
11 changes: 7 additions & 4 deletions role_diagram.svg
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
11 changes: 7 additions & 4 deletions role_diagram.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,13 @@
<rec name="MOC" x="430" y="405" w="33"/>

<thisrec name="DALI" x="310" y="290" w="33"/>

<rec name="STC" x="580" y="255" w="30"/>
<prerec name="Meas" x="456" y="305" w="35"/>
<prerec name="Coords" x="501" y="305" w="44"/>
<rec name="ConeSearch" x="665.5" y="155" w="69"/>
<rec name="SSAP" x="682" y="180" w="36"/>
<rec name="SIAP" x="683.5" y="230" w="33"/>
<rec name="TAP" x="686" y="255" w="28"/>

Copy link
Copy Markdown
Collaborator

@pdowler pdowler May 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we could nominally add DAP (prerec) since I think the WG has agreed to pursue this in favour of more SIA, SSA, etc. And there is an ivoa-std repo where the work is happening.

I also just transferred a SLAP2 repo to ivoa-std, so that's nominally another... maybe too far in future?

<rec name="Meas" x="456" y="305" w="35"/>
<rec name="Coords" x="501" y="305" w="44"/>
<prerec name="Transform" x="465" y="330" w="60"/>

<rec name="UWS" x="633.5" y="460" w="33"/>
Expand Down