Wikidata

Wikidata:Property proposal/Sister projects

< Wikidata:Property proposal


Property proposal: Generic Authority control Person Organization
Creative work Place Sports Sister projects
Transportation Natural science Computing Lexeme

See also edit

This page is for the proposal of new properties.

Before proposing a property

  1. Search if the property already exists.
  2. Search if the property has already been proposed.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
  4. Select the right datatype for the property.
  5. Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
  6. Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.

Creating the property

  1. Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
  2. Creation can be done 1 week after the creation of the proposal, by a property creator or an administrator.
  3. See property creation policy.

On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2024/04.


Wikipedia edit

Wiktionary edit

Wikiquote edit

Wikisource edit

Wikivoyage edit

Wikinews edit

Wikiversity edit

Wikibooks edit

Wikispecies edit

See Wikidata:WikiProject Taxonomy; Wikidata:Wikispecies; wikispecies:Wikispecies:Project Wikidata

Wikimedia Incubator edit

Wikimedia Commons edit

image revision-id edit

   On hold
DescriptionQualifier to inidicate the particular revision of an image that a statement refers to
Data typeString
Domainstatements with value: media
Allowed values\d+
Example 1File:Pigot and Co (1842) p2.138 - Map of Lancashire.jpg (revision-sensitive statement) → 279847594
Example 2File:Larousse,_Plan_de_Paris,_1900_-_David_Rumsey.jpg (revision-sensitive statement) → 180884966
Example 3File:1768_Jeffreys_Wall_Map_of_India_and_Ceylon_-_Geographicus_-_India-jeffreys-1768.jpg (revision-sensitive statement) → 345654849
Planned useTo indicate which revision of a map image has been georeferenced on Commons MapWarper. But further use-cases are likely to emerge.
See alsoWikimedia import URL (P4656)

Motivation edit

Sometimes it is important to be able to indicate which particular revision of a Commons image a Wikidata or SDC statement refers to. For example, georeferencing information will fail to be correct if an image has been cropped. A mechanism is therefore necessary to be able to specify a particular version of a Commons file. Jheald (talk) 13:16, 14 August 2019 (UTC)[reply]

Discussion edit

I marked this proposal as on hold. Currently we have two solutions:

  • Wait phab:T28741 to be fixed so file versions have unique identifiers
  • Create a property "image timestamp", but 1. we still does not have the datatype unless we store timestamp as string and 2. timestamp may still be not unique.

--GZWDer (talk) 23:20, 28 May 2020 (UTC)[reply]

depicts lexeme form edit

   On hold
Descriptionlexeme form depicted in the media file
Data typeForm
DomainCommons images
Example 1File:Bandera_de_los_Treinta_y_Tres_Orientales.JPG → L562031#F1 invalid ID (L562031#F1)
Example 2File:Protests_in_Puerta_del_Sol,_Madrid_-_Ahora_o_Nunca.jpg → L56980#F1 invalid ID (L56980#F1)
Example 3File:BULLSHIT_rubber_stamp_(mirrored)_on_the_desk_of_a_street_photographer.jpg → L299205#F1 invalid ID (L299205#F1)
Example 4File:Mrs._Susanna_Morin_Swing_160028v.jpg → L9656#F1 invalid ID (L9656#F1)
Example 5File:Vignet_Ende.jpg → L29356#F1 invalid ID (L29356#F1)
See alsodepicts (P180)

Motivación edit

In Wikimedia Commons there are thousands of images depicting lexemes (a few of them: c:Category:Images by text, not categorised by language yet). Creating a property to indicate the lexemes depicted in a file would be great (IMHO) with regard to structuring linguistic data in media files. This was posted here. Apparently this was also proposed here a few months ago. strakhov (talk) 16:06, 16 July 2022 (UTC)[reply]

Discussion edit

  Comment To make this really useful, wouldn't it be better if it was "depicts lexeme form"? That way, we would capture more specifically what is on the image. Ainali (talk) 17:31, 16 July 2022 (UTC)[reply]

