Looking to make a C# implementation

[Cicatriiz]

Hey, saw that I should make a discussion when wanting to add support in other languages. In truth, I've already started + decently far in, but would love to align on additional needs/spec if and as necessary.

[Cicatriiz]

@h3xxit Here's the C# implementation here: https://github.com/Cicatriiz/csharp-utcp

I would appreciate any feedback you can give. Thanks.

[h3xxit]

There are also a couple of conceptual misunderstandings. The 0.1 version of UTCP names a way to call an endpoint a "provider". In the RFC for 1.0 I proposed renaming it to "transport" as it is easier to understand. These concepts are however the same thing and should not be mixed. I would recommend you first make sure you first have all base data types identical to the python implementation (so the data classes in /shared) and the interfaces a.k.a the concepts (like the UtcpClientInterface).

If you want to match the 1.0 implementation directly, then please not that the transport (now Provider) data classes are different than the TransportInterface logic classes (actually implements the calls the data transports have the data for).

[Cicatriiz]

Apologies here as well, been busy the past couple days. Thank you for the feedback + issues on the repo! I'm looking to get those all solved in the next day or so. Official maintainer + repo transfer would be great once I get everything squared away.

Thanks again!

[Cicatriiz]

@h3xxit

Thank you again for the feedback. I've refactored the C# UTCP client to address the conceptual misunderstandings.

Here’s a summary of the fixes:

• "Provider" vs. "Transport": The outdated "provider" term has been completely removed and replaced with "transport" to align with the v1.0 RFC.
• Separation of Data and Logic: The transport data classes (e.g., HttpTransport) are now separate from the execution logic, which has been moved into dedicated *TransportLogic classes.
• Alignment with Python Implementation: All data models (Auth, Tool, Transport, etc.) have been updated to match the fields and structure of the Python reference implementation.

These changes align the C# implementation with the UTCP v1.0 specification.

Would love additional feedback as necessary! Thanks

[h3xxit]

Hey @Cicatriiz, very cool! Really excited to see that this is making a lot of progress. My goal is to finalize the official python implementation for 1.0 this or next week to have a clear guideline for all other implementations. Then we would need to align this C# one with that and then we would be ready to transfer this to the organization and make you a maintainer!

Feel free to join the discord: https://discord.gg/Y6Ycyz8nJR

And until then try and also make it compliant with the 0.2.0 security patch.

Details of 0.2.0:
"To comply with 0.2 UTCP Clients need to namespace the variables inserted into the providers. So a provider named open_ai requesting an ${API_KEY} variable, needs to look for variables called open__ai_API_KEY. This namespacing prevents manuals looking into the keys of different manuals. The rule is that the underscores of the provider are duplicated and then appended using a single underscore to the variable name.

Additionally the provider names must be checked for uniqueness and are only allowed to contain a-z A-Z 0-9 and '' characters. Any other characters should be automatically converted to '' "

[Cicatriiz]

Thanks for the update @h3xxit ! I'll keep an eye out for the update and check the discord too.

I'll try to get that 0.2.0 update out by tomorrow as well.

[h3xxit]

Very nice! Please join the discord: https://discord.gg/Y6Ycyz8nJR
I'll take a look over it!