XML schema (XSD) was and is still a great idea. Change my mind.
41
21
6
256
Replying to @rotnroll666
XSD relies on namespaces, which were added to XML too late, it mixes record-style structure definition into a markup language universe, and it led to the abominable infoset concept. I much preferred RNG or Schematron.

Apr 18, 2022 · 5:54 AM UTC

4
10
Replying to @stilkov @rotnroll666
The horrible code generation approach led people to believe concepts applicable to local method calls could be transferred to network programming, and thus gave the world the horror that was WSDL
1
1
Having to use XSD to support backwards-compatible services, or trying to build modular components, or dealing with namespace names in attribute values, it all sucked
1
3
more replies
Replying to @stilkov @rotnroll666
isn't an infoset what every data representation should have and only few are grown-up enough to actually define? i am not defending the way it came to be or how it came out. but i always liked the fact that there is such a thing that seems to have universal consensus behind it.
2
I always considered it way too abstract and explicitly disliked the idea of schema validation adding information to it. Might have been very different if XML, namespaces and schema had all been designed at the same time, forming a consistent whole
1
1
more replies
Replying to @stilkov
Valid point.
Replying to @stilkov @rotnroll666
IIRC there where DTDs first which I recall as unwieldy, cumbersome, and not expressive enough. However, XML, XSD and I get along quite happily, but I have to agree: It would have been nice if XSD would have been there right from the start.
1