2013-02-20 10:31:10.087222-08 by Dan Lyke 4 comments
Among the things to love about XML namespaces: I have yet to find one of those "http://..." specifiers that doesn't 404. #misuseofconvention
comments in ascending chronological order (reverse):
Here's how I try to make sense of that practice. They are only offering an identifier, not an address. They still make it look like a website address because that's a public namespace that everyone already has a place in. To be consistent, they ought to remove the http: prefix, which implies that a web server is ready to deliver a document, and just use something that doesn't promise any particular protocol, like url:.
Yep. "ns:" or something similar. "http:..." is just hogwash. Actually, not putting the schema or docs at that address is also hogwash.
Along these lines, http://blog.python.org/2013/02...ng-defusedxml-fixes-for-xml.html has a lot of o_O
Ya know, it's been so long since I've seen some of the more advanced features of XML, I'd actually forgotten about those.
JSON or standard HTTP variable encoding for the win.
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Connectivity provided by highertech.net , awesome bandwidth, well away from fault lines and other potential for natural disasters, reliable, and run by cool people.
Questions, comments, flames: contact Dan Lyke
Flutterby™ is a trademark claimed byDan Lyke for the web publications at www.flutterby.com and www.flutterby.net.