Document OntoJIT as ESKA related work

[GerhardBalz-Admin]

Summary

Adds a focused OntoJIT related-work note based on the reviewed Private SKE analysis.

Main points

• positions OntoJIT as a historical ontology-to-executable-code precedent rather than as equivalent to ESKA;
• explains the developer/runtime motivation: bring OWL semantics into a conventional C#/CLR environment;
• distinguishes generated C# + semantic meta-properties from the OntoJIT semantic runtime/inference support required to interpret semantics not supplied by ordinary CLR behavior;
• treats the Pizza CWA/OWA divergence as a runtime semantic choice/limitation, not an inevitable consequence of compiling OWL to C#;
• derives the ESKA lesson that semantic continuity depends on both the projected representation and the semantics of the runtime interpreting it;
• preserves the reviewed boundary that ImplementationProjection is optional in ESKA generally and is used here only to describe the OntoJIT translated path.

Sources

Uses stable DOI references for the OntoJIT papers and Selena Baset's thesis.

Boundary

Documentation only. No ESKA/SMO vocabulary, runtime, executable example, release, or immutable artifact is changed. No contact/outreach content is published.

Related private analysis: GerhardBalz/semantic-knowledge-engineering-private#26 / PR #31.