XOM API for Processing XML with Java

[Diego Campo <diego.campo AT properazzi.com>]

Thanks for the reply.

Now that I'm reading it, I've found there is some jargon on the mail
I've sent, and that my points may not be clear. Sorry about that.

The url that I provide here, appears on another page (which I'm not
responsible for, but try to crawl and extract info from).

Please focus on this text:
wherefrom=web&lang=D&job=detail
Firstly the & is correctly read to &. That's ok. Then it comes as:
wherefrom=web&lang=D&job=detail
And here, as ⟨ is one of the HTML Entities, it is assuming that
&lang unclosed means the HTML Entity ⟨ , when it is not closed!
wherefrom=web〈=D&job=detail

The thing is, I don't expect it to be taken as an entity, because it's
not. Since xom has correctness as its first goal, this surprises me. 

I hope this is clear enough.

El mar, 15-01-2008 a las 15:00 -0500, Elliotte Rusty Harold escribió:
> Diego Campo wrote:
> > Hi,
> > There are two sites are producing bad detail urls.
> > 
> > This detailurl (as it appears on the serp):
> > 
> > http://www.sucasita.es/search.cgi?wherefrom=web&lang=D&job=detail&ref=CN-0072
> > 
> > is transformed to:
> > 
> > http://www.sucasita.es/search.cgi?wherefrom=web(=D&job=detail&ref=CN-0072
> > 
> > transforming the &lang to &lang (correct) and then interpreting it
> > as a non-closed entity.
> > 
> 
> You haven't provided enough details to be certain, but it very much 
> sounds like you have some badly constructed documents.
>