Repository navigation
feat(site): publish pinned vocabulary identifiers and entity redirects - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publishes eleven pinned vocabulary namespaces as Turtle, JSON-LD and responsive HTML, with a fixed-destination entity 404 redirect to the existing explorer. A bijective ownership ledger preserves legacy vocabulary aliases and keeps HTTP/HTTPS property pairs distinct.
The generator removes internal tracking references from diagnostic prose. GitHub Pages uses its existing Jekyll build with explicit
data/andscripts/exclusions; raw pinned compiler inputs remain source-review material and are not published website resources. The served-tree guard rejects tracking references, service hosts, published raw inputs and disabled exclusions. Legacy vocabulary IRIs are admitted aliases; no runtime graph or shape migration occurs.Validation: eleven RDF/source/privacy controls, all eleven namespace pages at desktop/mobile sizes, browser entity redirect/refusal controls, original playground and twelve-component stack controls. Full suite plus focused final privacy guard pass; 157 watched HOME paths and five resources untouched. Exact current hosted Playground check passes. The original independent review findings remain in history; SAME-feedback review is required before merge.
Rollback: named
revert-ids-publication-611.patchreconstructs the entire prior site tree9c55a60d7487b43f98ef327d678e9917d7fbf90funder a private index. Revert through normal Pages on a real source regression. Exact Pages completion, all 33 live namespace resources, raw-input 404 checks, and actual entity forwarding remain deployment acceptance. Upstream w3id registration/content negotiation is separate; entity RDF responses remain unsupported.Demo: recording and replay instructions. Same private HTTP requests change from 404 on the base to 200 on the candidate, with homepage 200 as a positive control. Namespace request behavior remains unchanged by the privacy feedback repair; this is a local recording, not live Pages proof.