Repository navigation
feat(extensions): register OMNI vendor name - #663
Merged
Merged
Conversation
The Omni converter in apache/ossie-converters tags its custom extensions with vendor_name OMNI. Add OMNI to extensions/vendors.md and to OssieVendor so the registry and the SDK stay in sync. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
christianeu-db
approved these changes
Oct 30, 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
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
Registers
OMNIas a known vendor name. The Omni converter inapache/ossie-converters
already tags its
custom_extensionswithvendor_name: OMNI, and theconverters README lists it under Supported Vendors; this brings the registry
here into line.
extensions/vendors.md: addOMNIto the Known vendors table.python/src/ossie/models.py: addOMNItoOssieVendor, so the SDK and theregistry list the same vendors (
test_vendor_enum_matches_the_registry).Related Issues
None. Omni converter originally added in #175.
Checklist
Specification
N/A: no
core-spec/change;extensions/is a registry outside the normative spec (#617).Ontology
N/A
Converters
OMNI; no converter change needed.Validation
N/A
Documentation
N/A
Examples
N/A: no new spec constructs.
Tests
python/tests: 268 passed;validation/tests: 490 passed;generate-spec-types.py --checkclean)Compliance
🤖 Generated with Claude Code