Olle E. Johansson
Olle E. Johansson
Investigate if WebHooks fits in or if there are other solutions
I think from the consumer side, they have a TEI and just want to reference that to find the product. Having the client understand different TEI types makes it too...
Do you see any usage for the TYPE in the API? A single product can have many TEIs both of the same type and different types. I think we should...
> The question is really _where_ the TEI originates. In the current API spec it's a server-side generated UUID. In your vision, is the TEI provided by the user when...
I think you are mixing the UUID for the product index object and the one used in the TEI. Those are two different entities (but can be the same). I...
I still think that would lead to a massive API that always changes. We have to find another model for the metadata and not have it in the structure like...
The UUID generated by the system for the product object needs to be enforced to be unique in the system, like the leaf, collection and other objects. But a single...
We have to separate a query for the `product object UUID` from a TEI of type UUID with a specific value. Those are two different things. * `/product/` asks for...
How would a query based on type and value look into modern API? There are certainly solutions to query for key/value pairs that would work here too.