Difference: VOTable14WorkingDraftNotes (1 vs. 16)

Revision 162019-06-03 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

This page is now frozen. Please make future comments on VOTable 1.4 Request For Comments. -- TomDonaldson - 2019-05-03

Changed:
<
<

Active Proposed Changes

>
>

 
Changed:
<
<
The current working draft is WD-VOTable-1.4.20190318
>
>

Change Logs for WD-VOTable-1.4

 
Changed:
<
<
This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date

Maybe it's worth a note near where you discuss schemaLocation in section 3 advising to use the version-specific URL for schemaLocation attributes for that reason?

  Discuss at IVOA meeting 2019-05-02
>
>
Description Source volute Revision(s)

Between WD-VOTable-1.4.20190403 and PR-VOTable-1.4.20190604

Duplication of words:

Page 11 . section 3.2, "...represents therefore a a valid name".
Page 22 section 5.2 "...a cell value flagged as null is filled with with the NaN value...".
email 5487
|

One other tiny doc bug; the schema has

      <xs:attribute name="timescale" use="required" type="xs:token">
Deleted:
<
<
|

One other tiny doc bug I noticed today; the schema has
      <xs:attribute name="timescale" use="required" type="xs:token">
  This is the time scale used. Values SHOULD be taken from the IVOA timescale ( http://ivoa.net/rdf/timescale).
Changed:
<
<
I think "IVOA timescale" should read "IVOA timescale vocabulary" (matching the wording for refposition).

| | Include in next 1.4 draft | 2019-05-02 |
>
>

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

| | 5487 |

Fix vocabulary URLs to use www.ivoa.net. (rather than ivoa.net; this follows the pattern set by Datalink and VOResource)

  5406
Deleted:
<
<

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Description Source volute Revision(s)
 

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403

Deliver the document for publishing properly so that images show up the html version. N/A N/A

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.

email 5378

Sec 5:

 <INFO name="HISTORY">
The very first Virtual Telescope observation made in 2002
</INFO>
This is not legal - the value attribute
(optional at VOTable 1.0 but mandatory since VOTable 1.1)
is missing. It should read:
<INFO name="HISTORY"
value="The very first Virtual Telescope observation made in 2002"/>
Also, the INFO needs to be moved to the top of the RESOURCE as required by the VOTable schema.
email 5377
Sec 3:
 "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)"
email 5367
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368

Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318

Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 152019-05-03 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

This page is now frozen. Please make future comments on VOTable 1.4 Request For Comments. -- TomDonaldson - 2019-05-03

Active Proposed Changes

Changed:
<
<
The current working draft is WD-VOTable-1.4.20190318
>
>
The current working draft is WD-VOTable-1.4.20190318
  This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date

Maybe it's worth a note near where you discuss schemaLocation in section 3 advising to use the version-specific URL for schemaLocation attributes for that reason?

  Discuss at IVOA meeting 2019-05-02

One other tiny doc bug I noticed today; 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).

  Include in next 1.4 draft 2019-05-02

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Description Source volute Revision(s)

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403

Deliver the document for publishing properly so that images show up the html version. N/A N/A

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.

email 5378

Sec 5:

 <INFO name="HISTORY">
The very first Virtual Telescope observation made in 2002
</INFO>
This is not legal - the value attribute
(optional at VOTable 1.0 but mandatory since VOTable 1.1)
is missing. It should read:
<INFO name="HISTORY"
value="The very first Virtual Telescope observation made in 2002"/>
Also, the INFO needs to be moved to the top of the RESOURCE as required by the VOTable schema.
email 5377
Sec 3:
 "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)"
email 5367
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368

Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318

Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 142019-05-03 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Added:
>
>
This page is now frozen. Please make future comments on VOTable 1.4 Request For Comments. -- TomDonaldson - 2019-05-03
 

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date

Maybe it's worth a note near where you discuss schemaLocation in section 3 advising to use the version-specific URL for schemaLocation attributes for that reason?

  Discuss at IVOA meeting 2019-05-02

