Aug 8 2018
Aug 2 2018
Jun 8 2018
I consider that this Ticket has been addressed here: https://www.wikidata.org/wiki/Wikidata_talk:Lexicographical_data#Outcome_of_the_conversation
Jun 6 2018
Thanks for your reply. Since you have introduced yourself, I would also like to introduce myself to the readers. I'm Micru, volunteer of the Wikimedia movement since 2004 and active in several projects and affiliates. First of all I would like to clarify with you that the Wikimedia movement is NOT the same as the WMF. Members of the Wikimedia movement, like the WMF, share a goal, collaborate with each other, and sometimes have misunderstandings that need to be clarified.
Jun 5 2018
Yesterday I was informed on T196069 about the plans of the WMF to appropriate the Wikimedia Blog. I asked if this had been discussed somewhere and I didn't receive any satisfactory answer, so I assume that it hasn't. Before this action is performed, I request that the role of the Wikimedia Blog is discussed at least on the Wikimedia-l mailing list, so that more members of the community are informed about this intention and feedback can be collected.
Jun 4 2018
@Aklapper yes, you can call the planets our community blogs, however I still feel important to clarify the role of the Wikimedia Blog before any move happens.
@EdErhart-WMF: I don't find correct to call it the "Wikimedia Foundation blog" either. Has it been discussed somewhere the intention of the WMF to appropriate this blog?
Hi @EdErhart-WMF! Can I see where it has been discussed that the community blog will be moving into the new Foundation website?
Jun 1 2018
@Lea_Lacroix_WMDE Why do we need to use a a list of language codes at all? Why not to do like with units and let the user select any item, and then have it checked with the constraints?
May 31 2018
May 30 2018
May 29 2018
@Mbch331 Thanks for clarifying that. I have never used [[:d:Wikidata]] myself, so I didn't consider that it was so important for other people. For the record I have to add that typing [[:w:Wikipedia]] links to the English Wikipedia article for Wikipedia and not to the Main page of https://www.wikipedia.org/
I have adapted the description of this task in a way that I feel it is more accurate to all what is needed. If you don't agree with this new description, please speak up.
Ah yes, you are right, I hadn't noticed that Lexemes have their own namespace. In that case. What would be easier? To create a new namespace for automated disambiguation pages for form/lexemes? Or perhaps move Items to their own namespace and use ns0 for the automated disambiguation pages for form/lexemes? I assume that the second option is not possible, but I ask anyway for clarification.
@Lydia_Pintscher As far as I understand ns0 is Items and Lexemes. Would it be possible to have items, lexemes, and form/lexemes automated disambiguation pages all together in ns0?
I replied on the thread that I would prefer to reserve ns0 for automatically filled pages that disambiguate lexemes/forms with the same spelling (see T195411).
May 25 2018
From the conversation here I think that recording lexemes with the same spelling is not as interesting as recording forms with the same spelling. Or perhaps both can be recorded. In any case I find this idea interesting, would it be possible to have dynamic pages like https://www.wikidata.org/wiki/orange or is it necessary to do it through a special page?
May 24 2018
@Lydia_Pintscher So if I understood properly what you suggest is that we create a property "homograph" to link lexemes and forms across languages?
Hey Lydia, indeed, I should have explained the changes. Yes, the line now pulls together everything related to one Form, and that requires reducing the horizontal space that the statement box takes.
May 22 2018
May 20 2018
In my understanding, it would need an update to the CC license itself, which would need to be done by CC, and then have the license be adopted by the Foundation together with the community
May 18 2018
since I hold the rights to that text
Aside from the fact that every single contributor would have to be asked to agree to the change of the license
Not really, the license is one of the non-negotiable aspects of Wikimedia projects.
I have a question regarding Wikipedia(s)->Wikidata imports. Since the license in the Wikipedia(s) is managed by the community, and the community has the power to change the license, or made amendments to the license , would it be feasible to ask the several Wikipedia(s) communities to add a clause where it is stated that statements can be mined by the Wikidata community (exclusively or not) and re-released as CC0 on the Wikidata platform?
May 2 2018
Apr 16 2018
So if I understand correctly, you would like to have custom Entity IDs instead of the usual Q followed by an integer (Qxxxx). On Wikidata normally the Entity IDs are not visible, what the user sees is the label of the entity. So I assume that in the use case of OSM you could have an entity with all the labels with the same string value for all languages, which could be enforced with a bot. That way you can maintain the value of the tag or change it when necessary.
Apr 6 2018
In ISO 8601 (same standard that Wikidata follows for the time data type), the duration data type is specified as follows: PnYnMnDTnHnMnS
Mar 22 2018
Jan 12 2018
May 23 2017
@Jonas I am very pleased to see you working on this, thank you! Here there is an example that I use often for maintenance:
Apr 28 2017
Ah, ok, thanks for the clarification! Looking forward to the announcement/activation!
@Ladsgroup When I try to create a property I see that "Geographic shape" is an option in the drop-down list, but I don't see "Tabular data set" in the list yet.
Apr 25 2017
@thiemowmde I don't know if you have any bone to pick with @Danwe but from an outside perspective his comment seems legitimate and constructive. The description of this task indeed misleading, and it should be corrected to reflect what the task is truly about.
Apr 24 2017
When I go to https://www.wikidata.org/wiki/Special:NewProperty there is a type by default (String). Shouldn't it be a blank value?
Apr 21 2017
Mar 16 2017
Where is the geoshape/dataset datatype being tracked? In WD it is still not available for property creation.
Jan 24 2017
Any news about this? See also: https://www.wikidata.org/wiki/Wikidata:Bot_requests#User_script_to_notify_participants_in_a_property_proposal
Jan 19 2017
Jan 12 2017
The webconsole says:
I can reproduce it on Firefox 50.1.0 on Windows 7.
Jan 6 2017
There is some criticism about using a fixed set of codes for the representation of languages and variants:
@Jonas If your patch adds a new datatype for Commons datasets, could you please update the ticket description? It seems to me that it doesn't have anything to do with KML files...
Jan 3 2017
Dec 23 2016
@Yurik What about using a wiki page to store categories and metadata about the dataset and then the dataset itself in a subpage. Would it work?
@Esc3300 There is data that cannot be modeled easily in WD, like geodata and climate data, and this is the ideal complement.
@Dereckson Yes, I was using HotCats at the bottom of the page.
Dec 22 2016
Structured datasets are officially available on Commons:
@Nikki Thanks for the query, I have completed the missing information and now it should return only one result - the sandbox item.
Dec 21 2016
Ok, I can imagine that it is not straight-forward. I hope that the same development for Lexicographical data can be reused for the monolingual text, because right now there are users selecting "mis" and not qualifying it with the corresponding language/dialect/variant.
It would be most useful if texts marked as "mis" would accept an item to specify the language used.
Dec 18 2016
@Yurik As the data blobs are finally stored on Commons, can this task be closed?
Dec 8 2016
Will it support URLs generated by external identifier?
Nov 17 2016
Nov 15 2016
Mar 13 2016
@Gymel the issue you describe is different and should be in a different task. This task is only for the "edition/edition of" relationship.
Mar 9 2016
The manual list of properties classifies them per topic. Propbrowse doesn't include the field of application, and that makes hard to find related properties, or properties applicable to a particular item. There is a property tree, from there it should be possible to automate a list of properties. See:
The extension Proofread page features section transclusion. Maybe it can provide some ideas.
Mar 8 2016
@Aklapper What happened with the code? Has it been reviewed?
Mar 5 2016
There is also needed a place to store JSON data, and CSV files for visualization. Would this be the right place for it?
Mar 4 2016
There is no need to create a new module, but some programming is needed to make it work with Template:infobox book. Some versions would need discussion in their talk pages to improve the layout, other wikipedias like the French, have designs better suited for the task. For instance, see the infobox on:
Mar 3 2016
I see that the stalled bug has been marked as resolved, Could this task become a GsoC project?
They could be different properties: "file creator on Commons", "file creator on Flickr", etc. however that would require more data types...
@Purodha It is not the same issue. This task refers to items in wikidata that are split into more two or more items to represent the metadata. Each of the so-called "edition items" has an interwiki link to a different domain. The problem is that since the structure it is like this, it is necessary to aggregate them. For example given the following wikidata items:
Work item (contains interwikis to wikipedia articles)
+Edition item 1 (contains 1 interwiki link to 1 wikisource page)
+Edition item 2 (contains 1 interwiki link to 1 wikisource page)
+Edition item 3 (contains 1 interwiki link to 1 wikisource page)
Mar 1 2016
Some users have created Lua modules that add extra interwiki links based on properties
IIRC @raylton.sousa was mentoring the project last year, I don't know if he could do it again, or if it should be listed as "looking for mentor"
@Aklapper Could it be again featured as a GsoC project?
Feb 28 2016
Feb 26 2016
Feb 25 2016
Some comments from 2014