Property talk:P220
Latest comment: 5 years ago by Jura1 in topic Allow “reason for deprecation” as qualifier?
Documentation
ISO 639-3 code
3-letter identifier for language defined in ISO 639-3, extension of ISO 639-2
3-letter identifier for language defined in ISO 639-3, extension of ISO 639-2
[create Create a translatable help page (preferably in English) for this property to be included here]
List of violations of this constraint: Database reports/Constraint violations/P220#Format, hourly updated report, SPARQL
Type “languoid (Q17376908), writing system (Q8192), spurious language (Q5015649), type of language (Q20829075)”: item must contain property “instance of (P31)” with classes “languoid (Q17376908), writing system (Q8192), spurious language (Q5015649), type of language (Q20829075)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: no linguistic content (Q22282939)List of violations of this constraint: Database reports/Constraint violations/P220#Type Q17376908, Q8192, Q5015649, Q20829075, 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
Qualifiers “start time (P580), end time (P582), including (P1012), end cause (P1534), reason for deprecated rank (P2241), reason for preferred rank (P7452), latest start date (P8555), earliest date (P1319), earliest end date (P8554), latest date (P1326), issued by (P2378), writing system (P282), has characteristic (P1552), depicts (P180), represents (P1268), nature of statement (P5102)”: this property should be used only with the listed qualifiers. (Help)
List of violations of this constraint: Database reports/Constraint violations/P220#allowed qualifiers, hourly updated report, SPARQLAllowed 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:
List of this constraint violations: Database reports/Complex constraint violations/P220#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)
editIf instance of (P31) is a Wikimedia disambiguation page (Q4167410) the presence of ISO 639-3 code (P220) is prohibited.
Wikimedia projects
editShould 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?
editShould 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)
- 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)
- 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)