So if I understand you right, you're using XML for data because it's well known, and you've created HSS because XML isn't really suitable for styling?
Presumably that means you're prioritising developer familiarity over architectural simplicity?
Presumably that means you're prioritising developer familiarity over architectural simplicity?
It also provides a very big ecosystem that AXR actually use.
XML is clear and precise and extensible, but it's not exactly known for having a simple syntax, right? So aren't you choosing XML primarily because of the ecosystem and tooling?
I consider XML proved itself as a reliable data layer. JSON is not considered because it does not even supports attributes and extensibility.
I would really appreciate if you would consider contributing some nice ideas. Come over to the mailing list :P
By choosing XML you're using a syntax with a wide ecosystem and very good tooling, but you're given up some simplicity in your design. Presumably you consider this to be a good trade-off, and I don't necessarily disagree with that choice.
My concern is that in order to compete with an existing standard, a technology either needs to be a considerably better, or trivial to substitute for the old standard. XML/HSS seems to satisfy neither criteria, clinging to familiarity on the one hand, but having a high barrier to adoption on the other.