Re: [Wikidata] The WikiCite 2018 program is live

[David Cuenca Tudela]

Hi Nicolas,

Here you will find the videos of the conference:
https://www.youtube.com/playlist?list=PLN4mEhpy3b8Sayl_QsSjpa8H1wqo82hxr

Regards,
Micru

On Sat, Nov 24, 2018 at 6:06 PM Nicolas VIGNERON 
wrote:

> Hi,
>
> Maybe I missed the info but is there any livestream?
>
> Cheers, ~nicolas
>
> Le ven. 16 nov. 2018 à 22:19, Tito Dutta  a écrit :
>
>> Interesting. Thanks for letting us know.
>>
>> Thanks
>> Tito Dutta
>> Note: If I don't reply to your email in 2 days, please feel free to
>> remind me over email or phone call.
>>
>>
>> On Sat, 17 Nov 2018 at 01:35, Dario Taraborelli <
>> dtarabore...@wikimedia.org> wrote:
>>
>>> The program of WikiCite 2018
>>>  (Berkeley, 27-29
>>> November 2018) is now available
>>> .
>>>
>>> The plenary sessions and the tutorials will be recorded and we're
>>> looking into the possibility of making a livestream available.
>>>
>>> Dario -- on behalf of the organizing committee
>>> 
>>> wikic...@wikimedia.org
>>> ___
>>> Wikidata mailing list
>>> Wikidata@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>>
>> ___
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Aliases on Sense Statement ?

[David Cuenca Tudela]

There are no aliases. The way to do this is to create another lexeme and
connect their senses with the property "synonym".

Regards,
Micru

On Sun, Nov 11, 2018 at 1:04 AM Thad Guidry  wrote:

> I read through the current documentation and Talk pages, but didn't find
> any cases for Aliases on Sense Statements.
> But this seems useful.  Let me explain...
>
> https://www.wikidata.org/wiki/Lexeme:L36454
> Verb:   mistype
> alias:  fat finger
>
> How to get that alias on L36454-S1 ?
> "fat finger" would be a synonym phrase for the verb sense L36454-S1 of
> "mistype".
>
> I see this being extremely useful for building out "urban dictionaries",
> etc. in the future.
>
> -Thad
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] [Consultation] Using Q-items for senses

[David Cuenca Tudela]

Hi,

On the project chat we are discussing about using Q-items for senses:
https://www.wikidata.org/wiki/Wikidata:Project_chat#[Consultation]_Using_Q-items_for_senses

It would be nice to have more input on the topic, since it is a different
use of items than the usual.

Thanks,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Wikimedia Sverige receives $65k+ in funding for our Library Data project

[David Cuenca Tudela]

Congrats! I'm glad to hear about this and I hope that more libraries take
this step :-)

On Mon, Aug 27, 2018 at 4:17 PM Alicia Fagerving <
alicia.fagerv...@wikimedia.se> wrote:

> Wikimedia Sverige is proud to be
> the recipient of $65,500 in support from the Swedish National Library for
> our project Library Data.
>
> We will work in collaboration with the Swedish
> National Library to include a number of datasets onto Wikidata, such as
> data about authors, libraries and different special databases of
> bibliographies[1]. This is a pilot project where we aim to discuss with the
> community what to include and what to exclude. Based on the discussions and
> the requests from the community we will design a continuation of this
> project (if this first part is deemed successful continuous funding is
> possible for 3-4 more years).
>
> We started investigating a possible long term
> partnership with the National Library in 2017 when Wikimedia Sverige
> delivered inputs to the new National Strategy for the Library Sector on how
> Sweden's libraries can work with Wikimedia for mutual benefits.[2] The
> National Library has just made history as the world's first national
> library to fully transition to Linked Open Data (BIBFRAME 2.0),[3] so the
> timing could not have been better; we are now in position to examine how
> this move can benefit Wikidata and other Wikimedia projects.
>
> Please contact
> the project manager André Costa (andre.co...@wikimedia.se) or the
> developer Alicia Fagerving
> (alicia.fagerv...@wikimedia.se) if you have
> any questions.
>
> As always, you can find the full application on our wiki (in
> Swedish):
>
> *
> https://se.wikimedia.org/wiki/Projekt:Strategisk_inkludering_av_biblioteksdata_p%C3%A5_Wikidata_2018/Ans%C3%B6kan
>
> [1] 
> [2] <
> https://commons.wikimedia.org/wiki/File:Wikimedia_Sverige_-_Wikipedia_och_biblioteken_i_Sverige.pdf
> >
> (in Swedish)
> [3] <
> http://www.mynewsdesk.com/se/kungliga_biblioteket/pressreleases/kb-becomes-the-first-national-library-to-fully-transition-to-linked-data-2573975
> >
>
>
> Kind regards,
>
> ~*~
> Alicia Fagerving
> Developer
> Wikimedia Sverige (WMSE)
>
> e-mail: alicia.fagerv...@wikimedia.se
> phone: +46 73 950 09 56
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Wikidata SPARQL query logs available

[David Cuenca Tudela]

If someone could post the 10 (or 50!) more popular items, I would really
appreciate it :-)

Cheers,
Micru

On Tue, Aug 7, 2018 at 5:59 PM Maximilian Marx <
maximilian.m...@tu-dresden.de> wrote:

>
> Hi,
>
> On Tue, 7 Aug 2018 17:37:34 +0200, Markus Kroetzsch <
> markus.kroetz...@tu-dresden.de> said:
> > If you want a sorted list of "most popular" items, this is a bit more
> > work and would require at least some Python script, or some less
> > obvious combination of sed (extracting all URLs of entities), and
> > sort.
>
>   zgrep -Eoe '%3Chttp%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ[1-9][0-9]+%3E'
> dump.gz | cut -d 'Q' -f 2 | cut -d '%' -f 1 | sort | uniq -c | sort -nr
>
> should do the trick.
>
> Best,
>
> Maximilian
> --
> Dipl.-Math. Maximilian Marx
> Knowledge-Based Systems Group
> Faculty of Computer Science
> TU Dresden
> +49 351 463 43510
> https://kbs.inf.tu-dresden.de/max
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Wikidata SPARQL query logs available

[David Cuenca Tudela]

Hi Markus,

Thanks for making the logs available. Personally I would be interested in
knowing how often a certain item pops up in queries. That way it would make
easier to know the popularity of certain items.

Do you think it's something that could be accomplished?

Regards,
Micru



On Tue, 7 Aug 2018, 17:01 Markus Kroetzsch, 
wrote:

