okf: align timestamp as recommended and note staleness use (SPEC 4.1)#187
Open
manumishra12 wants to merge 1 commit into
Open
okf: align timestamp as recommended and note staleness use (SPEC 4.1)#187manumishra12 wants to merge 1 commit into
manumishra12 wants to merge 1 commit into
Conversation
Section 4.1 lists timestamp under Recommended, but the frontmatter example comment still labelled it Optional. Aligns the comment and adds a sentence explaining that consumers rely on timestamp to detect stale knowledge, so producers SHOULD set it whenever a concept is created or updated. Addresses GoogleCloudPlatform#97.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Section 4.1 already lists
timestampunder Recommended (in priority order), but the frontmatter example comment still labelled it# Optional last-modified time, and the field description did not explain why it matters. This aligns the two.Changes
Optional->Recommended.timestampfield description: note that consumers rely on it to detect stale knowledge, so producers SHOULD set it whenever a concept is created or updated.Wording only; no normative change beyond matching the existing "Recommended" listing.
Addresses #97.