Skip to content

State and intended role of this repository #33

@goekay

Description

@goekay

Hi everyone,

I just happily stumbled upon this repository and was very excited to see this effort. First of all, thanks for the work on this project.

I had two questions regarding the current state and intended positioning of this OpenAPI specification project:

  1. What is the current maturity/state of the specification? Is feature parity with the official OCPI specification achieved, or should this repository still be considered work-in-progress / experimental?

  2. What is the intended relationship to the official OCPI specification? Is this repository considered an unofficial community effort, a companion project, or something that is expected to become more formally aligned with the official OCPI ecosystem over time? Is this the long-awaited and heavily requested official spec finally?

We are currently evaluating the repository for potential production usage and would like to better understand its current status and long-term direction.

Thanks!

P.S: github-pages at https://ocpi.github.io/openapi-specification/ are not working.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions