Opened 11 years ago
Closed 10 years ago
#206 closed enhancement (fixed)
Update VOTable spec to 1.3
Reported by: | MatthewWhiting | Owned by: | MatthewWhiting |
---|---|---|---|
Priority: | high | Milestone: | Release-1.6 |
Component: | Output | Version: | 1.5 |
Severity: | normal | Keywords: | |
Cc: |
Description
From ASKAP ticket 5729:
Hi Ben, I’m writing a simple reader to load the VO Table XML files and I’m trying to use schema driven parsers to do it, however I’ve run into a small issue and James pointed me your way. The issue is that the namespaces on the selavy-fitResults.xml and selavy-fitResults_full.xml files are: <VOTABLE version="1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.ivoa.net/xml/VOTable/VOTable/v1.1"> However, they should be something like this (which avoids the use of a ns prefix): <VOTABLE version="1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.ivoa.net/xml/VOTable/v1.1" xsi:schemaLocation="http://www.ivoa.net/xml/VOTable/VOTable/v1.1"> The differences are highlighted in bold and I’ve verified the second form does pass my unit tests. Is this a change that you can make? Cheers, Simon
And Ben notes in the ticket:
Looking at the IVOA standards Duchamp implements 1.1, where the change Simon asks for seems to be consistent with the 1.3 standard. The following document specifies VOTable 1.3: http://www.ivoa.net/documents/VOTable/20130920/ Its time to update Duchamp to conform to VOTable 1.3 I guess.
Do this for the next release so we can incorporate into Selavy pronto.
Change History (3)
comment:1 Changed 11 years ago by
Status: | new → assigned |
---|
comment:3 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
That link again: http://www.ivoa.net/documents/VOTable/20130920/