Marco Deicas

Sorry for the late response, but I think the lesson learned is that an ingestion pipeline may have been designed with an assumption of only ingesting documents once, or otherwise...

@nathannaveen, @pxp928, and I chatted about this. The plan is to first identify critical dependencies using hasSbom nodes and expose that as an endpoint in the Rest API, and then...

# Standard Rest API The standard approach is to define the schema with OpenAPI and generate server and client code. Two code generators seemed the most promising: - [deepmap/oapi-codegen ](https://github.com/deepmap/oapi-codegen)...

> > The drawback of deepmap/oapi-codegen is that it can only generate client code in Go. > > I think I misunderstood this the first time round so want to...

Adding the OpenAPI Spec I used to generate the examples above for reference: ``` openapi: "3.0.0" paths: "/search/packages/names": get: summary: Search packages by package name operationId: searchPackageNames parameters: - name:...

We're going to go with a standard REST API because it is the simplest option and, and use `oapi-codegen` over `OpenAPITools/openapi-generator` for the reasons outlined in a previous comment. Either...

Yup I think these are good points. Using the ontology API as a level of indirection also limits the use of capabilities that each datastore may have, such as native...

I’m happy to create the proposal for the new predicate type. I’d like to come to agreement beforehand, though, if the use case (referring to and signing out-of-band metadata) is...