One other tiny doc bug I noticed today; 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).

  Include in next 1.4 draft 2019-05-02

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Description Source volute Revision(s)

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403

Deliver the document for publishing properly so that images show up the html version. N/A N/A

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.

email 5378

Sec 5:

 <INFO name="HISTORY">
The very first Virtual Telescope observation made in 2002
</INFO>
This is not legal - the value attribute
(optional at VOTable 1.0 but mandatory since VOTable 1.1)
is missing. It should read:
<INFO name="HISTORY"
value="The very first Virtual Telescope observation made in 2002"/>
Also, the INFO needs to be moved to the top of the RESOURCE as required by the VOTable schema.
email 5377
Sec 3:
 "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)"
email 5367
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368

Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318

Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 132019-05-03 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
Changed:
<
<

Maybe it's worth a note near

where you discuss schemaLocation in section 3 advising to use the

version-specific URL for schemaLocation attributes for that reason?

  Discuss at IVOA meeting 2019-05-02
|

One other tiny doc bug I noticed today; the schema has
>
>

Maybe it's worth a note near where you discuss schemaLocation in section 3 advising to use the version-specific URL for schemaLocation attributes for that reason?

  Discuss at IVOA meeting 2019-05-02
|

One other tiny doc bug I noticed today; the schema has
  This is the time scale used. Values SHOULD be taken from the IVOA timescale ( http://ivoa.net/rdf/timescale). I think "IVOA timescale" should read "IVOA timescale vocabulary"
Changed:
<
<
(matching the wording for refposition).

| | Include in next 1.4 draft | 2019-05-02 |
>
>
(matching the wording for refposition).

| | Include in next 1.4 draft | 2019-05-02 |
 

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Description Source volute Revision(s)

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403

Deliver the document for publishing properly so that images show up the html version. N/A N/A

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.

email 5378

Sec 5:

 <INFO name="HISTORY">
The very first Virtual Telescope observation made in 2002
</INFO>
This is not legal - the value attribute
(optional at VOTable 1.0 but mandatory since VOTable 1.1)
is missing. It should read:
<INFO name="HISTORY"
value="The very first Virtual Telescope observation made in 2002"/>
Also, the INFO needs to be moved to the top of the RESOURCE as required by the VOTable schema.
email 5377
Sec 3:
 "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)"
email 5367
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368

Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318

Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 122019-05-02 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
Changed:
<
<
       
>
>

Maybe it's worth a note near

where you discuss schemaLocation in section 3 advising to use the

version-specific URL for schemaLocation attributes for that reason?

  Discuss at IVOA meeting 2019-05-02
Added:
>
>

One other tiny doc bug I noticed today; 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).

  Include in next 1.4 draft 2019-05-02
 

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Description Source volute Revision(s)

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403

Deliver the document for publishing properly so that images show up the html version. N/A N/A

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.

email 5378

Sec 5:

 <INFO name="HISTORY">
The very first Virtual Telescope observation made in 2002
</INFO>
This is not legal - the value attribute
(optional at VOTable 1.0 but mandatory since VOTable 1.1)
is missing. It should read:
<INFO name="HISTORY"
value="The very first Virtual Telescope observation made in 2002"/>
Also, the INFO needs to be moved to the top of the RESOURCE as required by the VOTable schema.
email 5377
Sec 3:
 "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)"
email 5367
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368

Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318

Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 112019-04-04 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
       

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Description Source volute Revision(s)

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403

Added:
>
>
Deliver the document for publishing properly so that images show up the html version. N/A N/A
 

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.

email 5378

Sec 5:

 <INFO name="HISTORY">
The very first Virtual Telescope observation made in 2002
</INFO>
This is not legal - the value attribute
(optional at VOTable 1.0 but mandatory since VOTable 1.1)
is missing. It should read:
<INFO name="HISTORY"
value="The very first Virtual Telescope observation made in 2002"/>
Also, the INFO needs to be moved to the top of the RESOURCE as required by the VOTable schema.
email 5377
Sec 3:
 "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)"
