Strategy/Wikimedia movement/2017/Sources/Japanese Wikidata Facebook Messenger Interview
Information
[edit]What group or community is this source coming from?
| name of group | Japanese Wikidata Facebook Messenger Interview |
| virtual location (page-link) or physical location (city/state/country) | offwiki |
| Location type (e.g. local wiki, Facebook, in-person discussion, telephone conference) | Facebook Messenger |
| # of participants in this discussion (a rough count) | 1 |
- By asking Code for Japan Summit (civic-tech conference) participants what you feel about Wikidata on Facebook Messenger.The interview is done via Facebook Messenger, by a long-term Wikidata contributor
Summary
[edit]The summary is a group of summary sentences and associated keywords that describe the relevant topic(s). Below is an example.
The first column (after the line number) should be a single sentence. The second column should be a comma-separated list of keywords about that sentence, and so on. Taken together, all the sentences should provide an accurate summary of what was discussed with the specific community.
| Line | Statement (summary sentence) | keywords |
| 1 | Do not limit the range of subjects to be registered on to Wikidata (should not be bound to notability). Usually value of data will increase as comprehensiveness will get higher. And value of data vary by users. Data such as list of shops of fast food franchises or small monuments in an undocumented area may be very useful according to purposes. | value of data, comprehensiveness, use cases |
| 2 | Provide local discussion place (email list or something like that). Delegate authorities to determine local rules or properties, such as determining structures of administrative division. Discussing local things at a global place is very hard. | delegation, forum |
| 3 | Associating Wikipedia articles and Wikidata items can be done 1 by 1 currently. Hope it to be associated to a part of an article because dividing Wikipedia articles is very hard. | data relationship, data structure |
| 4 | Abstract concept can not necessarily be translated 1 to 1 between languages. For example, differences "position" and "status" in an organization can not be associated with 1 to 1 between Japanese and English. Flexible structure of meaning hyponymy is desired, like hierarchy. Not 1 by 1. We do not mind simple data structure inside machines, but want more flexible one when humans see. | data structure |
| 5 | Want some tools to support to input data, especially for updates (after the first input). E.g. updates when a mayor changed after election. Doing it all by hands is difficult to keep editing. Let alone import tools, automatic update method which works autonomously, like, when given some data structure, with specified items, where somewhere designated, is desired. | support tool, automatic update |
| 6 | Clarifying of policy about license compatibility. There are a lot of CC-BY opendata in Japan, for example. Basically copyrights shall not reach facts, regardless which license is applied. We want to clarify basic policies like "this way shall not be a problem" (we understand slight differences among cases, or between legal jurisdictions, though). | policy, license |
| 7 | Want images to be linked other than Wikimedia. Images on Mapillary are licensed under CC BY-SA 4.0. Location files should be registered or be linkable (e.g. geojson, shp, kml, or gpx). | registered data types |
| 8 | How about preparing input templates and make input easier? It is better that new comer can input data well, without searching properties. Examples: templates for municipalities, shrines, parks. | data input, template |
| 9 | Current Query Service is an excellent tool, however, it is useful just as one-time visualization. Preparing more specific output template (along with 8) is required, to embed on blogs (as direct output of information), or to output PDFs. It will increase user base if we can provide tools to fulfill specific purposes/needs, not just a one-time tool. | data output, tool |
| 10 | ||
| 11 | ||
| 12 | ||
| 13 | ||
| 14 | ||
| 15 | ||
| 16 | ||
| 17 | ||
| 18 | ||
| 19 | ||
| 20 | ||
| 21 | ||
| 22 | ||
| 23 | ||
| 24 | ||
| 25 | ||
| 26 | ||
| 27 | ||
| 28 | ||
| 29 | ||
| 30 | ||
| 31 | ||
| 32 | ||
| 33 | ||
| 34 | ||
| 35 | ||
| 36 | ||
| 37 | ||
| 38 | ||
| 39 | ||
| 40 |
If you need more lines, you can copy them from Strategy/Wikimedia movement/2017/Sources/Lines.
Detailed notes (Optional)
[edit]If you have detailed notes in addition to the summary, you may add them here. For example, the notes may come from an in-person discussion or workshop. If your discussion happened on a wiki or other online space, you do not need to copy the detailed notes here.
The interviewer asked a question to 3 participants of Code for Japan Summit (civic-tech conference), and 1 of them replied. The interview is done via Facebook Messenger, by a long-term Wikidata contributor