Commons:Structured data/Get involved/Feedback requests/Statements 2

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search


A core feature of structured data is providing a machine-readable metadata option for the file description page. This metadata feature uses properties such as copyright status, licensing, and ways to describe file from Wikidata.  The statements about the copyright status, etc., are displayed and edited on Commons. Editing metadata is compatible with RevisionDeletion, so all administrative tools will be available though they are not shown in these mockups. No existing templates, text, formatting, or anything else will change from the existing file page as part of the development team's work.

What's new[edit]

Updates from our last consultation:

  • In the previous version, not all concepts were shown as links to their respective Wikidata pages. This is fixed now.
  • We’re experimenting with different wording. The main license statement is now called “file terms of use”.
  • The tabs for Wikitext content and metadata (respectively called 'File information' and 'Structured data' for the purposes of this discussion) are now true tabs instead of anchor links, which should reduce/eliminate the occurrence of super long pages. This will also ensure that Depicts statements are closer to the image to aid in adding/editing Depicts statements.
  • Retooled usage rights and usage justification. In this model, usage justification can be used to provide a number of details, including specifics about why a particular depicted element might be public domain. This is accomplished via what we’re calling “rights statement codes”, which are essentially Commons PD template names (but existing Wikidata items for these templates specifically refer to them is templates, which is a bit inaccurate, so we might need new items on Wikidata to refer to the codes themselves).

Frequently asked questions from last time[edit]

Is this final?

Not at all. We are just putting ideas out there to provide a starting point for community discussion and decisions.

Where will all the new properties live?

With the current state of Wikibase Federation, the new properties will have to be created on Wikidata.

Why does it look differently than Wikidata?

Wikidata's UI is in some ways barebones, and in some ways pretty specific for its purpose as a model for (almost) everything, and it's not exactly comfortable for all users. We have the opportunity to make the design fit the specific use cases of Commons. This is all still a work in progress as we, along with the community, delve further into what it means to use Wikibase in a multimedia-centric application. Also, WMF and WMDE are working together to establish similar visual language for the future, so some ideas that start here on Commons may make their way to Wikidata later.

What will happen with licensing templates?

We have no plans to touch, alter, or remove existing licensing templates. There will be a question of exactly what to do with them once structured licenses arrive, but that will be up to the community to decide.

Questions to the community for this round[edit]

We (the Structured Data team) are providing these examples as a starting point. But ultimately our users are the ones who will have to live with it so we need your input and, perhaps more importantly, your consensus. This is a major new element to Commons and it is imperative that the community is proactive in the decision making process.

With that said, we have some questions about this proposed model:

Does this cover all reasonable cases you can think of?

If not, please offer some examples files or Q items where this wouldn’t work. Extreme edge cases should be considered but not necessarily required.

Do you want Structured Data to replace current license systems, or just supplement them?

The original idea was to add structured data to improve the machine-readable use case for algorithms and bots (search, analysis, etc.). In the previous consultation there was some concern about ease of readability/explanation for ordinary humans. Is this a requirement, since we already have human-readable templates in place?

If this doesn’t work for you, how would you like it to work?

Specific counter-proposals are welcome and encouraged.


Pokemon airplane[edit]

Original file: PokemonJA8288.JPG

Here is an example of an image that depicts things that are in copyright, but the image itself is freely licensed as the use of copyrighted material is considered de minimis.

Museum piece[edit]

Original file: Chinese_-_Camel_-_Walters_492383_-_Profile.jpg

This example has an object on display in a museum. The image was donated so it has an OTRS permission, as well as crediting the donating institution.

New example: Timeline[edit]

This file is an example of a file that remixes many other files. This complicates copyright, licensing, and attribution.