Re: [Connotea-code-devel] XML error

[Martin F. <ma...@ne...>]

It's really bizarre, the database literally contains that data. It's not 
an encoding issue (or perhaps you could say it's a lack of escaping).

It's true that XML can't display certain characters like 1 and 2 as pure 
legal fiction of the specification, and it does get annoying sometimes 
when someone else introduces those characters because it always seems 
like such a completely irrelevant note in the spec....

For now I've just stripped them out because I can't believe the author 
meant to have them in there.

If you're getting 503's in the last couple hours it may be because I'm 
restarting the production service unusually often. If you're talking 
about a longer time span, it could be because of our bot throttling.

You should never be getting 503's in your browser. If you do please tell 
us the browser type and version. If you are using an API such as Java 
you may be running afoul of our freshly minted bot throttling rules:
http://www.connotea.org/wiki/Throttling
Please let us know if you think our rules are too harsh.

Martin

Benjamin Good wrote:
> http://www.connotea.org/data/?q=vegf&num=100 
> <http://www.connotea.org/data/?q=vegf&num=100>
> 
> produces an xml parsing error:
> 
> error on line 4595 at column 41556: xmlParseCharRef: invalid xmlChar value 1
> 
> My SAX parser dies with the message:
> Character reference "&#1" is an invalid XML character
> 
> --
> 
> I'm also getting accustomed to frequent 503 errors.  Anything I should 
> be doing to minimize this result ?
> 
> thanks
> -Ben(G)