-
Notifications
You must be signed in to change notification settings - Fork 0
Standards Map
Nick Rygiel edited this page Jul 3, 2026
·
1 revision
pwcli-core uses standards maturity to prevent hype-driven architecture.
| Reference | Maturity | Use |
|---|---|---|
| OpenAPI | stable / formal standard | HTTP API contracts. |
| JSON Schema | stable / formal standard | Structured payload validation. |
| OAI-PMH | stable / formal standard | Archive metadata harvesting. |
| Dublin Core | stable / formal standard | Minimal descriptive metadata. |
| MARC 21 | stable / formal standard | Bibliographic cataloging target. |
| IIIF | stable / formal standard | Compound digital object presentation. |
| W3C PROV-O | stable / formal standard | Provenance graph model. |
| RDF / JSON-LD | stable / formal standard | Linked data. |
| DCAT | stable / formal standard | Dataset catalogs. |
| SPDX | stable / formal standard | License, BOM, and system metadata. |
| schema.org | widely adopted vocabulary | Public web structured data. |
| MCP | open agent protocol | Agent tools, resources, and prompts. |
| A2A | open agent protocol | Agent cards, task lifecycle, artifacts. |
| RO-Crate | community standard | Research object packaging. |
| llms.txt | emerging convention | LLM-readable website map. |
| AGENTS.md | emerging convention | Repository instructions for coding agents. |
| context-pack/ | pattern only | Local Markdown operating context. |
| WebMCP | experimental / watch layer | Browser-agent tool exposure. |
Rule: if a standard fits, reference it. If it does not fit, create a local schema that still preserves source identifiers, rights, provenance, confidence, review state, and fallback routes.