Skip to content

Added AQM datamodel #12

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

Merged
merged 8 commits into from
Aug 17, 2021
Merged

Conversation

shyam28598
Copy link
Contributor

No description provided.

Copy link
Contributor

@albertoabellagarcia albertoabellagarcia left a comment

Choose a reason for hiding this comment

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

Thank you very much for the contribution

Please attend the comments and do not hesitate to contact us for further explanation or to attend to the "Open session" on Mondays.
https://smartdatamodels.org/index.php/summary-open-session/

Thanks

"type": "string",
"description": "Property. Model:'https://schema.org/Text'. Major pollutant in the Air Quality Index (AQI)."
},
"": {
Copy link
Contributor

Choose a reason for hiding this comment

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

The name of the property?

"": {
"type": "object",
"description": "Property. ",
"properties": {}
Copy link
Contributor

Choose a reason for hiding this comment

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

Object's properties should be defined. there are approaches for generic needs. I'd mail you if necessary.

"co2": {
"type": "object",
"description": "Property. Observed value of environmental pollutant Carbon Dioxide (CO2). Value is an object containing attributes representing statistical aggregates derived from past data.",
"properties": {}
Copy link
Contributor

Choose a reason for hiding this comment

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

See first this https://smartdatamodels.org/co2
Why object?

"co": {
"type": "object",
"description": "Property. Observed value of environmental pollutant Carbon Monoxide (CO). Value is an object containing attributes representing statistical aggregates derived from past data.",
"properties": {}
Copy link
Contributor

Choose a reason for hiding this comment

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

"description": "Property. Observed value of environmental pollutant Carbon Monoxide (CO). Value is an object containing attributes representing statistical aggregates derived from past data.",
"properties": {}
},
"relativeHumidity": {
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't be this a number?
https://smartdatamodels.org/relativeHumidity

"illuminance": {
"type": "string",
"format": "uri",
"description": "Relationship. Model:'https://schema.org/URL'. Observed instantaneous ambient light intensity."
Copy link
Contributor

Choose a reason for hiding this comment

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

A uri? shouldn't be a number? https://smartdatamodels.org/illuminance

"no2": {
"type": "object",
"description": "Property. Observed value of environmental pollutant Nitrogen Dioxide (NO2). Value is an object containing attributes representing statistical aggregates derived from past data.",
"properties": {}
Copy link
Contributor

Choose a reason for hiding this comment

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

same as previous

@@ -0,0 +1,11 @@

Copy link
Contributor

Choose a reason for hiding this comment

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

it would be good to mention where the data model is used

@@ -0,0 +1,166 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

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

I have reviewed first detail by detail and then globally. My question, how could we ensure a quick and simple interoperability if we do not define what are the objects' properties? There is not a problem with defining them as objects and defining all the possible values (or extending later). But how could you prepare on the other end the reading of the values? In fact, what you are doing is creating a not documented standard (under the need for being very flexible).
Let's comment this

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hey Alberto, I have made some changes with respect to the schema.json document I believe it should have all the properties required now. If there are modifications required in the payload files please let me know I will modify them as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

With regard to the reading of the values we have a different file called the Data Descriptor in which the detailed description of each and every property is mentioned.You can check out Example 1 in this IUDX Vocabulary. This contains the detailed information about each of the properties in the data model.

@@ -0,0 +1,102 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

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

This payload is not validated by the schema.json

@shyam28598
Copy link
Contributor Author

right

Hey Alberto, I have taken a look at the incubated data model and made some changes accordingly(Please check modified-schema.json), since some properties remain as [timeseriesaggregation](https://voc.iudx.org.in/TimeSeriesAggregation

) it will contain max,min,avg and instvalue and the pollutants have been put in an array as mentioned in the incubated schema, Please get back to me if there are any more changes

Copy link
Contributor

@albertoabellagarcia albertoabellagarcia left a comment

Choose a reason for hiding this comment

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

some additional changes has been introduced in the official version

@albertoabellagarcia albertoabellagarcia merged commit f788628 into smart-data-models:master Aug 17, 2021
@albertoabellagarcia
Copy link
Contributor

reviewed before publishing

@albertoabellagarcia
Copy link
Contributor

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