email 5367
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368

Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318

Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 102019-04-03 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
       

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Deleted:
<
<
Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403
 
Description Source volute Revision(s)
Changed:
<
<

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.

email  
>
>

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403

Added:
>
>

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.

email 5378
 

Sec 5:

 <INFO name="HISTORY">
The very first Virtual Telescope observation made in 2002
</INFO>
This is not legal - the value attribute
(optional at VOTable 1.0 but mandatory since VOTable 1.1)
is missing. It should read:
<INFO name="HISTORY"
value="The very first Virtual Telescope observation made in 2002"/>
Also, the INFO needs to be moved to the top of the RESOURCE as required by the VOTable schema.
email 5377
Sec 3:
 "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)"
email 5367
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368
Changed:
<
<
>
>

Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318

Deleted:
<
<
Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318:

Description Source volute Revision(s)
 
Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334
Changed:
<
<
>
>

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218

Deleted:
<
<
Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218:

Description Source volute Revision(s)
 

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 92019-04-03 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
Changed:
<
<
|

Sec 5:

       <INFO name="HISTORY">
>
>
       
Deleted:
<
<
The very first Virtual Telescope observation made in 2002 I've just noticed this is not legal - the value attribute (optional at VOTable 1.0 but mandatory since VOTable 1.1) is missing. It should read: <INFO name="HISTORY" value="The very first Virtual Telescope observation made in 2002"/>

| email | In next 1.4 draft | 2019-03-22 |
 

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Changed:
<
<
Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.2019????
>
>
Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.20190403
 
Description Source volute Revision(s)
Added:
>
>

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.

email  

Sec 5:

 <INFO name="HISTORY">
The very first Virtual Telescope observation made in 2002
</INFO>
This is not legal - the value attribute
(optional at VOTable 1.0 but mandatory since VOTable 1.1)
is missing. It should read:
<INFO name="HISTORY"
value="The very first Virtual Telescope observation made in 2002"/>
Also, the INFO needs to be moved to the top of the RESOURCE as required by the VOTable schema.
email 5377
 
Sec 3:
 "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)"
email 5367
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368

Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318:

Description Source volute Revision(s)
Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218:

Description Source volute Revision(s)

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 82019-03-31 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
Changed:
<
<
|

Sec 5:

       <INFO name="HISTORY">
>
>
|

Sec 5:

       <INFO name="HISTORY">
  The very first Virtual Telescope observation made in 2002 I've just noticed this is not legal - the value attribute (optional at VOTable 1.0 but mandatory since VOTable 1.1) is missing. It should read: <INFO name="HISTORY" value="The very first Virtual Telescope observation made in 2002"/>

| email | In next 1.4 draft | 2019-03-22 |
Deleted:
<
<
Probably the "STC" reference in figure 1 should be removed now. email In next 1.4 draft unless it's difficult. 2019-03-22
 

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.2019????

Description Source volute Revision(s)
Changed:
<
<
Sec 3:
   "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)"
email 5367
>
>
Sec 3:
 "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)"
email 5367
Added:
>
>
Remove (somewhat crudely) STC from figure 1, the architecture diagram. email 5368
  Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318:

Description Source volute Revision(s)
Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218:

Description Source volute Revision(s)

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 72019-03-31 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
Changed:
<
<
|

Sec 3:
>
>
|

Sec 5:

       <INFO name="HISTORY">
Deleted:
<
<
"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)" Sec 5:
  The very first Virtual Telescope observation made in 2002 I've just noticed this is not legal - the value attribute (optional at VOTable 1.0 but mandatory since VOTable 1.1) is missing. It should read: <INFO name="HISTORY" value="The very first Virtual Telescope observation made in 2002"/>

| email | In next 1.4 draft | 2019-03-22 |
Probably the "STC" reference in figure 1 should be removed now. email In next 1.4 draft unless it's difficult. 2019-03-22

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.2019????

