Difference: PhotDM10RFC (1 vs. 23)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

The architecture diagram and description should be moved to the Introduction. Once done, it is approved

-- SeverinGaudet - 2013-09-28

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

This is a nice document. I approve it for DAL. I have a few remarks

• possible Typos ? page 7 = "is that the metadata fields defined here WILL be included".
• possible Typo page 7 again "and the description of (the) how the units of the measurement"
• Fixed -- JesusSalgado - 2013-09-27
• Data Model Summary Table . PF Acces Metadata section. Should that also Include the transmissionPoint utypes ?

• Data Model Summary Table. PF Spectral and Time axis Characterization. Should it be called characterization or coverage ? Actually the concepts are analogous but the utypes there and those in characterization ObsCore are very different. So maybe coverage (also used in ressource metadata) is of wider extent.

• Data Model Summary Table. AsinHZeroPint.softeningParameter doesn't have the PhotCal prefix.

in the case of inheritance using the current utypes approach (probably solved if VO-DML or other data modeling language is assumed)

For the time being, I think this is the more proper approach (use the child class name as prefix for metadata present only in the child

but not in the mother) -- JesusSalgado - 2013-09-27

• VOTABLE Example Filter profile service. Three param have no utypes (Facility, ProfileReference, CalibrationReference"

utypes). In any case, fields with no clear standard utype could appear without it in the response. -- JesusSalgado - 2013-09-27

-- FrancoisBonnarel - 2013-09-22

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Approved-- JesusSalgado - 2013-09-09

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Approved - AndreSchaaff - 2013-09-09

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Approved -- GretchenGreene - 2013-09-20

Semantics Working Group ( _Norman Gray, Mireille Louys)

This datamodel is a central description for binding Photometric calibration of an observation to the coordinate system description of the Flux frame. It has great potential for re-usability for data products in the VO: not only spectra , but also images , spectral cubes, etc.

I approve the document -- MireilleLouys - 2013-09-25

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

This is a nice document. I approve it for DAL. I have a few remarks

• possible Typos ? page 7 = "is that the metadata fields defined here WILL be included".
• possible Typo page 7 again "and the description of (the) how the units of the measurement"
• Fixed -- JesusSalgado - 2013-09-27
• Data Model Summary Table . PF Acces Metadata section. Should that also Include the transmissionPoint utypes ?

• Data Model Summary Table. PF Spectral and Time axis Characterization. Should it be called characterization or coverage ? Actually the concepts are analogous but the utypes there and those in characterization ObsCore are very different. So maybe coverage (also used in ressource metadata) is of wider extent.

• Data Model Summary Table. AsinHZeroPint.softeningParameter doesn't have the PhotCal prefix.

in the case of inheritance using the current utypes approach (probably solved if VO-DML or other data modeling language is assumed)

For the time being, I think this is the more proper approach (use the child class name as prefix for metadata present only in the child

but not in the mother) -- JesusSalgado - 2013-09-27

• VOTABLE Example Filter profile service. Three param have no utypes (Facility, ProfileReference, CalibrationReference"

standard, we prefer to maintain the fields without utypes until to have a formal definition (to prevent future deviations in the

utypes). In any case, fields with no clear standard utype could appear without it in the response. -- JesusSalgado - 2013-09-27

-- FrancoisBonnarel - 2013-09-22

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Approved-- JesusSalgado - 2013-09-09

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Approved - AndreSchaaff - 2013-09-09

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Approved -- GretchenGreene - 2013-09-20

Semantics Working Group ( _Norman Gray, Mireille Louys)

This datamodel is a central description for binding Photometric calibration of an observation to the coordinate system description of the Flux frame. It has great potential for re-usability for data products in the VO: not only spectra , but also images , spectral cubes, etc.

I approve the document -- MireilleLouys - 2013-09-25

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

This is a nice document. I approve it for DAL. I have a few remarks

• possible Typos ? page 7 = "is that the metadata fields defined here WILL be included".
• possible Typo page 7 again "and the description of (the) how the units of the measurement"

• Data Model Summary Table . PF Acces Metadata section. Should that also Include the transmissionPoint utypes ?

• Data Model Summary Table. PF Spectral and Time axis Characterization. Should it be called characterization or coverage ? Actually the concepts are analogous but the utypes there and those in characterization ObsCore are very different. So maybe coverage (also used in ressource metadata) is of wider extent.

• Data Model Summary Table. AsinHZeroPint.softeningParameter doesn't have the PhotCal prefix.

• VOTABLE Example Filter profile service. Three param have no utypes (Facility, ProfileReference, CalibrationReference"

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Approved-- JesusSalgado - 2013-09-09

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Approved - AndreSchaaff - 2013-09-09

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Approved -- GretchenGreene - 2013-09-20

Semantics Working Group ( _Norman Gray, Mireille Louys)

This datamodel is a central description for binding Photometric calibration of an observation to the coordinate system description of the Flux frame. It has great potential for re-usability for data products in the VO: not only spectra , but also images , spectral cubes, etc.

I approve the document -- MireilleLouys - 2013-09-25

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

• possible Typo page 7 again "and the description of (the) how the units of the measurement"
• Data Model Summary Table . PF Acces Metadata section. Should that also Include the transmissionPoint utypes ?
• Data Model Summary Table. PF Spectral and Time axis Characterization. Should it be called characterization or coverage ? Actually the concepts are analogous but the utypes there and those in characterization ObsCore are very different. So maybe coverage (also used in ressource metadata) is of wider extent.
• Data Model Summary Table. AsinHZeroPint.softeningParameter doesn't have the PhotCal prefix.
• VOTABLE Example Filter profile service. Three param have no utypes (Facility, ProfileReference, CalibrationReference"

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Approved-- JesusSalgado - 2013-09-09

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Approved - AndreSchaaff - 2013-09-09

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Approved -- GretchenGreene - 2013-09-20

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

This is a nice document. I approve it for DAL. I have a few remarks

• possible Typos ? page 7 = "is that the metadata fields defined here WILL be included".
• possible Typo page 7 again "and the description of (the) how the units of the measurement"
• Data Model Summary Table . PF Acces Metadata section. Should that also Include the transmissionPoint utypes ?
• Data Model Summary Table. PF Spectral and Time axis Characterization. Should it be called characterization or coverage ? Actually the concepts are analogous but the utypes there and those in characterization ObsCore are very different. So maybe coverage (also used in ressource metadata) is of wider extent.
• Data Model Summary Table. AsinHZeroPint.softeningParameter doesn't have the PhotCal prefix.
• VOTABLE Example Filter profile service. Three param have no utypes (Facility, ProfileReference, CalibrationReference"

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Approved-- JesusSalgado - 2013-09-09

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Approved - AndreSchaaff - 2013-09-09

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Approved -- GretchenGreene - 2013-09-20

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Approved-- JesusSalgado - 2013-09-09

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Approved - AndreSchaaff - 2013-09-09

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Approved -- GretchenGreene - 2013-09-20

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Approved-- JesusSalgado - 2013-09-09

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Approved-- JesusSalgado - 2013-09-09

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

mantain the placeholder. A comment has been added to clarify this -- JesusSalgado - 2013-09-03

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

-- MarkTaylor, PierreFernique - 2013-07-18

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).

• Sec 3.2.8: "the more representative" -> "the most representative"

• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

This is a clear and as far as I can tell well-motivated document. I don't have expert knowledge about photometry, so I can't comment on its adequacy for its intended purpose, but I don't see any problems with it from the Applications WG point of view, so we are happy to recommend acceptance.

There are a few typos and minor errors:

• Sec 3: Figure 1 contains the box "Source" which doesn't seem to be doing anything - remove it?

• Appendix B: Table heading "UCD+1" should be "UCD 1+"?

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

• Acknowledgements: "initials versions" -> "initial versions"
• Sec 2: "as per explained" -> "as explained"

• Sec 3.2.6: " YYYY-MM-DD[T[hh[:mm[:ss[.s[TZD]]]]]] " - I don't quite understand the "[TZD]" here. If TZD is supposed to be a time zone designator, the (unexplained, but fairly obvious) syntax suggests it is only permissible to use it if a fractional part of the seconds is explicitly included, which seems a bit strange. Also, I think I'm right in saying that general usage elsewhere in IVOA standards does not encourage/permit time zone indicators (e.g. DALI sec 3.1.2).
• Sec 3.2.8: "the more representative" -> "the most representative"
• Sec 3.6.3: "See Appendix 5.2" - what document does this refer to? Not PhotDM itself.
• Appendix B: Table heading "UCD+1" should be "UCD 1+"?
• Appendix B: "may belong to on of three" -> "may belong to one of three"
• Appendix B: "Transmission curve are also" -> "Transmission curves are also"
• Appendix B: "Other serialization using array of points" -> "Other serializations using arrays of points"
• Appendix C.1: "PhotometryFilter.identifer" -> "PhotometryFilter.identifier"
• Appendix C.1: ' <PARAM name="magtype" ... value="VEGmag" datatype="int"/> ' - the datatype appears to be wrong; also according to the table on p.35 the value should be "VEGAmag" not "VEGmag".
• Appendix C.2: "service will contains some" -> "service will contain some"

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

Photometry DM RFC

This document will act as RFC centre for the Photometry DM http://www.ivoa.net/Documents/PHOTDM/

This is the second RFC process for this DM. Previous RFC page can still be found at: http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotDM10RFCOLD

Please notice this version is an updated version of the previous Photometry DM with some changes in the UML but maintaining the utypes as in the

current way. A parallel PhotDM draft is being prepared in parallel with the VO-DML utypes approach.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (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.

Discussion about any of the comments or responses should be conducted on the dm@ivoa.net. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document.

Implementation details

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 04 July 2013 - 04 August 2013

Comments from the IVOA Community during RFC period:

TCG Review Period: 05 August 2013 - 10 September 2013

Comments from TCG member during the TCG Review Period:

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Séverin Gaudet, Matthew Graham)

Applications Working Group ( _Mark Taylor, Pierre Fernique)

Data Access Layer Working Group ( Patrick Dowler, Francois Bonnarel)

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group ( Andre Schaaff, Andreas Wicenec)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group ( _Norman Gray, Mireille Louys)

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Francoise Genova)

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner)

Time Domain Interest Group (John Swinbank, Mike Fitzpatrick)

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

PhotDM-1.0 Proposed Recommendation: RFC period

This document serves as the RFC center for the Proposed

Recommendation entitled "IVOA Photometry DM, Version 1.0".

The latest version of PhotDM:

• http://www.ivoa.net/Documents/PHOTDM/

• http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotometryDataModel

Reference Interoperable Implementations

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 05 June 2012 - 05 July 2012 (closed)

TCG Review Period: 05 July 2012 - 05 September 2012

Comments from the IVOA Community during RFC period: 05 June 2012 - 05 July 2012

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Christophe Arviset, Séverin Gaudet)

Applications Working Group ( _Mark Taylor)

As Gretchen points out, there are some questions raised by Appendix C.2. TAP services to be marked up in such a way should I think use the TAPRegExt <dataModel> element, but I'm not sure about Cone Search.

The response curve in the example table in Appendix C.1 seems to have all its transmission values as zero - is that a mistake?

Given consideration of those points, I approve.

-- MarkTaylor - 05 Jul 2012

Agree with first point. Tap services could make use of the datamodel element. As commented in the registry section, details on how to register cone search services can be considered out of the scope of the DM itself, so they should be discussed in another context.

About second point, unfortunately the example has been taken from a real example and cut to minimize the size (the first element are zero). The example will be modified to get transmission numbers different than zero.

JesusSalgado - September 5, 2012

Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick))

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Appendix C.2 describes using a new capability type for Cone Search, i.e. Photometry. This is confusing to me, in the sense that the capability is more what we would refer to as the standard functional capability, e.g. cone, sia, ssa, sla, tap, etc. It is an interesting concept you are defining, i.e. how to describe data model implementation contained in a specifc service capability. I'm looking further to try to understand this in the context of registry schema. Currently i do not see the metadata mapping which would demonstrate how this would comply. Perhaps you had a specific example to explain further?

GretchenGreene - July 3, 2012

This was a proposal done, mainly, by our CDS colleagues in order to publish future Cone Searches with the extra metadata information. I agree this should be more discussed in the registry context and, as mentioned, the services should be registered using a standard registry extension (e.g. TAPRegExt for tap services). As this is out of the scope of the DM itself, I will remove some details on how to register these services. This could be added to the related IVOA note in coordination with the Registry group

JesusSalgado - September 5, 2012

Semantics Working Group ( _Sebastien Derriere, Norman Gray)

VOEvent Working Group ( _Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group ( Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group ( Giuseppe Longo)

Theory Interest Group ( _Herve Wozniak, Franck Le Petit)

Standards and Processes Committee ( Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

PhotDM-1.0 Proposed Recommendation: RFC period

This document serves as the RFC center for the Proposed

Recommendation entitled "IVOA Photometry DM, Version 1.0".

The latest version of PhotDM:

• http://www.ivoa.net/Documents/PHOTDM/

• http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotometryDataModel

Reference Interoperable Implementations

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 05 June 2012 - 05 July 2012 (closed)

TCG Review Period: 05 July 2012 - 05 September 2012

Comments from the IVOA Community during RFC period: 05 June 2012 - 05 July 2012

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair ( _Christophe Arviset, Séverin Gaudet)

Applications Working Group ( _Mark Taylor)

As Gretchen points out, there are some questions raised by Appendix C.2. TAP services to be marked up in such a way should I think use the TAPRegExt <dataModel> element, but I'm not sure about Cone Search.

The response curve in the example table in Appendix C.1 seems to have all its transmission values as zero - is that a mistake?

Given consideration of those points, I approve.

-- MarkTaylor - 05 Jul 2012

Agree with first point. Tap services could make use of the datamodel element. As commented in the registry section, details on how to register cone search services can be considered out of the scope of the DM itself, so they should be discussed in another context.

About second point, unfortunately the example has been taken from a real example and cut to minimize the size (the first element are zero). The example will be modified to get transmission numbers different than zero.

JesusSalgado - September 5, 2012

Data Access Layer Working Group ( Patrick Dowler, Mike Fitzpatrick))

Data Model Working Group ( _Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group ( Andreas Wicenec, Andre Schaaff)

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner)

Appendix C.2 describes using a new capability type for Cone Search, i.e. Photometry. This is confusing to me, in the sense that the capability is more what we would refer to as the standard functional capability, e.g. cone, sia, ssa, sla, tap, etc. It is an interesting concept you are defining, i.e. how to describe data model implementation contained in a specifc service capability. I'm looking further to try to understand this in the context of registry schema. Currently i do not see the metadata mapping which would demonstrate how this would comply. Perhaps you had a specific example to explain further?

GretchenGreene - July 3, 2012

This was a proposal done, mainly, by our CDS colleagues in order to publish future Cone Searches with the extra metadata information. I agree this should be more discussed in the registry context and, as mentioned, the services should be registered using a standard registry extension (e.g. TAPRegExt for tap services). As this is out of the scope of the DM itself, I will remove some details on how to register these services. This could be added to the related IVOA note in coordination with the Registry group

JesusSalgado - September 5, 2012

Semantics Working Group ( _Sebastien Derriere, Norman Gray)

VOEvent Working Group ( _Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group ( Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group ( Giuseppe Longo)

Theory Interest Group ( _Herve Wozniak, Franck Le Petit)

Standards and Processes Committee ( Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

PhotDM-1.0 Proposed Recommendation: RFC period

Reference Interoperable Implementations

TCG Review Period: 05 July 2012 - 05 September 2012

Comments from the IVOA Community during RFC period: 05 June 2012 - 05 July 2012

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

The response curve in the example table in Appendix C.1 seems to have all its transmission values as zero - is that a mistake?

Given consideration of those points, I approve.

PhotDM-1.0 Proposed Recommendation: RFC period

This document serves as the RFC center for the Proposed

Recommendation entitled "IVOA Photometry DM, Version 1.0".

The latest version of PhotDM:

• http://www.ivoa.net/Documents/PHOTDM/

Discussion page is at:

• http://wiki.ivoa.net/twiki/bin/view/IVOA/PhotometryDataModel

where some auxiliary documents can be found.

Reference Interoperable Implementations

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 05 June 2012 - 05 July 2012 (open)

TCG Review Period: 05 July 2012 - 05 September 2012

Comments from the IVOA Community during RFC period: 05 June 2012 - 05 July 2012

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick))

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

PhotDM-1.0 Proposed Recommendation: RFC period

This document serves as the RFC center for the Proposed

Recommendation entitled "IVOA Photometry DM, Version 1.0".

The latest version of PhotDM:

• http://www.ivoa.net/Documents/PHOTDM/

Discussion page is at:

Reference Interoperable Implementations

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 05 June 2012 - 05 July 2012 (open)

TCG Review Period: 05 July 2012 - 05 September 2012

Comments from the IVOA Community during RFC period: 05 June 2012 - 05 July 2012

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick))

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

PhotDM-1.0 Proposed Recommendation: RFC period

This document serves as the RFC center for the Proposed

Recommendation entitled "IVOA Photometry DM, Version 1.0".

The latest version of PhotDM:

• http://www.ivoa.net/Documents/PHOTDM/

Discussion page is at:

• http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/PhotometryDataModel

where some auxiliary documents can be found.

Reference Interoperable Implementations

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 05 June 2012 - 05 July 2012 (open)

Comments from the IVOA Community during RFC period: 05 June 2012 - 05 July 2012

Comments from TCG member during the TCG Review Period: 05 July 2012 - 05 September 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick))

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

PhotDM-1.0 Proposed Recommendation: RFC period

This document serves as the RFC center for the Proposed

Recommendation entitled "IVOA Photometry DM, Version 1.0".

The latest version of PhotDM:

• http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/PhotometryDataModel

where some auxiliary documents can be found.

Reference Interoperable Implementations

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick))

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

PhotDM-1.0 Proposed Recommendation: RFC period

This document serves as the RFC center for the Proposed

Recommendation entitled "IVOA Photometry DM, Version 1.0".

The latest version of PhotDM:

• http://http://www.ivoa.net/Documents/PHOTDM/

Discussion page is at:

• http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/PhotometryDataModel

where some auxiliary documents can be found.

Reference Interoperable Implementations

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick))

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

PhotDM-1.0 Proposed Recommendation: RFC period

This document serves as the RFC center for the Proposed

Recommendation entitled "IVOA Photometry DM, Version 1.0".

The latest version of PhotDM:

• http://http://www.ivoa.net/Documents/PHOTDM/

Discussion page is at:

• http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/PhotometryDataModel

where some auxiliary documents can be found.

Reference Interoperable Implementations

• VOSpec (ESAVO) (client)
• Filter Profile Service (SVO) (Server + Client)
• Catalogs with Photometry Data (CDS) (Server)

RFC Review Period: 20 May 2012 - 20 June 2012 (open)

TCG Review Period: 20 June 2012 - 20 July 2012 (open)

Comments from the IVOA Community during RFC period: 20 May 2012 - 20 June 2012

Comments from TCG member during the TCG Review Period: 20 June 2012 - 20 July 2012

WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard.

IG chairs or vice chairs are also encouraged to do the same, although their inputs are not compulsory.

TCG Chair & Vice Chair (Christophe Arviset, Séverin Gaudet)

Applications Working Group (Mark Taylor, Enrique Solano)

Data Access Layer Working Group (Patrick Dowler, Mike Fitzpatrick))

Data Model Working Group (Jesus Salgado, Omar Laurino)

Grid & Web Services Working Group (Andreas Wicenec, Andre Schaaff)

Registry Working Group (Gretchen Greene, Pierre Le Sidaner)

Semantics Working Group (Sebastien Derriere, Norman Gray)

VOEvent Working Group (Matthew Graham, John Swinbank)

Data Curation & Preservation Interest Group (Alberto Accomazzi)

Knowledge Discovery in Databases Interest Group (Giuseppe Longo)

Theory Interest Group (Herve Wozniak, Franck Le Petit)

Standards and Processes Committee (Francoise Genova)

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->