Hello James, thanks for the useful pointer about completeness on Wikidata!
Just to clarify, when P299 has the property P2429 with the value "is complete", does it mean that Wikidata already has all countries with all their ISO 3166-1 numeric code connected by P299 (as in https://en.wikipedia.org/wiki/ISO_3166-1#Current_codes)? For the more fine-grained usage, I agree that that could be also a way to write completeness statements on Wikidata. Another way is to write completeness statements in RDF. We are indeed exploring on how to best provide a syntax for completeness statements on Wikidata. On the other hand, on the abstract level one possible way to represent completeness statements is by using BGPs: we are complete for the graph captured by the BGP. Regards, Fariz On Wed, Mar 2, 2016 at 12:09 PM, James Heald <[email protected]> wrote: > Note that there is a property P2429 which can be used to record the > completeness expected for a particular property. > > Approved values so far are: > * Q21874050 -- is complete > * Q21873974 -- aspire to eventually complete > * Q21873886 -- will never be complete > > At the moment this information can be recorded on a whole property basis, > eg for P299 "ISO 3166-1 numeric code", P2429 has the value "is complete". > https://www.wikidata.org/wiki/Property:P299 > > One way to allow a more fine-grained usage would be to define a new > property "is the object of" on items, so that e.g. > > Q15700818 "Grade I listed building" -> "is the object of" -> P1435 > "heritage status" > > or > > Q167654 "Frans Hals" -> "is the object of" -> P170 "creator" > > One could then attach P2429 to such statements as a qualifier, to indicate > that we aspire to a complete tabulation of Grade I listed buildings, or > works by Frans Hals. > > -- James. > > > > > > > On 02/03/2016 10:26, Jane Darnell wrote: > >> I had no problem reading your mail. Thinking it over, this would also be a >> way to track the connection of dictionaries in Wikisource to items in >> Wikidata. So for example, Wikisource has lots of imported articles from >> the >> Encyclopedia Britannica 1911, and it would be nice to track >> 1) Completeness in Wikisource (how many articles are complete in section >> "A"?) >> 2) Completeness of matchups in section "A" to articles in English >> Wikipedia >> (how many subjects of Wikisource EB 1911 "A" articles have items on >> Wikidata with a link to English Wikipedia) >> >> Once you have all that, it would be interesting to know about the relative >> completeness of >> a) Places >> b) Events >> c) Male people >> d) Female people >> >> etc. >> >> On Wed, Mar 2, 2016 at 10:57 AM, Fariz Darari <[email protected]> wrote: >> >> Hello Jane, >>> >>> thank you! Yes, that sounds like a suitable use case for COOL-WD! >>> >>> PS: Pardon the formatting of the announcement email, somehow the >>> linebreaks are vanished :( >>> I am now experimenting with another email client, hopefully the >>> linebreaks >>> are there. >>> >>> Regards, >>> Fariz >>> >>> On Wed, Mar 2, 2016 at 10:38 AM, Jane Darnell <[email protected]> wrote: >>> >>> Wow this sounds great! I would love to use this for oeuvre catalogs of >>>> top painters! The latest Rembrandt catalog is complete on Wikidata, as >>>> well as a few other ones, but older ones are not yet complete. This >>>> could >>>> be a great tracking tool for WikiProjects. >>>> >>>> On Wed, Mar 2, 2016 at 10:17 AM, Darari Fariz < >>>> [email protected]> wrote: >>>> >>>> Hello Wikidata community! Wikidata is a great platform for collecting >>>>> information, and the high quality work of many authors yields very >>>>> reliable >>>>> information. Still, a challenge for users of Wikidata is that there is >>>>> no >>>>> way to see whether *all* data on a certain topic is in Wikidata. For >>>>> instance, it is easy to see that Malia and Sasha are children of >>>>> Obama, but >>>>> there is no way to specify that these are all his children. More >>>>> generally, >>>>> Wikidata stores many facts, but it stores no information about which >>>>> topic >>>>> it contains all facts. Today we are happy to share with you a prototype >>>>> that allows to add and manage such completeness information, and would >>>>> be >>>>> happy to get your feedback on how useful you consider this tool, or >>>>> where >>>>> you see space for improvements. With our prototype, called COOL-WD >>>>> (Completeness Tool for Wikidata), one can: 1. See completeness >>>>> statements >>>>> for Wikidata facts 2. Add, remove, aggregate and filter completeness >>>>> statements 3. See how completeness statements allow conclusions about >>>>> the >>>>> completeness of SPARQL queries over Wikidata. COOL-WD is available at >>>>> http://cool-wd.inf.unibz.it/ and a 3-min demo video can be found at >>>>> http://cool-wd.inf.unibz.it/coolwd-hd.mp4 It employs various >>>>> libraries, >>>>> most importantly GWT, Apache Jena, SQLite and the Wikidata API. The >>>>> formal >>>>> background and description of the tool including an indexing technique >>>>> for >>>>> completeness statements have been accepted as a research paper at ICWE >>>>> 2016 >>>>> (http://icwe2016.inf.usi.ch/) available to download at: >>>>> http://bit.ly/1VOsRCH Below are some naive ideas of how completeness >>>>> could be useful to users: > Use Case 1: Rido is a geographer who would >>>>> like >>>>> to contribute to Wikidata about the administrative divisions of >>>>> regions. He >>>>> cares so much about data quality, especially data completeness, and is >>>>> collaborating with Simon, another geographer. However, when completing >>>>> data >>>>> on Wikidata, there is currently no way to mark which data is complete. >>>>> Rido >>>>> and Simon must make these notes about completeness manually in, say, a >>>>> Google Doc. Worse still, the effort from Rido and Simon to complete >>>>> data >>>>> could not be appreciated by Wikidata users since to the users’ eyes, >>>>> there >>>>> is no difference between complete data and incomplete data on Wikidata. >>>>> Demo: Wikidata is complete for all administrative divisions of Saxony ( >>>>> http://cool-wd.inf.unibz.it/?p=Q1202) > Use Case 2: Jen is a developer >>>>> of a moviegoer application. She usually integrates data between >>>>> multiple >>>>> sources including Wikidata. If some movies on Wikidata have >>>>> completeness >>>>> statements, she might optimize her application to not search in other >>>>> data >>>>> sources for those movies. Demo: So, when her app is asking on COOL-WD >>>>> at >>>>> http://cool-wd.inf.unibz.it/?p=query for cast and screenwriters of the >>>>> movie Before Sunset (http://cool-wd.inf.unibz.it/?p=Q652186): SELECT * >>>>> WHERE { wd:Q652186 wdt:P161 ?c . wd:Q652186 wdt:P58 ?s } Her app gets >>>>> not >>>>> only query answers but also the completeness information of her query. >>>>> We >>>>> are looking forward to your feedback! Best, Fariz, Simon, Rido, and >>>>> Werner >>>>> Free University of Bozen-Bolzano, Italy >>>>> >>>>> _______________________________________________ >>>>> Wikidata mailing list >>>>> [email protected] >>>>> https://lists.wikimedia.org/mailman/listinfo/wikidata >>>>> >>>>> >>>>> >>>> _______________________________________________ >>>> Wikidata mailing list >>>> [email protected] >>>> https://lists.wikimedia.org/mailman/listinfo/wikidata >>>> >>>> >>>> >>> _______________________________________________ >>> Wikidata mailing list >>> [email protected] >>> https://lists.wikimedia.org/mailman/listinfo/wikidata >>> >>> >>> >> >> >> _______________________________________________ >> Wikidata mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/wikidata >> >> > > _______________________________________________ > Wikidata mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikidata >
_______________________________________________ Wikidata mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata
