Sean Barnum

>>The CASE Ontology Committee had discussed in the past whether InvestigativeActions would always have a ProvenanceRecord among their outputs. I recall, informally, we had said yes, this is a requirement....

I would object to Investigation being made a subClass of Event and especially any proposal to remove it as a subClass of ContextualCompilation. It is true that one aspect of...

While I agree with this proposal in intended spirit I do not feel it is viable due to Risk 1 and Risk 2 above. I do not believe either of...

We may need to bring someone into this discussion who has been involved in the security working group all along. I was participating with the security WG early on helping...

Based on the current structures in the security profile and the discussion above I strongly believe that this issue is out of scope for 3.0. I think it MAY be...

I agree that using a GUID for uniqueness is the right approach. I strongly believe the GUID should be part of the local-part of the ID rather than in the...

Consensus of the Feb 06, 2024 Tech call was to pursue changing the currently existing `standard` property on Artifact to be `standardName` and to remain a string for now. A...

A PR #631 has been created to implement the above reached consensus.

I think this might be viable but definitely has its downsides. We should be careful to understand the following: - The chances of producers inadvertently asserting elements as external would...

There are two issues that need fixed before merging this PR. 1. In the 'Pedigree' section within the RelationType enumeration in Core, the "copiedTo" and "expandsTo" values need swapped in...