Conversation
Incorporate Blue feedback
last minute trims
…ion into dev # Conflicts: # policy/README.md
|
Feedback solicited. I've got a couple of additional explanatory diagrams in the works. This doc is a little thin on verbiage, so please ask for clarification where you think it's needed. A prototype of this service is currently running in LA, and is part of the code-drop in CityOfLosAngeles/mds-core. |
* Add optional event_type specification to rule statuses * Add JSONSchema Draft 7 for Geography and Policy endpoints/types.
Update markdown so it renders a table properly
|
moving milestone. |
compliance/README.md
Outdated
| | Name | Type | R/O | Description | | ||
| | ------------- | ---- | --- | ----------------------------- | | ||
| | `provider_id` | UUID | O | If not provided in the JWT. | | ||
| | `end_date` | UUID | O | Take snapshot at a given time | |
There was a problem hiding this comment.
Hi, I guess the UUID type is a typo, and it's a timestamp in milliseconds as usual.
There was a problem hiding this comment.
It was indeed -- the spec has been updated.
|
|
|
Should we consider for the 1.0.0 release? |
…apshot response, tweak formatting
|
Hello @evansiroky can please you sign the OMF CLA for this commit you made in this PR? |
|
This is going to get re-written based on what we've learned in LA from the micro-mobility pilot. |
|
See the notes from the last WG call.
Realize this PR is closed but wanted to capture this year for the new re-written version. |
9 participants
Explain pull request
This API describes a Compliance service that takes as inputs Events and Telemetry (received via Agency) and measures against Policy and Geography documents to produce a measurement of policy compliance or non-compliance.
Is this a breaking change
A breaking change would require consumers or implementors of the API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint).
ProviderorAgencyWhich API(s) will this pull request impact:
Additional context
This is a branch off of the Policy PR, so that file is also included. That PR is a prerequisite.