Richard L. Pyle

@Archilegt: I defer to @baskaufs on the main parts of your post, but with respect to: > For solving the current issue, I think that we need to look back...

We have dealt with this before in our data modelling and implementation. Our conclusion was that it mostly applies in cases where an instance of Organism has individual constituents (e.g....

Thanks, @fja062 ! This is very helpful! > Imagine a hunting season where 30 individuals are shot, and we know that 10 are female, 10 are male, and 3 of...

> Then what is the purpose of individualCount? This term predates the establishment of the `Organism` class. In an ideal world, this term would be organized in the `Organism` class,...

I share the concerns about the term "parent" in this context, but I'll focus my comments here in response to @fja062 : > Could you give an example of where...

> The question of examples to include is extremely important for this term, I think. I agree completely! I also agree that a pragmatic approach is best, as an exhaustive...

I agree with @qgroom: There is definitely a need for `eventDate` to accommodate a range (span). ALL events span some period of time (even if it's just milliseconds). In pretty-much...

> `eventDate` already accommodates a range. Yes, but in a somewhat clunky way. Also, the "Not suitable for a time in a geological context" qualifier in the definition precludes defining...

I do not agree with this proposal. I think a better approach is to embrace `MaterialSample` as currently defined, and instead alter the various "BasisOfRecord" terms that are represented as...

@dshorthouse : 100% agreement on all of this. We likewise came to the exact same conclusions (including the move of `catalogNumber`, `otherCatalogNumbers`, `associatedSequences` and `preparations` from `Occurrence` to `MaterialSample`). Obviously...