Glossary — SOAP-2-REST by Specaria

Plain-language definitions of the terms used across the marketing material. For the operator/technical glossary, see the public knowledge base → Getting Started → Concepts.

| Term | Meaning | |---|---| | SOAP estate | The collection of SOAP web services an organization runs — often hundreds, built over many years. | | REST facade / Publish | Exposing a SOAP backend as a REST API. Consumers call REST; the platform converts to SOAP. | | SOAP facade / Consume | Presenting a SOAP interface (WSDL) in front of a backend that has migrated to REST, so legacy SOAP clients keep working. | | WSDL | The contract that describes a SOAP service — its operations and message shapes. | | XSD | The schema language that defines the data types inside SOAP messages. | | OpenAPI v3 | The industry-standard contract format for REST APIs. The platform generates one per published service. | | Full-field mapping | A mapping that covers the entire request and response tree — every element, attribute, and optional field — not just the common path. | | Deterministic mapping | A mapping generated from the contract by rules, so the same WSDL always produces the same result (no guesswork, no drift). | | Conversion preference | A tunable setting that controls how a SOAP shape becomes a REST shape (date format, casing, null handling, etc.), set platform-wide and overridable per service/operation/field. | | Traffic-driven discovery | Learning which SOAP services exist by observing live gateway-edge traffic, rather than uploading WSDLs by hand. | | Learned example | A real request/response payload captured from production traffic and attached to a service, so consumers see what actually flows. | | Connector | The integration that lets the platform discover services and ingest traffic from a specific gateway or load balancer. | | Generic-HTTP receiver | A universal "bring your own gateway" ingest path for any edge that can emit accessible HTTP traffic logs. | | Gateway edge | The load balancer or API gateway your SOAP traffic already flows through. | | Correlation ID | A unique identifier attached to a request and carried through the whole lifecycle, used to trace and search. | | Contract drift | When a backend's response no longer matches the expected contract — the platform flags it. | | SLO report | A report measuring the conversion layer against availability and latency targets. | | RBAC | Role-based access control — admin, operator, and reader roles. | | IAP / OIDC / SAML | Identity standards the platform uses to authenticate operators via your identity provider. | | VPC | Your private cloud network. The product runs inside it; your data never leaves it. | | Heartbeat | A small, numeric, PII-free signal the product sends to the Specaria platform for licensing — never your traffic or payloads. | | Capacity (discovered / converted services) | The two published dimensions used to count usage for licensing and pricing. | | GA | General Availability — the production-ready v1 release. |