- From: Rob Atkinson <ratkinson@ogc.org>
- Date: Wed, 26 Nov 2025 04:23:04 +0000
- To: Roberto Polli <robipolli@gmail.com>, Alastair Parker <alastair@jargon.sh>
- CC: "public-json-ld@w3.org" <public-json-ld@w3.org>, Alejandro Villar <avillar@ogc.org>
- Message-ID: <SJ0PR01MB7448C32F8630B359D1D07C7CBCDEA@SJ0PR01MB7448.prod.exchangelabs.com>
Hi Roberto, Alastair Would be keen to touch base and compare notes sometime. We have a relatively sophisticated ecosystem that supports examples, inheritance of SHACL rules, transformations and integration with Knowledge Graphs - with an emphasis on supporting profiling of standards. Pairing this with tools to help author components has always been a desired goal. Likewise lining up our approaches and putting forward a standardised approaches would certainly be of interest. Its very empowering to have tooling that supports modular JSON-LD driven by the schemas in use in the wider community, rather than the much smaller RDF native practitioner space, itself fractured by upper ontology issues. We have open questions about where JSON structures do not map using JSON-LD to concepts from ontologies, but need some form of transformation. We can test and publish these, but wonder whether there is scope for improved interoperability in JSON-LD power, or a JSON-LD++ and tooling. I'm pretty flat out until at least mid-December, unless there was a conversation directly driving future implementation or standards development that is urgent in this timeframe. Rob Atkinson Senior Research Engineer | Open Geospatial Consortium (OGC) Mobile: +61 419 202973 ratkinson@ogc.org<mailto:ratkinson@ogc.org> | ogc.org<http://ogc.org/> | @opengeospatial [https://ci3.googleusercontent.com/meips/ADKq_NYvdzG5CnR-DX7WeJyPCnJuhbJ_G7lH1yVbaql72titKCiG-t4HQ92DiCCRM2jU42bDT20Ge7sBVIodm8VpmVBlrnTKCg=s0-d-e1-ft#https://portal.ogc.org/files/?artifact_id=99287] ________________________________ From: Roberto Polli <robipolli@gmail.com> Sent: Wednesday, November 26, 2025 1:11 AM To: Alastair Parker <alastair@jargon.sh> Cc: public-json-ld@w3.org <public-json-ld@w3.org> Subject: Re: Sharing some real-world use of JSON-LD You don't often get email from robipolli@gmail.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi Alastair et al, On Tue, 7 Oct 2025 at 13:31, Alastair Parker <alastair@jargon.sh<mailto:alastair@jargon.sh>> wrote: [..] I’m Al, founder of Jargon, a modelling tool that we use to generate JSON Schema, JSON-LD contexts, and related artefacts from composable domain models. Nice to meet you :) United Nations Transparency Protocol (UNTP): While I can’t speak on behalf of the UNTP team, I can share that the team use Jargon to model trade and supply-chain domains - a mix of UN-specific properties and references to established vocabularies like schema.org<http://schema.org>. From these models, the team generate both JSON Schema and JSON-LD contexts, and Jargon ensures they work together: the schema enforces mechanical @type properties that the context file then relies on for expansion In Italy we implemented a similar mechanism to annotate existing and future APIs with JSON-LD Keywords. This approach will ensure that all APIs produced by more that 12k Italian agencies will be semantically interoperable. On each JSON Schema we associate: - x-jsonld-type: representing the rdf:Class - x-jsonld-context: representing the context. This tool supports the annotation process and shows the RDF generated by the schema example, and shows a semantic diagram of the annotated schema (preview feature, still WIP): - https://teamdigitale.github.io/dati-semantic-schema-editor/latest/ showing whether referenced classes are present or not on the national SparQL endpoint provided on schema.gov.it<http://schema.gov.it> The relevant specifications (Linked Data Keywords, or LDK) are here: - https://www.ietf.org/archive/id/draft-polli-restapi-ld-keywords-07.html @ratkinson Hi! Just saw the OGC approach now. It is not far from LDK, but there are some major differences: - LDK:x-jsonld-type only references rdf:Class, while iiuc OGC:x-jsonld-id can reference both classes and properties - LDK only annotate objects because a single scalar field cannot be converted to RDF. See https://www.ietf.org/archive/id/draft-polli-restapi-ld-keywords-07.html#appendix-C-2.18.1 - iiuc LDK:x-jsonld-context ~ x-jsonld-prefixes Feedback welcome + Have a nice day! R.
Received on Wednesday, 26 November 2025 04:23:12 UTC