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

Derivation Redefined #19

Open
cbode opened this issue Jan 23, 2017 · 0 comments
Open

Derivation Redefined #19

cbode opened this issue Jan 23, 2017 · 0 comments

Comments

@cbode
Copy link
Member

cbode commented Jan 23, 2017

I propose narrowing the definition of 'derived' to clarify its purpose.

Derived: "a datastream that is calculated from an existing datastream." This is critically important, because it means you can go back and recalculate the datastream in the future. It doesn't matter if the calculate is simple or complex or whether the calculation occurs on the logger or server-side. It only matters that the source data is recorded as a datastream.

Datastream schema has 2 fields for derived. Remove "derived" boolean, keep "derivation_description". Add new field, "derived_from_datastream_ids": [array of object ids].

Note: a derived datastream should not have any "thing_id" objects. They should be mutually exclusive. However, we are not enforcing that at this time.

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

No branches or pull requests

1 participant