okf: add optional erasure conformance profile (SPEC 9.1)#191
Open
manumishra12 wants to merge 1 commit into
Open
okf: add optional erasure conformance profile (SPEC 9.1)#191manumishra12 wants to merge 1 commit into
manumishra12 wants to merge 1 commit into
Conversation
Plain deletion of a concept can still disclose that it existed (dangling inbound links, index/log references, recoverable git history). Adds an opt-in erasure profile specifying what erased means for bundles that must not leak removed knowledge. The profile is opt-in and does not change the validity of ordinary bundles. Additive and backward-compatible (per SPEC 11). Addresses GoogleCloudPlatform#90.
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
1 participant
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.
What
Adds an optional erasure profile to SPEC section 9 (as section 9.1). Issue #90 notes that erasing a concept currently discloses it; this specifies an opt-in profile for bundles that must not leak removed knowledge.
Why
A plain file deletion still discloses the concept: dangling inbound links keep naming it,
index.md/log.mdmay still reference it, and git history keeps the content recoverable.The profile
When a concept is erased, a bundle conforming to the erasure profile:
index.mdandlog.md.Opt-in: consumers MUST NOT assume a bundle follows it unless it says so, and ordinary bundles remain valid under section 9.
Additive and backward-compatible (SPEC section 11 minor-version rules).
Addresses #90.