> Dear all,
>
> I am happy to announce that as part of an ongoing research collaboration
> between TU Dresden researchers and Wikimedia [1], we could now release
> pre-processed logs from the Wikidata SPARQL Query Service [2]. You can
> find details and download links on the following page:
>
> https://iccl.inf.tu-dresden.de/web/Wikidata_SPARQL_Logs/en
>
> The data so far comprises over 200 million queries answered in
> June-August 2017. There is also an accompanying publication that
> describes the workings of and practical experiences with the SPARQL
> query service [3].
>
> The logs have been pre-processed to remove information that could
> potentially be used for identifying individual users (e.g., comments
> were removed, geo-coordinates coarsened, and query strings reformatted
> completely -- see above page for details). Nevertheless, one can still
> learn many interesting things from the logs, e.g., which properties and
> entities are used in queries, which SPARQL features are most prominent,
> or which languages are requested.
>
> We also have preserved some amount of user agent information, but
> without overly detailed software versions and only in cases where the
> agents occurred many times across several weeks. This can at least be
> used to recognise the (significant amount) of queries generated, e.g.,
> by Magnus' tools, or to do a rough analysis of which software platforms
> are mostly used to send queries from. We used #TOOL comments found in
> queries to refine user agent information in some cases.
>
> We also made an effort to identify those queries that come from browser
> agents *and* also behave like one would expect from a browser (not all
> "browsers" did). We called such queries "organic" and provide this
> classification with the logs (there is also a filtered dump of only
> organic queries, which is much smaller and therefore nicer to process,
> also for testing). See the paper for details on our methodology.
>
> Finally, the data contains the time of each request, so one can
> reconstruct query loads over time.
>
> Feedback is very welcome, both in terms of comments on the data (is it
> useful to you? would you like to see more? do you have concerns?) and in
> terms of insights that you can get from it (we did some analyses but one
> can surely do more).
>
> Cheers,
>
> Markus
>
> [1]
> https://meta.wikimedia.org/wiki/Research:Understanding_Wikidata_Queries
> [2] https://query.wikidata.org/ (or rather the web service that powers
> this UI and many other applications).
> [3] Stanislav Malyshev, Markus Krötzsch, Larry González, Julius Gonsior,
> Adrian Bielefeldt: Getting the Most out of Wikidata: Semantic Technology
> Usage in Wikipedia’s Knowledge Graph. In Proceedings of the 17th
> International Semantic Web Conference (ISWC-18), Springer 2018.
> https://iccl.inf.tu-dresden.de/web/Wikidata_SPARQL_Logs/en
>
> --
> Prof. Dr. Markus Kroetzsch
> Knowledge-Based Systems Group
> Center for Advancing Electronics Dresden (cfaed)
> Faculty of Computer Science
> TU Dresden
> +49 351 463 38486
> https://kbs.inf.tu-dresden.de/
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Machine translation efforts for underserved languages

[David Cuenca Tudela]

Hi Olya,

There is also another topic to consider with translations. Normally a text
reflects the reality of a speaker, which doesn't mean that that reality is
interesting for a speaker of another language who might have different
circumstances.

For instance the translation of an article about metabolic pathways might
not be so interesting to a farmer in Rwanda, however an article about the
planting seasons might be more interesting. That article might not exist in
English, yet the speakers of that language I'm sure they have the knowledge
to generate an article on the topic.

What I am trying to say is, that while translations are interesting to a
certain extent, you cannot translate the interest that a person might have.
Normally that interest is already shared with the community so sometimes it
is more empowering to give the tools and explain how to use them, so that
the community can create articles about what they find interesting. With
that in mind, it seems that when articles are translated from English into
Swahili, their speakers are benefiting from our global culture. But also
when translating Swahili articles into English the global culture would
benefit from knowing better a local culture. For that to happen there
should be some articles written natively in Swahili.

I find also that it might be more interesting to translate to/from
neighbouring languages for several reasons: a) The languages tend to be
similar, so it is easier to use machine-translation, b) there is
familiarity with the interest that neighbouring cultures have, c)
understanding your neighbours is a good basis for having peaceful
relationships.

In any case I wish you a lot of success in your project, and I hope it
benefits many people!

Regards,
Micru

On Fri, Jun 22, 2018 at 3:04 PM Olya Irzak  wrote:

> Dear Gerard, Scott, Lucie and Amir & everyone,
>
> Thank you for the helpful responses!
>
> Gerard - great to hear about your work and thank you for the reference on
> Cebuano Wikipedia. We weren't familiar with that case, but had similar
> fears. We are putting our machine translated content on a separate site
> (Wikibabel) rather than Wikipedia, and we never expect it to show up nearly
> as high in search engine results, and so the native content will always
> take precedence.
>
> Scott - for the time being, the Wikibabel experiment will not have a
> Wikidata or Lexicographical portion, as for now this is an experiment to
> see if machine translated content in certain categories is useful given the
> state of machine translation currently (and we are doing this on a separate
> site in order to avoid any contamination). If we'll measure good user
> engagement and survey results, we'd love to think about how to integrate
> this better. We'd love to eventually have an editing interface on top of
> the translation and with existing native content if exists and has fewer
> details. If this editing interface becomes popular, then we'll start
> accumulating a dataset which may be useful to machine translation services.
> We, however, are not developing anything novel in the machine translation
> algorithm space.
>
> Lucie - ah, that's what this is! We noticed the large number of recent one
> sentence articles and were wondering what project that was. Those are
> awesome! Both in terms of information availability and because it allows us
> to measure relative interest within the generated set. I would love to
> discuss further your plans to expand beyond the introductory sentence, and
> if we can be helpful in any way. Thank you for the publication links as
> well.
>
> Amir - thank you for the pointers to these projects. Your 2 points of
> feedback, if I understand correctly:
> 1. Machine translation might not be good enough to yield useful
> information.
> 2. People can translate the pages for free.
> Those are excellent points that we've thought about deeply before starting
> the projects (though we find a much higher translation quality recently
> than you perhaps). Here's what we think:
> 1. This is exactly the central question of our experiment, and very much
> still open. Machine translation (or at least Google translate) has improved
> significantly in the last 12 months or so. The quality of the translation,
> particularly when there is context (longer sentences) has improved leaps
> and bounds. For the Wikibabel project, we spot checked with Swahili
> speakers that some pages translate very well (not perfect human level, but
> very understandable with a few awkward turns of phrase) and some are bad
> enough to not be useful. Given how little information there is on the
> Internet in Swahili, particularly on technical topics (easier to translate
> in some ways) and that there aren't many participants in the Swahili
> Wikipedia, we hypothesize that the best X% of translations would be useful,
> and that we can measure and tell the difference between well translated
> pages and not from page analytics and surveys.
> We are, 

[Wikidata] What makes a good Wikidata community representative?

[David Cuenca Tudela]

Hi everybody,

As you might know I would like to represent the Wikidata community at the
Wikimedia movement strategy 2018-20, more specifically at the working group
of Roles & Responsibilities [1].

Regardless of whether I have enough support to legitimize my claim, I'm
interested in knowing what you think that the requirements should be,
because it can be useful to appraise this or future applications.

Things that have been mentioned so far: on-wiki activity, public-facing
experience, knowing Wikidatans in person, particular insights.

If you have more ideas, please share them!

Thanks
Micru


[1]
https://www.wikidata.org/wiki/Wikidata:Project_chat#Representation_of_Wikidata_at_the_Wikimedia_movement_strategy_process
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Lexicographical data: Removing language codes from the user interface

[David Cuenca Tudela]

I realized that I had framed the topic incorrectly. The intention is not
only to remove the language codes from the user interface, but to replace
them by items, hence this new title/link:

https://www.wikidata.org/wiki/Wikidata_talk:Lexicographical_data#Replacing_language_codes_by_items_in_the_user_interface

Regards,
Micru

On Fri, Jun 1, 2018 at 9:16 AM, David Cuenca Tudela 
wrote:

> Hi,
>
> I have just started a consultation about removing language codes from the
> user interface in the Lexeme pages. I would appreciate your input here:
> https://www.wikidata.org/wiki/Wikidata:Project_chat#Lexicographical_data:_
> Removing_language_codes_from_the_user_interface
>
> Thanks,
> Micru
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] Lexicographical data: Removing language codes from the user interface

[David Cuenca Tudela]

Hi,

I have just started a consultation about removing language codes from the
user interface in the Lexeme pages. I would appreciate your input here:
https://www.wikidata.org/wiki/Wikidata:Project_chat#Lexicographical_data:_Removing_language_codes_from_the_user_interface

Thanks,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] First experiment of lexicographical data is out

[David Cuenca Tudela]

Congratulations on releasing this!

I think the usefulness will improve after releasing Senses, but it is good
that we have something to play with and start suggesting improvements.

Regards,
Micru

On Wed, May 23, 2018 at 11:25 PM, Eran Rosenthal 
wrote:

> Kudos to the development team. It's great to see it is finally in
> production.
> There is still a long way to go to have a more friendly user interface,
> but Q17117425 :)
>
> On Wed, May 23, 2018 at 9:12 PM, Gerard Meijssen <
> gerard.meijs...@gmail.com> wrote:
>
>> Hoi,
>> Sorry the Q-number refers to a thing or an idea absolutely. The labels
>> don't; they describe the idea and with the possible exception of special
>> cases like templates lists and categories these labels can be associated
>> with lexical information. It is vitally important to have lexical
>> information about them because they will spark the development of better
>> use of the information inherently available in the Q-items.
>> Thanks,
>>GerardM
>>
>> On 23 May 2018 at 14:33, Léa Lacroix  wrote:
>>
>>> Hello all,
>>>
>>> After several years discussing about it, and one year of development and
>>> discussion with the communities, the development team has now released the
>>> first version of lexicographical data support on Wikidata
>>> .
>>>
>>> Since the start of Wikidata in 2012, the multilingual knowledge base was
>>> mainly focused on concepts: Q-items are related to a thing or an idea, not
>>> to the word describing it. Starting now, Wikidata stores a new type of
>>> data: words, phrases and sentences, in many languages, described in many
>>> languages. This information will be stored in new types of entities, called
>>> Lexemes, Forms and Senses. It will allow editors to describe precisely all
>>> words in all languages, and will be reusable, just like the whole content
>>> of Wikidata, by multiple tools and queries, everything that the community
>>> creates to play with words. Lexicographical data can be reused inside and
>>> outside the Wikimedia projects, and can provide support for Wiktionary.
>>> The first release
>>>
>>> A new namespace and several new entity types have been created in order
>>> to model words and phrases. If you’re new to this project, you can learn
>>> more by looking at the documentation
>>> ,
>>> briefly describing the data model and the interface. The technical
>>> structure is set, but the editors remain free to model and organize data as
>>> they prefer, with the usual open discussions and community processes that
>>> we apply on Wikidata. Some discussions about new properties
>>>  to
>>> create have already started: if you want to be involved in the early stage
>>> of the project to shape it, please participate!
>>>
>>> Please note that the version that is now deployed is a first experiment,
>>> that will be continuously improved in the future. Some features are
>>> missing, some bugs may certainly occur. Here are the features that are
>>> included in the first release:
>>>
>>>- Add, edit and delete Lexemes, Forms, statements, qualifiers,
>>>references
>>>- Link between the different entity types (Item to Lexeme, Form to
>>>Item, etc.)
>>>- Entity suggestion when adding a property or a value
>>>
>>> And the following features will not be included in the first version,
>>> but are planned for the future:
>>>
>>>- Find Lexemes and Forms via Special:Search
>>>- RDF support (which also means: the ability to query it with
>>>query.wikidata.org)
>>>- Support for Senses
>>>- Merging of Lexemes
>>>- Including the data on other Wikimedia projects, such as Wiktionary
>>>
>>> How to try it?
>>>
>>> The features described above are now deployed on Wikidata.org. Here are
>>> some suggestions of what you can do to explore this new territory:
>>>
>>>- If you’re not familiar with the structure of Lexemes, have a look
>>>at the documentation
>>>
>>> 
>>>- Look at what is already existing
>>>.
>>>Please note that Special:Search and the search bar on the top right 
>>> corner
>>>of pages is not supporting Lexemes yet. We’re working on this.
>>>- Create a new Lexeme with Special:NewLexeme
>>>
>>>- If a property that you need is missing, you can suggest it here
>>>
>>>- Discuss about how to model words and ask questions on Wikidata
>>>talk:Lexicographical data
>>>- Report bugs or issues that you may encounter: either on the talk
>>>page or on Phabricator, if you’re comfortable using it (create a
>>>

Re: [Wikidata] Knowledge Integrity: A proposed Wikimedia Foundation cross-departmental program for 2018-2019

[David Cuenca Tudela]

On Tue, Apr 17, 2018 at 11:39 AM, Finn Aarup Nielsen  wrote:

> I do not think Wikimedia should collect this information without a clear
> opt-in.


I agree, it could be enabled as a Beta feature: "Volunteer to usage
research"



> I regard a non-opt-in as an invasion of privacy and such data seems not to
> have much strategic importance for Wikimedia and Wikimedians.
>

It depends on what you do with the data, if you just put it into the drawer
obviously doesn't have much importance, however if it can be used to gain
more understanding about which parts of a text spark more interest, maybe
it can be useful.

Regards,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Knowledge Integrity: A proposed Wikimedia Foundation cross-departmental program for 2018-2019

[David Cuenca Tudela]

Hi Dario&Jake,

Thanks for sharing the plan. Any possibility to include in the plan a
system to archive all reference URLs and external identifiers linked from
Wikidata?
https://phabricator.wikimedia.org/T143488

Additionally I think it would be interesting to have some research done on
which references are DISPLAYED or CLICKED the most on several Wikipedias.
We know already which sources are cited the most, but on which sources do
users hover their mouse the most? Can we also identify which statements are
involved? It could be used to expand them, improve them, or add more
context.

Finally I believe it would be that a tool to assess the
openness/accessibility of the sources of any given article could be really
interesting.

Regards,
Micru


On Tue, Apr 17, 2018 at 2:32 AM, Dario Taraborelli <
dtarabore...@wikimedia.org> wrote:

> Hey all,
>
> (apologies for cross-posting)
>
> We’re sharing a proposed program
> 
>  for the Wikimedia Foundation’s upcoming fiscal year
> 
>  (2018-19) and *would love to hear from you*. This plan builds
> extensively on projects and initiatives driven by volunteer contributors
> and organizations in the Wikimedia movement, so your input is critical.
>
> Why a “knowledge integrity” program?
>
> Increased global attention is directed at the problem of misinformation
> and how media consumers are struggling to distinguish fact from fiction.
> Meanwhile, thanks to the sources they cite, Wikimedia projects are uniquely
> positioned as a reliable gateway to accessing quality information in the
> broader knowledge ecosystem. How can we mobilize these citations as a
> resource and turn them into a broader, linked infrastructure of trust to
> serve the entire internet?  Free knowledge grounds itself in verifiability
> and transparent attribution policies. Let’s look at 4 data points as
> motivating stories:
>
>- Wikipedia sends tens of millions of people to external sources each
>year. We want to conduct research to understand why and how readers leave
>our site.
>- The Internet Archive has fixed over 4 million dead links on
>Wikipedia. We want to enable instantaneous archiving of every link on all
>Wikipedias to ensure the long-term preservation of the sources Wikipedians
>cite.
>- #1Lib1Ref reaches 6 million people on social media. We want to bring
>#1Lib1Ref to Wikidata and more languages, spreading the message that
>references improve quality.
>- 33% of Wikidata items represent sources (journals, books, works). We
>want to strengthen community efforts to build a high-quality, collaborative
>database of all cited and citable sources.
>
> A 5-year vision
>
> Our 5-year vision for the Knowledge Integrity program is to establish
> Wikimedia as the hub of a federated, trusted knowledge ecosystem. We plan
> to get there by creating:
>
>- A roadmap to a mature, technically and socially scalable, central
>repository of sources.
>- Developed network of partners and technical collaborators to
>contribute to and reuse data about citations.
>- Increased public awareness of Wikimedia’s vital role in information
>literacy and fact-checking.
>
>
> 5 directions for 2018-2019
>
> We have identified 5 levers of Knowledge Integrity: research,
> infrastructure and tooling, access and preservation, outreach, and
> awareness. Here’s what we want to do with each:
>
>
>1. Continue to conduct research to understand how readers access
>sources and how to help contributors improve citation quality.
>2. Improve tools for linking information to external sources,
>catalogs, and repositories.
>3. Ensure resources cited across Wikimedia projects are accessible in
>perpetuity.
>4. Grow outreach and partnerships to scale community and technical
>efforts to improve the structure and quality of citations.
>5. Increase public awareness of the processes Wikimedians follow to
>verify information and articulate a collective vision for a trustable web.
>
>
> Who is involved?
>
> The core teams involved in this proposal are:
>
>- Wikimedia Foundation Technology’s Research Team
>- Wikimedia Foundation Community Engagement’s Programs team (Wikipedia
>Library)
>- Wikimedia Deutschland Engineering’s Wikidata team
>
>
> The initiative also spans across an ecosystem of possible partners
> including the Internet Archive, ContentMine, Crossref, OCLC, OpenCitations,
> and Zotero. It is further made possible by funders including the Sloan,
> Gordon and Betty Moore, and Simons Foundations who have been supporting the
> WikiCite initiative to date.
>
> How you can participate
>
> You can read the fine details of our proposed year-1 plan, and provide
> your feedback, on mediawiki.org: https://www.mediawiki.org/wiki/Wikimedia_
>

Re: [Wikidata] Deletion nomination of Template:Cite Q on English Wikipedia

[David Cuenca Tudela]

On Thu, Sep 21, 2017 at 1:22 AM, Dario Taraborelli <
dtarabore...@wikimedia.org> wrote:

> I don't know exactly how this should be designed (some user research seems
> in order before coming up with any solution). The problem to me is how to
> design subscription/synchronization mechanisms giving people freedom to
> choose which data to reuse or not and which "fixes" to send upstream to a
> centralized knowledge base. I believe this is how the relation between
> Wikidata and other projects was originally conceived: something like this
> would allow structured data to be broadly reused without neglecting the
> very legitimate concerns, policies and expectations of data consumers.
>

 One of the main issues is when using the wikitext editor on Wikipedia.
Most of the editors complain about unreadable references ({{cite
Q|Q29581755}}), but in order to be readable, the wikitext editor should
have some sort of mechanism to display more information about the item. I
don't know if with the current Wikitext editor it is doable, however I
think it is worth exploring.

Cheers,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] Input needed on Wikidata:Schema.org

[David Cuenca Tudela]

Hi all,

In case you didn't notice Denny posted a great RFC yesterday. Apparently
Schema.org is considering to encourage the use of Wikidata as a common
entity base for the target of the sameAs relation.

To read more and to give feedback, check:
https://www.wikidata.org/wiki/Wikidata:Schema.org

In my opinion this is great news. Thanks for reaching out, Denny! :)

Cheers,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] SPARQL query property. Which datatype?

[David Cuenca Tudela]

Hi,

There is a property proposal to store a SPARQL query equivalent to a
category:
https://www.wikidata.org/wiki/Wikidata:Property_proposal/Wikidata_SPARQL_query_equivalent

I have some doubts about the appropriate datatype. I guess it depends on
future plans/community preferences.

My ideal scenario would be a datatype "SPARQL query" that would store the
plain text and it would be collapsed in the user interface. Users would be
able to expand the code or just run it directly. Additionally, queries
could be qualified with qualifiers TBD, that would allow to query existing
queries, or define how frequently the cached query should be updated.

If that would be too much work, then the datatype "string" or a short/long
URL to the query seem also valid options.

What are your thoughts on the issue?

Cheers,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Wikidata Query Service + Mediawiki API = Love

[David Cuenca Tudela]

Hi Nicolas,

Indeed! That was it :) A typical case of PEBCAK :P

Cheers,
Micru

On Fri, Apr 28, 2017 at 9:19 AM, Nicolas VIGNERON <
vigneron.nico...@gmail.com> wrote:

> Hi Micru,
>
> It looks like you tried on https://query.wikidata.org (where I get the
> same error) and not on http://wdqs-test.wmflabs.org (where the
> implementation is installed).
>
> Cdlt, ~nicolas
>
> 2017-04-28 8:57 GMT+02:00 David Cuenca Tudela :
>
>> Hi Stas,
>>
>> Thanks for working on this. I tried to run the examples, but I get the
>> following error when I hit the button: Query is malformed: QName
>> 'mwapi:titles' uses an undefined prefix
>>
>> And here you can see more details about the error output:
>> https://pastebin.com/yNd7vPw4
>>
>> I hope you can fix it :)
>>
>> Thanks
>> Micru
>>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Wikidata Query Service + Mediawiki API = Love

[David Cuenca Tudela]

Hi Stas,

Thanks for working on this. I tried to run the examples, but I get the
following error when I hit the button: Query is malformed: QName
'mwapi:titles' uses an undefined prefix

And here you can see more details about the error output:
https://pastebin.com/yNd7vPw4

I hope you can fix it :)

Thanks
Micru



On Thu, Apr 27, 2017 at 11:40 PM, Stas Malyshev 
wrote:

> Hi!
>
> I am developing functionality that will allow WDQS query to get data
> from Mediawiki API [1].
>
> Currently, the design is as follows:
> - The API should have a pre-defined template
> - The template also specifies which results are available from the API
>
> The need for template is currently because we need to convert data from
> API's treelike format to tabular format that SPARQL needs, and the
> template allows to specify how the conversion is done.
> See https://www.wikidata.org/wiki/Wikidata:WDQS_and_Mediawiki_API for
> detailed description of how it works.
>
> The prototype implementation is running on http://wdqs-test.wmflabs.org/
> (only Categories API described in the page above is configured now, but
> more will be soon). I'd like to hear feedback about this:
> - does template model make sense at all? Is it enough?
> - what APIs would we want to expose?
> - any other features that would be useful?
>
> Other comments and ideas on the matter are of course always welcome.
> Please comment on the talk page[2] or reply to this message.
>
> [1] https://phabricator.wikimedia.org/T148245
> [2]
> https://www.wikidata.org/w/index.php?title=Wikidata_talk:
> WDQS_and_Mediawiki_API&action=edit
>
> Thanks,
> --
> Stas Malyshev
> smalys...@wikimedia.org
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] New Wikidata accounts can't edit labels?

[David Cuenca Tudela]

Hi Daniel,
The usual procedure is explained here:
https://meta.wikimedia.org/wiki/Mass_account_creation
https://www.mediawiki.org/wiki/Help:Mass_account_creation
https://meta.wikimedia.org/wiki/Grants:Learning_patterns/Six-account_limit

Normally to request a temporary lift of the IP cap, they should file a task
as explained on that page. There are some quick workarounds, like creating
accounts with smartphones.

Cheers,
Micru



On Tue, Apr 11, 2017 at 11:26 PM, Daniel Mietchen <
daniel.mietc...@googlemail.com> wrote:

