-
Notifications
You must be signed in to change notification settings - Fork 10
Class:Event #362
Comments
From December 16th meeting notes: The important distinction of a Latimer Core record from a Darwin Core record is that it should always make reference to and include event-based groups of occurrences, that is information/evidence that was situated in/taken from space and time. The event can be as simple as a historical approach “all the things [being managed/curated] by a museum at a point in time” or as specific as a particular research project “a monitoring survey of a single animal over a period of time”. However an event doesn’t have to be mandatory in all collection description use cases. |
see also ABCD class "Gathering": A class to describe a collection or observation event. |
A gathering is intermediate between an event and an observation. A gathering is defined in the The International Code of Nomenclature for algae, fungi, and plants (ICN)
see: https://www.iapt-taxon.org/nomen/pages/main/glossary.html Note that this is quite specific, whereas a dwc:event can involve many more species, a longer duration and more people. |
... and need not refer to gatherings at all.
…On Tue, Feb 15, 2022 at 12:28 PM Quentin Groom ***@***.***> wrote:
A gathering is intermediate between an event and an observation. A
gathering is defined in the The International Code of Nomenclature for
algae, fungi, and plants (ICN)
gathering. A collection presumed to be of a single taxon made by the same
collector(s) at the same time from a single locality ([Art. 8.2 footnote](
https://www.iapt-taxon.org/nomen/pages/main/art_8.html#Art8.2); see also
[Art. 8 Note 1](https://www.iapt-taxon.org/nomen/pages/main/art_8.html)).
see: https://www.iapt-taxon.org/nomen/pages/main/glossary.html
Note that this is quite specific, whereas a dwc:event can involve many
more species, a longer duration and more people.
—
Reply to this email directly, view it on GitHub
<#362 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADQ725RQDT6UQXQNW5UIVLU3JWKTANCNFSM5L4FLQ4Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
This sounds as if LC's Event is more in line with ABCD's Dataset(s). However, with properties "samplingProtocol" and "habitat", those sounded to me more like ABCD's Unit/Gathering/Method: "The method (including technical means) used to make the collection or observation or to describe the capture event." and Unit/Gathering/Biotope: "An element for citing biotope type terms (e.g. classification terms) and measurements (e.g. vegetation height, salinity, slope) related to the unit's gathering site". Until now I understood Unit/Gathering as capturing the spatiotemporal, abiotic and biotic (aka "ecological") context from which a collection originated. Does a mapping exist between abcd:Unit/Gathering and dwc term(s)? |
see misplaced comment here
Does a mapping exist between abcd:Unit/Gathering and dwc term(s)? |
Such a mapping exist on the Darwin Core side in an attribute called abcd_equivalence, which is best seen in the term versions document (https://github.com/tdwg/dwc/blob/master/vocabulary/term_versions.csv), but is also shown for each term on the normative term definitions page (for example, see https://dwc.tdwg.org/list/#dwc_catalogNumber). |
Thanks @tucotuco Following your links (see https://dwc.tdwg.org/list/#dwc_Event) |
For these purposes, yes, though the dwc:Event is a broader concept of which
a DataSets/DataSet/Units/Unit/Gathering is one type.
…On Thu, Feb 17, 2022 at 1:52 PM jbstatgen ***@***.***> wrote:
Thanks @tucotuco <https://github.com/tucotuco>
Following your links (see https://dwc.tdwg.org/list/#dwc_Event)
dwc:Event is equivalent to abcd: DataSets/DataSet/Units/Unit/Gathering
—
Reply to this email directly, view it on GitHub
<#362 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADQ722YNH4PDQWT5GJMUVLU3URU3ANCNFSM5L4FLQ4Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I agree, that Gathering is a type of event, but I am not sure about mapping abcd:Gathering to dwc:Event with any property that implies equivalence. In ABCD so far we have done mappings using skos:hasExactMatch and skos:hasBroaderMatch, to DwC and other vocabularies. However, this is as well not normative and the semantic implications of this usage are a bit tricky (see tdwg/ac#220 ). We just used it to bring a bit nuance into the mappings, maybe here a mapping using skos:broader (or similar) would be useful. If anybody is interested, here is a query to show all of the mappings of the classes and properties that are connected to gathering, such as "Measurement Or Fact": query to show all the mappings
That is how it is used. It is a bit more flexible than the definition Quentin provided from the ICN. For instance an observation can also be expressed using the gathering event, just not with a specimen connected to the unit. |
@DavidFichtmueller Thanks for the explanations and the query.
If a Unit/Gathering can be associated with, that is, produce a material sample or an information artifact, what else is there that lets dwc:event be broader than abcd:unit/gathering? |
A dwc:Event need not generate a material sample or an information artifact. An example from an ecological dataset would be to have a parent-most Event that represents the entire spatiotemporal scope of a project, within which there could be spatiotemporal Events associated with activities at a site, within which may be other nested spatiotemporal subdivisions, within which there might be the kinds of Events you are talking about that produce the material samples, digital media, or or other information artifacts. |
Ah, agreed. |
Updated the Notes field to clarify how this class is related to dwc:Event. |
Are the only events expected expeditions? The properties available appear to point in that direction. I am unsure how this is meant to be used - the records in this collection arose because of this event? The records in this collection were affected by this event? It seems there could be multiple kinds of events of interest (one of them being a change in "status"). If the collection has come about due to hundreds of expeditions should I be expected to add them all? |
HI @Jegelewicz , good question. Rereading our exchange from half a year ago, it seem that we all agree that a dwc:Event can be broader than a typical abcd:Gathering. The reason is that dwc:Event can include events that don't necessarily result in a sample/object/artefact/entity. As far as I understand it, the expected usage in LtC is that a ltc:Event is something that happens in space and time, and is an activity that relates to an occurrence s. lat., ie. reality out there. Somebody traveling around the world in 80 days is an event (prov:Activity is traveling for 80 days), even if it doesn't result in any collection objects. However, a chance acquaintance that the Verne travelers met during their journey, who collected an entity while talking to them, can refer to the Verne event as an activity related to their collection event.
This seems only practical, if you assemble the list of the associated expeditions by machine action.
Yes, this is how I'm seeing "Event" in the context of the DES and its transactions-based implementation enabled by FAIR Digital Objects (FDOs), cp. DiSSCo. Here also activities in the digital realm are events, ie. open FAIR Digital Objects of type Event (openDEs). Time remains the same, however locality (space) in this case relates to hard- and software. For example a certain CMS software platform on a certain hardware server (standing in some server farm) acting as endpoint (prov:Agent) changes the status (prov:Activity) of a system, digital object or data entity (prov:Entity). How the concepts for real-world events and digital transactions develop in relationship to each other seems currently open. Maybe they will start to merge, maybe not. |
The text was updated successfully, but these errors were encountered: