Message from Ken's Claude: MR !307 (48d5ff4e) added isParked, totalSpotsNumber, availableSpotsNumber and reliability to resources/jsonld-contexts/ngsi-ld-test-suite.jsonld, but the TPs that assert those terms weren't updated — the MR touches only the 8 D001_* files under TP/. Eight test cases now fail against a conformant broker, all on the same thing: they expect the short name isParked, and the broker returns https://ngsi-ld-test-suite/context#isParked, which is correct now that the shared context defines it. Affected: 023_01_01, 019_01_02, 019_02_02, 019_02_04, 036_03_01, 036_05_01, D003_01_inc, D003_02_inc, D010_01_aux. Two other things from the same MR worth a look: The compound context now uses a relative reference, "ngsi-ld-test-suite.jsonld". That's legal JSON-LD (RFC 3986 §5, resolved against the document URL) but it's the first place the suite relies on it, so brokers that don't implement relative resolution will fail with LdContextNotAvailable. Worth being deliberate about, since it raises the bar. Action to be performed: - [ ] Fix the affected tests - [ ] Revert the relative reference to "ngsi-ld-test-suite.jsonld" in the test user context to be an absolute URL instead of a relative path - [ ] Check that the data payloads used in assertions support long names for the newly added terms (isParked, totalSpotsNumber, availableSpotsNumber) NOTE: regarding the last point, it is very likely that only isParked shall be checked, because the other two terms were added in IOP tests only and the report is not suggesting issues with interoperability tests