Integrations

A municipality does not model everything itself. Much of what it needs is already standardised: XÖV standards for German public administration, Smart Data Models for the common smart-city entities. Model Forge imports from both catalogues, so a Tenant starts from a published model instead of a blank page.

An import is a normal write. The catalogue supplies the document; Model Forge mints the URN, splits the members into Elements, records the references and stores the result. From that point the artifact behaves like any other — it is versioned, it can be referenced, and a Mapping can read from it.

Catalogue	Page	What it gives
XRepository (XÖV)	XRepository Integration	XSD standards of German public administration. Search the catalogue, convert an XSD to JSON Schema Elements, or store the raw XSD
Smart Data Models	Smart Data Models Integration	JSON Schemas for the common smart-city entities, addressed by a (subject, dataModel) pair

Both are adapters behind a port of the runtime, and both are reached through the facade — searchXRepository, importFromXRepository and importFromSmartDataModels. A host decides which of them it offers to a user; see API Reference.

Neither catalogue is reachable without the network. A fetch goes through the SSRF guard, which rejects a host that resolves to a non-public address. Only XRepository has a configurable endpoint; the Smart Data Models schemas come from a fixed public GitHub location. See Configuration.