OPML Validator case-unfriendliness
Dave, I have a question: The spec says nothing about OPML being case-unfriendly, and the OPML Editor doesn’t treat attributes as case-sensitive 1, but the validator fails a file when the attributes “xmlurl” and “htmlurl” are used, but not the same file when “xmlUrl” and “htmlUrl” are used. Is this an oversight?
1 I say this because I have a right-click menu item that looks like this:
if dialog.ask (“What attribute do you want to modify?”, @myatt)
op.attributes.getOne (myatt, @myval)
if dialog.ask (“Enter the ” + myatt + ” for this headline:”, @myval)
op.attributes.setOne (myatt, myval)
When I use it to check “xmlurl” and “xmlUrl” they both return the same value, which indicates to me that it’s treating both strings as equivalent.