Repository navigation
Activate immutable ESKA core 0.2.0 W3ID routes #87
Description
Status
UPSTREAM W3ID PR SUBMITTED.
The governed eska-v0.2.0 release exists, the tagged core backend is verified, PR #92 recorded the release-published / route-pending state on main, and the minimal W3ID contribution has now been submitted upstream as:
Goal
Activate immutable W3ID routes for ESKA core 0.2.0 only against the governed eska-v0.2.0 release.
Required routes
https://w3id.org/eska/model/core/0.2.0
https://w3id.org/eska/dist/0.2.0/eska-core.ttl
Both must resolve exclusively to the immutable eska-v0.2.0 release tag, never to main.
Prerequisites
- ESKA Publish governed ESKA v0.2.0 release #86 completed:
eska-v0.2.0exists; - release tag points to exact governed commit
a6ce0b9e795d271dce8a2b7be93d44932e8448d4; - tagged
model/eska-core.ttlis publicly fetchable and verified as core0.2.0; - tagged core contains
eska:SemanticModel owl:equivalentClass smo:SemanticModel; - tagged core retains
dcterms:requires <https://w3id.org/smo/0.1.0>and the non-deprecated ESKA compatibility term; - PR Record ESKA v0.2.0 release evidence #92 recorded release evidence on governed
mainasaf35a390a181c86263edbff24bc22b01d7f6520e; - post-merge focused contract verification passed;
- full Pizza/ESKA regression passed on unchanged rerun after one transient downstream
RemoteDisconnected.
Upstream contribution
W3ID PR:
perma-id/w3id.org#6543
Source branch/head:
GerhardBalz/w3id.org:eska-core-0.2.0-routes
0a213385a247adcf3293c1077e9c58e64fda9308
Base:
perma-id/w3id.org:master
84d541d959006ea6df14014e880020223c3c059b
Verified upstream submission state at creation:
- open;
- non-draft;
- mergeable;
- exactly one commit;
- exactly two changed files:
eska/.htaccessandeska/README.md; .htaccessadds exactly five lines;- no change to existing current or immutable routes;
- every new immutable backend target uses
eska-v0.2.0, nevermain; - no maintainer comments yet;
- no commit-status checks reported yet.
Remaining sequence
- wait for upstream #6543 merge or maintainer feedback;
- verify the actual merged head and upstream merge commit;
- externally verify current + all immutable ESKA routes, including core
0.2.0; - synchronize the repository-owned W3ID mirror with the active upstream state;
- record upstream merge/live verification evidence in ESKA publication metadata;
- close Activate immutable ESKA core 0.2.0 W3ID routes #87 and then close parent Align ESKA SemanticModel with published SMO in the next core minor version #84 / downstream SMO Add a third executable-semantic mode #11 if all acceptance criteria are fulfilled.
Non-goals
Do not:
- change core semantics while adding routes;
- modify existing core
0.1.0or other module routes; - retag
eska-v0.1.0oreska-v0.2.0; - point any immutable route to mutable
main; - mark core
0.2.0W3ID routing active before upstream merge plus successful external live verification.
Completion rule
Close only when both core 0.2.0 routes are upstream-active and externally verified against eska-v0.2.0.
Refs #84, completed #86/#88, merged PRs #85/#89/#92, upstream perma-id/w3id.org#6543.
Activity
GerhardBalz-Admin commentedon Aug 13, 2026
Preparation update — no route has been activated or submitted upstream yet.
All release prerequisites are objectively satisfied by
eska-v0.2.0at commita6ce0b9e795d271dce8a2b7be93d44932e8448d4, and the tagged core backend is verified.A minimal W3ID fork branch has therefore been prepared safely:
GerhardBalz/w3id.orgeska-core-0.2.0-routesperma-id/w3id.org:masterat84d541d959006ea6df14014e880020223c3c059b0a213385a247adcf3293c1077e9c58e64fda9308eska/.htaccess,eska/README.mdThe only redirect behavior added is:
model/core/0.2.0→ immutableeska-v0.2.0/model/eska-core.ttl;dist/0.2.0/eska-core.ttl→ immutableeska-v0.2.0/model/eska-core.ttl.No new immutable route targets
main, and all existing routes are preserved. Upstream PR submission remains intentionally deferred until the release-evidence state in PR #92 is reviewed/merged.GerhardBalz-Admin commentedon Aug 13, 2026
Post-merge verification note: the first full
Pizza ESKA referencerun (31676893328, attempt 1) passed all seven executable modes, release/tag evidence, tagged core verification, and the first live W3ID checks, then failed on a transient downstream HTTPSRemoteDisconnected. The unchanged job was rerun and attempt 2 completed successfully end-to-end. No code or publication-state change was required.#87 remains READY FOR UPSTREAM W3ID SUBMISSION.
GerhardBalz-Admin commentedon Aug 13, 2026
Upstream merge observed
perma-id/w3id.org#6543was merged on 13 August 2026.Verified upstream PR evidence:
This satisfies the upstream-merge prerequisite but does not by itself close #87. The completion rule still requires external verification that both immutable core 0.2.0 routes resolve against
eska-v0.2.0, followed by repository publication-state synchronization/evidence.Next action: run the governed external route verification and record the resulting live evidence before marking the routes active.
GerhardBalz-Admin commentedon Aug 13, 2026
Upstream merge and live verification complete
perma-id/w3id.org#6543merged successfully.Verified upstream evidence:
The repository follow-up is PR #93.
A dedicated GitHub-hosted live verification run completed successfully:
It verifies all three public representations:
https://w3id.org/eska/model/core/0.2.0withAccept: text/html;Accept: text/turtle;https://w3id.org/eska/dist/0.2.0/eska-core.ttlwithAccept: text/turtle.The checks require an HTTP 303 redirect and final immutable backends under
eska-v0.2.0.PR #93 now synchronizes the repository-owned W3ID mirror and advances the governed publication contract/backend metadata from route-pending to active. The updated SMO/publication contract workflow is also green on head
713f59f457c84afcdc61f623908af972c121d408.Issue #87 should close when PR #93 is reviewed and merged; parent #84 can then be closed if no other acceptance item remains.