Comment Re:URLs, URIs and URNs 101 (Score 1) 134
I've never understood why the XML conceptors and users
have always maintained the confusion.
I mean, using a URI like "http://www.foo.com/dtds/mydtd.dtd"
is very confusing. when you see something like that (I mean HTTP !!)
you are very likely to be tempted to load it.
Ok, you'll argue that the specs say : Don't do it.
But instinctively, you will. And if the specifications
are far from the instinct, my guess is that specs are crap.
It would have been better to force special URN that are NOT URL from the beginning
eg : xmlns="foo.com:mydtds:mydtd.dtd". In that case, I won't be tempted
to load it, but it is still a valid URI though.
have always maintained the confusion.
I mean, using a URI like "http://www.foo.com/dtds/mydtd.dtd"
is very confusing. when you see something like that (I mean HTTP !!)
you are very likely to be tempted to load it.
Ok, you'll argue that the specs say : Don't do it.
But instinctively, you will. And if the specifications
are far from the instinct, my guess is that specs are crap.
It would have been better to force special URN that are NOT URL from the beginning
eg : xmlns="foo.com:mydtds:mydtd.dtd". In that case, I won't be tempted
to load it, but it is still a valid URI though.