Description Source volute Revision(s)
Changed:
<
<
     
>
>
Sec 3:
   "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)"
email 5367
  Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318:

Description Source volute Revision(s)
Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218:

Description Source volute Revision(s)

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 62019-03-22 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
Changed:
<
<
       
>
>
|

Sec 3:
Added:
>
>
"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)" Sec 5: The very first Virtual Telescope observation made in 2002 I've just noticed this is not legal - the value attribute (optional at VOTable 1.0 but mandatory since VOTable 1.1) is missing. It should read: <INFO name="HISTORY" value="The very first Virtual Telescope observation made in 2002"/>

| email | In next 1.4 draft | 2019-03-22 |
Probably the "STC" reference in figure 1 should be removed now. email In next 1.4 draft unless it's difficult. 2019-03-22
 

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs for WD-VOTable-1.4

Added:
>
>
Between WD-VOTable-1.4.20190318 and WD-VOTable-1.4.2019????

Description Source volute Revision(s)
     
  Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318:

Description Source volute Revision(s)
Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218:

Description Source volute Revision(s)

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 52019-03-18 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

The current working draft is WD-VOTable-1.4.20190318

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
       

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       
Changed:
<
<

Change Logs

>
>

Change Logs for WD-VOTable-1.4

  Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318:

Description Source volute Revision(s)
Changed:
<
<
Miscellaneous minor edits. email  
Remove namespace declarations from examples. email  
Make footnotes visible in HTML (already correct in PDF) email  
>
>
Miscellaneous cleanup edits. email 5337
Remove unused namespace declarations from examples. email 5336

Make footnotes visible in HTML (already correct in PDF).

Addressed by displaying those as hyperlinks in HTML version.

email 5335
 
Require "ref" for uses of TIMESYS email 5334

Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218:

Description Source volute Revision(s)

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Revision 42019-03-17 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

Changed:
<
<
This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.
>
>
The current working draft is WD-VOTable-1.4.20190318
 
Added:
>
>
This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.
 
Title Source Default Disposition Disp. Date
       

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       

Change Logs

Changed:
<
<
Between VOTable/20190131 and VOTable/20190218
>
>
Between WD-VOTable-1.4.20190218 and WD-VOTable-1.4.20190318:
 
Changed:
<
<
Description Source Revision(s) Updated
Miscellaneous minor edits. email    
Remove namespace declarations from examples. email    
Make footnotes visible in HTML (already correct in PDF) email    
Require "ref" for uses of TIMESYS email    
>
>
Description Source volute Revision(s)
Miscellaneous minor edits. email  
Remove namespace declarations from examples. email  
Make footnotes visible in HTML (already correct in PDF) email  
Require "ref" for uses of TIMESYS email 5334
Deleted:
<
<

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.

  5316 2019-02-17
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317 2019-02-17

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

2019-02-17, 2019-02-14
Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the DocStd appendix.   5318 2019-02-17
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320 2019-02-18
 
Changed:
<
<

<--  
-->
>
>
Between WD-VOTable-1.4.20190131 and WD-VOTable-1.4.20190218:

Description Source volute Revision(s)
Added:
>
>

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.

  5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the Document Standards appendix.   5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320


<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

 

Revision 32019-03-16 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposed Changes

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
Changed:
<
<
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-02-21
>
>
       
Deleted:
<
<
Require "ref" for uses of TIMESYS email Accept; include in next draft 2019-02-21
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-02-21
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5 2019-02-21
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5 2019-02-21
 

Proposals for VOTable 1.5

Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Changed:
<
<
Title Source
Port the VOTable source to ivoatex. email
   
>
>
Title Source Notes Updated
Port the VOTable source to ivoatex. email    
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-03-17
Added:
>
>
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-03-17
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5. 2019-03-17
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5. 2019-03-17
       
 

Change Logs

Between VOTable/20190131 and VOTable/20190218

Changed:
<
<
Description Revision(s)

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.

5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used. 5317

