--
You received this message because you are subscribed to the Google Groups "OpenRefine Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrefine-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openrefine-dev/2fa0ff75-9604-1bd5-c1a6-3c999c9f2c7a%40antonin.delpeuch.eu.
Hi Antoine,
Thanks for the reminder. Yes I can reproduce your issue: this must be linked to the new format for Wikibase schemas or manifests.
I think that is called "forward compatibility" (unless it is the other way around?) and we have not been enforcing that so far. It is harder to enforce than backwards compatibility.
We can think about how to support that better, but I think it should not be a blocker for 3.6.0.
Best,
Antonin
--
You received this message because you are subscribed to the Google Groups "OpenRefine Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrefine-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openrefine-dev/f5bc4259-fe48-44ea-81ac-92519755137bn%40googlegroups.com.
Hi Antonin,
> I think that is called "forward compatibility" (unless it is the other way around?)
Hum. From what I understand, being able to open a v3.5 file in v3.6 is forward compatibility, and that is expected of most softwares, and we do it.
https://en.wikipedia.org/wiki/Backward_compatibility
> and we have not been enforcing that so far.
I've never seen here a strong commitement to backward compatibility, nor do I think a lot of users would need it, unless they must use an extension that is not working with the latest release.
> It is harder to enforce than backwards compatibility.