-
Notifications
You must be signed in to change notification settings - Fork 51
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
Api 2.0.0 dev #200
Merged
Merged
Api 2.0.0 dev #200
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Rework ActionRequest and dependent classes * Rework ontology according to best practices. Best practices taken from https://www.w3.org/TR/ld-bp/ and http://mowl-power.cs.man.ac.uk/protegeowltutorial/resources/ProtegeOWLTutorialP4_v1_3.pdf * Fix Notifications properties. Add `referenceesLogisticsObject` and `eventType` to `Notification` * Add LO reference to ChangeRequest
…and access delegations
* Use verb form for data properties * Fix naming and cardinality * Rename `referencesLogisticsObject` to `hasLogisticsObject` * remove `referencesLogisticsObject` from `ChangeRequest` * change cardinality of `revokedBy` to `max 1` in `ActionRequest` --------- Co-authored-by: Daniel A. Döppner <[email protected]>
migrated data properties to new naming schema added guidelines for action requests fixed examples added recommended openapi besides minimal compliant openapi yaml fixed state diagram for action requests removed unnecessary restrictions in data classes; removed providesNotificationsEndpoint fixed symlinks
updated security sections fixed links in and to refactored security section
…sObject example B3
- Review of all API specification pages - Add postman collection - Review all examples
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merging the API 2.0.0 dev to master