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

Schema allow for a data campaign to be staked out #4

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kilojoules
Copy link
Contributor

No description provided.

@@ -10,6 +10,7 @@ By "defined semantics" we mean that it is expressed in a particular [schema lang
Schema allow you to:

* de-risk projects involving data,
* Scope a data campaign. This is how to be strategic about what data you capture
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no corresponding example for this, so we can either add one or not include this.

Probably the best thing to do to keep things succinct is to modify the prior line to "scope and de-risk projects involving data"

Copy link
Contributor Author

@kilojoules kilojoules Dec 16, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps there should be an example about scoping a data campaign. Something like this:

It is important for all parties involved in data generation and transformation to have transparent expectations around what data to collect. Schemas allow for boxes to be checked when collecting data. Implementing standard schemas allow for such transparency across the lifespan of a data campaign. Strategic implementation of schema can add enormous value to the current workflow of many processes in the wind energy sector. For example, it would be very useful for an anemometer's orientation to be recorded by the installation technician, in a way that this metadata is accessible to data analysts.

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.

2 participants