Property talk:P94

From Wikidata
Jump to navigation Jump to search

Documentation

coat of arms image
image of the item's coat of arms
Descriptioncoat of arms (Q14659) image. See also coat of arms (P237). For seal (Q162919), rather use seal image (P158).
Representscoat of arms (Q14659)
Data typeCommons media file
Template parameterde:Vorlage:Infobox_Gemeinde_in_Österreich, de:Vorlage:Infobox_Gemeinde_in_Deutschland, de:Wikipedia:Formatvorlage_Ort_Schweiz, de:Vorlage:Infobox_Staat
Domain
According to this template: Various places and persons
According to statements in the property:
geographical object (Q618123), family (Q8436), human (Q5), organization (Q43229), position (Q4164871), fictional location (Q3895768), fictional character (Q95074), fictional organization (Q14623646), fictional noble family (Q19791817) and mythical place (Q24334893)
When possible, data should only be stored as statements
Allowed values
According to this template: Image files. Don't add the ones from c:Category:Coat of arms placeholders (check)
According to statements in the property:
(?i).+\.(svg|png|jpg|jpeg|gif|tif|tiff)| (image filename with extension: svg or png or jpg or jpeg or gif or tif or tiff (case insensitive))
When possible, data should only be stored as statements
ExampleStannis Baratheon (Q12056060)Coat of Arms of Stannis Baratheon.png
Monaco (Q235)Coat of arms of Monaco.svg
Windsor (Q182625)Wappen von Windsor O in Kanada.jpg
Formatter URLhttps://commons.wikimedia.org/wiki/File:$1
Embed URLhttps://commons.wikimedia.org/wiki/File:$1
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: sameno label (Q41539179)
Tracking: differencesno label (Q41539177)
Tracking: usageCategory:Pages using Wikidata property P94 (Q23909098)
Tracking: local yes, WD nono label (Q41539180)
See alsoseal image (P158), coat of arms (P237), flag image (P41), logo image (P154)
Lists
  • Count of items by number of statements (chart)
  • Count of items by number of sitelinks (chart)
  • Items with the most identifier properties
  • Items with no other statements
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history
  • <chart by item creation date>
  • Database reports/Complex constraint violations/P94
  • Database reports/Constraint violations/P94
  • Proposal discussionProposal discussion
    Current uses109,736
    [create] Create a translatable help page (preferably in English) for this property to be included here
    Format “(?i).+\.(svg|png|jpg|jpeg|gif|tif|tiff|webp)|: value must be formatted using this pattern (PCRE syntax). (Help)
    List of this constraint violations: Database reports/Constraint violations/P94#Format, hourly updated report, SPARQL, SPARQL (new)
    Link to Commons namespace “File”: this property should contain a well-formed link to an existing page on Wikimedia Commons. (Help)
    List of this constraint violations: Database reports/Constraint violations/P94#Commons link, hourly updated report, SPARQL (new)
    Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Conflicts with P31, SPARQL, SPARQL (new)
    Qualifiers “start time (P580), end time (P582), point in time (P585), coat of arms (P237), media legend (P2096), literal translation (P2441): this property should be used only with the listed qualifiers. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Allowed qualifiers, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Cc]oats of [Aa]rms of none).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ff]ührt kein wappen).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Nn]o coats of arms).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ww]appen fehlt).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ss]in escudo).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Bb]lason à dessiner).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Nn]e havas blazonon).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ss]ense escut oficial).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Uu]nknow escutcheon).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ee]scutcheon to draw).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ss]eal\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ss]ello\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ss]ceau\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ss]iegel\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ff]lag\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Dd]rapeau\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Bb]andiera\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Ff]lagge\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Bb]andera\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Bb]andeira\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?!.*\b[Vv]lag\b).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “(?i)((?!\b(logo)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Format “^(?![Vv]oert geen wapen\.svg).*$: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P94#Format, SPARQL, SPARQL (new)
    Pictogram voting comment.svg Too short filename
    (Help)
    Violations query: SELECT DISTINCT ?item { ?item wdt:P94 ?value. BIND(STRLEN(STR(?value)) AS ?length). FILTER (?length < 58) }
    List of this constraint violations: Database reports/Complex constraint violations/P94#Too short filename


    Format constraints to exclude coat of arms placeholders (see c:Category:Coat of arms placeholders)...


    Format constraints to exclude files whose names suggest that they are seals...


    Format constraints to exclude files whose names suggest that they are flags...


    This property is being used by:

    Wikivoyage:


    Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

    This property is being used by:

    Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

    This property is being used by:

    Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

    Unique value[edit]

    I'm not sure the Unique value constraints is applicable in this case. There is nothing preventing two objects from using the the same coat of arms image. As an example we could have two successive kings both using the state coat of arms or a municipal coat of arms being the same as that of the original city. /Lokal Profil (talk) 10:18, 9 September 2013 (UTC)

    • It is needed to analyze violations list. How many false positive values in it? — Ivan A. Krestinin (talk) 12:47, 9 September 2013 (UTC)
      • I'd leave it. It helps spot things like "File:Sin escudo.svg". That there can be exceptions isn't a problem as such. There are also few errors of my bot I need to fix. --  Docu  at 18:13, 9 September 2013 (UTC)
    Hi @Lokal Profil, Ivan A. Krestinin, Docu: not sure Unique value constraint is a good idea. Members of the same familly or territories with shared history could have the same blazon (very common for commune of France (Q484170)) ; if we keep this constraint there will be a huge amont of exceptions.
    For instance on Saint-Didier (Q963301) I just add coat of arms image (P94) : File:Héraldique - fretté.svg. Should I add it as an exception on Wikidata? Should I duplicate the file on Commons? (which is a bad pratice but not uncommon).
    Cdlt, VIGNERON (talk) 18:12, 14 July 2015 (UTC)
    I would remove the unique value constraint. Is it instead possible to blacklist values (such as Sin escudo.svg)? /Lokal Profil (talk) 19:20, 14 July 2015 (UTC)
    Exceptions for unique value are present of course. The question is how many exceptions we have in real data. Also you mention some cases, lets discuss one case: members of some family have shared coat of arm. There are two ways to model this case:
    1. We add this image to every human (Q5) item.
    2. We create special lineage (Q1642895) item and add coat of arm image to this item only. human (Q5) items are linked with lineage (Q1642895) using family (P53).
    The second way is better describes reality as I see, but it has some limitations too. — Ivan A. Krestinin (talk) 20:04, 14 July 2015 (UTC)
    I've added human (Q5) since there are also some coat of arms for individuals (e.g. unique CoAs for members of royal families) for this reason I wouldn't restrict CoA use to only lineage (Q1642895).
    In general I think it might be worth creating Qitems for the CoAs themselves then connect these to lineage (Q1642895) (and/or human (Q5)) using coat of arms (P237). This allows other statements (such as coat of arms image (P94), blazon, history etc) to be given in one place without unduly cluttering the lineage (Q1642895)/human (Q5) item. /Lokal Profil (talk) 15:02, 15 July 2015 (UTC)
    Per Wikidata:Project_chat#New_Constraint_.3F filenames such as sin escudo.svg could be blacklisted using a second {{Constraint:Format}} instead. Sadly I'm not enough of a regexp ninja to make that work. /Lokal Profil (talk) 15:26, 16 July 2015 (UTC)


    Great discussion (I was away for some time, sorry I missed your comment).
    Ivan A. Krestinin : lineage (Q1642895) could have been a good idea but it's not since the reality is far more complex. Members of the same familly could have the same coat of arms but not always. Different famillies can have the same coat of arms too. Plus, it's not unusual for a coat of arms to be shared between a familly and a territories. In ecclesiastical heraldry, coat of arms can be shared between people (not in the same familly obviously) and/or places (an abbey and its abbots for example; but high rank people like popes or bishops have usually their own coat of arms). Simple coat of arms like « Azure a cross argent » are very common and shared by unrelated places and people (qv. commons:Category:Azure a cross argent for examples), sometimes the files are duplicated with different names on Wikimedia Commons but sometimes the same simple file is used for differents articles/items.
    Right now there is only 1967 contraint violations but there is only 52115 uses of P94.
    Lokal Profil : the Project chat discussion doesn't seems to give a way to forbid placeholder. A regex is nearly impossible since the placeholders have too differents names. I'm maybe wrong but I thought it was impossible to use two Constraint:Format on the same page (I think I remember something like « only the last one will be consider »). Maybe we can use an extern tools for that? (Autolist??)
    Cdlt, VIGNERON (talk) 12:38, 29 July 2015 (UTC)
    @VIGNERON:. The project chat (now archived) suggests that you can use two Constraint:Format. You are probably right about the regexp though. Other than having a long list of strings to compare to I think it might be hard. Ideally with CommonsData we could tag such files as placeholder and then do something fancy but that is still some time away. /Lokal Profil (talk) 10:34, 4 August 2015 (UTC)
    Please delete the unique value constraint. I edited dozens of items of persons, members of the same family, that used the same coat-of-arms. Everywhere I get a violation message. Can't say I get happy from those messages. HRvO (talk) 20:45, 18 August 2018 (UTC)

    Still the same problem, about which evidently nobody has cared enough since 2013. Good to see some things in life are still reliable. In this case, a modern city (Tartu City, Q42307965) uses the same coat of arms as did the medieval Bishopric of Dorpat (Q389360). There's nothing to prevent them IRL but hey, what do we care in WD? It's not like constraints have to make sense, right? --Ehitaja (talk) 23:21, 19 January 2019 (UTC)

    I went ahead and removed the unique value constraint. The main successful use case that this constraint used too reveal - "no coat of arms" placeholder images - are now handled by RegEx "format" constraints. It seems that most people here agree that it is counterproductive in general to throw warnings at multiple items having the same coat of arms, when in real life it is common for related people and groups to share the same coat of arms, and sometimes even for unrelated groups to happen to use exactly the same coat of arms. Deryck Chan (talk) 12:23, 20 January 2019 (UTC)

    Automatic fix for "Flag of"[edit]

    JFYI: violations like "Flag of" can be automatically fixed using {{Autofix}}. — Ivan A. Krestinin (talk) 18:40, 22 May 2017 (UTC)

    Related constraint[edit]

    Just a note here that I raised a question about a related constraint over at Property talk:P237#Inappropriate_constraint. /Lokal Profil (talk) 22:35, 8 November 2018 (UTC)