Dear Henri,
Le 7 août 2012 à 16:04, Henri Bergius a écrit :
> Hi,
>
> Thanks for reporting these!
>
> On Tue, Aug 7, 2012 at 2:52 PM, François-Paul Servant <
f...@semanlink.net> wrote:
>> - capital of Mongolia : I don't get anything
>> (looking with firebug: everything seems OK (all GETs get 200))
>
> In JS console I see:
>
> Something went wrong while parsing the returned results!
> Object { name="InvalidValue",
> message="2010-01-01T00:00:00+02:...1/XMLSchema#gYear value"}
> vie-2.0.0.js (line 1)
sorry, I hadn't noticed this.
>
> So, I suspect DBpedia has changed their return format.
(a change in dbpedia return format? -- ins't it RDF? ;-) )
Hmm: an invalid date in dbpedia (if it is actually the case - or anything unexpected in the RDF) should not break (in particular, silently break) the result here -- please don't take it bad - just a remark of a novice user who doesn't know anything about the problems and the difficulties.
> We need to fix
> this in VIE ASAP and release a bugfix version. This is probably the
> issue with the other ones as well.
>
> Running the VIE unit tests I'm also getting errors from the IKS
> Stanbol server. Rupert, could you look at that?
(again, the opinion of a novice user who didn't think more about the difficulties): if something goes wrong in a service that you invoke, you probably should inform the end user ("Ah, it is not their VIE stuff that doesn't work, it is just a remote service that is experiencing problems. I'll try later")
>
> Stanbol connection error
> [Object { readyState=0, status=0, statusText="timeout"}, "timeout", "timeout"]
>
>> fps
>
> /Henri
>
Best,
fps