pmelon
muesliIt's only called JSON if it comes from the Jéson region of France. Otherwise it’s just sparkling structured data.
Wolf480pl@fribbledom
can't be plain and sparkling a the same time I think?
"sparkling structured data" maybe?
Haha, I like that even better. Edited.
viq@fribbledom @wolf480pl yaml with punctuation ;P
Jules 🍺
Daniel Bohrer@fribbledom … without superfluous commas, null values, or comments, because the PDO forbids their use as ingredients
Here and Today Gadgets@fribbledom, excellent point! Chris Rohe from hereandtodaygadgets.com
Sean Purcell (he/him)@fribbledom Everywhere else it's known as a sweet potato, but in data science its known as YAML
Bankbintje@fribbledom I heard some french-speakers pronounce it as 'gison' (sounds like french 'bison' but with the second g of garage)
Robert Casties@fribbledom Clearly we need an Appellation d'Origine Controllée for JSON. Stop those cheap knockoffs!
Stefan Baur 8 * 💉@fribbledom "It's only called Goth if it's from the Gotha region of Thuringia, Germany. Otherwise it's just a generic angsty teen, dressed in black."
Die Stimme der Vernunft
aburka 🫣@fribbledom "structured" is a bit of a stretch tbh
🐜@fribbledom Not JASON?
Andy@fribbledom Funny story: We had a problem with a web service involving JSON responses and the responsible person was named Jason. So we made fun by constructing sentences which worked both with JSON the data format and Jason the person.
�@fribbledom its only called sql when it portrays events in the same fictional universe as an earlier work. whaat?
Alex Gordienko@fribbledom nerd entered the room: it’s actually semi-structured data. Nerd left the room
rk: it’s hyphen-minus actually
gunstick@fribbledom oh, that's what SSD stands for!
Never understood why it's called "disk" as there is no disk shaped thing anywhere.
Never understood why it's called "disk" as there is no disk shaped thing anywhere.
Xeniac@fribbledom I was raised with XML, so I would call it slightly structured data. 😉
Alexandre DUPUY, aka Sillynius@xeniac @fribbledom I totally understand, as even the 32-year-old me has studied and used XML before 2020.
But :
- tags have a name as JSON properties
- attributes could be rendered as "@someAttribute" keys, still not standard, yep...
- JSON schema can be a thing, and there was attempts, not as standard as XML schemas...
- yeah, no namespaced stuff by default
=> JSON may totally be used as an XML, less verbose, more customizable, but in a non-standard way
Always the freedom vs safety debate, and the minimal weight of a piece of information problem. Real world is hard !
@adupuy Thank you for this verbose reply. I agree with you. Everything has it's pros and cons.
IMHO are these missing namespaces an argument pro JSON.... er... Sparkly markup language.😂
I only miss an accepted schema standard.
IMHO are these missing namespaces an argument pro JSON.... er... Sparkly markup language.😂
I only miss an accepted schema standard.