| ||||||||
Changed: | ||||||||
< < | The third edition of the SemanticsCalls series of telecons will take place Wed, 2021-03-10 at 16:00 UTC on the mumble server | |||||||
> > | The third edition of the SemanticsCalls series of telecons took place Wed, 2021-03-10 at 16:00 UTC. | |||||||
Deleted: | ||||||||
< < | telco.g-vo.org. Participation with a browser-based client from https://telco.g-vo.org is also possible. | |||||||
Agenda
Minutes | ||||||||
Deleted: | ||||||||
< < | Will be collected on https://yopad.eu/p/semcall3. | |||||||
Added: | ||||||||
> > | Steps towards a vocabulary of object typesUse cases:
obj_type='double-star' for an exact match,
1=gavo_vocmatch('otype', 'double-star', obj_type) to match the entire branch.
But of course SIMBAD could use custom ways to make common use cases more straightforward.
Then there's candidate problem: The old hierarchy had some classes that said "we're not sure yet".
The current thinking is to have a Candidate-X for every X. MD suggests that perhaps a "we're not sure about the object type yet" flag in the table might work as well? SD considers if this could perhaps work like the membership likelihood for star clusters and the like?
Action: CDS->MD: prototype hierarchy+prototype mapping to UAT. MD then tries how far he gets with forming this into an IVOA vocabulary.
Pre-RFC check of Vocabularies in the VO 2Implementations:
AOBhttp://volute.g-vo.org/svn/trunk/projects/semantics/veps/VEP-006.txt is still open; ML will voice her concerns on how this might overload #progenitor on-list. | |||||||
<--
|
Agenda
MinutesWill be collected on https://yopad.eu/p/semcall3.<--
|