Invalid '@base' IRI is accepted by the context processing algorithm in deserialization test suite.

From the step 5.7 of the context processing algorithm it is clear that a @base value is accepted iff it is null (step 5.7.2) or an IRI (5.7.3) or a relative IRI reference (5.7.4). In particular, if it is an invalid IRI reference, then an invalid base IRI error is always returned.

In the deserialization test #tli12, an invalid IRI reference is given as context @base, but the expansion algorithm is expected to succeed. This seems in contradiction with step 5.7.

My implementation strictly follows step 5.7, so it fails at processing the context defined in this test input, which in turns makes any deserialization algorithm based on my implementation to fail.

Start with deserialization test #tli12 and compare its expected expansion result with context processing algorithm step 5.7, especially the handling of an invalid @base IRI reference. Check the linked implementation issue for the observed failure, then determine whether the algorithm or the test expectation is inconsistent and update the relevant test or specification behavior accordingly.