Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
54 changes: 36 additions & 18 deletions extensions/vendors.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,8 @@ Custom extensions attach platform-specific metadata to a model (see

```yaml
custom_extensions:
- vendor_name: string # Free-form string identifying the vendor
data: string # JSON string containing vendor-specific data
- vendor_name: string # Free-form string identifying the vendor
data: string # JSON string containing vendor-specific data
```

`vendor_name` is a free-form string and `data` is an opaque string that Ossie
Expand All @@ -34,22 +34,23 @@ community uses (see [`README.md`](README.md) for how these lists are used).

## Known vendors

| Vendor | Description |
|--------|-------------|
| `COMMON` | Common/standard extensions |
| `SNOWFLAKE` | Snowflake-specific attributes |
| `SALESFORCE` | Salesforce/Tableau-specific attributes |
| `DBT` | dbt-specific attributes |
| `DATABRICKS` | Databricks-specific attributes |
| `GOODDATA` | GoodData-specific attributes |
| `SEMANTIDO` | Semantido-specific attributes |
| `HONEYDEW` | Honeydew-specific attributes |
| `WISDOM` | WisdomAI-specific attributes |
| `POWER_BI` | Microsoft Power BI-specific attributes |
| `SIGMA` | Sigma Computing-specific attributes |
| `THOUGHTSPOT` | ThoughtSpot-specific attributes |
| `HEX` | Hex-specific attributes |
| `ATACCAMA` | Ataccama-specific attributes |
| Vendor | Description |
| ------------- | -------------------------------------- |
| `COMMON` | Common/standard extensions |
| `SNOWFLAKE` | Snowflake-specific attributes |
| `SALESFORCE` | Salesforce/Tableau-specific attributes |
| `DBT` | dbt-specific attributes |
| `DATABRICKS` | Databricks-specific attributes |
| `GOODDATA` | GoodData-specific attributes |
| `SEMANTIDO` | Semantido-specific attributes |
| `HONEYDEW` | Honeydew-specific attributes |
| `WISDOM` | WisdomAI-specific attributes |
| `POWER_BI` | Microsoft Power BI-specific attributes |
| `SIGMA` | Sigma Computing-specific attributes |
| `THOUGHTSPOT` | ThoughtSpot-specific attributes |
| `HEX` | Hex-specific attributes |
| `ATACCAMA` | Ataccama-specific attributes |
| `PRECISELY` | Precisely-specific attributes |

## Examples

Expand Down Expand Up @@ -98,3 +99,20 @@ community uses (see [`README.md`](README.md) for how these lists are used).
"default_schema": "gold"
}'
```

**PRECISELY Extension:**

```yaml
- vendor_name: PRECISELY
data: '{
"CDE": true,
"PII": true,
"tags": ["Confidential"],
"semanticType": "EMAIL.ADDRESS",
"updatedAt": "2026-10-29T00:00:00Z",
"scores": {
"Quality":90,
"Governance": 70
}
}'
```
Comment on lines 55 to +118

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're trying to de-emphasize specific vendor details in the top-level docs (e.g. we pulled vendor / dialect enums out of the core spec and made them free-form. Do you mind removing this new example and, in fairness, the other examples?

As far as I can tell, these examples even pre-dated the converters so may not even be valid. In general, the vendor-specific converters should be the source of truth

Loading