| META TOPICPARENT |
name="IvoaTCG" |
IVOA TCG Meeting - Thu, 08 Nov 2018 @8:30am(Local Time) (13:30 UTC) - Diamondback room
last edit - Nov06 - JE
Draft Agenda: (Additions welcomed)
- Recent highlights - from WG/IG leads
- Document status (list below)
- Actions (list below)
- Adapting IVOA standards/software by outside group (interest in HIPS) - AS
- Exoplanetary Systems Data Model (and connection to Source DM & al.): quick info report - MM
- AOB
IVOA TCG Hosted by CXC Data Systems Thursday 8:30 am | 2 hours 30 minutes | (UTC-05:00) Eastern Time (US & Canada) Meeting number: 730 696 935 https://sao.webex.com/sao/j.php?MTID=ma063b49830c25cdcb6471b34839a2881 Join by phone 1-877-668-4493 Call-in toll-free number (US/Canada) 1-650-479-3208 Call-in toll number (US/Canada) Access code: 730 696 935
Roadmap
Document Submission Logs (since last Interop; will retake from http://www.ivoa.net/documents/ just before mtg)
Actions: (Please update in status section)
- ACTION-F0518-1: PD - Add SSIG to RFC template page
- ACTION-F0518-2: PD - Resend the VOSpace recommendation to Exec
- ACTION-F0518-3: FG - Ensure that the important IVOA standards are in the RDA registry of standards.
- ACTION-F0518-4: MCD - Produce documentation on how the models relate and how to get started with certain use cases.
- ACTION-F0518-5: PD - Set the status of the XML Schema Versioning to ENDORSED
- ACTION-F0518-6: ThD - Registry WG to define way forward for querying data collections through capabilities. Endorsement of Discovering data collections is deferred for now.
- ACTION-F0518-7: ML - Semantics working group to come up with a plan for managing a vocabularies web page.
- ACTION-F0518-8: DM/PD - Prototype hosting a document standard and issue tracking in GitHub.
- ACTION-F0518-9: Giulia - investigate why the errata link is missing on some landing pages (eg VOTable) - sent to GL 10/30 **DONE**
- Note from Giulia: It is quite difficult check old errata because we do not have a list of accepted errata. If someone send me an accepted erratum I update the corresponding landing page.
- ACTION-F0518-10: DM - Include ADQL errata into current ADQL PR.
- ACTION-F0518-12: TM - Will go over the Publishing in the VO page.
- ACTION-F0518-13: MD/FG - make an official proposal of the IVOA Architecture document
- ACTION-T0718-2: AN - send pointer to requirements
- ACTION-T0718-3: WG chairs – Send a list of outdated standards to remove to Doc Coordinator with a cc to PD/JE.
Status
WG/Apps (TD/RD)
- Open Issue(s)
- Official VOTable schema needs an update w.r.t. recent erratum. This will be resolved at the interop.
- VODML Mapping
- Little discussion since prior meeting. Work may have been done in background.
- No documents/changes in progress
WG/DAL (MM/JD)
status
- ongoing efforts
- TAP-1.1: PR out, authenticated endpoints agreement before going REC
- ObsLocTAP & ObjVisSAP: progressing
- SLAP-2.0: new draft (unpublished), see "issues"
- ADQL-2.1: ongoing implementation effort
- DataLink-1.1: close to start, see Note on DAL feedback
- ProvTAP & ProvSAP: prototypes
- waiting
- DALI-1.2 (has some material)
- SIAP-2.1
- SODA-1.0 (feedback)
issues
- SSLDM-2.0: not in VO-DML, is it a problem for SLAP-2.0?
- CCW-winding polygons: JD summarizing: how to go on after
documents
- Note: TimeSeries Discovery and Access DAL procedure [22.07.2018] - as per roadmap
- Note: Recent DAL protocols feedback [22.07.2018] - as per roadmap
- (iWD): SLAP-2.0
- (iWD): SSLDM-2.0
WG/DM (MCD/LM)
Status:
- VO-DML
- REC document delivered to ivoa repository; new registry records submitted.
- "STC" component models (coords, meas, trans)
- wrote xslt translation script for vo-dml/xml to ivoatex
- updated coords model with documentation, extracted from AR versions and STC-1.33 as possible.
- process model into ivoatex; incorporate into ivoatex document template
- currently tweaking output formats (table overflows, etc) to make sure all info is included.
- coords WD nearly complete (end of Nov 2018), meas and transform by end of Dec. 2018.
- Provenance
- group hit road block in attempt to factor in a new use case... delayed progress of document to RFC
- RFC period started (Oct 22 - Nov 19, 2018)
- Heavy discussion ongoing from review
- DatatsetMetadata - no action needed; lien on measurment model
- NDCube - no action needed; lien on "STC" component models (meas, trans)
- -------------------------------------------------------------------------------------------
- TimeSeries
- Face-2-face meeting in Strasbourg, with focus on generating a single model based on cube which covers current use cases
- working serializations of example data products.
- SourceDM
- Call to group for people involved in large surveys (GAIA, LSST..) to define which quantities are highest priority
Issues:
- VO-DML Mapping: stalement?
- my impression is that the focus group feels they have done what they can with
- mapping syntax spec; usability demos; helper tools, etc
- but without concrete implementation feedback from external users, they do not have the information needed to work simplifications/changes
- 'alternate' syntax-s are still being worked/proposed which gain attention because the 'appear' simpler, but are not vetted against the requirements.
- TDIG has agreed to consider using serializations using the mapping syntax in their model assessment study, but cannot do so if it produces a road-block to getting the assessment done.
Action Updates:
WG/GWS (BM/GT)
Status:
- Two VOSI errata:
- Only the VOSI Tables XSD version should have been updated to 1.1 (not Capabilities and Availability) -- no impact to implementations
- The table response examples are using the wrong datatypes--should be vs:TAPType
- New Working Draft: Group Membership Service 1.0
Issues:
- XML Schema Versioning Note: work out issues with versioning attribute context
- UWSRegExt - The note has been completed but its use is in question and will be up for disussion in the joint GWS/DAL/Reg session.
Action Updates:
WG/Registry (ThD/PLS)
WG/Semantics (ML/MD)
- New page for vocabularies under the ivoa semantics group/ M.D and Giuilia http://ivoa.net/rdf/
- Planned : A Census on usage of the datalink terms : what is used in practice ? how can we maintain this vocabulary?
| 
