Re: Was there any other reason to start some properties with @ than to make it harder to generate the JSON?!?

C# has the ability to define the name of a property when it is serialised to json. Your json serialiser should have docs on it.

Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Oscar del Olmo <oscardelolmo@gmail.com>
Sent: Saturday, March 2, 2024 4:20:55 PM
To: Jan Krynicky <jan.krynicky@linksoft.cz>
Cc: public-schemaorg@w3.org <public-schemaorg@w3.org>
Subject: Re: Was there any other reason to start some properties with @ than to make it harder to generate the JSON?!?

Jan, this is NOT the language nor tone you should be using within this group (or any other professional setting). You can provide formal, professional documentation on this C# limitation for the steering group to take into consideration, even make a request of the specific change you might propose, with clear examples of the issue you are trying to address, and receive feedback.

I invite you to follow the basic etiquette rules you would use in any formal setting to address the group to avoid being excluded from this community, whose intention is the constructive discussion.

Regards.

O.

On Fri, Mar 1, 2024 at 8:49 PM Jan Krynicky <jan.krynicky@linksoft.cz<mailto:jan.krynicky@linksoft.cz>> wrote:
The subject says it all.

This "thing" is insanely overcomplicated and overdesigned as it is, but whose bright idea was it to invent the "@type" and "@content"?!?

For crying out loud, you supposedly chose JSON so that people could build the structure in some other language and then serialize the object into JSON and include it on a page or something and then you invent this?

HOW AM I SUPPOSED TO HAVE A PROPERTY NAMED @type IN C#?

Yes, I know I can first generate the JSON with sane, doable property names and then search and replace to get your insane, idiotic "@type".

Jenda