uri-reference instead of iri-reference for href

[m-mohr]

Due to opengeospatial/ogcapi-records#430 we should consider disallowing IRIs for href in STAC and instead use uri-reference in the schemas.

[gadomski]

Disallowing a thing feels breaking? Or is this one of those "we wrote the spec this way and we're just getting the json schema to match"?

[m-mohr]

That's to be investigated. It looks like the written spec doesn't say IRI anywhere, but instead it uses usually the term "URL". The schema says iri, but in practice I don't think that's used because it doesn't work well with HTTP anway, see opengeospatial/ogcapi-records#430 (comment)

The use of iri-reference was probably me being not well informed about the differences of iri and uri and as such just choosing for the most flexible one for JSON Schema.

If OGC also goes towards uri-reference, we'd have issues that the API spec would make something more liberal than in the spec we inherit from, which doesn't work well (Liskov substitution principle). So in that sense I'd think if OGC goes towards uri-reference, we should do it, too. Arguing that the JSON Schema was broken and the written spec didn't allow it anyway.