Section 3 reworked to clarify namespace and schema versioning.

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the DocStd appendix. 5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4. 5320
>
>
Description Source Revision(s) Updated
Miscellaneous minor edits. email    
Remove namespace declarations from examples. email    
Make footnotes visible in HTML (already correct in PDF) email    
Require "ref" for uses of TIMESYS email    

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.

  5316 2019-02-17
Added:
>
>
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used.   5317 2019-02-17

Section 3 reworked to clarify namespace and schema versioning.

 

5319, 5315

2019-02-17, 2019-02-14
Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the DocStd appendix.   5318 2019-02-17
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4.   5320 2019-02-18
 
<--  
-->

Revision 22019-02-21 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Changed:
<
<

Active Proposals

>
>

Active Proposed Changes

  This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.
Changed:
<
<
Title Source Default Disposition Disp. Date
>
>
Title Source Default Disposition Disp. Date
Added:
>
>
DataLink recommends using a "content" parameter. Consider mentioning it in sec. 8 (MIME types) to avoid other standards reinventing the same thing with a different name. email Defer to 1.5. There are no responses yet. If consensus is reached that this is a simple change, then it could be in 1.4. 2019-02-21
 
Require "ref" for uses of TIMESYS email Accept; include in next draft 2019-02-21
Changed:
<
<
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5 2019-02-21
Remove mention UType in section 1.4, as it is lacking a standard. email Defer to 1.5 2019-02-21
>
>
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5. This change has support, but the details are not yet resolved, so may delay 1.4. 2019-02-21
Remove mention of UType in section 1.4, as it is lacking a standard. email Defer to 1.5 2019-02-21
 
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5 2019-02-21
Deleted:
<
<
  email   2019-02-21
  email   2019-02-21
  email   2019-02-21
  email   2019-02-21
  email   2019-02-21
 
Added:
>
>

Proposals for VOTable 1.5

 
Added:
>
>
Work will begin on VOTable 1.5 immediately after 1.4 goes to Recommendation.

Title Source
Port the VOTable source to ivoatex. email
   
 

Change Logs

Between VOTable/20190131 and VOTable/20190218

Changed:
<
<
Description Revision(s)

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.

5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used. 5317

Section 3 reworked to clarify namespace and schema versioning.

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the DocStd appendix. 5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4. 5320
>
>
Description Revision(s)

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.

5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used. 5317

Section 3 reworked to clarify namespace and schema versioning.

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the DocStd appendix. 5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4. 5320
 
<--  
-->

Revision 12019-02-21 - TomDonaldson

 
META TOPICPARENT name="IvoaApplications"

VOTable 1.4 Working Draft Notes

Active Proposals

This is the list of proposed changes still under discussion for VOTable 1.4. The "Default Disposition" is what we will do with the proposal if there is no more discussion.

Title Source Default Disposition Disp. Date
Require "ref" for uses of TIMESYS email Accept; include in next draft 2019-02-21
Add optional "origin" or "refposition" attribute to COOSYS email Defer to 1.5 2019-02-21
Remove mention UType in section 1.4, as it is lacking a standard. email Defer to 1.5 2019-02-21
Sec. 4.6: Remove paragraph "In order to avoid name collisions..." email Defer to 1.5 2019-02-21
  email   2019-02-21
  email   2019-02-21
  email   2019-02-21
  email   2019-02-21
  email   2019-02-21

Change Logs

Between VOTable/20190131 and VOTable/20190218

Description Revision(s)

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.

5316
In the section 3.5 TIMESYS example, remove the ID values from the FIELDs since they are not used. 5317

Section 3 reworked to clarify namespace and schema versioning.

5319, 5315

Replace the claimed REC status of the document with the appropriate Working Draft disclaimer from the DocStd appendix. 5318
In sections 4.3 and 4.4, add references to DALI and VOUnits respectively since those standards came about since the writing of VOTable 1.3. Also mention those resources in section 1.4. 5320


<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback