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

INCODE Application Areas data models #144

Merged
merged 6 commits into from
Jul 9, 2024
Merged

INCODE Application Areas data models #144

merged 6 commits into from
Jul 9, 2024

Conversation

feki-rihab
Copy link
Contributor

I have added all the data models produced from the INCODE Application Areas (AA1, AA2, AA3, AA4)

Next steps:

  1. Validating these data models
  2. Generating the examples in the other formats
  3. Generating the specification and readme files.

@albertoabellagarcia
Copy link
Contributor

  1. the examples directory starts lowercase. You have it starting capital
  2. the png file is not requested
  3. Description of the data model entity has to be longer
  4. there are missing NGSI types in the description of the attributes (page 10 of contribution manual)
  5. too many required attributes, however type which is mandatory is not there
  6. If you have used a broker please include also the normalized example according to the contribution manual
    In general try to pass the testing process
    https://smartdatamodels.org/index.php/data-models-contribution-api/

@albertoabellagarcia
Copy link
Contributor

if you need support please let me know or book a support session here

examples lower case - deleted png files - added some missing examples
@feki-rihab
Copy link
Contributor Author

feki-rihab commented Jul 1, 2024

I have made some changes in the latest commits to the data models of the different Application Areas (AA1 - AA2 - AA3 - AA4)

  • the examples directory starts lowercase. You have it starting capital
  • the png file is not requested
  • Description of the data model entity has to be longer => I do not have enough information from the partners, I made my best effort to collect that data that we have now.
  • there are missing NGSI types in the description of the attributes => Following the data provided I only can provide the example.json >>> would it be possible to generate the rest automatically via the scripts in the pysmartdatamodels or a service?
  • too many required attributes, however type which is mandatory is not there >>> I added type as required
  • If you have used a broker please include also the normalized example according to the contribution manual >>> The data provided does not reflect that it was collected via a Context Broker.

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.

Please check the same errors you have in the first two models across the rest of them. And eventually try to validate first with the testing service before contributing
https://smartdatamodels.org/index.php/data-models-contribution-api/

thanks

INCODE/AA1/UWB/schema.json Show resolved Hide resolved
INCODE/AA1/sensehat/ADOPTERS.yaml Show resolved Hide resolved
INCODE/AA1/sensehat/Examples/example.json Show resolved Hide resolved
INCODE/AA1/sensehat/schema.json Show resolved Hide resolved
INCODE/AA1/sensehat/schema.json Show resolved Hide resolved
"engineStatus": 1,
"phi": "37.8745952",
"lamda": "23.921456",
"z": "87",
Copy link
Contributor

Choose a reason for hiding this comment

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

same

INCODE/AA1/telematics/Examples/example.json Show resolved Hide resolved
INCODE/AA1/telematics/schema.json Show resolved Hide resolved
@@ -0,0 +1,96 @@
{
"$schema": "http://json-schema.org/schema#",
"$schemaVersion": "0.1.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

0.0.1

INCODE/AA1/telematics/schema.json Show resolved Hide resolved
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.

I am approving the PR because I need to for fixing a problem. but the changes needs to be addressed anyway

@albertoabellagarcia albertoabellagarcia merged commit 998b521 into master Jul 9, 2024
4 checks passed
@feki-rihab
Copy link
Contributor Author

Thank you Alberto, I will check your comments and make the necessary changes that I can do. (I will still do it on this branch, so i will not delete it yet)

@feki-rihab
Copy link
Contributor Author

All the comments are resolved (in a new pull request: #146)

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.

3 participants