VOTable 1.4 Working Draft Notes

One other tiny doc bug; the schema has

      <xs:attribute name="timescale" use="required" type="xs:token">
        <xs:annotation>
          <xs:documentation>
            This is the time scale used.  Values SHOULD be
            taken from the IVOA timescale ( [[http://ivoa.net/rdf/timescale][http://ivoa.net/rdf/timescale]]).
          </xs:documentation>
        </xs:annotation>
      </xs:attribute>

I think "IVOA timescale" should read "IVOA timescale vocabulary" (matching the wording for refposition).

Sec 7.1

• Change the RESOURCE element diagram to clarify the necessary position(s) of INFO children.
• Include a comment that in case of any discrepancies between the schema and the diagram, the schema is definitive.

Also added page break prior to section 1.4 so that architecture figure shows up somewhere near the relevant text.

 "documents may include schemaLocation attribute" 
 -> "documents may include the schemaLocation attribute"
 (or "a" or "some" ...)
Sec 3.5:
 "A \elem{TIMESYS} element referenced via a ref attribute MUST..."
 -> "A \elem{TIMESYS} element referenced via a \attr{ref} attribute MUST..."?
Sec 4.1, item concerning the ref attribute:
 "(reference to the GROUP attribute which specifies the coordinate frame)"
 -> "(reference to the COOSYS attribute which specifies the coordinate frame)"

Section 3.5: reword the sentence:

The TIMESYS element defines such a time system and gives itself the identifies itself with ID="time frame".

to

In the example, the TIMESYS element describes that time system. The TIMESYS ID value just needs to be unique within the document so that it can be referenced by FIELDs or PARAMs.

Section 3 reworked to clarify namespace and schema versioning.