Pavel Shukhman

> This is another purl weirdness. I am now facing a situation where the repository_url is not the same as the namespace. OCI images can be published to multiple registries...

I believe that this does not mean source code repository. From the current purl spec definition (https://github.com/package-url/purl-spec/blob/main/PURL-TYPES.rst): > repository_url: A repository URL where the artifact may be found, but not...

Should be closed as resolved per #194 and #195.

That's a great point, but I don't believe we should try to tackle this problem or add it to a list of use-cases. There are several other projects dealing with...

We actually have concept of artifact update, but it's not expanded. Particularly, we have collection update event enum, which includes: ARTIFACT_UPDATED and special case for VEX_UPDATED. > artifacts can only...

> I don't see a reason why an alternative port should be used, except for tests. Thank you, this sounds reasonable. I think we just need to formally agree on...

Pagination was generally implemented via #195 . However, I'm keeping this open based on @nscuro comment above whether we should tweak the way we paginate.

Check the commit I referenced - it was previously part of the Artifact object. And I think we discussed on the meeting yesterday that it is needed per some regulations....

Ok, so the question becomes whether we want to expose it outside of the document and as part of TEA. For some reason, I thought we were discussing on the...

Compiled a list of terms we are (or may be) using and those with some definitions in the referenced documents (not necessarily fitting definitions, just for faster search). Blank entries...