Include schema type in the vendor property of the self-describing schema

Is it a bad idea to include the type of a schema in the vendor property like com.abc.contexts or com.abc.events?

The self-describing JSON schema defines its “vendor” property as “tells us who created this JSON Schema”. So by definition, the vendor property should not include the type of a schema. But any other practical disadvantage for including type/category of schema in the “vendor” property?

We are planning to have quite a few context schema and I think it is more clear to defines contexts under “com.abc.context” vendor name because we don’t need to include “_context” suffix to each context name.

I don’t see anything wrong with doing that. It’s just a naming convention, really there’s no actual difference between a path like com.acme.events and a path like com.snowplowanalytics.mobile.

As far as pipeline behaviour goes, it has 0 effect. :slight_smile:

Thank you for your reply. Got it.

1 Like