> Dear all,
> I was just pinged by a Wikidata hackathon in Suriname
> (cf. https://www.spangmakandra.com/big-data-seminar-suriname )
> that they can't edit Wikidata any more - see also
> https://twitter.com/twitferry/status/851907389087502338 .
> We are musing that this may be due to an IP ban, since more than six
> new accounts were registered from the same IP (186.179.xxx.xx).
> Can anyone help sort this out quickly, so that the event can move on?
> Thanks,
> Daniel
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Languages in Wikidata4Wiktionary

[David Cuenca Tudela]

Personally I would prefer a mixed approach, where there is a list of
top-level items that are authorized, and then verifying that the item used
is a subclass of any of those items. Whether those constraints are
hard-enforced or just supervised could be a topic of discussion, but IMHO
the more automated, the better.

Regarding the codes, it can be generated with the code of the top-level
item+the Q number of the item used. If someone wants to use one or the
other, it should be quite easy to remove.

Cheers,
David

On Thu, Apr 6, 2017 at 6:51 PM, Denny Vrandečić  wrote:

> The current spec of the data model states that an L-Item has a lemma, a
> language, and several forms, and the forms in turn have representations.
>
> https://www.mediawiki.org/wiki/Extension:WikibaseLexeme/Data_Model
>
> The language is a Q-Item, the lemma and the representations are
> Multilingual Texts. Multilingual texts are sets of pairs of strings and
> UserLanguageCodes.
>
> My question is about the relation between representing a language as a
> Q-Item and as a UserLanguageCode.
>
> A previous proposal treated lemmas and representations as raw strings,
> with the language pointing to the Q-Item being the only language
> information. This now is gone, and the lemma and representation carry their
> own language information.
>
> How do they interact? The language set referencable through Q-Items is
> much larger than the set of languages with a UserLanguageCode, and indeed,
> the intention was to allow for every language to be representable in
> Wikidata, not only those with a UserLanguageCode.
>
> I sense quite a problem here.
>
> I see two possible ways to resolve this:
> - return to the original model and use strings instead of Multilingual
> texts (with all the negative implications for variants)
> - use Q-Items instead of UserLanguageCodes for Multilingual texts (which
> would be quite a migration)
>
> I don't think restricting Wiktionary4Wikidata support to the list of
> languages with a UserLanguageCode is a viable solution, which would happen
> if we implement the data model as currently suggested, if I understand it
> correctly.
>
> Cheers,
> Denny
>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] IBM's Watson using Wikdata

[David Cuenca Tudela]

Hi,

I didn't see it around here, but in a paper from Nov 2016 a group of
researchers from IBM used Wikidata to select which entities to feed Watson
for automatic QA generation:
"Training IBM Watson using Automatically Generated Question - Answer Pairs"
https://arxiv.org/abs/1611.03932

Cheers,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Confusion about memorials: Q5003624 (Gedenkstätte) and Q1885014 (Mahnmal)

[David Cuenca Tudela]

As I recently discovered, the proper place to discuss this is on this page:
https://www.wikidata.org/wiki/Wikidata:Interwiki_conflicts

Please start a conversation there.

Thanks
Micru

On Sat, Jan 7, 2017 at 5:36 PM, Edward Betts  wrote:

> Q5003624 (memorial) is a subclass of Q1885014 (no English label).
>
> Labels for Q5003624   https://www.wikidata.org/wiki/Q5003624
> English: memorial
> French: mémorial
> German: Gedenkstätte
> Portuguese: Monumento comemorativo
> Spanish: Monumento conmemorativo
>
> Labels for Q1885014   https://www.wikidata.org/wiki/Q1885014
> English: no label
> French: monument commémoratif
> German: Mahnmal
>
> These are the relevant articles on German language Wikipedia:
> Q5003624: https://de.wikipedia.org/wiki/Gedenkst%C3%A4tte
> Q1885014: https://de.wikipedia.org/wiki/Mahnmal
>
> The English description of Q1885014 is "type of monument that serves as a
> warning". Is that right?
>
> Should we invent an English label, for Q1885014? How about "Warning
> memorial"?
>
> It seems the like the French label for Q1885014 is the same as the
> Portuguese
> and Spanish labels of Q5003624. Maybe one of these labels is wrong.
>
> Is Q5003624 (Gedenkstätte) genuinely a subclass of Q1885014 (Mahnmal)?
> --
> Edward.
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] [Wikitech-l] Now live: Shared structured data

[David Cuenca Tudela]

Anyway, this is great news! I hope that it gets adopted by the community.
Congratulations, Yuri!

I was going to suggest a Wikidata property, but I see that the data type
for datasets is not there yet:
https://phabricator.wikimedia.org/T151334

On Thu, Dec 22, 2016 at 8:48 PM, Yuri Astrakhan 
wrote:

> Micru, thanks, I think Datasets sounds like a good name too!
>
> On Thu, Dec 22, 2016 at 2:44 PM David Cuenca Tudela 
> wrote:
>
> > On Thu, Dec 22, 2016 at 8:38 PM, Brad Jorsch (Anomie) <
> > bjor...@wikimedia.org
> > > wrote:
> >
> > > On Thu, Dec 22, 2016 at 2:30 PM, Yuri Astrakhan <
> > yastrak...@wikimedia.org>
> > > wrote:
> > >
> > > > Gift season! We have launched structured data on Commons, available
> > from
> > > > all wikis.
> > > >
> > >
> > > I was momentarily excited, then I read a little farther and discovered
> > this
> > > isn't about https://commons.wikimedia.org/wiki/Commons:Structured_data
> .
> > >
> >
> > Same here, I think it needs a better name...
> >
> > What about calling it datasets or structured datasets?
> >
> > Cheers,
> > Micru
> > ___
> > Wikitech-l mailing list
> > wikitec...@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> ___
> Wikitech-l mailing list
> wikitec...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] SQID now supports PrimarySources

[David Cuenca Tudela]

Hi Markus,

Great tool! I have a question, how do I find the items that contain
potential statements from the Primary Sources Tool to be added to WD?

I was expecting to find a list, or a "show random item with Primary Source
statements". Maybe I am not looking at the right place?

Thanks and regards,
David

On Fri, Dec 16, 2016 at 1:32 PM, Markus Kroetzsch <
markus.kroetz...@tu-dresden.de> wrote:

> Dear all,
>
> I am happy to announce that we have just deployed a new version of the
> SQID Wikidata browser at
>
> https://tools.wmflabs.org/sqid/
>
> The main news are the first working editing features. Users that log in
> will be given options to modify the data directly. (Regular users may have
> to hard reload the page to see the new version; it should have a "login"
> option on the top right.)
>
> == Features ==
>
> * Users can login with their Wikimedia accounts
> * Statement suggestions from Primary Sources are offered to logged in
> users, who can approve or reject them
> * Approving/rejecting statements takes immediate effect, without a slow
> page reload
> * Statement suggestions are shown in the same "smart" order used for all
> data on SQID. For example, statements with start time will be ordered by
> time so you can compare suggested data to existing data more easily.
> * There is a minimal "edit label" functionality for logged in users too
>
> We hope this can help to speed up the work of editors who want to get more
> PS data merged into Wikidata (e.g., for Freebase import).
>
> == Known issues ==
>
> * Some statements cannot be rejected in Primary Sources. This problem
> affects both SQID and the Wikidata gadget in the same way. It seems to be a
> bug in the PS web service, which we hope will be fixed at some point.
> * There is no error reporting yet -- if PS fails, the user can see that a
> requested action does not happen but errors are logged on the Javascript
> console only.
> * If many references for the same statement are suggested, they will show
> as many statements with one reference each instead. The editing
> functionality is there, but the UI needs to be improved.
> * Label editing is pretty minimal, e.g., you cannot edit descriptions yet.
> * If a suggestion (reference or additional statement value) is in a
> collapsed panel in the UI, there is no indication of it.
>
> Please report issues and requests through github:
> https://github.com/Wikidata/SQID/issues
>
> == Next steps ==
>
> * Address the open issues above (those that can be fixed in SQID)
> * Add further editing controls (e.g., direct statement deletion)
> * Add further suggestion sources
>
>
> == Acks ==
>
> This implementation was mainly done by Michael Günther. Many thanks are
> also due to Magnus, whose Widar service for editing Wikidata is used to
> make the actual changes in the back (so edits will get a Widar tag in
> Wikidata's history).
>
> As usual, feedback is welcome.
>
> Cheers,
>
> Markus
>
> --
> Prof. Dr. Markus Kroetzsch
> Knowledge-Based Systems Group
> Center for Advancing Electronics Dresden (cfaed)
> Faculty of Computer Science
> TU Dresden
> +49 351 463 38486
> https://iccl.inf.tu-dresden.de/web/KBS/en
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] Unable to edit items on Firefox

[David Cuenca Tudela]

Hi,

This problem is quite important, I hope someone can take a look.
https://www.wikidata.org/wiki/Wikidata:Project_chat#Unable_to_edit_items_on_Firefox

Thanks,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Wikidata logo

[David Cuenca Tudela]

Also very nice are all the logos that were created for the Wikiprojects,
really creative! :)
https://commons.wikimedia.org/wiki/Category:Wikidata_WikiProjects

Cheers,
Micru

On Thu, Oct 27, 2016 at 9:09 PM, Amir Ladsgroup  wrote:

> There was a survey on Wikimedia branding (including branding of its
> projects) in Wikimania 2016. I was reading the results and I found it
> fascinating that Wikidata logo is liked the most between community people.
>
> Notes:
> "The barcode is great"
> "It is quite clever, It spells wiki in Morse code" (I didn't know that. I
> checked it and it's true. WOW)
> "In terms of semantics, It's perfect. The color, font, barcode"
> "It is simple and obvious"
>
> Read more: https://upload.wikimedia.org/wikipedia/commons/0/0f/
> Wikimedia_Brands_Community_Perceptions_Report_2016.pdf
> 
> https://meta.wikimedia.org/wiki/Communications/Wikimedia_
> brands/Perceptions/2016
>
>
> Best
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Controversy around Wikimania talks

[David Cuenca Tudela]

> what is the function of all the policies when they so obviously are
hardly worth the bits they consist of.

Policies are not commands that have to be blindly obeyed. They are a
general framework for the admins and users to approach the blurry or
defined limits, but of course some autonomy is needed to decide in edge or
uncertain cases. That means to take decisions that eventually will make
some people (like you in this case) unhappy.

I generally prefer to have admins with more autonomy than with less, more
specifically because when there are less regulations the type of people
involved tend to create in general a more amiable climate, and I think that
has been the case so far for Wikidata. If you are complaining about the
health of the community, then you should be careful with the things you
seem to wish for (regulations, processes, etc), because it can backfire and
have the opposite effect.

OTOH, if Commons is going to have its own structured database and those
items might qualify there with less opposition, why to make such a big deal
about it?


Regards,
Micru



On Thu, Aug 11, 2016 at 1:05 PM, Gerard Meijssen 
wrote:

> Hoi,
> What is trivial. I find that the disappointment in what our policies bring
> us amounts to a lot. Effectively it is only who you are that determines
> what you get away with. The quality of arguments are easily dismissed with
> "I have a different opinion" (that is NOT an argument.
>
> When you look at my credentials you will agree that I have been involved
> heavily in our project and for all the wrong reasons I am disengaging. I
> object to the way conflicts are handled. I object to the collective shrug
> of not caring, not wanting to be involved of our admins. In the end it does
> not matter.
>
> Wikidata is a very important project that is underserved in attention to
> its community. It just sort of happens and the statistics are so good that
> we do not even look at the relative health of Wikidata as a community.
>
> It is one thing for stewards to say what they say, it is one thing for
> individual administrators to say what they say but when the situation goes
> rogue, when arguments presented by others do not get the collective
> attention of the administrative processes that are in place. When the
> allegation that admins do as they please is just a determination it becomes
> obvious to raise the question what is the function of all the policies when
> they so obviously are hardly worth the bits they consist of.
> Thanks,
>   GerardM
>
> On 1 August 2016 at 02:05, Vi to  wrote:
>
>> [Note: I'm using the last message for a cumulative reply]
>>
>> Wikidata has 16k active users, 66 admins, 3 'crats, with a pretty active
>> community. This thread has turned into a weird mix of inclusionism vs.
>> deletionism catfight + a request to undelete some contents in a specific
>> project + a series of off-topics. The first part might fit the scope of
>> this list (though is *so* boring), same for the third one. Instead, the
>> second part must be discussed on Wikidata following local policies.
>>
>> Finally, just to clarify: undeletions by stewards are completely out of
>> our mission and policies (I, for one, would rather intervene to delete ^^),
>> same for the staffers. No chances to overrule a community for such trivial
>> reasons.
>>
>> Vito
>>
>> 2016-08-01 0:36 GMT+02:00 Info WorldUniversity <
>> i...@worlduniversityandschool.org>:
>>
>>> If, as Jimbo Wales' wrote the purpose of Wikipedia involves imagining
>>> "a world in which every single person on the planet is given free access to
>>> the sum of all human knowledge. That's what we're doing.—Jimbo Wales
>>> [3]
>>> "
>>> https://en.wikipedia.org/wiki/Wikipedia:Purpose ...
>>>
>>> and the mission of the Wikimedia Foundation includes:
>>>
>>> "The mission of the Wikimedia Foundation is to empower and engage people
>>> around the world to collect and develop educational content under a free
>>> license  or in the
>>> public domain, and to disseminate it effectively and globally.
>>>
>>> In collaboration with a network of chapters
>>> , the Foundation
>>> provides the essential infrastructure and an organizational framework for
>>> the support and development of multilingual wiki projects
>>>  and other endeavors
>>> which serve this mission. The Foundation will make and keep useful
>>> information from its projects available on the Internet free of charge
>>> , in perpetuity."
>>>
>>> https://wikimediafoundation.org/wiki/Mission_statement
>>>
>>> I'd vote as a Wikidata community member for aggregating conferences and
>>> courses in all languages with machine and wiki (human) processes. Whether
>>> this is best done in Wikidat

Re: [Wikidata] first Commons prototype is live \o/

[David Cuenca Tudela]

Fantastic! Is the data from the mediainfo supposed to appear on the file
page? Or is it meant to be independent?

Cheers,
Micru

On Thu, Jul 28, 2016 at 6:41 PM, Info WorldUniversity <
i...@worlduniversityandschool.org> wrote:

> So GREAT! :)
>
> Scott
>
> On Thu, Jul 28, 2016 at 9:21 AM, Luca Martinelli  > wrote:
>
>> Oh, sing osannah! :D
>>
>> L.
>>
>> 2016-07-28 18:10 GMT+02:00 Magnus Manske :
>> > YES!
>> >
>> > On Thu, Jul 28, 2016 at 5:02 PM Lydia Pintscher
>> >  wrote:
>> >>
>> >> Hey everyone :)
>> >>
>> >> I just posted exciting news about structured data support for Commons
>> >> at
>> >>
>> https://commons.wikimedia.org/wiki/Commons_talk:Structured_data#It.27s_alive.21
>> >> *SPOILER* There is a first demo system now! *SPOILER*
>> >>
>> >> Cheers
>> >> Lydia
>> >>
>> >> --
>> >> Lydia Pintscher - http://about.me/lydia.pintscher
>> >> Product Manager for Wikidata
>> >>
>> >> Wikimedia Deutschland e.V.
>> >> Tempelhofer Ufer 23-24
>> >> 10963 Berlin
>> >> www.wikimedia.de
>> >>
>> >> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
>> >>
>> >> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
>> >> unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
>> >> Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.
>> >>
>> >> ___
>> >> Wikidata mailing list
>> >> Wikidata@lists.wikimedia.org
>> >> https://lists.wikimedia.org/mailman/listinfo/wikidata
>> >
>> >
>> > ___
>> > Wikidata mailing list
>> > Wikidata@lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/wikidata
>> >
>>
>>
>>
>> --
>> Luca "Sannita" Martinelli
>> http://it.wikipedia.org/wiki/Utente:Sannita
>>
>> ___
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>
>
>
> --
>
> - Scott MacLeod - Founder & President
>
> - http://worlduniversityandschool.org
>
> - 415 480 4577
>
> - PO Box 442, (86 Ridgecrest Road), Canyon, CA 94516
>
> - World University and School - like Wikipedia with best STEM-centric
> OpenCourseWare - incorporated as a nonprofit university and school in
> California, and is a U.S. 501 (c) (3) tax-exempt educational organization.
>
>
> World University and School is sending you this because of your interest
> in free, online, higher education. If you don't want to receive these,
> please reply with 'unsubscribe' in the body of the email, leaving the
> subject line intact. Thank you.
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] weekly summary #201

