Deposit

This document sets out how each record states who owns it, who deposits it, who keeps it, and to whom its interpretations belong.

---

0. In one line

A deposit is not a transfer of ownership (HGP-0003 Article 1). Even as a physical item becomes photographs, transcriptions, translations and training data, “whose it is, how far it is open, and how far it closes when withdrawn” follows it through every layer.

1. Why this is needed

• Korean holders of old documents already separate ownership from custody in managing physical items. The deposit schemes of Korean studies institutions leave ownership with the depositor. Few publish this in machine-readable fields. The Korea Heritage Service OpenAPI, which gives the owner (ccbaPoss) and the administrator (ccbaAdmin) separately for each designated national heritage item, is nearly the only one. Example: for the Treasure “유성룡 종가 문적” (documents of the head family of Yu Seong-ryong), the owner is “유＊＊＊” (personal name masked) and the administrator is “한국국학진흥원” (Korean Studies Advancement Center) (checked directly on 2026-10-12). But these are fields about the physical item of a designated heritage item. There is no field anywhere that records, layer by layer, whose it is after it has become photographs, transcriptions and translations (Nodeone survey, 2026-10).
• Until now hgp also recorded only one thing: “depositor = owner of the original” (01-Permissions section 2). For recordings that is enough. The person who spoke is the owner and the one who deposited.
• Old documents are different. One family holds the physical item, a relative takes photographs and hands them to someone else, and that person uploads them to the store. arkive already has volumes like this. Transcription and translation are the work of yet another person (a scholar), and that translation carries the translator’s copyright.
• So we separate four roles, keep the agreement as a record, and state a rights basis for each interpretive layer.

2. Four roles

Role	Meaning	Ledger field	Example
Owner	The owner of the physical item or the original	owner	clan (munjung), family, individual, institution
Depositor	The person who deposits records with the store and gives instructions (01-Permissions section 2)	depositor (existing field)	the person who recorded, the clan representative, the relative who received the photographs
Physical holder	The place that keeps the physical item. Different from the store	holder	Korean studies institution, museum, the family itself
Store	The place that keeps the digital original and the ledger (layer 1). The administrator in 01-Permissions	(the party writing the ledger itself)	arkive (Nodeone)

• By default, owner = depositor. For recordings this is always so. In that case owner need not be written.
• If the two differ, owner must be written. If unknown, record that it is unknown with {"known": false, "note": "…"}.
• If the depositor is not the owner and there is no record of the owner’s permission (the agreement in section 4), the depositor has the same limits as a “stand-in depositor” (01-Permissions section 4 addendum, decision 0011). The depositor cannot widen the scope to public, order destruction, name a successor, or give consent to AI training. The depositor can archive, transcribe, and show records to people who have been granted permission.
• A physical holder is not a permission. It is a field that says where the physical item is. For the physical holder to see the record digitally, it must obtain viewer permission like anyone else.
• There can be more than one depositor (01-Permissions section 3, “joint owners”).
• A person’s name is interpretive information. The ledger records only an ID number, and the name is locked inside the store (03-manifest section 3).

3. Rights in the interpretive layer

Each layer derived from a single original has a different rights basis. So we do not ask “what are the terms of use for this material?” but “what is the rights basis and scope of this layer?”

Interpretive records carry a rights field.

rights.basis	Meaning	Typical layer
none	There are no rights. The old text itself	the characters of a 400-year-old original text
ownership	Ownership and the agreement are the basis	scan of the original, photograph of the original
copyright	The creator’s copyright	translation, annotation, commentary written by a person
contract	The agreement sets this separately	layers named in the agreement
unsettled	The law is not yet clear. Pending legal review	machine draft, talcho (transcribing cursive script) and pyojeom (adding punctuation), which are close to copying as is

• rights.holder records the ID number of the person who holds the rights. Machines do not hold rights (01-Permissions section 1, item 3). For a machine draft, leave holder empty and set basis to unsettled.
• Inside the store, an interpretive layer is never opened more widely than the scope of the original. It inherits the narrowest scope among its sources (the same rule as 06-Relation network section 9). Even if the translator wants it public, if the original is “private”, it is “private” in the store.
• Use by the creator of an interpretation outside the store (such as publishing a translation as a book) is governed only by the “survives separately” clause of the agreement. If the agreement says nothing, the original’s terms apply.
• A confirmation stamp (01-Permissions section 2) is not a right. The person who applied the stamp does not thereby hold rights in that layer.

4. The deposit agreement is a record

An agreement does not end with spoken words. The agreement document itself is deposited in the store as an original (it gets a fingerprint), and the ledger holds an agreement entry. Each record’s agreement field points to that agreement.

Field	Meaning	Required
id	Agreement ID	required
parties	Parties and their roles: owner, depositor, holder, store, rights holders of interpretive layers	required
covers	Which volumes, which faces	required
from	Start date	required
review_at	Review date. Default is 5 years later	required
owner_consent	What the owner has permitted (scope, the four use-consent fields)	when owner ≠ depositor
layers	For each interpretive layer, its rights and whether it “survives separately”	optional
doc	Fingerprint of the original agreement document	required

