Open main menu

Property talk:P220

Documentation

ISO 639-3 code
identifier for a language defined in ISO 639-3
RepresentsISO 639-3 code (Q56217712)
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)
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)
Sourcehttp://www-01.sil.org/iso639-3/
Formatter URLhttp://www-01.sil.org/iso639-3/documentation.asp?id=$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)
Lists
Proposal discussionProposal discussion
Current uses8,262
Search for values
  Format “[a-z]{3}: 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/P220#Format, SPARQL, SPARQL (new)
  Type “languoid (Q17376908): element must contain property “instance of (P31)” with classes “languoid (Q17376908)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P220#type Q17376908, SPARQL, SPARQL (new)
  Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Known exceptions: Standard Chinese (Q727694)
List of this constraint violations: Database reports/Constraint violations/P220#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new)
  Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P220#Single value, SPARQL, SPARQL (new)
  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. Known exceptions: Albanian (Q8748), Armenian (Q8785), Basque (Q8752), Chinese (Q7850), Japanese (Q5287), Quechua (Q5218)
List of this constraint violations: Database reports/Constraint violations/P220#Conflicts with P1798, search, SPARQL, SPARQL (new)
  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. Known exceptions: Sakizaya language (Q718269)
List of this constraint violations: Database reports/Constraint violations/P220#Item P305, search, SPARQL, SPARQL (new)
  Qualifiers “start time (P580), end time (P582), including (P1012), end cause (P1534): this property should be used only with the listed qualifiers. (Help)
List of this constraint violations: Database reports/Constraint violations/P220#Allowed qualifiers, hourly updated report, SPARQL, SPARQL (new)

constraint report relating to Wikimedia disambiguation page (Q4167410)Edit

Wikimedia projectsEdit

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

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)
So see the main discussion here: Property talk:P218#WMF_projects. --Infovarius (talk) 20:42, 11 January 2016 (UTC)

Allow “reason for deprecation” as qualifier?Edit

Should ISO 639-3 code (P220) be changed to allow reason for deprecation (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)

  • 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)
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)
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)
Return to "P220" page.