Specification · 09
Product data model
Definitions for products, packages and versions, and how their records relate across systems.
When this is useful
A product may have several packages, versions and contract-specific rights. Its records need to distinguish what is offered from what a particular customer can use.
My contribution
I define the product entities, their relationships and authoritative sources, including how versions and customer-specific terms are recorded.
A versioned market-data package defines six datasets, venue coverage, delivery, latency and history. A separate contract limits effective quote latency and depth access.
What it covers
- Product, dataset and package identifiers and source systems
- Attributes, units, coverage and permitted values
- Variants, bundles, subscriptions and their relationships
- Access rights, usage allowances and contract-specific terms
- Product versions, effective dates and historical records
The output
A product data specification with identifiers, attributes, package relationships, access terms and change rules.
For an enquiry, describe the question and the systems involved.
contact@fiftystork.com ↗