Structured Data on Commons Part Five - Other Statements

Originally published at: https://space.wmflabs.org/2019/09/17/structured-data-on-commons-part-five-other-statements/

With depicts statements available to make the most basic claims about files on Commons, it was time to make more fully-formed statements. The Structured Data on Commons development team developed and released the first level of support for types of statements other than depicts.

“Other statements” offer expanded data about a file. Wikidata properties such as creator (P170), location (P276), Commons quality assessment (P6731), license (P257), and more. For an example of depicts plus other statements, here’s a file that is an image of sugar cubes:

Dietmar Rabich / Wikimedia Commons / “Würfelzucker — 2018 — 3564” / CC BY-SA 4.0


This is the representation of the file in structured data, using depicts with qualifiers in combination with other statements:

Structured data for “Würfelzucker — 2018 — 3564”

This information is “machine-readable,” meaning that people can write software to interact with it, soon there will be the power to query the data, and a host of other potential uses. Lucas Werkmeister wrote a separate blog covering some of the possibilities of Structured Data on Commons. Importantly, all of this information is multilingual as well, as previously most data was restricted to English when used in templates and categories.

Taken as a whole, depicts and other statements, contributors to Wikimedia Commons can now begin to fully contribute structured data. The development team continues to work on support for different data beyond words, such as geocoordinates, time stamps, and other such types. Additional support for community tools such as Lua functionality is making progress as well. After this multi-year effort, the partners involved in the project can start the work of building a more accessible Commons at last.

Previously: Part Four – Depicts Statements

4 Likes

I am not sure here, so when would location (P276) be a better choice than properties like location of the point of view (7108) and coordinates of the point of view (P1259)? Because if the location is depicted, then surely depicts should be used?

1 Like

I can imagine a situation - say a military parade, picture taken from a specific location. Then depicts would say Military parade, and location would say the street or smth. But this is probably a relatively uncommon situation.

Great news!
Will this be added to the ISA tool ? (for now it only allows isolated items).

In that case, why would you prefer location (P276) over location of the point of view (P7108) (which is a property especially designed for this use case)? If you are trying to state the location of the parade, then it should be as a qualifier on the depicts statement (since there can be many things on different streets in the same picture).

I meant indeed the location of the parade (the liocation of the point of view is a different thing). Setting it as qualifyer to depicts works fine for me.

These kinds of questions around data modeling (which properties to use? why?) are indeed still very new and unresolved, and discussed by the Wikimedia Commons community at https://commons.wikimedia.org/wiki/Commons:Structured_data/Modeling, see for instance https://commons.wikimedia.org/wiki/Commons:Structured_data/Modeling/Location. If you have any questions or opinions, please also share them there, to help the community figure out best practices!