Skip to content

[ISIN] Prefix data refresh: Guidelines V26 + ZZ provisional status #178

Description

@azaharizaman

Follow-up to #177 (ISIN capability, paxman/capabilities/ISIN/).

Status quo: paxman/capabilities/ISIN/rules/data/country_codes.py pins the prefix vocabulary to ANNA ISIN Guidelines V25 (Dec 2025), which is superseded by V26 (Jun 2026) — recorded in the module refresh procedure and in the rule provenance (paxman/capabilities/ISIN/rules/anna_isin_guidelines_ed2025.py:21). Provisional ZZ is excluded from SPECIAL_PREFIXES (no RA source; isolation vector ZZ0378331001 → INVALID pins this).

Ask: (1) review V26 for prefix-vocabulary changes and update SPECIAL_PREFIXES + provenance version accordingly; (2) re-check whether ZZ (or any new special prefix) gained Registration Authority attestation — if yes, add it with a per-prefix provenance comment; if no, keep excluded. Follow the refresh procedure in the data module docstring.

Acceptance sketch: data diff limited to attested changes; test_prefix_sets_present + isolation vectors updated only if membership changes; docs provenance (guide + citations) bumped to match.

Activity

  1. added
    v1.0.0v1.0.0 release
    followupFollow-up from merged PR — deferred or skipped review concern
    on Sep 30, 2026
  2. azaharizaman commented on Sep 30, 2026

    @azaharizaman
    CollaboratorAuthor

    Triage 2026-09-30: keeping open, labeled v1.0.0 + followup (follow-up to PR #177). Plain English: the ISIN country-prefix list is pinned to the Dec 2025 rulebook, which has since been superseded (Jun 2026); this refreshes the list to the new rulebook and re-checks one provisional code (ZZ). Data + docs only. No consolidation needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    followupFollow-up from merged PR — deferred or skipped review concernv1.0.0v1.0.0 release

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions