From 06b1595a11d9b4003dbb6093afe99182bc6b4aa3 Mon Sep 17 00:00:00 2001 From: Markus Demleitner Date: Wed, 3 Jun 2026 20:04:25 +0200 Subject: [PATCH 1/2] Perparing for second 1.1 WD --- TAPRegExt-v1.1.xsd | 18 +++++++++--------- TAPRegExt.tex | 20 ++++++++++---------- 2 files changed, 19 insertions(+), 19 deletions(-) diff --git a/TAPRegExt-v1.1.xsd b/TAPRegExt-v1.1.xsd index 8c191b7..b9d2645 100644 --- a/TAPRegExt-v1.1.xsd +++ b/TAPRegExt-v1.1.xsd @@ -63,8 +63,8 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> The capabilities of a TAP server. - 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”). @@ -275,7 +275,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> - 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. @@ -393,8 +393,8 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 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. @@ -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-”. @@ -498,7 +498,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> minOccurs="0" maxOccurs="unbounded"> - 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. @@ -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-”. @@ -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 diff --git a/TAPRegExt.tex b/TAPRegExt.tex index d3c8add..da4b571 100644 --- a/TAPRegExt.tex +++ b/TAPRegExt.tex @@ -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} @@ -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. @@ -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} @@ -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] @@ -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. @@ -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 @@ -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} @@ -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. From 5b3237d4378a0ea407ecde1038119fff371b9567 Mon Sep 17 00:00:00 2001 From: Markus Demleitner Date: Wed, 3 Jun 2026 20:07:43 +0200 Subject: [PATCH 2/2] Adding author email --- Makefile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index e576cff..4cde8ea 100644 --- a/Makefile +++ b/Makefile @@ -30,6 +30,8 @@ VECTORFIGURES = # Additional files to distribute (e.g., CSS, schema files, examples...) AUX_FILES = $(SCHEMA_FILE) sample.xml +AUTHOR_EMAIL=msdemlei@ari.uni-heidelberg.de + -include ivoatex/Makefile ivoatex/Makefile: @@ -40,7 +42,7 @@ ivoatex/Makefile: sample.xml: make-sample.sh ./make-sample.sh - + install: # local to Markus' setup ~/gavo/standards/fixschema $(SCHEMA_FILE) > ~/gavo/trunk/gavo/resources/schemata/TAPRegExt.xsd