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

Define mobility message contracts #137

Open
1 of 11 tasks
tigroo opened this issue Jul 4, 2024 · 1 comment
Open
1 of 11 tasks

Define mobility message contracts #137

tigroo opened this issue Jul 4, 2024 · 1 comment
Assignees
Labels
Schema JSON schema files
Milestone

Comments

@tigroo
Copy link
Collaborator

tigroo commented Jul 4, 2024

GIVEN I decided to create a new ITS message among CAM, DENM, CPM, information or status
WHEN I use the provided JSON schema file as specification to build the message
THEN I will be able to validate the format

  • ETSI ITS messages
    • CAM
    • CPM
    • DENM
  • Orange ITS messages
    • Information
    • Status
  • remove the bad ls contract
  • validate the contracts into the GitHub workflow
  • standardize the header for all the messages (review cross the files)
  • align the version for the first packaging
@tigroo tigroo added this to the Sprint 2 milestone Jul 4, 2024
@tigroo tigroo added the documentation Improvements or additions to documentation label Jul 4, 2024
@tigroo tigroo changed the title Mobility message contracts Define mobility message contracts Jul 4, 2024
@tigroo tigroo added Schema JSON schema files and removed documentation Improvements or additions to documentation labels Sep 6, 2024
@nbuffon
Copy link
Member

nbuffon commented Sep 10, 2024

ls script is actually used in the validation workflow to list all the schemas that has to be validated
In the same workflow the validate script uses the output of ls one to validate each yielded script

@nbuffon nbuffon modified the milestones: Sprint 2, Sprint 3 Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Schema JSON schema files
Projects
Status: Ready
Development

No branches or pull requests

3 participants