On 12.02.2015 07:17, Gerard Meijssen wrote:
Hoi, It is pointless to include automated descriptions when they are then saved in a fixed form. The point of automated descriptions is exactly that they change as new statements are made. This is one reason why they are superior to manual descriptions. The other is that when one label is added in a language, it immediately affects all items that include the associated item.
Sure, I am all for having automated descriptions that are updated regularly. I think we are in agreement here.
When the argument is that external users need the best descriptions available at whatever time, it is best to have the automated descriptions separate. We have enough experience of the disruption caused by failing dumps. Given that there is a need for descriptions for off line usage, it makes sense to consider caching such a file and removing the content that is changed and have it regenerated in a batch process. When a description is needed it can always be generated there and then. These can be used interactively as well.
You are suggesting to create a file that caches the current autodescriptions and that is generated in a batch process? Seems like a good idea to me. The easiest solution for dump consumers would be if this file would be integrated directly into the dump files rather than having a separate download that needs to be merged with the dump locally (as I said before, splitting the current dump into many separate files may have its own merits; but this is another discussion).
Cheers
Markus