Data extracted from Wikivoyage, the free travel guide at http://wikivoyage.org. Leverage Wikivoyage listings on your smartphone, or in your own mashups.
People will be more willing to reuse our data if it is guaranteed valid.
For instance, a malformed latitude makes my GPS app refuse the whole file.
And unfortunately there are always some malformed latitude, and there will always be some in the wikitext.
I think we should prevent invalid data from being used in the output format.
How do you think that could be implemented?
My current idea: After generating the list of WikivoyagePOI objects, generate validationreport, then using the existing validators filter out broken strings from the list of WikivoyagePOI objects, and give that to the other output classes.
People will be more willing to reuse our data if it is guaranteed valid.
For instance, a malformed latitude makes my GPS app refuse the whole file. And unfortunately there are always some malformed latitude, and there will always be some in the wikitext.
I think we should prevent invalid data from being used in the output format.
How do you think that could be implemented? My current idea: After generating the list of WikivoyagePOI objects, generate validationreport, then using the existing validators filter out broken strings from the list of WikivoyagePOI objects, and give that to the other output classes.