Spectral v2.0: Proposed Recommendation: Request for Comments

This page contains public discussion of the Spectral 2.0 Proposed Recommendation; latest version PR-SpectralDM-2.0-20140730

RFC Review Period

13 May 2014 - 31 July 2014

TCG Review Period

1 August 2014 - 15 September 2014

Reference Interoperable Implementations

Spectral 2.0 has been implemented at:

• VAO: speclib - Java library for interpreting Spectral2.0 model
  • loads model definition from ancillary file, with design capable of alternate resource types ( DB, vo-dml, etc)
  • generates interfaces for model components, supports all primitive datatypes, Quantity, Lists, used in Spectral model
• SVO: TSAP - Theorical Spectral Model Service

Comments from the IVOA Community during RFC period: 13 May 2014 - 31 July 2014

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 Wiki Name so that 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.

Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document

• Comments by -- JesusSalgado - 2014-05-13
  • Comment
• Comments by -- -- MireilleLouys - 2014-06-19 Here are comments I made by iterating with the Mark Cresitello-Dittmarr during the Interop meeting in Madrid, last May(2014).

1. Section 4: Characterisation

• This section reads : "The following named instances may be used for defining axis requirements for specific use cases" - the diagram shows specializations for 'domain' restrictions (e.g. SpectralCharAxis) which is consistent with the Char-1.13 model. However, the description as "named instances" does not seem correct. We suggest the text be changed to: "The following labels may be used for defining axis requirements for specific use cases".

• The *CharAxis objects are the "specialized realizations of the CharacterisationAxis" which are identified by the simple labels.

• Attributes names and spelling:
  • CalibStatus: CalibrationStatus To agree with proposed ObsCore-1.1 changes this should be
• • • lower case 'calibrationStatus' attribute
    • with UTypes changed to match "CalibStatus" -> "CalibrationStatus"
  • BinSize|BinLow|BinHigh
    • should be annotated as additions for DataAxis support... they are not part of Char-1.13 model
• • SampleExtent
    • we could discuss about the ambiguity of this with BinSize on SpectralAxis.. However, since the BinSize is only a DataAxis element, this should not be a conflict. The SampleExtent can provide the characteristic BinSize.

1. Section 6: IVOA Conventions

1. • subsection "6.1.3 UTypes" describes labels FluxAxis etc, as "denote specific instances of CharacterisationAxis"
     • the phrasing should be consistent. CharacterisationAxis can be considered as a template.. *CharAxis are specialized realizations of that template.. and these (FluxAxis, SpectralAxis, etc) are the labels for these specialized realizations in the UType string.Moreover these labels express the role of each specialised axis with respect to the Characterisation class.

• Comment by -- IVOA.OmarLaurino - 2014-08-08

In order to help implementors upgrading from Spectrum 1.1 to Spectral 2.0, Mark Cresitello Dittmar and Jamie Budynkiewicz produced this "cheat-sheet" highlighting how elements in Spectral 2.0 map to elements in Spectrum 1.1 and the new elements utypes in Spectral 2.0: map-document-new.pdf

Comments from TCG member during the TCG Review Period: 1 August 2014 - 15 September 2014

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, François Bonnarel )

Data Model Working Group ( _Jesus Salgado, Omar Laurino )

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

Registry Working Group ( _Gretchen Greene, Pierre Le Sidaner )

Semantics Working Group ( _Norman Gray, Mireille Louys )

Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )

Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )

Data Curation & Preservation Interest Group ( Alberto Accomazzi, Françoise Genova )

Knowledge Discovery in Databases Interest Group ( George Djorgovski )

Theory Interest Group ( _Franck Le Petit, Rick Wagner )

Standards and Processes Committee ( Françoise Genova)