Skip to content

Perparing for second 1.1 WD #12

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
msdemlei merged 1 commit into from
Jun 3, 2026
Merged

Perparing for second 1.1 WD #12

Show file tree
Hide file tree
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
18 changes: 9 additions & 9 deletions TAPRegExt-v1.1.xsd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,8 +63,8 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
The capabilities of a TAP server.
</xs:documentation>
<xs:documentation>
The capabilities attempt to define most issues that the
TAP standard leaves to the implementors ("may", "should").
The capabilities attempt to define most properties that the
TAP standard leaves to the implementors (“may”, “should”).
</xs:documentation>
</xs:annotation>
<xs:complexContent>
Expand Down Expand Up @@ -275,7 +275,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xs:complexType name="DataModelType">
<xs:annotation>
<xs:documentation>
An IVOA defined data model, identified by an IVORN
An IVOA defined data model, identified by an Ivoid
intended for machine consumption and a short label
intended for human comsumption.
</xs:documentation>
Expand Down Expand Up @@ -393,8 +393,8 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
</xs:documentation>
<xs:documentation>
A feature type is a language-dependent concept like
"user defined function", "geometry support", or possibly
"units supported". A featureList gives all features of
“user defined function”, “geometry support”, or possibly
“units supported”. A featureList gives all features of
a given type applicable for the service. Multiple featureLists
are possible.

Expand All @@ -403,7 +403,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
the value of which will typically be an IVOID.
To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with "features-".
resource record and look for keys starting with “features-”.
</xs:documentation>
</xs:annotation>
<xs:sequence>
Expand Down Expand Up @@ -498,7 +498,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>
Other values of FORMAT ("shorthands") that make the service return
Other values of FORMAT (“shorthands”) that make the service return
documents with the media type.
</xs:documentation>
</xs:annotation>
Expand All @@ -520,7 +520,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
or StandardsRegExt document defining the format more
precisely. To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with "output-".
resource record and look for keys starting with “output-”.
</xs:documentation>
</xs:annotation>
</xs:attribute>
Expand All @@ -536,7 +536,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Descriptions can be obtained by dereferencing this
IVOID. To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with "upload-".
resource record and look for keys starting with “upload-”.

You can register custom upload methods, but you must use the
standard IVOIDs for the upload methods defined in the TAP
Expand Down
20 changes: 10 additions & 10 deletions TAPRegExt.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,7 @@ \subsection{Declaring Instantiated Data Models}
\renewcommand*\descriptionlabel[1]{%
\hbox to 5.5em{\emph{#1}\hfil}}\vspace{2ex}\noindent\textbf{\xmlel{tr:DataModelType} Type Schema Documentation}

\noindent{\small{}An IVOA defined data model, identified by an IVORN
\noindent{\small{}An IVOA defined data model, identified by an Ivoid
intended for machine consumption and a short label
intended for human comsumption.\par}

Expand Down Expand Up @@ -511,8 +511,8 @@ \subsection{Languages Supported}
a specific type implemented by the language.\par}

\noindent{\small{}A feature type is a language-dependent concept like
{"}user defined function{"}, {"}geometry support{"}, or possibly
{"}units supported{"}. A featureList gives all features of
“user defined function”, “geometry support”, or possibly
“units supported”. A featureList gives all features of
a given type applicable for the service. Multiple featureLists
are possible.

Expand All @@ -521,7 +521,7 @@ \subsection{Languages Supported}
the value of which will typically be an IVOID.
To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with {"}features-{"}.\par}
resource record and look for keys starting with “features-”.\par}

\vspace{1ex}\noindent\textbf{\xmlel{tr:LanguageFeatureList} Type Schema Definition}

Expand Down Expand Up @@ -692,7 +692,7 @@ \subsection{Output Formats}
or StandardsRegExt document defining the format more
precisely. To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with {"}output-{"}.
resource record and look for keys starting with “output-”.
\end{description}

\item[forMode]
Expand Down Expand Up @@ -726,7 +726,7 @@ \subsection{Output Formats}
\item[Element \xmlel{alias}]
\begin{description}
\item[Type] string: \xmlel{xs:token}
\item[Meaning] Other values of FORMAT ({"}shorthands{"}) that make the service return
\item[Meaning] Other values of FORMAT (“shorthands”) that make the service return
documents with the media type.
\item[Occurrence] optional; multiple occurrences allowed.

Expand Down Expand Up @@ -805,7 +805,7 @@ \subsection{Upload Methods}
Descriptions can be obtained by dereferencing this
IVOID. To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with {"}upload-{"}.
resource record and look for keys starting with “upload-”.

You can register custom upload methods, but you must use the
standard IVOIDs for the upload methods defined in the TAP
Expand Down Expand Up @@ -1431,8 +1431,8 @@ \subsection{The Capability Record}

\noindent{\small{}The capabilities of a TAP server.\par}

\noindent{\small{}The capabilities attempt to define most issues that the
TAP standard leaves to the implementors ({"}may{"}, {"}should{"}).\par}
\noindent{\small{}The capabilities attempt to define most properties that the
TAP standard leaves to the implementors (“may”, “should”).\par}

\vspace{1ex}\noindent\textbf{\xmlel{tr:TableAccess} Type Schema Definition}

Expand Down Expand Up @@ -1545,7 +1545,7 @@ \section{Obtaining the Schema}

The recommended way to obtain the TAPRegExt schema is to retrieve the
namespace URI, \url{http://www.ivoa.net/xml/TAPRegExt/v1.0}, which will
usually involve one or two redirects. Despite to suggestive name, this
usually involve one or two redirects. Despite the suggestive name, this
will always return the latest version of the TAPRegExt schema in major
version 1; see \citet{2018ivoa.spec.0529H} for the background of this
somewhat unfortunate circumstance.
Expand Down
Loading