When compacting a JSON-LD with a `@base` context, I remarked different behaviour for URIs and URNs: **URIs** With a `"@base": "http://example.com"`, a `"@id":"http://example.com/nosec_sc"` becomes `"@id": "nosec_sc"`, which is expected. [Playground link](https://json-ld.org/playground/#startTab=tab-compacted&json-ld=%7B%22%40id%22%3A%22urn%3Amy%3Aurn%22%2C%22http%3A%2F%2Fontology.com%23prop%22%3A%7B%22%40id%22%3A%22http%3A%2F%2Fexample.com%2Fnosec_sc%22%7D%7D&frame=%7B%22%40context%22%3A%5B%7B%22td%22%3A%22https%3A%2F%2Fwww.w3.org%2F2019%2Fwot%2Ftd%23%22%2C%22security%22%3A%7B%22%40id%22%3A%22td%3Asecurity%22%7D%7D%2C%7B%22%40base%22%3A%22urn%3Aexample%3A1234%2F%22%7D%5D%2C%22%40type%22%3A%22td%3AThing%22%7D&context=%7B%22%40base%22%3A%22http%3A%2F%2Fexample.com%22%7D) **URNs** With a `"@base": "urn:something/"`, a `"@id":"urn:something/no_sec"` remains the same after compaction though we would expect a `"@id":"no_sec"`. [Playground link](https://json-ld.org/playground/#startTab=tab-compacted&json-ld=%7B%22%40id%22%3A%22urn%3Amy%3Aurn%22%2C%22http%3A%2F%2Fontology.com%23prop%22%3A%7B%22%40id%22%3A%22urn%3Asomething%2Fnosec_sc%22%7D%7D&frame=%7B%22%40context%22%3A%5B%7B%22td%22%3A%22https%3A%2F%2Fwww.w3.org%2F2019%2Fwot%2Ftd%23%22%2C%22security%22%3A%7B%22%40id%22%3A%22td%3Asecurity%22%7D%7D%2C%7B%22%40base%22%3A%22urn%3Aexample%3A1234%2F%22%7D%5D%2C%22%40type%22%3A%22td%3AThing%22%7D&context=%7B%22%40base%22%3A%22urn%3Asomething%2F%22%7D)