• Nothing opens automatically when the review date arrives. The depositor is asked “Shall we leave it as it is?”, and the answer is recorded as a new entry. If there is no answer, things stay as they are (“what is not decided stays closed”, 01-Permissions section 1).
• The store may not put these conditions into an agreement: attaching conditions or time periods to export or withdrawal (HGP-0003 Article 6), passing records to third parties (Article 8), selling the content (Article 7, principle 8). If the agreement of a physical holder (such as a Korean studies institution) has a notice period for withdrawal, that applies to the physical item and cannot block the export of the digital original.
• When an agreement changes, the old entry is not deleted; a new entry replaces it (replaces). Consent history has the same shape (referencing ISO/IEC TS 27560 and W3C DPV).

5. Time-limited scope

A scope can carry a time limit, as in “sealed until 2050, public after that”. This is the same as the “restricted disclosure year” in the oral history guidelines of the National Library of Korea.

• Field: scope_after: [{"at": "2050-01-01", "scope": "public"}]. The current scope stays in scope.
• Only the depositor sets it. A successor cannot bring the date forward or widen the scope. A successor can postpone or narrow it (01-Permissions section 2, “a successor cannot widen the scope”).
• When the date arrives, the depositor is notified before the change. If the depositor is alive, they confirm once more. If the depositor has passed away, the change happens as the depositor arranged.
• Even after the change, private passages about other possibly living persons stay closed (06-Relation network section 9, item 3, decision 0008). A time limit opens only the depositor’s own share.
• “Sealed”, even with a time limit, means that until then only the depositor can open it.

6. When a group is the depositor

When a group such as a clan (munjung), a Confucian academy (seowon) or a cooperative is the depositor:

• Authority is attached to the office, not the person. The head heir of the main lineage (jongson), the clan representative, the head of the Confucian academy, the chair of the cooperative. When the person changes, authority passes along with the office.
• The group decides how it decides. Whether the representative decides alone, by vote of a general meeting, or how many must agree, is written in the agreement’s parties. Nodeone does not set the rules inside a group (HGP-0100 section 12, “each community has its own charter”).
• The consent entry records who consented, in which office, and by what resolution (the fingerprint of the resolution document). If there were dissenting opinions, those are recorded too.
• If a group contains smaller groups, such as a grand clan association (daejonghoe), a branch (pa) or a head family (jongga), the agreement records who entrusted what to whom.
• Nodeone attaches only notices; use labels (“within the clan only”, “for research only”) are attached only by the group. This references Local Contexts’ “institutions use Notices, communities use Labels”.
• The voice and place of a person who leaves the group are not erased. What remains and what returns when someone leaves is set in advance by agreement, not negotiated at the time of leaving (HGP-0100 section 10).

7. How far withdrawal closes things

Withdrawal can be made at any time, and no reason is asked (00-Principles section 4). What closes depends on what is withdrawn.

What is withdrawn	By whom	What closes	What remains
Only the AI training consent	The depositor (and also the owner, if owner ≠ depositor)	It is left out of the next training data. Those who received training data are notified	It cannot be removed from models that have already learned from it. This fact is written in the withdrawal entry (decision 0003)
Narrowing the scope	The depositor	The record, and the interpretations and derivatives made from it, are narrowed together	Nothing can be done about the memory of those who already saw it. When it was narrowed is recorded
The whole deposit (withdrawal)	The depositor	The original is returned (export, HGP-0003 Article 6) or destroyed. Interpretive layers close along with the original	Interpretations that “survive separately” are returned to their rights holders and closed in the store. The deletion entry (fingerprint, when, why, what was done). A registry entry put on the public ledger (one fingerprint, decision 0016) cannot be deleted; it only gets a “revoked” mark. This is said in advance when the agreement is made
One’s own interpretive layer	The rights holder of that interpretation (a translator, etc.)	Only that layer, and derivatives made from it, close	The original and other people’s interpretations stay as they are
Ownership changes (return, inheritance)	The new owner and the depositor	Any widening of scope stops until a new agreement	The old agreement and the records made in the meantime

• To close means that the item is no longer visible or used in the store from now on. Destroying an original means destroying its key (01-Permissions section 4), and the fact of deletion remains.
• On withdrawal, each action actually taken (hidden from view, key destroyed, removed from the next version, recipients notified) is written one by one in the withdrawal entry.

8. Use consent and AI

• The four use-consent fields (00-Principles section 4) stay as they are. If owner ≠ depositor, “use in books, films and the like” and “use for AI training” also need the owner’s permission.
• AI use is already split in two (00-Principles section 4): training (teaching it into a model; requires consent; cannot be removed after withdrawal) and reading and answering on demand (not put into the model; disappears from answers after withdrawal). The research report suggests also treating fine-tuning and “generating things that resemble the original” separately. Fine-tuning counts as training. Generating resemblances is left to section 15.
• When releasing training data outside, check rights for each source layer. A copyright layer also needs its rights holder’s consent.

9. Example (hypothetical)

Ten photographs of a woodblock-printed collected works. One family holds the physical item. A relative took the photographs and gave them to the head of Nodeone, who uploaded them to arkive. There is no deposit consent form.

{"type": "agreement", "id": "ag-0001", "parties": [
   {"role": "owner", "who": "g_house_a", "known": true},
   {"role": "depositor", "who": "u_5d2k8r"},
   {"role": "store", "who": "nodeone-arkive"}],
 "covers": ["book:<volume ID>"], "from": "2026-10-12", "review_at": "2031-10-12",
 "owner_consent": null, "doc": null,
 "note": "No record of owner permission. The depositor has the same limits as a stand-in depositor"}

• Since there is no owner permission, making it public, AI training and destruction are not possible. Showing it to permitted viewers and transcribing it are possible.
• When the transcription scholar adds a translation, the rights of that translation entry is {"basis": "copyright", "holder": "<scholar ID>"}. Inside the store it follows the scope of the original.
• If the owning family writes a letter of permission, a new agreement entry, with its fingerprint in doc and what was permitted in owner_consent, replaces the old entry.

10. Mapping to international standards

Standard	Mapping	Grade
CIDOC-CRM 7.1.3	owner = P52 has current owner, holder = P50 has current keeper, transfer of ownership = E8 Acquisition, transfer of physical custody = E10 Transfer of Custody	aligned
RiC-O 1.0 (ICA)	ownership = OwnershipRelation, custody = holder relation, intellectual property rights holder (R040) = rights.holder, agreement = Rule	referenced
Spectrum 5.1	Depositor, Depositor’s requirements, Return date	referenced
PREMIS 3	rights.basis = rightsBasis (copyright, license, statute, other)	aligned
W3C ODRL 2.2	permission in the agreement = Agreement, use = Permission (03-manifest section 7)	aligned
ISO/IEC TS 27560, W3C DPV	writing a new consent entry and linking the old one with replaces	referenced
National Library of Korea oral history guidelines (2023)	restricted disclosure year = scope_after, statement of closed portions = scope per passage	referenced
National Archives of Korea NAK 8 v2.3 (2022)	17.3.4 scheduled disclosure date = scope_after.at	referenced
Korea Heritage Service OpenAPI	ccbaPoss owner = owner, ccbaAdmin administrator = holder. Names of individual owners are masked when published	referenced
Local Contexts, Mukurtu	a group’s use labels are attached only by the group	referenced

11. What we did not take from the research report

• The layer numbers “L0 to L7”. Provenance grades are written as words (decision 0005).
• An akv: (arKive) name prefix. These rules belong to the protocol (layer 0), not to a single store. If a prefix is needed, use hgp:.
• Four disclosure levels (Open, Controlled, Conditional, Closed). hgp has five scopes (00-Principles section 3). arkive’s institutional levels are read through the mapping table in 00-Principles section 3.
• Clauses in which the store attaches a notice period or a fee to withdrawal. These conflict with HGP-0003 Article 6.

12. Aligning with arkive

• The “holding place” field in arkive’s book information currently puts the owner (a family) and the physical holder (an institution) in one field. Split it: a family goes in owner, an institution in holder.
• Content such as “no deposit consent form” written in the “deposit memo” moves to doc: null and note in the agreement entry.
• Add rights to interpretive layers such as the transcription scholar’s talcho and translations. Talcho is unsettled; translations and annotations are copyright.
• This is a change to the data structure, so it needs separate approval.

13. Aligning with secretary

• For recordings, owner = depositor, so owner is not needed. Other people’s voices go in voices as now (03-manifest).
• Nothing to do. Time-limited scope (section 5) will come together with the scope screen when it is built.

14. Terms added to 05-Glossary

owner, physical holder, deposit agreement, review date, rights basis, survives separately, time-limited scope (05-Glossary section 9).

15. Open questions

1. Legal review: whether talcho and pyojeom are copyrightable works, who holds rights in a machine draft, the rights in photographs taken by a public institution of originals owned by a clan, and whether the KOGL (Korea Open Government License) AI type can be applied.
2. Consent for sensitive information: whether sensitive information in recordings, such as health or beliefs, needs separate consent (Personal Information Protection Act, Article 23). This came up in the earlier review of the National Library of Korea guidelines.
3. Generating things that resemble the original: whether to block “generating outputs that resemble the original” separately, even when AI training consent exists. The KOGL AI type blocks this.
4. Original text of a physical institution’s agreement: obtain one copy of a Korean studies institution’s deposit agreement and compare it with the fields in section 4. The survey did not find a single public original.
5. Legal guardianship and proxy signatures: 01-Permissions section 6. The National Library of Korea guidelines collect proxy signatures, the relationship, and an emergency contact.