Restructuring/re-organisation of dotnet libraries

[thompson-tomo]

I would like to propose that asyncapi adopts standards for the naming of dotnet projects so that it is clear hierarchy and fosters greater adoption. This would be similar to what Open Telemetry does. This way it can also become easier to adopt new versions of the schema.

Proposal is as follows:

• New repo "sdk-dotnet" which produces a nuget package AsyncAPI.Schema which contains the schema classes & is versioned according to the schema version. Stage 2 is described in Move schema definition to yaml #1141
• Saunter package is renamed to AsyncAPI.Saunter and depends on AsyncAPI.Schema

The Lego group library focuses on serialisation & deserialisation and depends on AsyncAPI.Schema

[derberg]

Not sure it is a good place for such discussion 🤔 at the moment in AsyncAPI org we just have saunter so maybe better ask your question in an issue there?

I'll ping codeowners of saunter anyway, so they are aware - although not sure if they're looking at GH notifications from discussions

@m-wild @VisualBean @yurvon-screamo

From my perspective, I agree that we rename and do whatever AsyncAPI-dotnet community think is the best.

yeah, but I really think better if you ask in https://github.com/asyncapi/saunter/issues

[yurvon-screamo]

Hi, yes, let's open the issue in the repository and we are start planning these works

[thompson-tomo]

The renaming & namespacing has been created as asyncapi/saunter#192

[derberg]

Closing as relevant discussion under Saunter repo was opened