The TCS 2 Task Group will turn TCS into a form in which it can be maintained. The new version of TCS will be a vocabulary standard like Darwin Core and Audiovisual Core and will complement these other existing TDWG standards.
6
stars
0
forks
source link
Task Group Meeting: 01 February 2022, 21:00–22:30 UTC #201
The next meeting of the TCS 2 Task Group will be held on 1 February 2022 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 receive 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
In this meeting we will hopefully finish the terms in the Taxon Concept class. We have agreed in the previous meeting to have a "hackathon" in the 24 hours before each meeting in which we try to conclude (at least temporarily) our discussion on the issues and finalise the definitions and the comments of the terms. We have not settled on the best way to go about this, but I have created a dev branch and I imagine there could be a pull request just before the meeting, which we can then review during the meeting.
There is also an issue relating to the Taxon Concept class that we have not fully discussed before and I did not think of when I made the agenda for the last meeting. This has got to do with name strings, so is quite important.
1. Name string discussion
In TCS 1, being XML, you could – in the TaxonConcept element – have both the TaxonName and AccorgdingTo. as text content (so strings) of the element, or as a link to a TaxonName or Reference element (with an ID) via the ref attribute. We have explicitly decided that accordingTo should always be a Reference and, since a Reference can be as simple as a dcterms:bibliographicCitation (not that we would encourage that), we can have accordingTo as just an object (or URI) property, without the need for a literal equivalent (there is one in Darwin Core anyway, so people can take it from there if they want to).
For taxonName the situations might not be as simple. I myself think it could be that simple, as it is impossible to have TaxonName mean what any particular nomenclatural code says is a Name and a TaxonName can also be as simple as just a name string (and an ID), but I know there are people who do not agree with that and, if we do this, we need to do this with our eyes open, knowing that the TCS 1 User Guide says something different (not very explicitly). On the other hand, we can decide to have a literal equivalent, but then we need to justify why we cannot just use the taxonNameString property from the TaxonName class or the Darwin Core scientificName for this.
As this discussion could go on forever, I would like to cap it to 30 minutes (or a time we agree on in advance) after which we come up with a pragmatic solution for TCS 2.0.0.
2. (Quick) Review of Taxon Name class
Here we will go over the terms off the Taxon Concept class, for which by now we have hopefully completed the definitions and comments, and see if we are happy with them.
I have created a milestone where you can easily see all the issues together.
3. Example ideas
Following up on the discussion we had at our last meeting, we will have a little brainstorm about what sort of examples we think would be useful and where we can source them.
The next meeting of the TCS 2 Task Group will be held on 1 February 2022 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 receive 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
In this meeting we will hopefully finish the terms in the Taxon Concept class. We have agreed in the previous meeting to have a "hackathon" in the 24 hours before each meeting in which we try to conclude (at least temporarily) our discussion on the issues and finalise the definitions and the comments of the terms. We have not settled on the best way to go about this, but I have created a
devbranch and I imagine there could be a pull request just before the meeting, which we can then review during the meeting.There is also an issue relating to the Taxon Concept class that we have not fully discussed before and I did not think of when I made the agenda for the last meeting. This has got to do with name strings, so is quite important.
1. Name string discussion
In TCS 1, being XML, you could – in the
TaxonConceptelement – have both theTaxonNameandAccorgdingTo. as text content (so strings) of the element, or as a link to aTaxonNameorReferenceelement (with an ID) via therefattribute. We have explicitly decided thataccordingToshould always be a Reference and, since aReferencecan be as simple as adcterms:bibliographicCitation(not that we would encourage that), we can haveaccordingToas just an object (or URI) property, without the need for a literal equivalent (there is one in Darwin Core anyway, so people can take it from there if they want to).For
taxonNamethe situations might not be as simple. I myself think it could be that simple, as it is impossible to haveTaxonNamemean what any particular nomenclatural code says is a Name and aTaxonNamecan also be as simple as just a name string (and an ID), but I know there are people who do not agree with that and, if we do this, we need to do this with our eyes open, knowing that the TCS 1 User Guide says something different (not very explicitly). On the other hand, we can decide to have a literal equivalent, but then we need to justify why we cannot just use thetaxonNameStringproperty from theTaxonNameclass or the Darwin CorescientificNamefor this.As this discussion could go on forever, I would like to cap it to 30 minutes (or a time we agree on in advance) after which we come up with a pragmatic solution for TCS 2.0.0.
2. (Quick) Review of Taxon Name class
Here we will go over the terms off the Taxon Concept class, for which by now we have hopefully completed the definitions and comments, and see if we are happy with them.
I have created a milestone where you can easily see all the issues together.
3. Example ideas
Following up on the discussion we had at our last meeting, we will have a little brainstorm about what sort of examples we think would be useful and where we can source them.
Meeting times