[David Cuenca Tudela]

On Mon, Mar 21, 2016 at 12:54 PM, Lydia Pintscher <
lydia.pintsc...@wikimedia.de> wrote:

>
>- Started working on improving input for geocoordinates and dates
>(changing the advanced settings)
>
>
Is celestial coordinate support included in this?
https://phabricator.wikimedia.org/T127950

Cheers,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Status and ETA External ID conversion

[David Cuenca Tudela]

Markus, you are not the only one, I am also skeptical about the criteria
used. For me the main problem is perhaps the misunderstanding that the
"external identifier" label creates, actually what I was expecting was
something more like "external references", a place where to put all the
external sources to wikidata in one place. But we'll see how it goes.

Cheers,
Micru

On Sat, Mar 5, 2016 at 2:54 PM, Markus Krötzsch <
mar...@semantic-mediawiki.org> wrote:

> On 05.03.2016 14:45, Lydia Pintscher wrote:
>
>> On Sat, Mar 5, 2016 at 1:28 PM Markus Krötzsch
>> mailto:mar...@semantic-mediawiki.org>>
>> wrote:
>>
>> Thanks, Katie. I see that the external ID datatype does not work as
>> planed. At least I thought the original idea was to clean up the UI by
>> moving hard-to-understand string IDs to a separate section. From the
>> discussions on these pages, I see that the community uses criteria
>> that
>> are completely unrelated to UI aspects, but have something to do with
>> the degree to which the property encodes a one-to-one mapping. I guess
>> this is also valid, but won't be useful for UI purposes. I will need
>> to
>> use another solution for my case then.
>>
>>
>> Give it another 2 to 3 weeks and it'll get there. More and more editors
>> are exposed to the separation in the UI now and start noticing the ones
>> that intuitively should be moved into the identifier section.
>>
>
> Ok, let's see what happens. I am not saying that the other criteria
> applied now in the discussions are bad. It's just another use of the
> datatype than I would have expected.
>
> Markus
>
>
>> Cheers
>> Lydia
>> --
>> Lydia Pintscher - http://about.me/lydia.pintscher
>> Product Manager for Wikidata
>>
>> Wikimedia Deutschland e.V.
>> Tempelhofer Ufer 23-24
>> 10963 Berlin
>> www.wikimedia.de 
>>
>> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
>>
>> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
>> unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
>> Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.
>>
>>
>> ___
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Units are live! \o/

[David Cuenca Tudela]

Just created "area" after two years of waiting! yay! congratulations! \o/

On Wed, Sep 9, 2015 at 11:08 PM, Lydia Pintscher <
lydia.pintsc...@wikimedia.de> wrote:

> On Wed, Sep 9, 2015 at 9:49 PM, Lydia Pintscher
>  wrote:
> > Hey everyone :)
> >
> > As promised we just enabled support for quantities with units on
> > Wikidata. So from now on you'll be able to store fancy things like the
> > height of a mountain or the boiling point of an element.
> >
> > Quite a few properties have been waiting on unit support before they
> > are created. I assume they will be created in the next hours and then
> > you can go ahead and add all of the measurements.
>
> For anyone who is curious: Here is the list of properties already
> created since unit support is available:
>
> https://www.wikidata.org/w/index.php?title=Special:ListProperties/quantity&limit=50&offset=103
> and here is the list of properties that were waiting on unit support:
> https://www.wikidata.org/wiki/Wikidata:Property_proposal/Pending/2
> Those should change over the next hours/days.
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> Product Manager for Wikidata
>
> Wikimedia Deutschland e.V.
> Tempelhofer Ufer 23-24
> 10963 Berlin
> www.wikimedia.de
>
> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
>
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
> unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
> Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Goal: Establish a framework to engage with data engineers and open data organizations

[David Cuenca Tudela]

Hello Quim,

There was always the issue of where to publish datasets from partner
organisations like a http://datahub.io/

Is that being considered in this new iteration?

Cheers,
Micru

On Wed, Jul 1, 2015 at 6:19 PM, Romaine Wiki  wrote:

> Hello Quim,
>
> We have in Belgium (as Wikimedia Belgium) a partner organisation who is
> together with us working with cultural institutions to get open datasets to
> be used in Wikidata.
>
> So yes, we are interested.
>
> Greetings,
> Romaine
>
> 2015-07-01 17:31 GMT+02:00 Quim Gil :
>
>> Hi, it's first of July and I would like to introduce you a quarterly goal
>> that the Engineering Community team has committed to:
>>
>> Establish a framework to engage with data engineers and open data
>> organizations
>> https://phabricator.wikimedia.org/T101950
>>
>> We are missing a community framework allowing Wikidata content and tech
>> contributors, data engineers, and open data organizations to collaborate
>> effectively. Imagine GLAM applied to data.
>>
>> If all goes well, by the end of September we would like to have basic
>> documentation and community processes for open data engineers and
>> organizations willing to contribute to Wikidata, and ongoing projects
>> with one open data org.
>>
>> If you are interested, get involved! We are looking for
>>
>> * Wikidata contributors with good institutional memory
>> * people that has been in touch with organizations willing to contribute
>> their open data
>> * developers willing to help improving our software and programming
>> missing pieces
>> * also contributors familiar with the GLAM model(s), what works and what
>> didn't work
>>
>> This goal has been created after some conversations with Lydia Pintscher
>> (Wikidata team) and Sylvia Ventura (Strategic Partnerships). Both are on
>> board, Lydia assuring that this work fits into what is technically
>> effective, and Sylvia checking our work against real open data
>> organizations willing to get involved.
>>
>> This email effectively starts the bootstrapping of this project. I will
>> start creating subtasks under that goal based on your feedback and common
>> sense.
>>
>> --
>> Quim Gil
>> Engineering Community Manager @ Wikimedia Foundation
>> http://www.mediawiki.org/wiki/User:Qgil
>>
>> ___
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] ISRC property needs NEW sister property to hold sound recording length

[David Cuenca Tudela]

Hi Thad,
To import "length of time" you would need to use the quantity with units
datatype, which unfortunately is not available yet:
https://www.wikidata.org/wiki/Wikidata:Development_plan#Quantities_with_units

Cheers,
Micru

On Tue, Jun 23, 2015 at 9:18 PM, Thad Guidry  wrote:

