Type vocabulary

A concept’s type SHOULD name one of the following classes. Each maps to a public ontology term; consumers MUST tolerate unknown values by treating the concept as a generic lokf:Concept.

`type`	Class IRI (`@type`)	Aligned to
(abstract)	`lokf:Concept`	broad: `schema:CreativeWork`, `prov:Entity`
`Dataset`	`schema:Dataset`	exact: `dcat:Dataset`
`Table`	`lokf:Table`	is-a `Dataset`; close `dcat:Dataset`
`Metric`	`lokf:Metric`	close: `schema:Observation`, `skos:Concept`
`Service`	`schema:WebAPI`	close: `schema:SoftwareApplication`
`Playbook`	`lokf:Playbook`	exact: `schema:HowTo`
`Policy`	`lokf:Policy`	close: `schema:DigitalDocument`
`GlossaryTerm`	`schema:DefinedTerm`	exact: `skos:Concept`
`Reference`	`lokf:Reference`	close: `schema:CreativeWork`, `schema:WebPage`
`Document`	`lokf:Document`	close: `schema:DigitalDocument`
`Person`	`schema:Person`	exact: `foaf:Person`, `prov:Person`
`Organization`	`schema:Organization`	exact: `foaf:Organization`, `prov:Organization`

Type-specific fields

fields — a list of Field objects: name, datatype (FieldType → XSD), description, unit, is_key, constraints
distribution — dcat:Distribution

fields:
  - name: event_id
    datatype: string
    description: Globally unique event identifier.
    is_key: true

unit — schema:unitText
formula — lokf:formula
measures — lokf:measures, pointing at another Concept

unit: users
formula: COUNT(DISTINCT user_id) over trailing 7 days
measures:
  - https://acme.example/knowledge/glossary/active-user

endpoint — schema:url
http_method
documentation

endpoint: https://api.acme.example/v2/analytics
http_method: GET
documentation: https://developers.acme.example/analytics

definition — skos:definition
abbreviation — schema:alternateName

definition: A user who has performed at least one qualifying event.
abbreviation: AU