-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task Group Meeting: 14 December 2021, 21:00–22:30 UTC #198
Comments
Have the minutes from this meeting been posted? |
MinutesAttending: Nicholas Bailly, Steve Baskauf, Stan Blum, Anne Fuchs, Niels Klazenga, Johan Liljeblad, Rich Pyle, David Remsen, Mieke Strong, Andreas Müller, William Ulate, Cam Webb, Greg Whitbread Apologies: Jeff Gerbracht 1. Consider
|
The next meeting of the TCS 2 Task Group will be held on 14 December 2021 at 21:00 UTC (see below for other time zones). The meeting will be held via WebEx. People who have been to our meetings before or have already indicated their interest will received an invitation with a meeting link by email. If you are not on the list yet, but are interested in receiving meeting invitations, please email me on niels.klazenga(at)rbg.vic.gov.au and I will put you on.
Agenda
We will be working through the classes in the order TaxonConcept, TaxonRelationship (TaxonAlignment), TaxonName, so this meeting we will commence with TaxonConcept. As I want most of the work to take place between rather than in meetings though, we will just discuss two proposals that came out of the TCS Maintenance Group meetings in the TDWG Working Sessions in November and spend the rest of the meeting discussing the best way to progress the work on TCS 2. Steve Baskauf will join us to help with that.
1. Consider
specimenCircumscription
andcharacterCircumscription
out of scope for the TCS 2 Task GroupThese terms have come up in our discussions sometimes but we do not have any well-established use cases and we do not really know what to do with them, so we could spend a long time on them without getting anywhere. I propose to consider them out of scope for now and maybe deal with circumscription properly at a later stage.
2. Add controlled terms for "shared common concepts" and OTUs to TaxonConceptCategory controlled vocabulary
I propose we adopt the Taxonomic Concept Categories from the Franz & Peet (2009) as a starting point. I think that the common concepts that are derived from Taxon Concepts from individual publications – cf. AviBase – are also best dealt with as a category of Taxon Concepts, rather than as a class of their own (we'll need to think of a better name though). Also, I think it would be good to have a category for OTUs. We do not have issues for either term yet, but will decide if we are going to add them.
3. Add properties for pro parte synonyms and misapplications
At the Maintenance Group meetings, I suggested that we could have properties for misapplications and pro parte synonyms, which (I think) are left over when we resolve the
has synonym
Taxon Relationship Type in TCS 1. I myself am in two minds about this, so we will need to have a champion if we want to look into it further.4. Discussion on how to best move along with the work on TCS 2
I would like to get the terms in the TaxonConcept class finalised in the next couple of meetings, but I think that most of the work should be done between meetings, rather than during the meetings. So, in this meeting, I think we should at least decide which terms we want to have finalised by the next meeting (and what that means). We might also consider having hackathons again like we had before. We will also discuss next steps and what we need to have done before we take the next steps. As I said, Steve will join us to discuss this with us.
Meeting times
The text was updated successfully, but these errors were encountered: