Dropping vs:StandardSTC.

I don't think there have ever been records using this type, and I can't
remember why I would have postpone dropping the type.

Author: msdemlei

VODataService-v1.3.xsd

@@ -1472,49 +1472,6 @@
       </xs:simpleContent>
    </xs:complexType>
 
-   <xs:complexType name="StandardSTC">
-      <xs:annotation>
-         <xs:documentation>
-           A description of standard space-time coordinate systems,
-           positions, and regions.
-         </xs:documentation>
-         <xs:documentation>
-            This resource type is deprecated, and no resource records
-            of this type exist in the Registry.  It will be removed
-            in version 1.3 of VODataService.
-         </xs:documentation>
-      </xs:annotation>
-
-      <xs:complexContent>
-         <xs:extension base="vr:Resource">
-            <xs:sequence>
-
-               <xs:element name="stcDefinitions"
-                           type="stc:stcDescriptionType"
-                           minOccurs="1" maxOccurs="unbounded">
-                  <xs:annotation>
-                     <xs:documentation>
-                       An STC description of coordinate systems,
-                       positions, and/or regions
-                     </xs:documentation>
-                     <xs:documentation>
-                       Each system, position, and region description
-                       should have a an XML ID assigned to it.
-                     </xs:documentation>
-                     <xs:documentation>
-                       Because the STC schema sets
-                       elementFormDefault="qualified", it is
-                       recommended that this element specify the STC
-                       default namespace via an xmlns namespace.
-                     </xs:documentation>
-                  </xs:annotation>
-               </xs:element>
-
-            </xs:sequence>
-         </xs:extension>
-      </xs:complexContent>
-   </xs:complexType>
-
    <xs:complexType name="ForeignKey">
       <xs:annotation>
          <xs:documentation>

VODataService.tex

@@ -546,11 +546,13 @@ \subsubsection{VODataService Resource Classes}
 
 Two further resource classes defined by VODataService 1.1,
 \xmlel{vs:DataCollection} and \xmlel{vs:StandardSTC},
-are deprecated since version 1.2.
+have been deprecated since version 1.2.
 Resource record authors are requested to migrate or discard resource
-records using these deprecated types.  If all such records have
-disappeared from the VO by version 1.4 of this specification, their
-type declarations may be removed from the schema.
+records using these deprecated types.  \xmlel{vs:StandardSTC} has been
+dropped in VODataService 1.3 since there were no resource records using
+that type in the VO Registry. We will similarly drop
+\xmlel{vs:DataCollection} when the last records using the type have
+vanished from the Registry.
 
 \subsubsection{Discovering Data Within Other Services}
 \label{sect:discoverdata}
@@ -1017,16 +1019,6 @@ \subsubsection{DataCollection}
 This type may be removed from the schema when all resource records using
 it have vanished from the VO Registry.
 
-\subsubsection{StandardSTC}
-
-The \xmlel{vs:StandardSTC} type is deprecated and should no longer be
-used in new resource records.  Since the XML serialisation of the STC 1
-data model was never promoted to an IVOA recommendation, there also is
-no properly standardised way of creating such records.  Since no such
-records ever existed in the Registry, this type will probably be removed
-from the schema in version 1.4 of this specification.
-
-
 
 \subsection{Coverage in Space, Time, and Spectrum}
 \label{sect:cover}
@@ -2944,6 +2936,7 @@ \subsection{Changes since PR-1.3-20260601}
 \begin{itemize}
 \item Dropping an outdated example for how one would do ADQL functions
 in the tableset (which we don't do).
+\item Dropping StandardSTC after all.
 \end{itemize}
 
 \subsection{Changes since WD-1.3-20260324}