if schemaurl is a uri-ref, how do I get it?

Suppose I get a cloudevent with a schemaurl set to /spec/v0.1/data/schema/events.json

This is valid from the specs point of view. But from an event consumer, they are out of luck to know how to fetch that schema data.

[deissnerk]

I understand that it’s especially unfortunate because of the url part, but source is a piece of metadata that needs to be handled generically by middleware. A well-defined way for de-referencing relative uri references would be helpful. Otherwise you might end up with “if-then-else” logic in event routers. I realize that this is off-topic in this issue, though. 🤔

[n3wscott]

This makes sense for source because source is just metadata about the entity that produced the event, but schemarul is provided for the consumers benefit to understand the payload. And yet… they can not. Also, schemaurl is a uri-ref 😕