Zeotap · JSON-LD Context

Zeotap Context

JSON-LD context defining the semantic vocabulary for Zeotap from Zeotap.

2 Classes 4 Properties 4 Namespaces
View Context View on GitHub

Namespaces

schema: https://schema.org/
xsd: http://www.w3.org/2001/XMLSchema#
dcterms: http://purl.org/dc/terms/
zeotap: https://zeotap.com/schema#

Classes

ProfileRequest ProfileRecord

Properties

Property Type Container
orgId integer
regions list
search
updated_ts integer

JSON-LD Document

Raw ↑
{
  "@context": {
    "@vocab": "https://zeotap.com/schema#",
    "schema": "https://schema.org/",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "dcterms": "http://purl.org/dc/terms/",
    "zeotap": "https://zeotap.com/schema#",
    "ProfileRequest": "zeotap:ProfileRequest",
    "orgId": {
      "@id": "zeotap:orgId",
      "@type": "xsd:integer"
    },
    "regions": {
      "@id": "zeotap:regions",
      "@container": "@list"
    },
    "search": {
      "@id": "zeotap:search"
    },
    "ProfileRecord": "zeotap:ProfileRecord",
    "updated_ts": {
      "@id": "zeotap:updated_ts",
      "@type": "xsd:integer"
    }
  },
  "@type": "schema:Dataset",
  "schema:name": "Zeotap API JSON-LD context",
  "schema:description": "A JSON-LD @context for the objects Zeotap's own API contract declares: one class per component schema, one property per declared field, typed from the contract. Derived by script (derive-json-ld.py, 2026-10-28) from openapi/zeotap-openapi.yaml.",
  "dcterms:created": "2026-10-28",
  "dcterms:source": [
    "openapi/zeotap-openapi.yaml"
  ]
}