> Now that we have the new ISRC property (International Standard Recording
> Code) ...
>
> Can someone propose a new property to capture the "length of sound
> recording' with a property ?  (if another property doesn't exist, from my
> cursory inspection, it does not exist)
>
> See ISRC FAQ snippet below from
> https://www.usisrc.org/faqs/assignment.html
>
> *Q. When do changes in a recording merit a new ISRC?*
>
> A new ISRC must be issued when:
>
>- A sound recording is re-mixed or edited.
>- If a new fade changes the length of a track by more than 10 seconds.
>- Edits that change the length of a sound recording by more than 10
>seconds (playing time is measured from the first recorded modulation to the
>last recorded modulation).
>- A previously released sound recording is partially used as part of a
>compilation.
>- A 'full restoration' of a historical recording is performed by
>re-mastering, re-pitching, re-equalizing, de-noising or de-clicking a sound
>recording to meet contemporary quality standards. The registrant of the
>recording has discretion when making the determination between full
>re-mastering (sound restoration) and simple re-mastering (reproduction
>without sound restoration).
>
> Thad
> +ThadGuidry 
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>


-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Wikimania talk input

[David Cuenca Tudela]

Of course it would be nice to speak about arbitrary access and how wikidata
can be used to store references.

Also how to discover which properties to use, but perhaps it is better to
ask, is it easy to discover which properties to use?
At the moment the list is either manual, or all properties together in one
page, it would be nice to have a better property classification system for
Wikimania.
https://phabricator.wikimedia.org/T59843

And other nice projects that happened during the year :)

Cheers,
Micru

On Wed, Jun 10, 2015 at 10:34 AM, Andy Mabbett 
wrote:

> 2015-06-10 8:04 GMT+01:00 Lydia Pintscher :
>
> > I'll be giving a talk about the state of Wikidata at Wikimania in
> > Mexico City. Is there anything you think I should definitely talk
> > about?
>
> * How new properties can be proposed and created
>
> * Magnus' brilliant tools, to make life easier
>
> * How partner orgs can integrate their data, or identifiers
>
> --
> Andy Mabbett
> @pigsonthewing
> http://pigsonthewing.org.uk
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Data amplitude and representation

[David Cuenca Tudela]

Daniel, thanks for your example, it looks very good!

On Mon, Jun 1, 2015 at 3:31 PM, Daniel Kinzler 
wrote:

> If I understand you correctly, your are looking for a way to describe
> different
> meanings or facettes of a *word*, building clusters based on what other
> concept
> each of these meanings is related to.
>
> Since Wikidata does not (yet) deal with words at all, we can only defer
> this
> until we do (see the Wikidata/Wiktionary proposal). But others have done
> this:
> have a look at the "Wortschatz" project by the University of Leipzig:
>
> http://corpora2.informatik.uni-leipzig.de/res.php?corpusId=deu_newscrawl_2011&word=Bach
>
> The graph at the bottom shows clusters of collocations for each
> meaning/facette.
> It's a bit hard to find good examples though, usually one meaning is very
> dominant.
>
> Am 01.06.2015 um 15:14 schrieb David Cuenca Tudela:
> >
> > Hi Leila
> >
> > On Mon, Jun 1, 2015 at 9:32 AM, Leila Zia  > <mailto:le...@wikimedia.org>> wrote:
> >
> > Please correct me if I'm wrong: it seems to be tne case that these
> questions
> > are more about the interfaces and technologies built on top of
> Wikidata, not
> > so much about Wikidata itself (except for the point that the
> fundamental
> > data should exist in Wikidata).
> >
> >
> > Yes, in a way it is more about representation that anything else, but it
> also
> > has to do with the conceptual framework. In the current organization it
> is
> > assumed that I want to know about an specific Q item, whereas in my
> thinking
> > about signals I would prefer to have an overview of all items that are
> related
> > to a keyword.
> >
> > For instance if I enter Chopin, either I have to select one item from a
> list or
> > I have to perform a search, there is no middle way of displaying an
> overview of
> > all items grouped by the kind of relationship that they might have to the
> > keyword chopin. In a way it is a bit like creating a disambiguation page
> on the
> > fly, with the added difficulty of grouping elements that belong
> together. For
> > instance if I search Bach, it would make sense to group people with the
> string
> > "bach" related to the same family together, and divide it by topic, like
> a sort
> > of disambiguation page for data:
> > https://en.wikipedia.org/wiki/Bach_%28disambiguation%29
> >
> > What is difficult is to find an automatic arrangement that works for most
> > situations, or explore a different way of creating data disambiguation
> pages,
> > perhaps based on current disambiguation items. Is there any way to make
> this
> > item more useful with some visualization of items it disambiguates?
> > https://www.wikidata.org/wiki/Q107809
> >
> > Cheers,
> > Micru
> >
> >
> > ___
> > Wikidata mailing list
> > Wikidata@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikidata
> >
>
>
> --
> Daniel Kinzler
> Senior Software Developer
>
> Wikimedia Deutschland
> Gesellschaft zur Förderung Freien Wissens e.V.
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
Etiamsi omnes, ego non
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Data amplitude and representation

[David Cuenca Tudela]

Hi Leila

On Mon, Jun 1, 2015 at 9:32 AM, Leila Zia  wrote:

> Please correct me if I'm wrong: it seems to be tne case that these
> questions are more about the interfaces and technologies built on top of
> Wikidata, not so much about Wikidata itself (except for the point that the
> fundamental data should exist in Wikidata).
>
>
Yes, in a way it is more about representation that anything else, but it
also has to do with the conceptual framework. In the current organization
it is assumed that I want to know about an specific Q item, whereas in my
thinking about signals I would prefer to have an overview of all items that
are related to a keyword.

For instance if I enter Chopin, either I have to select one item from a
list or I have to perform a search, there is no middle way of displaying an
overview of all items grouped by the kind of relationship that they might
have to the keyword chopin. In a way it is a bit like creating a
disambiguation page on the fly, with the added difficulty of grouping
elements that belong together. For instance if I search Bach, it would make
sense to group people with the string "bach" related to the same family
together, and divide it by topic, like a sort of disambiguation page for
data:
https://en.wikipedia.org/wiki/Bach_%28disambiguation%29

What is difficult is to find an automatic arrangement that works for most
situations, or explore a different way of creating data disambiguation
pages, perhaps based on current disambiguation items. Is there any way to
make this item more useful with some visualization of items it
disambiguates?
https://www.wikidata.org/wiki/Q107809

Cheers,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] Data amplitude and representation

[David Cuenca Tudela]

Hi,

I am investigating some concepts about signal processing and relating them
to data manipulation. It is somehow difficult because the way computer
scientists relate to concepts is very dogmatic, something is either black
or white, however I have not found much on "things that under certain
circumstances can be considered black-ish, and under another set of
circumstances can be considered white-ish"
http://freethoughtblogs.com/singham/2012/06/25/shades-of-grey-optical-illusion/

In signal processing there is the concept of amplitude which is just the
signal strength. For humans language is like an amplitude communication
process where the receiver picks up not only the signal, but also its
amplitude depending on context, awareness, previous knowledge, etc. factors
which in turn can be considered waves being processed by the ontological
biological-organizational complex, the body-mind.

It is tough to describe that a certain concept might have a certain
amplitude in some situations and other amplitude in other situations, and
perhaps even harder to make a human interface for it.
Has anyone attempted it in the past? If Q items are not static entities,
what is the best way to convey that they are not? And is it possible or
desirable at all?

Perhaps these questions are more suitable for a Wikidata 2.0, or perhaps it
is already doable, who knows.

Any thoughts?

Cheers,
Micru
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata