A-spec

A-SPEC - Proposed Changes for Feedback

A-SPEC Proposed Changes

A-SPEC is regularly updated to meet the A-SPEC Community's changing needs. Changes may be driven by new technology, emerging Community expectations, suggestions from the Community, or research undertaken by GISSA.

No changes are introduced into the A-SPEC specifications without full consultation with the Community — members are contacted directly for comment on anything proposed.

Before any changes go live, we like to share what's being proposed here. Below is a summary of what's under consideration for the next A-SPEC release, across all specifications.

Have thoughts? Get in touch via our Contact form — we'd love to hear them.

Last updated: 8 July 2026

Changes Under Consideration

Topic Proposed Change for New Release (to be confirmed) Rationale Status
Codelists

Three (3) changes:

  1. Remove all Codelists from specifications
  2. Create an HTML link for each Codelist that leads the user to the live Codelist Master
  3. Provide a link from the Codelist master to the Code Dashboard in the event that a new code is required, so the user can create and follow the criteria for codes
  • Simplify the process for maintaining currency of codes
  • Provide users with access to a "live" list
  • Encourage the user community to take on creation of codes, when required
Draft — not yet open for comment
All Specifications

Two (2) changes:

  1. Reviewed and checked for inconsistencies and harmonisation
  2. Incorporate feedback from the user community
  • Catch inconsistencies introduced as individual specifications evolve independently
  • Ensure changes reflect what the community has actually asked for
  • Keep terminology and structure aligned across all specifications, so switching between specs feels consistent
Draft — not yet open for comment
X-Spec

Initial release of X-Spec for comment and adoption

  • Developed in response to a member request to include a new asset class
  • Extends A-SPEC coverage to supplementary asset classes that do not naturally "fit" within the existing B/D/O/R/S/T/W specifications
  • Released for comment first, so the Community can review and provide feedback before formal adoption into the A-SPEC suite
  • Ensures X-Spec is developed collaboratively with the same consultation process applied to changes in existing specifications
Draft — not yet open for comment

 

 

 

 

 

 

 

 

 

 

 

The changes will be summarised according to what has been :-

  1. Removed
  2. Added, or
  3. Modified

Importnat Note: In accordance with the agreement of the A-SPEC Community typically to allow a 6 month phase in period all data will be expected to comply with the new versions from the published date of the specifications unless otherwise notified.