Rename remaining OSI references to Ossie - #288
Merged
Merged
Conversation
6 tasks
QMalcolm
previously approved these changes
Jul 30, 2026
QMalcolm
left a comment
Contributor
There was a problem hiding this comment.
Looks like we have a small merge conflict, but otherwise looks good to me!
17 tasks
17 tasks
flyrain
approved these changes
Aug 26, 2026
RussellSpitzer
previously approved these changes
Aug 26, 2026
jbonofre
force-pushed
the
rename-remaining-osi-to-ossie
branch
2 times, most recently
from
August 26, 2026 06:13
2971bac to
efbeb07
Compare
Completes the OSI -> Ossie rename across the repository, covering the parts that still carried the former name: - core-spec: osi-schema.json -> ossie-schema.json (including its $id and all references in examples, docs, ROADMAP, python tests, and the Java schema-loader / pom resource copy). - Python package: OSI* model classes -> Ossie* (OssieDocument, OssieDataType, OssieSemanticModel, ...) and to_osi_json/to_osi_yaml -> to_ossie_*. - Converters: package/dir renames (osi_omni -> ossie_omni, honeydew_osi -> honeydew_ossie), plus source, test, and fixture files (osi_to_msi.py, test_osi_converter_*.py, tpcds_osi.yaml, ...). - Java converters: Osi* classes -> Ossie* (files kept in sync with class names), ALL_CAPS constants -> OSSIE, and the CLI direction flag toOSI -> toOssie. The historical note "formerly known as Open Semantic Interchange (OSI)" is intentionally preserved in README, CONTRIBUTING, and docs. English words that merely contain the substring (position, composite, repository, ...) are left untouched, as is the PyPI trove classifier "License :: OSI Approved", where OSI is the Open Source Initiative. All Python and Java test suites pass and the spec examples validate against the renamed schema.
jbonofre
force-pushed
the
rename-remaining-osi-to-ossie
branch
from
August 26, 2026 06:23
efbeb07 to
2d7756f
Compare
flyrain
approved these changes
Aug 26, 2026
RussellSpitzer
approved these changes
Aug 26, 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
Completes the OSI → Ossie rename across the repository, covering the parts that still carried the former name. 135 files changed (57 file/directory renames, the rest content edits).
Rebased onto current
main(1d9ebce).Structural renames
osi-schema.json→ossie-schema.json— including its$idand every reference (examples, docs, ROADMAP, python tests, and the Java schema-loader / pom resource copy).OSI*model classes →Ossie*(OssieDocument,OssieDataType,OssieSemanticModel, …);to_osi_json/to_osi_yaml→to_ossie_*.osi_omni→ossie_omni,honeydew_osi→honeydew_ossie) plus source, test, and fixture files (osi_to_msi.py,test_osi_converter_*.py,tpcds_osi.yaml, …).Osi*classes →Ossie*(files kept in sync with class names);ALL_CAPSconstants →OSSIE(e.g.SALESFORCE_TO_OSSIE); CLI direction flagtoOSI/"toosi"→toOssie/"toossie".Former-name references outside the
ositokengithub.com/open-semantic-interchange/Ossie→github.com/apache/ossie, inconverters/orionbelt/tests/test_ossie_tpcds_baseline.pyandconverters/orionbelt/ossie_obml_mapping_analysis.md. Two also had a stale path —converters/index.mddoes not exist here, so they now point atconverters/README.md, which carries the heading the anchor targets."Open Semantic Interchange"PyPI keyword, aligning it with the other nine packages ("Apache Ossie", "Ossie", "<Vendor>").Integration with newer
maincommitsThree references in code merged since this branch was opened pointed at names this PR renames:
converters/nvidia/tests/test_converter.py— schema pathcore-spec/osi-schema.json→ossie-schema.json(from [OSSIE][NVIDIA_GSF] Add bidirectional GSF semantic model converter #247/[OSSIE][NVIDIA_GSF] Rename GSF converter directory and package to NVIDIA #299).converters/dbt/tests/test_ossie_to_msi.py— the SUM_BOOLEAN tests (fix(dbt): resolve SUM_BOOLEAN semantic model for qualified columns #292) used_osi_doc/_osi_dataset/_osi_field/_osi_metric/OSIToMSIConverter, all renamed here; left as-is they would raiseNameError.python/README.md— kept both the "fundation" → "foundation" typo fix (Fix typo in python README.md #284) and theOSI documents→Ossie documentsrename on the same line.Intentionally preserved
License :: OSI Approved :: Apache Software Licenseinconverters/gooddata/pyproject.toml— that OSI is the Open Source Initiative, and the PyPI trove classifier is invalid under any other spelling. An earlier revision of this branch had renamed it, which broke the gooddata package build.position,composite,repository,cosine,posix, …) are untouched.Known remaining item, not addressed here
docs/index.md:339anddocs/working_groups.md:22still link the formeropensemanticxSlack workspace, while the four working-group channels indocs/working_groups.mdlive inapache-ossie.slack.com— so anyone following the join link lands in the wrong workspace. Left alone because there are two competingapache-ossieinvite tokens in the tree (zt-42zw4rflt-…in README/CONTRIBUTING,zt-42i1xkgy8-…indocs/index.md:367) and substituting a dead invite would be worse than the stale link. Worth a follow-up once someone confirms which invite is live.