Draft: add fog patch fragments and semantic seed#32
Merged
Conversation
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
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.
Summary
This PR is the follow-on integration tranche after the merged FogVault / FogCompute schema scaffold PR.
It adds:
openapi.fog.patch.yamlasyncapi.fog.patch.yamldocs/contract-additions/2026-04-fog-contract-index.mdsemantic/fog-vocabulary.jsonldWhy
The initial fog schema PR established object shapes. This PR makes those additions more discoverable and gives them dedicated additive API/event patch fragments plus a seed semantic vocabulary.
Included in this PR
API / event patch fragments
Discoverability
docs/contract-additions/Semantic seed
Intentionally deferred
This PR does not yet patch the existing root catalog files directly:
README.mdschemas/README.mdexamples/README.mdsemantic/README.mdThose files require direct in-place edits. This PR keeps the follow-on integration additive and non-destructive while preserving discoverability and machine-mergeable patch surfaces.
Follow-up
A subsequent cleanup PR should:
schemas/README.mdexamples/README.md