Clarify RoadEventFeedInfo update_date definition #190
Merged
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
j-d-b
added
Non-spec
mark-mockett
approved these changes
Aug 16, 2021
There was a problem hiding this comment.
@j-d-b The updated description looks good to me. Let's make sure it gets added to the v4.0 schema before release.
@mark-mockett completed. |
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.
Following issue #184, this PR updates the description of the RoadEventFeedInfo
update_dateproperty to clarify that this timestamp should reflect when the GeoJSON file representing the WZDx feed was generated.The recency of this property depends on if the producer is following a request/response model where the GeoJSON feed file is generated every time a consumer requests the feed, or if the producer is generating the file on an interval or other trigger and making that file available for consumers.
The WZDx specification does not require either method and there are currently producers doing it both ways.