Skip to content

Change meaning of acronym OSMP to "open-simulation-model-packaging" #67

Open

Description

@clemenshabedank

Describe the problem

I think the current acronym "osi-sensor-model-packaging" is confusing since not only sensor models (but also traffic participant models) can be packaged since OSI 3.3 / OSMP 1.1.

I suggest to consistently change the name to "open-simulation-model-packaging" instead.

Activity

  1. added
    questionGeneral questions about the standard, work-flow and code.
    on Jun 2, 2021
  2. pmai commented on Jun 16, 2021

    @pmai
    Contributor

    I'd be in favor of that, however would lead to repo renaming, etc.

  3. tbleher commented on Mar 21, 2022

    @tbleher

    Stumbled across this problem today, when trying to explain what OSMP is. I like the new expansion by @clemenshabedank . Suggestion for a first step: change the description of the repo (needs an admin, I guess). This is important since it is visible also on https://github.com/OpenSimulationInterface (in fact, the text "This document specifies the ways in which sensor models are to be packaged for use in simulation environments with FMI 2.0" is there twice). I think changing this (e.g. to "in which sensor models or agent models are packaged") should be relatively uncontroversial.

    Additionally, change the name and description in https://github.com/OpenSimulationInterface/osi-sensor-model-packaging/blob/master/README.md. I can create a patch if there is rough consensus that the name should be changed.

  4. clemenshabedank commented on Apr 6, 2022

    @clemenshabedank
    ContributorAuthor

    Hey @tbleher I will make a PR today! Will set you as a reviewer then...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionGeneral questions about the standard, work-flow and code.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions