About this site 한국어

Unofficial explanatory translation of the Korean AI-Ready Data (AIRD) draft standard. The Korean text prevails.

About the standard

Where it applies

Type · OverviewReading time · about 2 minAll readersAdoption decision-makers

ContentsContents
  1. Starting point by organization
  2. Discoverable — data catalogs
  3. Quality-Ready — quality evidence and acceptance
  4. Purpose-Ready — preparation for AI use purposes
  5. Outside the scope of the standard

Discoverable data applies to data catalogs; Quality-Ready data to published quality evidence and data acceptance; Purpose-Ready data to retrieval-augmented generation, machine learning and statistical analysis. The same procedure applies to public-sector and enterprise data.

Where each readiness state applies — public-sector and enterprise data alikeAI-ready data (Quality-Ready · Purpose-Ready)What it hasPublic sectorEnterpriseNowStage 1 · DiscoverableCan be foundMachine-readable catalog metadata(23 discovery-layer elements)Listing metadata of the nationaland agency portals (DCAT-AP-KR)Internal data catalogs ·data marketplace listingsPossible nowStage 2 · Quality-ReadyQuality confirmedDiagnostic report +quality tier under a guidelinePublished quality evidence ·code and key checks before joinsAcceptance terms for purchased data ·checks before pipeline releaseAfter tool release · guideline appliedStage 3 · Purpose-ReadyPrepared for a purposeOperation files per use purpose(6 purposes)RAG on legal documents · electricitydemand statistics · commercial KGInternal document search · trainingdata · fine-tuning on Q&A pairsAfter purpose criteria are registeredSource: TTA “AI-Ready Data” draft standard Parts 1–3 · public-sector examples are this site’s public data examples · aird.datahub.kr · CC BY 4.0
Where each readiness state applies. The same procedure applies to public-sector and enterprise data. The public-sector applications (legal documents, electricity demand, commercial districts) are examples this site built from real public data. Download · PNG · SVG

Starting point by organization

The stage an organization starts with, and how much it can do now, depend on its situation.

SituationStart withNow
Opening or providing data to othersStage 1 — bring listing metadata up to the discovery layer (Writing the manifest)Possible now
In-house AI or agents finding and using dataStage 1, with usability elements first (license, conditions of use, access rights) (What agents read)Possible now
Buying, procuring or delivering dataStage 2 — diagnostic report and operating guideline (Adoption brief)After the diagnostic tool is released
Processing data for RAG or machine learningStages 1 and 2 first, then stage 3After purpose criteria are registered
Ranking organizations by data qualityNot suitable. A tier must be read with the guideline applied, so tiers under different guidelines cannot be ranked against each other.—

Discoverable — data catalogs

This applies to national and agency portal listings in the public sector and to internal catalogs and marketplace listings in enterprises, and it is possible now.

Public-sector and enterprise examples

Stage 1 provides a dataset’s contents, location and conditions of use as machine-readable metadata, in the form of the 23 discovery-layer elements of the manifest. It is the stage that applies the standard to a data catalog: data values are not changed, and it can be done now without a diagnostic tool or operating guideline.

SectorApplies toWhat the standard adds
Public sectorListing metadata of the Korea Public Data Portal (data.go.kr) and agency portalsPortal listing fields can be expressed in the vocabulary of DCAT-AP-KR (Korean application profile of DCAT for data portals). The discovery layer uses this vocabulary, adds elements agents need for judgment (lifecycle status, creation method and others), and records values such as update frequency from standard value lists instead of text strings.
EnterpriseInternal data catalogs · data marketplace listings · data specifications given to partnersThe same elements and value lists apply. Title and description come from the internal catalog; identifiers use addresses based on the company domain.

After this stage, agents can find the data, and read and process its update frequency and conditions of use from the metadata. An MCP server that applies part of the draft standard’s judgments to the portal’s listing metadata (Public Data Lens) is a working example of this stage.

Quality-Ready — quality evidence and acceptance

This applies to published open-data quality in the public sector and to acceptance of purchased data in enterprises, and it is possible after the diagnostic tool is released. Data in the Quality-Ready state that meets the common readiness requirements is AI-ready data.

Public-sector and enterprise examples, and current status

Stage 2 measures the quality of data values with 16 indicators in 7 dimensions and records measured and unmeasured indicators together in the diagnostic report. The quality tier is judged with the thresholds of the operating guideline applied.

SectorApplies toWhat the standard adds
Public sectorQuality information of open data · checks before joining data from several agenciesQuality check results are published as a machine-readable diagnostic report. Indicators such as referential integrity against code tables and record-key uniqueness find problems before joins.
EnterpriseAcceptance of purchased or procured data · checks before releasing internal data pipelinesDelivery terms can state “guideline identifier, version and quality tier”. Wording for procurement and contracts is under review.

The distributable diagnostic tool that produces the report is in development. Organizations can build their own operating guideline; the guideline provided by the standard will be published when the standard is established. The schedule is in Current status and release plan.

Purpose-Ready — preparation for AI use purposes

This applies to preparation per use purpose, such as RAG on legal documents and electricity-demand statistics in the public sector, or internal document search and machine-learning data in enterprises. It is possible once purpose criteria are registered.

Public-sector and enterprise examples, and current status

Stage 3 prepares the data for each use purpose and produces operation files per purpose. The standard has six use purposes: machine learning (ML), deep learning (DL), retrieval-augmented generation (RAG), fine-tuning (FineTuning), knowledge graphs (KG) and statistical analysis (Stats).

SectorApplies toExamples on this site
Public sectorQ&A on laws and administrative documents · statistical analysis · knowledge graphsPublic data examples — legal documents × RAG · legal interpretation cases × fine-tuning · electricity demand × statistics · commercial district data × KG
EnterpriseInternal document search (RAG) · machine learning data · fine-tuning on customer-support instruction and response pairs—

A purpose tier is judged only after the purpose criteria (purpose profile) are registered. No purpose criteria are registered yet, so the purpose tier of every example is “not judged”, and the guide to preparing for a purpose will be published once purpose criteria are registered.

Outside the scope of the standard

  • Portal features: data portal features (search screens, Q&A, recommendations) are not covered. The subject of the standard is the data and a record of the data that machines can read and process.
  • Obligation: this standard is not an obligation under laws or regulations. Organizations cite it in management guidelines, project requirements or contract terms.
  • Personal data: it does not replace personal data assessment. Whether data contains personal data is recorded; the assessment is made by the privacy office.

Next step: Current status and release plan