Added the spec and IANA registry entries for embedded - #399
Merged
Conversation
glpatcern
force-pushed
the
embedded-proto
branch
2 times, most recently
from
August 14, 2026 13:48
daa3fc3 to
5622a0f
Compare
glpatcern
force-pushed
the
embedded-proto
branch
from
August 14, 2026 13:57
5622a0f to
176123d
Compare
Member
Author
|
@KrausMatthias would you have time to take a look and sketch a similar document for your GIS-related project? |
mickenordin
approved these changes
Aug 24, 2026
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
2 participants
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.
With this PR I add a document that could serve as blueprint of how to extend the OCM IANA registries when it comes to new protocols and resource types. This document is independent from the I-D Drafts and may be moved elsewhere, but for now I think it makes sense to version-control it here.
The specific case is for an
embeddedprotocol and anro-crateresource type. This follows the discussion at #180 and it has been updated to the latest OCM spec version for Discovery. The underlying concept is that anembeddedOCM Share may carry any resource that can be represented in JSON, withro-cratebeing a specific case.The text has been written with some AI assistance for the general structure.