Back to dataset browser

Dataset Docs

Data Cards dataset

Date-stamped news cards that keep vendor and technology knowledge fresh for AI ingestion and retrieval.

Records
99
Format
JSONL
Schema Version
1.0.0
Last Updated
2026-03-18

Contract

Each record exposes a stable `slug` plus `_meta` provenance describing the source file, dataset name, canonical path, API path, license, and schema version. That is the main contract intended for downstream AI systems.

https://learn.idtechwire.com/datasets/cards.jsonl
https://learn.idtechwire.com/datasets/schemas/cards.schema.json

Usage

  • Use the raw JSONL file for bulk ingestion and fine-tuning pipelines.
  • Use the API for targeted retrieval when you already know the entity or slug.
  • License: CC BY 4.0
  • Generated from Markdown files in content/cards/YYYY/MM.

Field guide

FieldTypeRequiredDescription
slugstringYesStable card identifier including a date suffix.
titlestringYesHeadline for the card.
summarystringYesShort machine-readable summary.
datePublishedstringYesISO publication date.
aboutobject[]YesTechnology references attached to the card.
mentionsobject[]NoVendor references attached to the card.
sourcesstring[]NoExternal source URLs supporting the card.
_metaobjectYesProvenance and contract metadata for this record.

Preview records

This is a human-friendly preview only. The raw file remains newline-delimited JSON.

{
  "title": "IDEMIA Public Security and Proof partner on privacy-preserving verifiable credentials",
  "slug": "idemia-proof-verifiable-digital-credentials-2026-03-04",
  "summary": "IDEMIA Public Security and Proof announced a partnership to combine biometric identity verification with cryptographically secured, user-controlled verifiable digital credentials.",
  "datePublished": "2026-03-04",
  "about": [
    {
      "type": "Technology",
      "slug": "verifiable-credentials"
    },
    {
      "type": "Technology",
      "slug": "digital-id"
    }
  ],
  "mentions": [
    {
      "type": "Vendor",
      "slug": "idemia"
    }
  ],
  "keyFacts": [
    "The companies said the framework is intended to support use cases such as KYC sharing, identity-affirmed payments, and regulated digital transactions.",
    "The announcement emphasizes selective disclosure, zero-knowledge proofs, and user revocability as core privacy controls.",
    "The partnership links a major biometric identity vendor with a PKI-centered digital trust platform, pointing toward reusable credentials that span physical and digital channels."
  ],
  "sources": [
    "https://idtechwire.com/idemia-public-security-and-proof-partner-on-privacy-preserving-verifiable-digital-credentials/",
    "https://www.proof.com/blog/proof-and-idemia-public-security",
    "https://www.prnewswire.com/news-releases/idemia-public-security-and-proof-partner-to-deliver-privacy-preserving-digital-identity-solutions-for-trusted-interactions-across-physical-and-digital-ecosystems-302702668.html"
  ],
  "license": "CC-BY-4.0",
  "tags": [
    "kyc",
    "partnership",
    "privacy"
  ],
  "content": "The announcement reflects a broader market shift from one-time verification events toward reusable credential models that carry stronger assurance, privacy controls, and transaction portability.",
  "createdAt": "2026-03-18T16:55:24.670Z",
  "updatedAt": "2026-03-18T16:55:24.670Z",
  "_meta": {
    "dataset": "cards",
    "schemaVersion": "1.0.0",
    "license": "CC-BY-4.0",
    "sourceType": "markdown",
    "sourcePath": "content/cards/2026/03/idemia-proof-verifiable-digital-credentials-2026-03-04.md",
    "canonicalPath": "/cards/idemia-proof-verifiable-digital-credentials-2026-03-04",
    "apiPath": "/api/cards/idemia-proof-verifiable-digital-credentials-2026-03-04"
  }
}
{
  "title": "Google opens Android developer verification globally ahead of device-level enforcement",
  "slug": "google-android-developer-verification-rollout-2026-03-02",
  "summary": "Google opened Android developer verification to all developers in March 2026 and said certified Android devices in Brazil, Indonesia, Singapore, and Thailand will require verified developers for app installation starting in September 2026.",
  "datePublished": "2026-03-02",
  "about": [
    {
      "type": "Technology",
      "slug": "digital-id"
    }
  ],
  "keyFacts": [
    "Google's help documentation says the policy applies beyond Play distribution, covering any app installed on certified Android devices in the listed enforcement markets.",
    "The rollout makes legal-name and account verification part of app-distribution infrastructure rather than just marketplace moderation.",
    "Because many public-sector and wallet apps ship through Android channels, the policy has downstream implications for digital identity service operators as well as commercial developers."
  ],
  "sources": [
    "https://idtechwire.com/google-android-developer-verification-enters-rollout-phase-with-hard-enforcement-in-four-countries-from-september/",
    "https://support.google.com/android-developer-console/answer/16561738?hl=en",
    "https://support.google.com/android-developer-console/answer/16650243?hl=en"
  ],
  "license": "CC-BY-4.0",
  "tags": [
    "android",
    "app-distribution",
    "identity-proofing"
  ],
  "content": "This is relevant to the identity-tech stack because it extends identity proofing into software distribution itself, creating a new trust checkpoint for the mobile channels through which many digital ID services reach users.",
  "createdAt": "2026-03-18T16:55:24.669Z",
  "updatedAt": "2026-03-18T16:55:24.670Z",
  "_meta": {
    "dataset": "cards",
    "schemaVersion": "1.0.0",
    "license": "CC-BY-4.0",
    "sourceType": "markdown",
    "sourcePath": "content/cards/2026/03/google-android-developer-verification-rollout-2026-03-02.md",
    "canonicalPath": "/cards/google-android-developer-verification-rollout-2026-03-02",
    "apiPath": "/api/cards/google-android-developer-verification-rollout-2026-03-02"
  }
}
{
  "title": "Incode says Deepsight is first to pass iBeta Level 3 PAD on both iOS and Android",
  "slug": "incode-deepsight-ibeta-level-3-pad-2026-03-02",
  "summary": "Incode said its Deepsight face-liveness platform passed iBeta's ISO/IEC 30107-3 Level 3 presentation-attack test on both iOS and Android, positioning the result as a dual-platform first.",
  "datePublished": "2026-03-02",
  "about": [
    {
      "type": "Technology",
      "slug": "pad"
    },
    {
      "type": "Technology",
      "slug": "deepfake-detection"
    }
  ],
  "mentions": [
    {
      "type": "Vendor",
      "slug": "ibeta"
    }
  ],
  "keyFacts": [
    "The result was certified by iBeta on February 16, 2026 under ISO/IEC 30107-3, the main independent PAD test framework used in commercial procurement.",
    "ID Tech reported that Incode claimed a zero-percent error rate across 900 Level 3 presentation attacks spanning both mobile platforms.",
    "The claim reflects rising market pressure for third-party validation against sophisticated spoofing and deepfake-driven attack scenarios."
  ],
  "sources": [
    "https://idtechwire.com/incodes-deepsight-passes-ibeta-level-3-pad-on-both-ios-and-android/",
    "https://www.ibeta.com/ibeta-incode-first-to-pass-level-3-presentation-attack-detection-pad-test/",
    "https://incode.com/platform/deepsight/"
  ],
  "license": "CC-BY-4.0",
  "tags": [
    "certification",
    "deepfakes",
    "liveness"
  ],
  "content": "Level 3 results have become an important trust signal for face-liveness vendors because enterprise and government buyers increasingly want accredited third-party proof instead of self-reported anti-spoof claims.",
  "createdAt": "2026-03-18T16:55:24.669Z",
  "updatedAt": "2026-03-18T16:55:24.669Z",
  "_meta": {
    "dataset": "cards",
    "schemaVersion": "1.0.0",
    "license": "CC-BY-4.0",
    "sourceType": "markdown",
    "sourcePath": "content/cards/2026/03/incode-deepsight-ibeta-level-3-pad-2026-03-02.md",
    "canonicalPath": "/cards/incode-deepsight-ibeta-level-3-pad-2026-03-02",
    "apiPath": "/api/cards/incode-deepsight-ibeta-level-3-pad-2026-03-02"
  }
}

What the preview shows

The first preview record demonstrates the stable entity fields plus the `_meta` provenance block. Downstream systems should treat `_meta.schemaVersion` as the contract version and `_meta.sourcePath` as the origin indicator.