Object types
The inventory, with their typed properties as the columns.
Read the AIP Ontology into one governed layer
The Ontology is the catalogue. Object types carry typed properties, link types are the join graph, and a Function is the only place a measure is declared. Everything below came from probing a live tenant.
The kind of credential decides whether you are in
A Foundry client secret is not a bearer token. Pasted as one it is refused on every endpoint, which reads as a bad credential when it is really the wrong kind of credential. The error names which one it is.
- A secret is refused by name. An access token or a user JWT is what works
- A scope refusal is reported separately, and names the read scope it needs
- The host has to be a tenant subdomain. A bare domain is never a tenant
Measures are read, never inferred
A metric view says which of its members is a measure. An ontology does not. It publishes typed properties and lets any caller aggregate any numeric one. Numeric is not the same as measurable.
- One live object type carries fifty-one properties, twenty of them numeric
- Among those numbers are a latitude and a longitude. Summing either means nothing
- A measure comes only from a Function whose declared output is numeric
The join graph is read one object type at a time
There is no ontology-wide list of link types. They are read from each object type in turn, and on that answer the type named is the far end of the link rather than the end that owns it.
- Reading the named type as the source would build the whole graph backwards
- One object type with no links never sinks the sweep
- A tenant carries more than one ontology. A configured name is honoured exactly
What it reads
Link types
The join graph, read per type, in the direction it actually runs.
Functions
The one place a measure is declared, and the only place one is read from.