Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifying combination of instances and aggregate for branches #425

Merged
merged 1 commit into from
Mar 15, 2022

Conversation

erikbosch
Copy link
Collaborator

Theoretically a branch can have both instances and aggregate defined.
This opens up two interpretations - that aggregate concerns the union of all instances or that aggregate concern individual instances. This PR intends to clarify interpretation

Example:

Wunderbaum:
  type: branch
  aggregate: true
  instances:
    - Number[1,100]
  description: All wunderbaums in the vehicle

Wunderbaum.Color:
  datatype: string
  type: sensor
  description: Color of Wunderbaum

Wunderbaum.Fragrance:
  datatype: string
  type: sensor
  description: Fragrance of Wunderbaum

The proposed interpretation is that aggregate here means that it makes sense to update color and fragrance for individual Wunderbaums together, but nothing prevents Wunderbaum1 from being updated separately from e.g. Wunderbaum3.

Theoretically a branch can have both instances and aggregate defined.
This opens up two interpretation - that aggregate concerns the union of all instances
or that aggregate concern individual instances.
@danielwilms
Copy link
Collaborator

decision to merge 2022-03-15

@danielwilms danielwilms merged commit fca4549 into COVESA:master Mar 15, 2022
@erikbosch erikbosch deleted the erikbosch/erik_aggregate branch June 20, 2022 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants