Skip to content
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

modifying provenance subsection #100

Merged
merged 1 commit into from
Feb 10, 2023
Merged

modifying provenance subsection #100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 18 additions & 11 deletions DataLink.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -280,11 +280,12 @@ \subsubsection{Datasets linked to an astronomical source}
\subsubsection{Metadata and data related to provenance entities}

The IVOA Provenance datamodel \citep{pr:provdm} represents metadata
tracing the history of data. This information can be retrieved through
ProvTAP \citep{iwd:provtap} or ProvSAP \citep{iwd:provsap} DAL services.
tracing the history of the data. This information can be stored and retrieved
in several ways including in DAL services.
The Entity instances represent the state of the data items between
various steps of the data processing flow. ``Entities'' can be hooked
to the more complete data they represent using the \blinks\ endpoint.
Reversely full provenance records can be linked to standard discovery service rows using the same endpoint.

\section{The \blinks\ endpoint}

Expand Down Expand Up @@ -950,15 +951,19 @@ \subsection{Input PARAMs}

For user-specified input PARAMs the value attribute is empty (\attval{value}{})
and the user supplies the value(s). The PARAM specifies the type of value required via
the datatype, arraysize, and xtype attributes; this may be augmented further by the ucd
and units attributes and a child DESCRIPTION element. To allow for expressive, usable user
interfaces, operators SHOULD indicate useful ranges of parameters in MIN and MAX children
or, for enumerated parameters, indicate the valid values in OPTIONS. In general, services
may have parameters of this type that are optional or required and this distinction is
not currently described; services \rfcshould\ use a child DESCRIPTION element to document any
requirements. Clients should assume that these user-specified parameters are optional, but
that specifying some of them may be necessary to have the service do something useful.
Services \rfcshould\ respond with an informative error message if the input is not adequate to
the datatype, arraysize, and xtype attributes; this may be augmented further by the ucd,
units and utypes\footnote{An example of utype usage for service
parameters is described in section 3.4 of the SODA specification} attributes
and a child DESCRIPTION element. To allow for expressive, usable user
interfaces, operators SHOULD indicate useful ranges of parameters in MIN and MAX children
or, for enumerated parameters, indicate the valid values in OPTIONS in case
these values cannot be inferred from relevant metadata retrieved
before the service descriptor discovery. In general, services
may have parameters of this type that are optional or required and this distinction is
not currently described; services \rfcshould\ use a child DESCRIPTION element to document any
requirements. Clients should assume that these user-specified parameters are optional, but
that specifying some of them may be necessary to have the service do something useful.
Services \rfcshould\ respond with an informative error message if the input is not adequate to
perform the operations(s).

\subsection{Example: Service Descriptor for the \blinks\ Capability}
Expand Down Expand Up @@ -1301,6 +1306,8 @@ \section{Changes}
\subsection{DataLink-1.1}

\begin{itemize}
\item added optional local\_semantics to identify corresponding rows
for different IDs in the same service
\item relax content-type usage to allow any valid VOTable MIME type
\item INFO element with standardID mandatory in \blinks\ response
\item added optional content\_qualifier to describe link target content with terms from
Expand Down