Pith Number

pith:OFZ6NBOI

pith:2026:OFZ6NBOIVNLUGGP2IKJIF372XH

not attested not anchored not stored refs resolved

Not All Anquan Is the Same: A Terminological Proposal for Chinese Computer Science and Engineering

Xingyu Zhao

Chinese technical discourse should use 'anbao' for security and reserve 'anquan' for safety to avoid conceptual compression.

arxiv:2605.13069 v2 · 2026-05-13 · cs.CY

Open paper page JSON Open Graph Bundle Merged state What is a Pith Number?

Add to your LaTeX paper

\usepackage{pith}
\pithnumber{OFZ6NBOIVNLUGGP2IKJIF372XH}

Prints a linked badge after your title and injects PDF metadata. Compiles on arXiv. Learn more

Record completeness

1 Bitcoin timestamp

2 Internet Archive

3 Author claim open · sign in to claim

4 Citations open

5 Replications open

✓ Portable graph bundle live · download bundle · merged state

The bundle contains the canonical record plus signed events. A mirror can host it anywhere and recompute the same current state with the deterministic merge algorithm.

Claims

C1strongest claim

This is not a cosmetic translation preference, but a proposal for terminological governance in scientific cognition, engineering risk communication and assurance argumentation.

C2weakest assumption

That the current single-term usage creates persistent conceptual compression that materially affects standards interpretation, risk analysis, and the examinability of scientific arguments in Chinese technical discourse.

C3one line summary

Proposes using 'anbao' for security and reserving 'anquan' for safety in Chinese technical writing to reduce conceptual overload in safety-security discussions.

References

64 extracted · 64 resolved · 0 Pith anchors

[1] ൮Ցԛགྷ safetyࠇsecurity ൈЌ਽ႇ໓ওᇿb২ೂoνಆྟč safetyĎ p oνЌྟ čsecurityĎ p b 2.଀b২ೂಯཿoGB/T 22239uྐ༏ν ॖඪૼoЧ໓ӫః෮උਵთູྐ༏ν Ќ/ຩ઎νЌp b 3.൐Ⴈ oνಆp ᆷսsecurityb ೏ં໓ఃൌษં੐ ଆđႪ༵ཿoνЌྟp b

[2] China-Peru bilateral security liaison mechanism 2023

[3] For example, νಆྟčsafetyĎ and νЌྟčsecurityĎ

[4] For example, still cite GB/T 22239 asЧေ౰ , and then explain that this article treats its field as ྐ༏νЌ/ຩ઎νЌ

[5] If the paper is about vulnerabilities, attacks, authentication, access control or threat modeling, prefer νЌྟ

Receipt and verification

First computed	2026-05-18T03:08:58.913687Z
Builder	pith-number-builder-2026-05-17-v1
Signature	Pith Ed25519 (`pith-v1-2026-05`) · public key
Schema	pith-number/v1.0

Canonical hash

7173e685c8ab574319fa429282effab9c42fd48021f025f9a4492bb49dfeb1eb

Aliases

arxiv: 2605.13069 · arxiv_version: 2605.13069v2 · doi: 10.48550/arxiv.2605.13069 · pith_short_12: OFZ6NBOIVNLU · pith_short_16: OFZ6NBOIVNLUGGP2 · pith_short_8: OFZ6NBOI

Agent API

Resolver JSON Graph JSON Events JSON Schema Signing key

Verify this Pith Number yourself

curl -sH 'Accept: application/ld+json' https://pith.science/pith/OFZ6NBOIVNLUGGP2IKJIF372XH \
  | jq -c '.canonical_record' \
  | python3 -c "import sys,json,hashlib; b=json.dumps(json.loads(sys.stdin.read()), sort_keys=True, separators=(',',':'), ensure_ascii=False).encode(); print(hashlib.sha256(b).hexdigest())"
# expect: 7173e685c8ab574319fa429282effab9c42fd48021f025f9a4492bb49dfeb1eb

Canonical record JSON

{
  "metadata": {
    "abstract_canon_sha256": "21f644210044fab1c55c0ffeb2b63f564abc9ec7d40c7424b88159d5188f65de",
    "cross_cats_sorted": [],
    "license": "http://creativecommons.org/licenses/by/4.0/",
    "primary_cat": "cs.CY",
    "submitted_at": "2026-05-13T06:42:17Z",
    "title_canon_sha256": "00d55295d9a16d69a4fa73354a4c432a72f03e7682a85b257488916230852b88"
  },
  "schema_version": "1.0",
  "source": {
    "id": "2605.13069",
    "kind": "arxiv",
    "version": 2
  }
}