Is it only for qualifiers? What if we want to add it as a statement to 🆓 (Q87576444), for example? AntisocialRyan (Talk) 18:14, 17 July 2022 (UTC)[reply]
@AntisocialRyan: In fact this property is not intended to be used as a qualifier, but as a main statement. But not (at least not mostly) here, but in Wikimedia Commons, with media files. strakhov (talk) 16:10, 18 July 2022 (UTC)[reply]
Oh, I see, I misunderstood the examples.   Support. AntisocialRyan (Talk) 17:00, 18 July 2022 (UTC)[reply]
@ChristianKl: with regard to the description, mirroring P180's English description, "word visually depicted in an image, see also P180 for entities depicted" may work (?). But please feel free to propose a better one.
With regard to what's valid and what not... I guess it's valid when the lexeme form is depicted in the file. Since depicts (P180) has no indication for what's not valid and what is valid, I do not know why this one would need such prescription. Use of P180 is at the discretion of the user and common sense. Anyway, if you believe there are situations when a form is depicted in a file but using this property would not be valid, please indicate them here. strakhov (talk) 15:59, 18 July 2022 (UTC)[reply]
@Strakhov: How is a person supposed to decide whether to use items or lexemes to tackle descriptions? ChristianKl ❪✉❫ 10:23, 19 July 2022 (UTC)[reply]
@ChristianKl: When depicts (P180) should be used and when not IMO falls under the scope of that property (not this one's), and IMO we cannot decide that here (it's a bit tricky and there are still discussions in Commons about when it's appropiate and when not). Anyway, for example, IMHO in the file c:File:Spain Poznan Spain could by You.jpg it would ok using "depicts lexeme form" = L254265#F1, but it would not be ok using depicts (P180) -> Spain (Q29) (the image is not even taken in Spain, but in Poland). On the contrary, in the file c:File:A.L. Hickmann's geographisch-statistischer universel-Taschen-Atlas. 1900 (80112515).jpg IMHO would be "OK enough" using "depicts lexeme form" = L36513#F1 and depicts (P180) -> Spain (Q29) (both properties). strakhov (talk) 15:20, 19 July 2022 (UTC)[reply]
@Jheald: inscription (P1684) is for entities, concepts, etc, not text: it's language independent, it does not capture different languages being used nor synonyms in the same language (but it captures senses). I guess the problem with someone adding a lot of "depicts lexeme form" statements is not different to someone adding too many P180/P1684P6568 statements (that properties could also be abused). Anyway, if someone believes a big "please, do not try to transcribe full book/newspaper pages such as this one while using this property, try to use common sense" is needed... Cheers. strakhov (talk) 15:59, 18 July 2022 (UTC)[reply]
  Comment Sorry, I confused inscription (P1684) with inscription mentions (P6568). strakhov (talk) 14:51, 19 July 2022 (UTC)[reply]
You are absolutely right about this proposal not relating to that property. My bad, I did not consider that one. Well, I guess inscription (P1684) is good for transcribing full sentences (they can be added in the file description, file caption, as free text,... too). But it's pretty bad when it comes to crosslinking Wikidata Lexicographical data and Wikimedia Commons. I am interested in the latest. strakhov (talk) 15:20, 19 July 2022 (UTC)[reply]
  •   Support with the change to lexeme form, great! Ainali (talk) 08:32, 31 August 2022 (UTC)[reply]
  •   Support in thinking about this, this would open up some interesting possibilities. If we want to document information about what a word looks like written by hand, which can often differ from the digital representation, this would be useful for linking photos showing this to lexeme forms. I uploaded an example of سلسہ just now which I would add this property to if available.
 
 – The preceding unsigned comment was added by Middle river exports (talk • contribs).

Type of representation (nl) – (Please translate this into English.) edit

   Under discussion
DescriptionProperty to indicate the representation type as a qualifier for Wikimedia Commons SDC Depicts statements of such Wikidata items, indicating the media type of the media file as can be derived from its registered property in Wikidata, being different from P18 (image).
Representsimage (Q478798)
Data typeItem
DomainWikidata items having a media file, registered via a media property other than P18 and having an SDC Depicts statement in Wikimedia Commons requiring an SDC qualifier to the Wikidata item number to indicate the type of representation; the Q-number is derived from the original Wikidata media file linking property. Eventually those properties should all be properties used on Wikidata to register media files that are on Wikimedia Commons and being linked to the depicting Wikidata item.
Allowed valuesThe proposed property should be used as a qualifier. The base properties must be of subtype audio, image, or video. One typical example is video (P10) and video (Q98069877); image (P18) and disk image (Q592312) should not use the qualifier, for being redundant. It is the related Q-number that is to be used with the qualifier to the SDC depicts statement. The properties and related media types are interconnected in Wikidata via the reciproque properties Wikidata item of this property (P1629) and Wikidata property (P1687). You can find a list via this Wikidata Query.
Example 1File:Novosibirsk_Regional_Museum_at_night_2.jpgdepicts (P180)City Trade House (Q19908752)→nighttime view (Q28333482)
Example 2File:Google_Contacts_icon.svgdepicts (P180)Google Contacts (Q1537673)→computer icon (Q138754)
Example 3File:Aftakking KW linie 07.jpgdepicts (P180)Waver-Halle-Ninove Line (Q92417301)→plan (Q611203)
SourceYou can find a related discussion here, describing the necessity of this new property
Planned useWikimedia Commons media files should be made discoverable via Wikidata items and SDC (Structured data on Commons) P180 (depict) statements. Example query: Special:Search/P180:Q19908752.

Therefore Wikidata items and Wikimedia Commons media files should be bidirectionally linked. Typically Wikidata P18 (image) and SDC P180 (depict) are used to register such relationships.

Wikidata contains numerous items with statements referring to media files using properties other than P18 (image).

We need to qualify those depict statements in Wikimedia Commons SDC statements, referring to the Wikidata items that are not using P18, but other media file representation properties.

Wikimedia Commons requires SDC Depict statements media files to refer to such Wikidata items, with a qualifier having a (new) property “type of representation” and pointing to the (metadata) Wikidata item related to the original Wikidata property as represented by the type of image/media file.
Expected completenesseventually complete (Q21873974)
Robot and gadget jobsA bot is available to make immediate use of such new property, but is currently stopped, because the community made a remark that a proper qualifier should be used instead. We searched for such qualifiers but did not find any to be available. Therefore we need a new property, in order to let the bot restart its activity, after approval, using that specific new property. After the new property exists, all previously "wrong" statements can be migrated to the new property.
See alsodepicted format (P7984) but this can't be used as a qualifier, and is restricted to specific art objects. The new property is required to be very general.
Single-value constraintyes

Motivation edit

Currently (2024-04-04) GeertivpBot is blocked for Wikimedia Commons, because the required Wikidata property does not exist.

Till recently the SDC depicts statements in Wikimedia Commons were registered by the bot as (example) File:Novosibirsk_Regional_Museum_at_night_2.jpgdepicts (P180)nighttime view (Q28333482)of (P642)City Trade House (Q19908752), but the community of users believed that this is not consistent, and complicates the search of such objects. SDC depict statements should have the fysical object as target with a qualifier to indicate the type of representation.

Those statements should all be migrated into (example) File:Novosibirsk_Regional_Museum_at_night_2.jpgdepicts (P180)City Trade House (Q19908752)→nighttime view (Q28333482) once the new property is created.

This way the relationship between the Wikidata (depicts) item and the Wikimedia Commons media file can be bidirectionally documented in both platforms, using structured data statements.

To make it concrete: this is the Pywikibot script to automatically generate SDC Depict statements for Wikidata items with media files, which will use the new property. It will map the following Wikidata properties to Wikimedia Commons SDC Depict qualifier statements to the relevant Wikidata items: (Just let me know if you see any other combinations; I may have overlooked any?). Property image (P18) does not use this new property because it is registered as a "direct" Depict statement, without qualifier. 

video (P10): video (Q98069877)
image with color chart (P10093): image with color correction chart (Q109592922)
signature (P109): signature (Q188675)
image of grave (P1442): grave (Q173387)
route map (P15): road map (Q2298569)
logo image (P154): logo (Q1886349)
place name sign (P1766): place name sign (Q55498668)
plaque image (P1801): commemorative plaque (Q721747)
locator map image (P242): locator map (Q6664848)
montage image (P2716): collaging (Q170593)
icon (P2910): computer icon (Q138754)
sheet music (P3030): sheet music (Q187947)
image of design plans (P3311): plan (Q611203)
nighttime view (P3451): nighttime view (Q28333482)
flag image (P41): flag (Q14660)
spherical panorama image (P4640): spherical panorama (Q658252)
winter view (P5252): winter view (Q54819662)
schematic (P5555): diagram (Q959962)
image of interior (P5775): interior (Q2998430)
view (P8517): view (Q2075301)
aerial view (P8592): aerial view (Q56240104)
small logo or icon (P8972): favicon (Q2130)
coat of arms image (P94): coat of arms (Q14659)
page banner (P948): project:banners (Q22920576)
audio recording of the subject's spoken voice (P990): voice recording (Q53702817)

Geertivp (talk) 19:20, 4 April 2024 (UTC)[reply]

The above properties should be all properties used on Wikidata to register media files that are on Wikimedia Commons and linked to a Wikidata item. I have written a Wikidata Query that should basically reflect the above list correctly and completely. So I will have to make some corrections and additions in the Pywikibot script (I manually created the above list via actual "cases" that I found on Wikidata). Geertivp (talk) 08:08, 7 April 2024 (UTC)[reply]
Due to advancing insight, I have withdrawn the following properties:
image of backside (P7417): verso (Q9368452)
image of frontside (P7418): recto (Q9305022)
Geertivp (talk) 08:18, 9 April 2024 (UTC)[reply]

I have now corrected a number of entries in the above list, and added additional entries in the Pywikibot script, based on the query: 

cantilever sign (P10544)}} cantilever sign (Q1519903)
model image (P11101) model (Q1979154)
information sign (P11702) information sign (Q6031215)
monogram (P1543) monogram (Q168346)
seal image (P158) seal (Q162919)
distribution map (P1846) distribution map (Q97378230)
sectional view (P2713) cross section (Q12139782)
film poster (P3383) film poster (Q374821)
astronomic symbol image (P367) astronomical symbol (Q645745)
pronunciation audio (P443) pronunciation (Q184377)
sail emblem (P5962) sail emblem (Q1668447)
music video (P6718) music video (Q193977)
code (image) (P7415) symbol (Q80071)
creator's signature (P7457) signature (Q1373131)
image of molecular model or crystal lattice model (P8224) molecular model (Q2196961)
twin town sign (P8667) twin town sign (Q96279156)
rank insignia (P8766) rank insignia (Q34941835)
inscription image (P9906) inscription (Q1640824)

Geertivp (talk) 14:17, 8 April 2024 (UTC)[reply]

I think we should distinguish between the following (still non-existent) properties: (the current one, and two additional properties)
  1. Type of representation (representation type): the current proposal (deals with what the shot represents, based directly on the corresponding Wikidata item)
  2. Point of view (view point): fish eye, bird's eye view, marcro, sunset, sunrise, frontal, dorsal (idea from @Bertux; cannot be automatically derived from Wikidata)
  3. Technique used (type of recording): colour, black and white, raster, negative, positive, collodion (mirrored), relief, bas-relief, etching, engraving, woodcut, glass negative, stencil and blueprint; suggestion by @PVanPamel (can possibly be derived from the EXIF)
I think we could benefit from the three properties. Note that all these properties could also be used for video recordings... so we must not use typical photo descriptions.
Geertivp (talk) 08:18, 9 April 2024 (UTC)[reply]

Discussion edit

General edit

Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Sister_projects&oldid=2119499834"