Re: Sharing some real-world use of JSON-LD

Hi Alastair!
I've tried Jargon for UNTP and it's very nice. Is it made with Langium?

But I made a review of UNTP
<https://docs.google.com/document/d/1R3yqaYCO3JTpWsIckSzbumzyQgwRvd5X4Ewg-9Ax4yU/edit?tab=t.0>,
and
I think some of the bugs in the ontologies are due to Jargon, and can be
fixed systematically by improvements to Jargon.
Could you please weigh in on that, or work with UNTP on identifying which
issues are due to Jargon?
The review links to individual issues at
https://opensource.unicc.org/un/unece/uncefact/spec-untp, or if you prefer
you can just comment in the doc and I'll reflect in the issues.
Here are some guessed issues due to Jargon:

   - #517
   <https://opensource.unicc.org/un/unece/uncefact/spec-untp/-/issues/517>
   Issue: When a term is reused from "core" to another ontology module, it
   is recast in the target namespace, resulting in duplicated terms (same
   localname, different namespaces).
   - #516
   <https://opensource.unicc.org/un/unece/uncefact/spec-untp/-/issues/516>
   Add Turtle variant of ontologies.
   - I don't know whether Jargon is intended to provide resolution. If so:
   amend semantic resolution by adding content negotiation for Turtle (it
   already returns HTML and JSON-LD).
   - #518
   <https://opensource.unicc.org/un/unece/uncefact/spec-untp/-/issues/518>
   Issue: *don't allow* props with the same local-name to be defined
   discrepantly as Object vs Datatype Property, eg

   untp-core:conformance a owl:DatatypeProperty, rdf:Property ;

   untp-dcc:conformance a owl:ObjectProperty, rdf:Property ;
   - Don't allow a datatype property to point to a class. Eg here the first
   one should be Boolean, the second string

   untp-dcc:conformance schema:rangeIncludes untp-core:conformance.

   untp-dte:name        schema:rangeIncludes untp-core:name .
   -

   #519
   <https://opensource.unicc.org/un/unece/uncefact/spec-untp/-/issues/519>
   Issue: generate owl:Ontology declaration.
   -

   Generate owl:imports
   -

   Use rdfs: domain/range in addition to schema: domain/rangeIncludes
   -

   In the ontology context, define the type of subClassOf:

   "rdfs:subClassOf" : {"@type" : "@id"}

   Else you get invalid axioms like this: untp-dte:ObjectEvent
   rdfs:subClassOf "untp-dte:Event" .
   - Collapsing of Class vs Property in Context: eg this is wrong
   "partyAlsoKnownAs": {"@id": "untp-core:Party"...}
   - On the Artifacts page, can you rename these two links to *Ontology as
   JSON-LD *and *JSON-LD Context*?
   [image: image.png]


Jargon is an example of what I call polyglot tools, see a list in Issue #19
· json-ld/yaml-ld - Polyglot Modeling
<https://github.com/json-ld/yaml-ld/issues/19>
Hi Roberto! Your efforts are listed at the polyglot list (Search for
@ioggstream), I've now added the 2 links that you shared.

Cheers!