Skip to content

Determine how to handle data semantics #335

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.

Sign up for GitHub

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

Jump to bottom
Open
sdruskat opened this issue May 5, 2025 · 0 comments
Open

Determine how to handle data semantics #335

sdruskat opened this issue May 5, 2025 · 0 comments
Labels
data model Related to the hermes data model ❔ Triage Issue needs to be validated (may be unrelated/deprecated/not applicable)

Comments

@sdruskat
Copy link
Contributor

sdruskat commented May 5, 2025

Change implementation details to a two or three layered matching that determines the semantics of the given data and how to handle this. Matching is done against the schema, the data, and the configuration. This will then determine how a certain field, collection, or record needs to be handled for comparison and update or setting respectively.
@sdruskat sdruskat added ❔ Triage Issue needs to be validated (may be unrelated/deprecated/not applicable) data model Related to the hermes data model labels May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
data model Related to the hermes data model ❔ Triage Issue needs to be validated (may be unrelated/deprecated/not applicable)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sdruskat