0014 Public name file and relation network rule table

Decision by the head of Nodeone: “Publish a public address that gives the meaning of the hgp fields” and “Put the 06 rule table at the same address.”

This replaces the temporary name urn:x-hgp:fixity in 0009. The rest of 0009 (volume fingerprints via metadata and seeAlso) stays as it is.

What

1. Addresses: description https://hgp.hahoe.io/ns/, name file https://hgp.hahoe.io/ns/v1.jsonld (JSON-LD 1.1), field base https://hgp.hahoe.io/ns#, rule table https://hgp.hahoe.io/ns/relations-v1.json, fixity bundle profile https://hgp.hahoe.io/ns/#fixity-v1. New document: 08-Name file.
2. Versions: the version number is part of the address. A version once published is never changed. v1 holds only the fingerprint fields and the relation network ledger fields. The 03-manifest fields come in v2, after 03 is approved.
3. IIIF: hgp:sha256 may be attached to canvases (with the hgp address placed before IIIF in @context). hgp:root is not attached to the manifest.
4. Rule table: a canonical version is published, based on arkive’s proposal. Violations are of two kinds: error (must not enter the ledger) and review (for a person to look at). A claim made by a machine cannot be confirmed from the start (error).
5. Roles in an event use fixed English values: visitor, host, sender, recipient, companion. Old Korean values are still read until they are migrated (review). “준 이” (giver) is merged into sender, and “받은 이(물건)” (receiver, of an object) into recipient (the event type already tells them apart).
6. Kinship relations use the terms of address exactly as in the source (족질 jokjil, clan nephew; 족숙 joksuk, clan uncle; 외숙 oesuk, maternal uncle). They are not closed into a list.
7. The shape is JSON. It is not published as SHACL for now.

Documents updated: 08-Name file (new), 02-Fingerprint section 9 (v0.3), 06-Relation network sections 4.1, 5 and 14 (v0.3), 03-manifest section 12, 05-Glossary.

Why

• When arkive tested with the official IIIF validator, with a context address present, hgp:sha256 on canvases passed and hgp:root on the manifest was rejected (issue #1). We follow that result.
• “Standards outside” (decision 0002) only works if other institutions’ programs have an address where they can look up what the fields mean. hgp.hahoe.io is open without login.
• hgp’s rule: field names are short English words, values come from standard vocabularies. The English site and outside institutions read the same values.
• Korean kinship terms number in the dozens and their meanings are subtle. Closing them into a list would lose the source text.

Other options

Option	Why not chosen
One address without a version number, edited over time	The meaning would change silently for programs already reading this address
Include the 03 fields in v1 too	03 is still a draft. A version once published cannot be changed
Keep role names in Korean as they are	Goes against the rule that values come from standard vocabularies, and is hard for the English site and outside institutions to read
Go straight to SHACL	arkive’s validator runs on JSON. It is written so it can be moved later
@base: urn:uuid: in the name file	Testing with a processor showed that relative address resolution does not work for urn: addresses. Instead, urn:uuid: is prefixed at export

Where it has effect

• arkive: put the address in the hgp_context setting and run the validator again. Rename the fixity bundle profile to the new name. Make its rule table proposal a copy of the canonical version. Migrate the 29 lines of role names in the old-document ledger to English values (arkive to-do).
• secretary: nothing to do for now. Uses the same address when publishing recordings as IIIF.
• server: nothing to do. hgp.hahoe.io is open without login, and the headers (application/ld+json, Access-Control-Allow-Origin: *) are set by configuration inside the hgp site.

Cost

0 won.