-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The links read of course:
[1] http://de.wikipedia.org/wiki/Vorlage:Elo-Punkte [2] http://de.wikipedia.org/wiki/Vorlage:Wechselkursdaten/EZB [3] http://de.wikipedia.org/wiki/Vorlage:Infobox_Kreditinstitut/DatenDE [4] http://de.wikipedia.org/wiki/Vorlage:Infobox_Kreditinstitut/DatenAT [5] http://de.wikipedia.org/wiki/Vorlage:Infobox_Kreditinstitut/DatenCH [6] http://de.wikipedia.org/wiki/Vorlage:Infobox_Kreditinstitut/DatenDE/Quelle [7] http://de.wikipedia.org/wiki/Vorlage:ITTF-Weltranglistendaten (there are examples on enwiki and others too...) [8] http://wikidata-test-repo.wikimedia.de/wiki/Q356 (sorry for that) On 31.12.2012 14:51, Dr. Trigon wrote: > Hello all! > > Sorry for my ignorance, if this is common knowledge: What about > lists? I know they are not very popular (or completely unsupported) > but my bot maintains several list like player rankings, currency > exchange rates or similar for infoboxes, see e.g. [1]-[7]. The bot > uses external sources (e.g. an URL) an retrieves data (e.g. a list > of player rankings) and syncronizes/updates the data in the wiki. > > Now as I can see the idea would be to have an item for each player > and then a property "ranking" containing the value. But that would > mean we have to split up data given in a list and spread it over > thousands of items (update all of them) in order to use a query to > re-collect them into a list and deliver it to the infobox as > before. Furthermore would it cause a huge effort setting up the > configuration for the bot since we would have to connect every (of > the 1000+ players) with the data from the external list needing an > own bot configuration. In case somethings changes on the external > site we would have to update all those configurations. > > As I see an item containing a list would be possible. But at the > moment every list entry or item would need a new property to be > created and filled with one or more claims. While this would be > technical feasible it seams strange to create thousands of > properties just for one single usage in one item. > > On the other hand it it would be possible to have > claims/statements that contain not only a value but a key-value > pair, then somthing like sketched in [8] (p32) could be easily done > with a simple configuration on the according talk page. > > So I hope we can find a solution here, since this would help to > have the most recent data on wikidata with minimal effort. > > Thanks and greetings DrTrigon > > [1] http://de.wikipedia.org/wiki/Vorlage:Elo-Punkte [2] > http://de.wikipedia.org/wiki/Vorlage:Wechselkursdaten/EZB [3] > http://de.wikipedia.org/wiki/Vorlage:Infobox > Kreditinstitut/DatenDE [4] > http://de.wikipedia.org/wiki/Vorlage:Infobox > Kreditinstitut/DatenAT [5] > http://de.wikipedia.org/wiki/Vorlage:Infobox > Kreditinstitut/DatenCH [6] > http://de.wikipedia.org/wiki/Vorlage:Infobox > Kreditinstitut/DatenDE/Quelle [7] > http://de.wikipedia.org/wiki/Vorlage:ITTF-Weltranglistendaten > (there are examples on enwiki and others too...) > > [8] http://wikidata-test-repo.wikimedia.de/wiki/Q356 > > > _______________________________________________ Wikidata-l mailing > list [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikidata-l > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDhq7cACgkQAXWvBxzBrDC47wCgxm7CxDwf8K+PQZK8jGGg1jk/ nyIAnRcUAniXcx05E9VdQTturnJcyD4g =NWtP -----END PGP SIGNATURE----- _______________________________________________ Wikidata-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-l
