Property talk:P2620

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

ISO 15924 numeric code
numeric code for a writing system in ISO 15924

Data type	External identifier
Template parameter	iso15924 in en:Template:Infobox writing system
Domain	According to this template: scripts According to statements in the property: notation (Q2001982) When possible, data should only be stored as statements
Allowed values	[0-9]{3} (three digits)
Example	Hangul (Q8222) → 286 Latin script (Q8229) → 215 reserved for private use (start) (Q109986276) → 900 reserved for private use (end) (Q110240135) → 949
Source	http://www.unicode.org/iso15924/iso15924-codes.html
See also	ISO 15924 alpha-4 code (P506)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Mix'n'match (Report) Database reports/Constraint violations/P2620 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 277 Main statement 273 98.6% of uses Qualifier 4 1.4% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

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).
List of violations of this constraint: Database reports/Constraint violations/P2620#Unique value, SPARQL (every item), SPARQL (by value)

Single value: this property generally contains a single value. (Help)

List of violations of this constraint: Database reports/Constraint violations/P2620#Single value, hourly updated report, SPARQL

Format “[0-9]{3}”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P2620#Format, hourly updated report, SPARQL

Item “ISO 15924 alpha-4 code (P506)”: Items with this property should also have “ISO 15924 alpha-4 code (P506)”. (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/P2620#Item P506, search, SPARQL

Type “notation (Q2001982)”: item must contain property “instance of (P31)” with classes “notation (Q2001982)” 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).
List of violations of this constraint: Database reports/Constraint violations/P2620#Type Q2001982, 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/P2620#Entity types

Scope is as main value (Q54828448): 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/P2620#Scope, SPARQL

This property is being used by: eu:Txantiloi:Mendi infotaula automatikoa, eu:Txantiloi:Mendate infotaula, eu:Txantiloi:Geografia fisiko infotaula ca:Plantilla:Infotaula sistema d'escriptura ast:Plantía:Ficha de sistema d'escritura ha:Template:Infobox physical geography, ha:Samfuri:Infobox physical geography kab:Talɣa:Infobox physical geography es:Plantilla:Ficha de sistema de escritura hu:Sablon:Írásrendszer infobox incubator:Template:Wp/shi/Infobox physical geography, incubator:Template:Wp/zgh/Infobox physical geography ig:Àtụ:Infobox physical geography shi:Talɣa:Infobox physical geography ga:Teimpléad:WD Bosca Sonraí Córais Scríbhneoireachta zgh:ⴰⵍⴱⵓⴹ:Infobox physical geography Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Format constraint

After creating reserved for private use (range) (Q105037964), I ran into the format constraint ([0-8]\d{2}|9[5-9]\d) "Exception: 900–949 (50 Codes reserved for private use)".

However, AFAIK the range 900–949 (Qaaa – Qabx) are well defined codes and numbers ([1]). Is there a reason why these are not acceptable? -DePiep (talk) 11:01, 23 January 2021 (UTC)

I also agree that such restriction is non-standard. This range of codes are perfectly valid, even if their usage is left undefined (i.e. independant of the usage of other script codes defined in the standard)

Note that other codes in the standard are NOT all mutually exclusive: e.g. "Latn" includes "Latf" and Latg"; "Cyrl" include "Cyrs"; "Hani" includes "Hans" and "Hant"; "Hang" includes "Jamo"; "Kore" includes "Hang", "Jamo", "Hani", "Hans" and "Hant"; "Zsym" includes "Zsye"... and all codes include "Zinh"; all codes, except "Geor" including "Geok" in Unicode property values, that are not mutually exclusive and do not create a partition are normally excluded in Unicode script values, but all they are not necessarily all encoded in Unicode/ISO/IEC 10646 while bieing assigned in SIO 15924).

Note also that the ISO 15924 standard is not meant to be used only for technical purpose (e.g. plain text encoding within the UCS), they also exist for other purposes (notably bibliographic: the Klingon script for example will not be encoded in the UCS, for legal reasons related to copyright, but is already actively used bibliographically, for various artistic classifications of printed media, videos and animations, including for managing their property rights, or ordering collections and searching/retrieving items from them).

For technical usage such as plain text encoding in the UCS, there's a "PVA" field defined in ISO 15924 that maps some of these script codes to a "Property Value Alias" defined in Unicode (not all characters encoded in the UCS have a PVA property mapped to them; notably not the PUA which may be privately assigned to any one of the private-use script codes in ISO 15924, or to any other ISO 15924 script codes, including special script codes like "Zzzz"; however, not all code points are characters in the UCS, and none of the codepoints that are not characters in the UCS may be mapped to any valid script code as they are only assigned for technical purpose, not for any valid text encoding or interchange; on the opposite, texts containing PUA, or tagged with private-use scripts ARE valid for interchange: the ISO 15924 standard does not define or limit the kind of private agreement which may be made for their use, as this is out of scope of the stanadrd itself and left to external protocol definitions and implementations). Verdy p (talk) 21:48, 8 December 2021 (UTC)