...

A component that implements logic to receive, process and redistribute events in an event-driven architecture fashion.  It must implement some kind of logical operations beyond simple "subscribe to all updates of this signal", and "notify all subscribers that this data changed".  If it has conditions like "Notify if this AND that event happened, and if signal value A < 3", then it is an event framework component.

In some cases the implementation of event frameworks have included some of the functionality of a data-server, data-client, etc. (see Variations)

VSS

...

Connector

A typically small component that is an implementation of a data source, and a binding/translator to/from non-VSS domains:

1. It writes VSS signal data to a State Storage.
2. It consumes data from non-VSS data sources and converts it to VSS-defined signals before writing into State Storage.
   The VSS signals are defined by one/more VSS catalog(s)  (=The shared VSS standard catalog and/or additional catalogs). The non-VSS format can be any data source and typically requires some kind of definition catalog as well. Finally, a conversion-mapping information between the non-VSS and VSS data definitions would be required.
3. A feeder connector may connect to specific technologies where non-VSS data is provided.  Example: A CAN-bus VSS-feederconnector, ingests CAN signals, converts to appropriate VSS catalog signals, and write those into a State Storage.
4. While it is less common, the same feeder connector component can of course handle "written" signals as well (data is read from state storage, written to the non-VSS domain).

Synonyms: the component may also be referred to as a Bridge or Feeder in some designs.

Data Connector

The generic form of the VSS Connector that manipulates any data model. Such as personal data.

OEM Database (a.k.a. Cloud database, a.k.a. Data Lake)

...