Property talk:P220

From Wikidata
Jump to navigation Jump to search

Documentation

ISO 639-3 code
3-letter identifier for language defined in ISO 639-3, extension of ISO 639-2
Data typeExternal identifier
Template parameter|iso3= in w:en:Template:Infobox language
Domain
According to this template: languoid (Q17376908) (form of language)
According to statements in the property:
languoid (Q17376908), writing system (Q8192) or spurious language (Q5015649)
When possible, data should only be stored as statements
Allowed values[a-z]{3} (3 lowercase letters)
ExampleJapanese (Q5287)jpn (RDF)
Ukrainian (Q8798)ukr (RDF)
Punjabi (Q58635)pan (RDF)
Punjabi (Q58635)pnb (RDF)
Sourcehttp://www-01.sil.org/iso639-3/
Formatter URLhttps://iso639-3.sil.org/code/$1
Tracking: usageCategory:Pages using Wikidata property P220 (Q26250077)
See alsoISO 639-1 code (P218), ISO 639-2 code (P219), ISO 639-5 code (P1798), ISO 639-6 code (P221), IETF language tag (P305)
Lists
Proposal discussionProposal discussion
Current uses
Total8,676
Main statement8,65399.7% of uses
Qualifier4<0.1% of uses
Reference190.2% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “[a-z]{3}|: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P220#Format, hourly updated report, SPARQL
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P220#Type Q17376908, Q8192, Q5015649, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Standard Mandarin (Q727694), Punjabi (Q58635)
List of violations of this constraint: Database reports/Constraint violations/P220#Unique value, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Punjabi (Q58635), Ovambo (Q36489), Kwanyama (Q1405077), Ndonga (Q33900)
List of violations of this constraint: Database reports/Constraint violations/P220#Single value, SPARQL
Conflicts with “ISO 639-5 code (P1798): this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Albanian (Q8748), Armenian (Q8785), Basque (Q8752), Chinese (Q7850), Japanese (Q5287), Quechua (Q5218), Punjabi (Q58635)
List of violations of this constraint: Database reports/Constraint violations/P220#Conflicts with P1798, search, SPARQL
Item “IETF language tag (P305): Items with this property should also have “IETF language tag (P305)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P220#Item P305, search, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P220#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P220#Scope, SPARQL
Check value
(Help)
Violations query: SELECT ?item ?value ?marc { ?item wdt:P220 ?value. ?item wdt:P4801 ?marc. BIND (SUBSTR(?marc, 1, 9) AS ?prefix). BIND (SUBSTR(?marc, 11) AS ?s). FILTER (?marc = ?s) }
List of this constraint violations: Database reports/Complex constraint violations/P220#Check value
Pattern ^-$ will be automatically replaced to novalue.
Testing: TODO list
This property is being used by:

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

constraint report relating to Wikimedia disambiguation page (Q4167410)[edit]

If instance of (P31) is a Wikimedia disambiguation page (Q4167410) the presence of ISO 639-3 code (P220) is prohibited.

see: Wikimedia disambiguation page (Q4167410) with ISO 639-3 (P220) gangLeri לערי ריינהארט (talk) 15:19, 19 May 2014 (UTC)[reply]

Wikimedia projects[edit]

Should we expand the domain to include Wikipedia language edition (Q10876391)? --Infovarius (talk) 08:39, 10 January 2016 (UTC)[reply]

I would say no. This property means the ISO code assigned to a language. Wikimedia projects are not languages and do not have ISO codes assigned to them. The codes they use are based on ISO codes and IETF language tags and we already have Wikimedia language code (P424) for that. In general, we should link to language items where we want to say which language something uses instead of using these properties. The language item will have the ISO codes, IETF language tags, Wikimedia language code and any other information people want. - Nikki (talk) 09:53, 10 January 2016 (UTC)[reply]
So see the main discussion here: Property talk:P218#WMF_projects. --Infovarius (talk) 20:42, 11 January 2016 (UTC)[reply]

Allow “reason for deprecation” as qualifier?[edit]

Should ISO 639-3 code (P220) be changed to allow reason for deprecated rank (P2241) as a qualifier? See Emilian–Romagnol (Q242648) for an example of a constraint violation that seems legitimate, specifically the statement for P220 on that item. Generally, I’d be interested in people’s thoughts on how to to best model deprecated language codes. See ISO 639-3 deprecations for the full list. There’s five different reasons for deprecating an ISO 639-3 code, and I’m not sure how to model them in Wikidata. Your advice would be appreciated. — Sascha (talk) 16:48, 8 February 2019 (UTC)[reply]

  • In principle, any property could use that qualifier. The problem with your application is that the "deprecated code" shouldn't have deprecated rank in Wikidata. They would just have normal rank with an "end date" and "end cause". The new code would have preferred rank. If there is none, "no value" could have preferred rank. --- Jura 09:15, 10 February 2019 (UTC)[reply]
Like this? It still is getting flagged as a constraint violation. ISO 639-3 code (P220) of Emilian–Romagnol (Q242648) and ISO 639-3 code (P220) of Romagnol (Q1641543)Sascha (talk) 14:17, 11 February 2019 (UTC)[reply]
Yes, more or less. Maybe end cause could be "code split" or something like that, but I'm not really sure about that. I also added "no value" in preferred rank. --- Jura 18:03, 11 February 2019 (UTC)[reply]