Property talk:P432
Latest comment: 8 years ago by André Costa (WMSE) in topic Formatter URL
Documentation
callsign of airline
identifier used in radio transmissions to refer to the subject airline
identifier used in radio transmissions to refer to the subject airline
| Description | callsign of an airline in radio traffic | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Represents | airline callsign (Q21562063) | |||||||||
| Data type | External identifier | |||||||||
| Template parameter | en:template:infobox airline : Callsign | |||||||||
| Domain | According to this template:
Organizations: airlines - airline (Q46970)
According to statements in the property:
When possible, data should only be stored as statementsairline (Q46970) | |||||||||
| Allowed values | [A-Z ]+ | |||||||||
| Example | According to this template:
<British Airways> → <SPEEDBIRD>
According to statements in the property:
When possible, data should only be stored as statementsWhite Airways (Q618093) → WHITE JET Sriwijaya Air (Q619089) → SRIWIJAYA | |||||||||
| Source | en:List of airline call signs (note: this information should be moved to a property statement; use property source website for the property (P1896)) | |||||||||
| See also | call sign (P2317) | |||||||||
| Lists |
| |||||||||
| Proposal discussion | Proposal discussion | |||||||||
| Current uses |
| |||||||||
| Search for values |
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “airline (Q46970)”: item must contain property “instance of (P31)” with classes “airline (Q46970)” 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/P432#Type Q46970, 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/P432#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P432#Format, 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). List of violations of this constraint: Database reports/Constraint violations/P432#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). List of violations of this constraint: Database reports/Constraint violations/P432#Single value, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P432#Scope, hourly updated report, 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/P432#Entity types
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Label / scope edit
The current description notes that it's for the callsign of airlines. Accordingly I changed the label to "callsign of airline".
We could also extend the scope to other callsigns (e.g. ships). In this case, "callsign" would be sufficient as label. -- Docu at 05:49, 19 April 2013 (UTC)
- Could also be interesting for the call sign of radio stations and amateur radio. I don't know if there are overlaps. --Kolja21 (talk) 03:51, 20 April 2013 (UTC)
- I don't think that there are overlaps, but I am not an expert for Ships, only for aviation. - Milad A380 (talk) 10:57, 25 April 2013 (UTC)
- Reading w:Airline codes it seems better to leave scope and label airline specific. -- Docu at 11:23, 25 April 2013 (UTC)
- I think this should be call sign, for use with all items which have a telephony-type call sign, with the exception of spaceflight related items (we need another property for that). Danrok (talk) 00:37, 30 August 2013 (UTC)
Possible extending of scope edit
See proposal of callsign property for space-crafts. --Base (talk) 20:03, 11 May 2013 (UTC)
Rename to telephony designator edit
My understanding is that the correct term for this is telephony designator, and it is not just airlines which have them. Take a look here: [1].
Renaming it to telephony designator would avoid it being mixed up with other types of call sign. Danrok (talk) 00:42, 24 June 2013 (UTC)
scope expanded edit
I've expanded the scope of this property, after a discussion in property proposals.
Now it effectively covers all call signs, as described here: Call sign. Danrok (talk) 13:54, 2 September 2013 (UTC)
- Would you link to the discussion? Potentially, this creates more problems than it solves. -- Docu at 17:52, 2 September 2013 (UTC)
- Link Call sign / Позывной. What are the problems this creates? Danrok (talk) 14:04, 4 September 2013 (UTC)
- It mixes all kind of callsigns eventually making it impossible to figure out if the value is correct. -- Docu at 03:09, 5 September 2013 (UTC)
- There is no need to "figure out if the value is correct" (how would you go about figuring it out?), the data can be extracted from sources, e.g. for airlines, airports and some others Chapter 3. ICAO AIRCRAFT COMPANY/TELEPHONY/THREE-LETTER DESIGNATOR AND U.S. SPECIAL TELEPHONY/CALL SIGNS. Danrok (talk) 00:49, 6 September 2013 (UTC)
- So we don't care about the values entered? Seems odd to me.
- en:Call sign lists at least 3 or 4 different ones with different definitions. -- Docu at 03:52, 6 September 2013 (UTC)
- There is no need to "figure out if the value is correct" (how would you go about figuring it out?), the data can be extracted from sources, e.g. for airlines, airports and some others Chapter 3. ICAO AIRCRAFT COMPANY/TELEPHONY/THREE-LETTER DESIGNATOR AND U.S. SPECIAL TELEPHONY/CALL SIGNS. Danrok (talk) 00:49, 6 September 2013 (UTC)
- It mixes all kind of callsigns eventually making it impossible to figure out if the value is correct. -- Docu at 03:09, 5 September 2013 (UTC)
- Link Call sign / Позывной. What are the problems this creates? Danrok (talk) 14:04, 4 September 2013 (UTC)
- Note that this is up for discussion again. If you oppose expanding the scope you should let your views be heard at Wikidata:Property_proposal/Unsorted. /André Costa (WMSE) (talk) 12:50, 21 September 2015 (UTC)
Formatter URL edit
How should we go about to add one (or several) to this property? --- Jura 10:34, 24 October 2015 (UTC)
- Not sure you can. It's not a true external identifier. Also be aware of the ongoing discussion about widening this to call signs in general. /André Costa (WMSE) (talk) 15:18, 25 October 2015 (UTC)
- We are currently working on making links for external identifiers possible for some that currently don't have them. This includes identifiers such as this one.
- To make it possible, you need to make sure that you clearly designate the type of identifier. This can be done through distinct properties or qualifiers on the statement. You can widen the scope, but you'd need to ensure to add proper qualifiers. --- Jura 15:39, 25 October 2015 (UTC)
- If you can have a formatter url which only kicks in when a certain qualifier is also present then that would be great. For airlinestehre might be some central online index but for e.g. ships I would assume you need a qualifier specifying which specific database should be linked to. /André Costa (WMSE) (talk) 08:27, 26 October 2015 (UTC)