I think we need a separate instalation of wikibase on our wiki. No need to fork wikibase. Then we can organize our tags in categories, subcategories, relations to outside data like wikidata and so on.
Not only that, but make that wikibase a sort of an API to our tags. For example, if a data consumer wants to render all places where you can get food (restaurants, fast foods, convenience stores) it would just link a category named "food places" to an icon and that would be it. No need for everyone to understand all the possible tags that our database has. Janko uto, 26. svi 2015. 16:56 Andy Mabbett <[email protected]> je napisao: > On 26 May 2015 at 13:01, Daniel Koć <daniel@koć.pl> wrote: > >> So a usecase: > >> > >> Say you want to locate all the streets and other objects named after > >> 17th century Dutch painters, worldwide. > >> > >> You could start by finding the painters from wikidata, then use the > >> Overpass API to do a regular expression search with all the resulting > >> Q-numbers. > > > Wikidata alone may be problematic, because it's independent project, > > Why would that be a problem? > > > but it > > is big database of objects and their relations, so we could have better > > classification of our objects. Maybe close cooperation or fork would suit > > our needs? > > Fork Wikidata? Why? Doesn't this community have enough to do, just mapping? > > > Wikimedia already use our data for showing maps in the articles, > > so I think it may be beneficial for both parties to have a close > > cooperation. > > That is indeed what's proposed. > > -- > Andy Mabbett > @pigsonthewing > http://pigsonthewing.org.uk > > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
