Add Korean translation of AIP-1 (core protocol spec)#82
Open
minhchee wants to merge 1 commit into
Open
Conversation
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.
Korean translation of AIP-1
This PR adds
specs/AIP-1.ko.md— the complete Korean (ko) translation of the core Open Agent Bounty Protocol specification.specs/AIP-1.md(74,304 bytes, 913 lines)specs/AIP-1.ko.md(81,288 bytes, 908 lines)specs/AIP-1.ja.md(existing Japanese translation)Coverage
All 13 top-level sections and appendices A/B/C translated: agent identity (incl. §1.4 registry propagation), mission & submission specs, all four verification methods, the ELO reputation primitive, reward escrow with portable mission-completion receipts, discovery surfaces (MCP transport declaration, transport-path enumeration, structured error responses, session lifecycle contract, A2A agent-card invocation contract, client identification), OpenAPI schema,
/.well-knowndiscoverability (oabp.json, spec bundles, agent-card aliases, OAuth discovery), security considerations, and prior-art analysis.Code blocks, JSON, RFC 2119 keywords (MUST/SHOULD/MAY/MUST NOT), and type identifiers are preserved verbatim per the established translation convention.
Status
This completes the 4-spec Korean translation set (AIP-1 through AIP-4). AIP-4 (#76), AIP-2 (#78), and AIP-3 (#80) are already submitted.