Resolving IRIs does not always emit IRI warnings.

[afs]

Version

5.2.0

What happened?

riot on

{
    "@context": {
        "blob": "vocab:blob:"
    },
    "blob:at": {
        "@id": "file:/pdf/2015.pdf"
    }
}

gives no warning,

But riot on

_:B42f7628296b620abed4ec598d76b4cf1 <dokk:vocab:blob:at> <file:/pdf/2015.pdf> .

does.,

Are you interested in making a pull request?

Yes

[afs]

This is not JSON-LD speciifc.
Title changed.

When the base URI and the URI being resolved both a URI scheme and it is the same scheme, the parsing of the input URI (to be resolved) is not checked for warning. Only errors and syntax errors.

[afs]

On further investigation, this isn't a bug. It is just the way that it plays out.

Jena is following RFC 3986 reference resolution (the "non-strict" version) in both jena-iri and jena-iri3986. This means that file: needs to be file:/// (empty host, not missing host).