I'm currently being bedeviled by some interesting XML to parse. To wit:
Ok, you can parse this, but why would you want to? Shouldn't this be:
Or even:
It's like they were being paid by the character...
<myObject>
<this value=fred>
</this>
<that value=barney>
</that>
</myObject>
Ok, you can parse this, but why would you want to? Shouldn't this be:
<myObject this=fred that=barney>
</myObject>
Or even:
<myObject this=fred that=barney />
It's like they were being paid by the character...
XML tricks
Date: 2015-10-30 12:57 am (UTC)Fred
Barney
My thought is that it's generated by a program that works well enough to accurately assemble XML that does what it's supposed to do, and once it reached that point there was no interest in optimizing it further.
Re: XML tricks
Date: 2015-10-30 04:24 am (UTC)Re: XML tricks
Date: 2015-10-30 04:26 am (UTC)no subject
Date: 2015-10-30 01:52 am (UTC)<myObject>
<property name="this" value="fred" />
<property name="that" value="barney" />
</myObject>
Did I mention that I don't like XML very much?
no subject
Date: 2015-10-30 12:26 pm (UTC)I've seen too many complicated XML schemas to have an opinion without detailed information, which I understand you can't give out here.
no subject
Date: 2015-10-30 08:25 pm (UTC)Which explains why, when I had that company moved to Pittsburgh out from under me, my new boss (who at one time had been my boss at the old place; pretty much the whole development team moved en masse across the Kennedy to avoid Pittsburgh), I found that I was the guy in charge of our XML schema, and the code to validate against it...