Property talk:P4213
Documentation
hexadecimal code point in Unicode
Description | codepoint in Unicode | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Represents | According to this template:
Unicode (Q8819)
According to statements in the property:
When possible, data should only be stored as statementsUnicode code point (Q109615047) | ||||||||||||
Data type | String | ||||||||||||
Template parameter | | CodeUnicode = in fr:template:Infobox Idéogramme | ||||||||||||
Domain | According to this template:
Unicode characters
According to statements in the property:
When possible, data should only be stored as statementsUnicode character (Q29654788) | ||||||||||||
Allowed values | 0[0-9A-F]{3}|1(0[0-9A-F]{2,4}|[1-9A-F][0-9A-F]{2,3})|[2-9A-F][0-9A-F]{3,4} (hexadecimal number with 4 to 6 uppercase digits in range between 0000 and 10FFFF; do not include D800-DFFF as characters) | ||||||||||||
Example | 雨 (Q3595028) → 96E8 Latin cross (Q200674) → 271D ⚾ (Q87527058) → 26BE | ||||||||||||
Source | https://unicode.org | ||||||||||||
Formatter URL | https://util.unicode.org/UnicodeJsps/character.jsp?a=$1 | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P4213 (Q126372563) | ||||||||||||
See also | Unicode character (P487), Unicode range (P5949), Unicode block (P5522) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P4213#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4213#Unique value, SPARQL (every item), SPARQL (by value)
0[0-9A-F]{3}|1(0[0-9A-F]{2,4}|[1-9A-F][0-9A-F]{2,3})|[2-9A-F][0-9A-F]{3,4}
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P4213#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4213#Entity types
List of violations of this constraint: Database reports/Constraint violations/P4213#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4213#Type Q29654788, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4213#Item P9382, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4213#Item P5522, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4213#Item P4575, search, SPARQL
![]() |
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
![]() |
Pattern ^[Uu]\+([A-F0-9]{4,5})$ will be automatically replaced to \1. Testing: TODO list |
|
Hospital 1F3E5 - must this property restrict subclass of(P279) items?
[edit]After I put this property with value "1F3E5" in the hospital (Q16917) item it gives me an error that hospital (Q16917) is not an instance of something. This is the general idea of a hospital and not a specific one, so in those cases we usually don't use 'instance of'
- emojipedia: https://emojipedia.org/hospital/
- unicode.org: https://unicode.org/cldr/utility/character.jsp?a=1F3E5
Emojis/unicode characters also usually refer to general ideas and not specific ones. It's in the case of specific emojis/symbols like ie. the Tokyo Tower (Q183536) which is a specific one and the tower itself is an instance of an observation tower (Q1440300). Now a subclass of (P279) an observation tower (Q1440300) might be ie. a gyro tower (Q13405507) What is your opinion? Should this property continue giving errors for items which are subclass of (P279) but lack an instance of (P31) which use this property? Seeitinmusic (talk) 12:43, 10 November 2019 (UTC)
- All Properties
- Properties with string-datatype
- Properties used on 100000+ items
- Properties with single value constraints
- Properties with unique value constraints
- Properties with format constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties with constraints on type
- Properties with constraints on items using them
- Han character properties