> > |
Priority model efforts:
- Errata:
- generate errata page for ObsCore-1.1 and migrate through process (early 2019)
- generate errata for 2 STC-1.33 errata and migrate through process (early 2019)
- Coords: Astronomical Coordinates and Coordinate Systems (Nov 2018)
- Meas: Measurements and Errors (Dec 2018)
- restore basic Velocity, correct Correlation Matrix
- complete WD documentation, and distribute for review
- Trans: WCS Transforms (Dec 2018)
- restore transform operations needed by LSST, implemented by AST library
- complete WD documentation, and distribute for review
- WG concensus on coord, meas, trans model content, move to PR/RFC process (Jan-May 2019)
- Provenance ( May 2019 )
- review/address RFC comments
- assess impact of compromise model on implementations
- update model/document accordingly
- update implementations
-
Secondary model efforts:
- Dataset Metadata
- no contention, ready to move forward when measurement model dependency is satisfied. ( May 2019 )
- NDCube
- no open issues, ready to move forward when dependencies are satisfied... most likely AFTER "STC" and Dataset are completed ( May 2019? )
- SSDL-2.0
- get volute workspace setup ( Jan 2019 )
- vo-dml compliant model representation - WD ( May 2019 )
Upcoming model efforts:
Most of these projects are being driven by the time domain work and feedback from the 'Hack-a-thon" in Victoria with data providers exercising existing models. There are no hard goals for these projects at this point, but will be worked as a 'best effort' level
- TimeSeries
- continue working with TDIG to flesh out requirements for time domain data models and prototype/develop models as time and resources permit
- PhotDM
- Generate VO-DML compliant model; it is not yet clear if this is a major version update or minor.. the original model had gone far in this direction.
- preliminary work has been done in Volute in preparation for Victoria demos
- pick up from there with 'official' model project; modeler=Jesus, domain=??, tech=??
- Characterisation
- Migrate Characterisation to a VO-DML compliant model; this is a major project, at least in part motivated by time domain project needs
- modeler=Francois/Mireille?, domain=??, tech=??
- SourceDM
- It is still unclear if a full SourceDM is required or useful at this point given the resources available.
- A better approach might be to concentrate on the Entities which might be most useful TO a SourceDM, and work to get those entities included in the proper model (eg: meas ).
|