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.

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

Property-change / Event-fire frequency #1213

Open
danielpeintner opened this issue Aug 9, 2021 · 2 comments
Open

Property-change / Event-fire frequency #1213

danielpeintner opened this issue Aug 9, 2021 · 2 comments
Labels
Defer to TD 2.0 Has Use Case Potential The use case can be extracted and explained Needs discussion more discussion is needed before getting to a solution

Comments

@danielpeintner
Copy link
Contributor

Coming from Scripting API, see w3c/wot-scripting-api#107

The scripting API task force is wondering whether it makes sense to provide means in a TD to indicate how frequent a given property can be updated or how frequent a event can be fired.

Note: the Generic Sensor API has also a concept w.r.t. to Sampling Frequency and Reporting Frequency.

A proposal could be to have a term (terms?) similar to safe and idempotent for actions.
@sebastiankb
Copy link
Contributor

I think we had this in the past with the term stable (or similar). Can we remember why this was removed ? Another issue that arises is that one term may not be enough. Maybe you want also express the unit like ms, h, years...

@egekorkan egekorkan added Defer to TD 2.0 Needs discussion more discussion is needed before getting to a solution labels Jun 15, 2022
@egekorkan egekorkan mentioned this issue Oct 19, 2022
Open
@lu-zero lu-zero added the Has Use Case Potential The use case can be extracted and explained label Jan 26, 2024
@lu-zero
Copy link
Contributor

lu-zero commented Jan 26, 2024

It has an impact on the time-series-related Use Cases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Defer to TD 2.0 Has Use Case Potential The use case can be extracted and explained Needs discussion more discussion is needed before getting to a solution
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lu-zero @danielpeintner @sebastiankb @egekorkan