Internationalization and Localization
Use this skill when APIs serve multiple locales/regions.
1. Split concerns
| Concern | Approach |
|---|---|
| Message language | Accept-Language → localized detail/UI strings |
| Data timestamps | Store/transmit UTC RFC 3339; client displays |
| Business rules (tax, catalog) | Explicit country / region param — not only language |
2. Guidance
- Do not overload
Accept-Languagefor currency/tax jurisdiction. - Keep machine-stable
typeURIs in problem+json; localizedetail/titleif needed. - Document default locale when header absent.
3. Quick checklist
- Accept-Language honored for user-facing text.
- Timestamps UTC on the wire.
- Country/region explicit for business logic.
- Defaults documented.
See reference.md and examples.md.