International Virtual Observatory Alliance

Difference: RfcPage (3 vs. 4)

Revision 42009-08-18 - MarkTaylor

META TOPICPARENT	name="IvoaVOTable"

VOTable1.2: Request for Comments

This document will act as RFC centre for the VOTable-1.2 Proposed Recommendation.

Review period: 2009 July 10 – 2009 August 21 (6 weeks)

In order to add a comment to the document, please edit this page and add your comment to the list below (include your WikiName so authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.

Discussions about any of the comments or responses should be conducted on the VOTable mailing list, votable@ivoa.net.

Comments from the community

Deleted:

<
<

Sample comment by WikiName
- Response (by WikiName)

Added:

>
>

From MarkTaylor

I will flag up here a couple of issues that I've noted in earlier drafts of this document. Francois and I disagree on them; I am happy to concede if other reviewers of the document don't regard them as problematic.

As I have argued elsewhere (http://www.ivoa.net/forum/votable/0907/date.htm) I do not believe that the introduction of the spurious "encoding" attribute on the TD element is justified.
As I and others have argued elsewhere (http://www.ivoa.net/forum/votable/0903/date.htm) the changes to the INFO element may cause backward compatibility issues. These issues are probably not too serious, but may cause annoyance, and I'm not convinced that justification for the change has been demonstrated.

There is also a small number of typos and minor items:

Section 3: "Each Resource element contains one or more TABLE elements" - should be "... zero or more ...".
Section 4.1: "elment" should be "element".
Section 4.3: "expresses a spatial of temporal coordinate" should be "... spatial or temporal ...".
Section 4.7: The new paragraph beginning "section 6 indicates ...": I don't believe that a null scalar "char" value can be represented with an empty TD element. Also, use in this paragraph of the phrase "default null value" seems a bit confusing to me; I suggest instead the phrase "representation of the null value" or "null representation".
Section 5.2: The example here contains a PARAM element with text content; this is not permitted.

Comments from the TCG during the normal RFC period (2009 July 10 -- 2009 August 21)

Applications (Tom McGlynn, Mark Taylor)

Data Access Layer (Keith Noddle, Jesus Salgado)

Data Model (Mireille Louys, AnitaRichards)

Grid&Web Sevices (Matthew Graham, Paul Harrison)

Registry (Ray Plante, Aurelien Stebe)

Semantics (Sebastien Derriere, Norman Gray)

VOEvent (Rob Seaman, Alasdair Allan)

VO Query Language (Pedro Osuna, Yuji Shirasaki)

VOTable (Francois Ochsenbein)

Standard and Processes (Francoise Genova)

Astro RG (Masatoshi Ohishi)

Data Curation & Preservation (Bob Hanisch)

Theory (Herve Wozniak, Claudio Gheller)

TCG (ChristopheArviset, Severin Gaudet)

<-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

View topic | History: r45 < r44 < r43 < r42 | More topic actions...