Travel Product & Inventory Management › Travel Product Master Data Governance

Travel Product Master Data Governance

BC-4000.60 Level 2 Travel & Hospitality 1 providers 1 API surfaces

Stewardship of product taxonomy, classifications, attribute standards, and identifier integrity across the travel product master.

Travel Product Master Data Governance (BC-4000.60) is a level-2 business capability under Travel Product & Inventory Management in the Travel & Hospitality model. The catalog holds 1 API surface(s) from 1 provider(s) that can perform some part of it. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Product Attribute Standards BC-4000.60.10

Standards for product attributes ensuring consistent semantics across systems and channels.

no catalog coverage

Product Classification & Tagging BC-4000.60.20

Classification and tagging of products against taxonomies used for search, merchandising, and reporting.

no catalog coverage

Product Master Lifecycle Status BC-4000.60.30

Master lifecycle status for products spanning sub-product types and aligning child status changes.

no catalog coverage

Product Identifier Stewardship BC-4000.60.40

Stewardship of canonical product identifiers and resolution of identifier collisions and duplicates.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Developing 1 Usable, with meaningful gaps to close
ViatorTaxonomy services1 API48.1
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Travel Product Master Data Governance. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →