0019 Refining withdrawal: one-way doors, stop new uses only, notifying, interpreter consent, interpretations also in layer 1
The Korean version is authoritative. This page was translated by AI (Claude) and has not yet been checked by a person. 한국어 원문
This is the decision record for 07-Deposit v0.3. It compares “what happens to interpretations when the original is withdrawn” with precedents (Nodeone survey, 2026-10-20) and fills in what was missing. It is reflected in 07-Deposit, 04-layer, 03-manifest, 00-Principles and 05-Glossary. The wording “cannot be removed” in decision 0003 is refined to the wording in item 5.
1. Interpretations are also kept in layer 1
Section titled “1. Interpretations are also kept in layer 1”- Both originals and interpretations (transcription, decipherment, translation, annotation, summary) are kept in the layer 1 store. layer 2 apps only make and show them; they do not keep interpretive-layer records for long. This is written in 04-layer section 1.
- That way, when an original is withdrawn, things close in one place. If interpretations are scattered across apps, we would have to chase down each app to close them.
- secretary moves transcriptions to arkive together with the originals (at the same time as decision 0004, 16 November 2026).
2. “Look inside” is the default, “take away” is the exception
Section titled “2. “Look inside” is the default, “take away” is the exception”- Viewers, researchers and apps view and use records inside the store. Handing over files is the exception. The app key (decision 0011) already works this way.
- This is because what is handed outside cannot be withdrawn. What appears on a screen can be photographed, so “viewing inside” is not perfect either, but once withdrawn it closes at once.
3. One-way doors
Section titled “3. One-way doors”Once past the doors below, there is no withdrawing later.
| Door | Examples |
|---|---|
| Public | widening the scope to public, putting a registry entry on the public ledger (decision 0016) |
| Handing over files | a viewer’s download, sending to an outside company (transcription), research data sets |
| Separate use outside | “survives separately”, publishing as a book or film, attaching an open license such as CC to an interpretation |
| Training | putting it into training data |
- When passing one of these doors, the depositor is shown “This cannot be withdrawn later”, and separate consent is obtained for each door. The consent entry records that this wording was seen.
- Daily work such as transcription is covered by a single first consent (turning on automatic transcription).
- One line in 00-Principles section 4: “When passing a one-way door (public, handing over files, separate use outside, training), the depositor is told so first and gives separate consent.”
4. What goes out leaves a mark
Section titled “4. What goes out leaves a mark”- Recipients go in the ledger. Not only what was sent to an outside company but also what a person downloaded is written in
sent_to. A company usesprovider; a person or institution usesto(ID number). - Status address. Each record that has gone outside gets an address that only tells “is it open now, or withdrawn”. It holds no content. Only those who already received the record know the address, so its existence reveals nothing new.
- Two recommendations: an invisible mark (watermark) per recipient cannot pull a copy back, but it can find who leaked it. A time limit on downloads (for example, the key expires after 30 days) means the file no longer opens after that time.
5. Changes to the table in section 7
Section titled “5. Changes to the table in section 7”- New row “Stop new uses only”: chosen by the depositor. What closes: new interpretations, new training, new publication, new downloads. What remains: existing interpretations stay at their current scope. This follows US Copyright Act section 203 (derivative works already made can continue; only new ones are blocked) and the withdrawal levels of UK Biobank.
- Rows “Narrowing the scope” and “The whole deposit (withdrawal)”: recipients (
sent_to, status address) are notified. If they cannot be notified, or doing so would take unreasonable effort, the reason is written in the withdrawal entry (the same level as Article 19 of the EU GDPR). - Row “Only the AI training consent”: “It cannot be removed from models that have already learned from it” is refined to “It cannot be removed from the current model version; it is left out from the next version on” (the wording of decision 0003).
6. Training ledger
Section titled “6. Training ledger”When sending for training, model (the model’s name and version) is also written in sent_to. Training is not bundled (decision 0017), so one entry remains per version. That way we can show “which versions it is in, and from which version it was left out”.
7. Consent of interpreters
Section titled “7. Consent of interpreters”- A person who starts making an interpretive layer (translator, decipherer, annotator) consents once, at the start, to that volume’s agreement as an interpretive-layer rights holder (07-Deposit section 4,
parties): “If the original is withdrawn, my interpretation closes in the store”, and whether or not it “survives separately”. - The default when there is no consent:
- In the store, it closes along with the original.
- A copyrighted interpretation (translation, annotation) is not deleted but returned to its rights holder. But if other people’s rights remain in the original (the voice or privacy of a living person, copyright in the original), it is not returned, only closed. This is because the translation contains the content of the original as it is.
- A machine draft has no rights holder, so it closes along with the original.
- If the original has no copyright, like a 400-year-old original text, the only grounds the owner of the original has to block interpretations outside the store are the agreement and ownership, not copyright. That is why this consent is needed.
8. Two lines in the agreement notice
Section titled “8. Two lines in the agreement notice”- “Copies that have gone outside (made public, downloaded, interpretations with CC attached, training) cannot be withdrawn.”
- “Before the depositor holds the key (09-Keys section 8), the store may have to hand records over if a court order comes. Even after the depositor holds the key, this is still true for interpretive layers that are not locked.” There is a case in the US where the Boston College oral history records were handed over under a court order.
9. One line of grounds for unsettled in section 3
Section titled “9. One line of grounds for unsettled in section 3”“Collation (correcting the original text) and punctuation marking were found not to be creative in Korean Supreme Court judgment 2019다268061 (30 June 2021). But taking someone else’s effort without permission can still be a tort.” The basis value will change after legal review.
- Almost all precedents “close only from now on”. The EU GDPR Article 7(3), the Korean Personal Information Protection Act Article 37, biobanks, CC licenses. 07-Deposit section 7 goes the same way, so the main line stays and we only fill in what was missing.
- No scheme exists that uses technology to pull back copies that have gone outside. What exists is sending out less, notifying, and leaving marks. So the effort goes into telling people about the one-way doors in advance and getting consent.
- The interpreter’s work is not destroyed. US section 203 keeps derivative works already made alive even after the original’s permission ends. On the other hand, Stewart v. Abend (1990) is a case where a dispute arose when there was no such clause.
- Interpretations must be in one place to be closed. Item 1 is the base that makes the rest actually work.
Other options
Section titled “Other options”| Option | Why not chosen |
|---|---|
| Using technology to pull back what has gone outside too (opening only in a dedicated app, with the e-book approach as default) | It forces a dedicated app, does not fit open standards like IIIF, and those who want to break it will break it. We only recommend letting people choose “downloads with a time limit” where needed |
| Deleting even interpretations already made, on withdrawal | It destroys the interpreter’s work. There is no precedent either |
| Once permitted, never withdrawable (the CC approach) | It conflicts with principle 1 “the original belongs to its owner” and 00-Principles section 4 “withdrawal at any time” |
| Keeping interpretations in layer 2 apps (secretary now) | On withdrawal, the places to close are scattered across apps |
Where it has effect
Section titled “Where it has effect”- hgp: 07-Deposit v0.3 (sections 3, 4, 7 and 8, new section “One-way doors”), 04-layer section 1, 03-manifest section 8 (
to,model, status address), one line in 00-Principles section 4 (approved), refined wording in decision 0003, 05-Glossary. - secretary: transcriptions also go to arkive (16 November 2026), a consent screen for each one-way door, one consent when turning on automatic transcription,
sent_to.model. - arkive: downloads in
sent_to, status address, interpreter consent screen, “stop new uses only”, notifying recipients.
0 won.