From 14d87959cbd2a8c965266dc13cd8299732d51bb5 Mon Sep 17 00:00:00 2001
From: Mark Taylor <m.b.taylor@bristol.ac.uk>
Date: Tue, 3 Feb 2026 14:55:56 +0000
Subject: [PATCH] Update XSD for version 1.6

I forgot to do this when I bumped the document version
a few commits ago.  The main effect is to allow the value "1.6"
for the version attribute of the VOTABLE element.
That may be the only substantial difference between the 1.5
and 1.6 schemas, but possibly we'll come up with some other
things before 1.6 REC.

I'm following previous VOTable practice by labelling the
xs:schema element with the attribute version="1.6pre"
while 1.6 is still under development.  I'm not exactly sure
what the effect of that is, but I think it's at least harmless
(as long as we remember to change it to "1.6" before REC).
---
 VOTable.xsd | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/VOTable.xsd b/VOTable.xsd
index 0979a2a..e551a30 100644
--- a/VOTable.xsd
+++ b/VOTable.xsd
@@ -27,12 +27,13 @@
 .Version 1.5pre2: MD: vocabularising system attribute in COOSYS
 .Version 1.5pre3: TD: Undo the FIELDref/PARAMref addition to COOSYS
 .Version 1.5: TD: Update version to 1.5 for REC
+.Version 1.6: MT: Update version to 1.6pre
 -->
 <xs:schema
    xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
    xmlns="http://www.ivoa.net/xml/VOTable/v1.3"
    targetNamespace="http://www.ivoa.net/xml/VOTable/v1.3"
-   version="1.5"
+   version="1.6pre"
 >
 <xs:annotation><xs:documentation>
     VOTable is meant to serialize tabular documents in the
@@ -626,6 +627,7 @@
          <xs:enumeration value="1.3"/>
          <xs:enumeration value="1.4"/>
          <xs:enumeration value="1.5"/>
+         <xs:enumeration value="1.6"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>