Semantics Calls 6 | ||||||||
Changed: | ||||||||
< < | The sixth edition of our telecon series will take place Monday, 2022-03-14, at 16:00 UTC. We will meet on the mumble server telco.g-vo.org (see http://mumble.info for a selection of clients or use the browser interface at https://telco.g-vo.org/mumble-web/). | |||||||
> > | The sixth edition of our telecon series took place on Monday, | |||||||
Added: | ||||||||
> > | 2022-03-14, at 16:00 UTC. Here are the minutes: | |||||||
Deleted: | ||||||||
< < | Collaborative minutes: https://yopad.eu/p/semcall6 | |||||||
Changed: | ||||||||
< < | Agenda (feel free to add items): | |||||||
> > | VEPs (standing item)"> Current VEPs (standing item) | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
What are the meanings of facility_name and instrument in obscore, VODataService...?Tamara has found unclear and partly conflicting definitions for what is supposed to be in facility and instrument in SSAP, Obscore, and VODataService. The was some discussion on this on the mailing list. | |||||||
Added: | ||||||||
> > | Proposal for resolution: Facility is the thing that collects messengers, instrument is what detects them. This would mean, essentially, we'll be saying facility would be analogous to FITS' TELESCOP.
Tamara would like to represent Observatory in that combo. Markus would just put in "2 Meter Schmidt at Byurakan" vs. "2 Meter Schmidt at Hamburg".
Markus and Tamara will work together to create a proposal for what might need to be changed in our standards to make that work based on Tamara's mail from February.
UCD List 1.5 progressMireille discusses progress towards UCD 1.5.
UCD-related Errata for SSAP and SLAP progressSSAP is instr.fov is done, https://wiki.ivoa.net/twiki/bin/view/IVOA/SSA-1_1-Err-2. However: the new UCD pos.outline;instr.fov is inconsistent with obscore's pos.outline;obs.field; this ugly in principle but particularly because some SSA services can run on top of ObsTap services. Which do we prefer? Mireille will ask around on the semantics mailing list, but at least Markus strongly urges to accept the large installed base of Obscore and have an Erratum to our Erratum. There's also meta.ref.url;meta.curation in SSAP, which is invalid because meta.curation is primary. A fix for that should also go in with the next SSAP Erratum. Next up: SLAP use of em.line. Proposal: make it meta.id;em.line. There are also wonky UCDs in Appendix B, but perhaps there's no need to clean them up. Markus will write the Erratum.The product-type vocabulary: Ready for Datalink RFC?The purpose of this vocabulary still is to satisfy the two cases "send to the proper client" (mainly Datalink) and "find a specific sort of data" (e.g., in Obscore). François wants to make sure we can represent the observable in there, too (e.g., velocity curve vs. photometric time series). Unless there's hidden traps, that should work by just introducing light-curve vs. velocity-curve or similar, but everyone is encouraged to think about cases we can't easily cover. Let's try to disuss these last questions at interop.arith.diff and arith.ratio in UCDs: Why are they S?PostponedFAIRsFAIR requirements and usPostponed | |||||||
<--
|
Semantics Calls 6The sixth edition of our telecon series will take place Monday, 2022-03-14, at 16:00 UTC. We will meet on the mumble server telco.g-vo.org (see http://mumble.info for a selection of clients or use the browser interface at https://telco.g-vo.org/mumble-web/). | ||||||||
Added: | ||||||||
> > | Collaborative minutes: https://yopad.eu/p/semcall6 | |||||||
Agenda (feel free to add items):
<--
|
Semantics Calls 6 | ||||||||
Changed: | ||||||||
< < | The sixth edition of our telecon series will take place Monday, | |||||||
> > | The sixth edition of our telecon series will take place Monday, 2022-03-14, at 16:00 UTC. We will meet on the mumble server telco.g-vo.org (see http://mumble.info for a selection of clients or use the browser interface at https://telco.g-vo.org/mumble-web/). | |||||||
Deleted: | ||||||||
< < | 2022-03-14, at 16:00 UTC. We will meet on the mumble server telco.g-vo.org (see http://mumble.info for a selection of clients or use the browser interface at https://telco.g-vo.org/mumble-web/). | |||||||
Deleted: | ||||||||
< < | ||||||||
Agenda (feel free to add items):
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
<--
|
Semantics Calls 6 | ||||||||
Changed: | ||||||||
< < | The sixth edition of our telecon series will take place in February or March 2022. | |||||||
> > | The sixth edition of our telecon series will take place Monday, | |||||||
Added: | ||||||||
> > | 2022-03-14, at 16:00 UTC. We will meet on the mumble server telco.g-vo.org (see http://mumble.info for a selection of clients or use the browser interface at https://telco.g-vo.org/mumble-web/). | |||||||
Changed: | ||||||||
< < | Topcis: | |||||||
> > | ||||||||
Added: | ||||||||
> > | Agenda (feel free to add items): | |||||||
<--
|
Semantics Calls 6 | ||||||||
Changed: | ||||||||
< < | The sixth edition of our telecon series will take place in February or | |||||||
> > | The sixth edition of our telecon series will take place in February or March 2022. | |||||||
Deleted: | ||||||||
< < | March 2022. | |||||||
Topcis:
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
Semantics Calls 6The sixth edition of our telecon series will take place in February or March 2022. Topcis:
<--
|