[07:21:18] is there a way to get a list of sitelinks in spreadsheet format (or copyable to such) for a certain item? [09:33:38] Lydia_WMDE, poke [09:34:12] is there a plan to use tagging for wikidata? [09:34:26] e.g. property "Tag" [09:35:04] hm? [09:35:38] sjoerddebruin, this would be a good replacement for the current "category" system - you simply add a generic "tag" property, allowing classification [09:36:49] this makes it possible to easily do a tag merge via query language [09:36:52] (sparql) [13:15:25] hello! [13:15:25] I'm working on a document versioning system and I was having a few questions on how Wikidata handles the thing, if any one can answer those or point to good readings, that would be awesome :) [13:15:25] - how does Wikidata stores entities versions? is it storing patches or a full JSON representation of the entity at every update? [13:15:25] - what happens when you add a statement: does the JS client just sends the current statement value, a patch, or a full updated version of the document? [13:15:25] - if using a patch system, which one? a standard one? [13:15:25] thanks in advance for any clue on those :) [15:05:17] zorglub27: still around? [15:05:57] Questions like these are perfect for the mailing list. [15:06:10] Thiemo_WMDE: ok, thanks! [15:06:26] Quick answers: [15:06:48] 1. Wikidata uses the revision system from MediaWiki, which stores the full JSON blob each time. [15:07:17] 2. Neither nor. The JS client does tiny API calls. [15:07:28] 3. What do you mean with "patch system"? [15:11:50] Thiemo_WMDE: on the 3/, I'm having a look at http://jsonpatch.com , a standard (RFC 6902 http://tools.ietf.org/html/rfc6902 ) to format document patches, but there are other patch systems like the one used in git and I guess many others. But if you are storing the full JSON document everytimes those are irrelevant I guess