Property talk:P1427
Latest comment: 3 years ago by Neo-Jay in topic Use on 'trek' violating constraint
Documentation
start point
starting place of this journey, flight, voyage, trek, migration etc.
starting place of this journey, flight, voyage, trek, migration etc.
| Description | the starting place of this journey, flight, voyage, trek, etc. (excl. spaceflight launch) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Represents | beginning (Q529711) | ||||||||||||
| Data type | Item | ||||||||||||
| Template parameter | |origin= in en:template:infobox aircraft occurrence | ||||||||||||
| Domain | According to this template:
event
According to statements in the property:
When possible, data should only be stored as statementsoccurrence (Q1190554), spacecraft (Q40218), vehicle (Q42889), payload (Q21211206), scientific instrument (Q3099911), pilgrims' way (Q337912), itinerary (Q1322323), fictional occurrence (Q14136353), expedition (Q2401485), space debris (Q275450) or travel (Q61509) | ||||||||||||
| Allowed values | places - airport, sea port, town, etc. (note: this should be moved to the property statements) | ||||||||||||
| Example | 2004 Tour de France, Stage 2 (Q282721) → Charleroi (Q81046) School of Civil Aviation Flight 111 (Q15644223) → Bucharest (Q19660) 1971 RAF Hercules crash (Q3997249) → Pisa International Airport “Galileo Galilei” (Q709169) | ||||||||||||
| Tracking: same | no label (Q42533354) | ||||||||||||
| Tracking: usage | Category:Pages using Wikidata property P1427 (Q20990037) | ||||||||||||
| Tracking: local yes, WD no | no label (Q101364437) | ||||||||||||
| <complementary property> | destination point (P1444) | ||||||||||||
| See also | via (P2825), destination point (P1444) | ||||||||||||
| 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]
Value type “geographic entity (Q27096213), physical location (Q17334923), service provider (Q2169973), building (Q41176), mother ship (Q538685), astronomical object (Q6999)”: This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value geographic entity (Q27096213), physical location (Q17334923), service provider (Q2169973), building (Q41176), mother ship (Q538685), astronomical object (Q6999) (or a subclass thereof). (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/P1427#Value type Q27096213, Q17334923, Q2169973, Q41176, Q538685, Q6999, SPARQL
Type “occurrence (Q1190554), spacecraft (Q40218), vehicle (Q42889), payload (Q21211206), scientific instrument (Q3099911), pilgrims' way (Q337912), itinerary (Q1322323), fictional occurrence (Q14136353), expedition (Q2401485), space debris (Q275450), travel (Q61509)”: item must contain property “instance of (P31), subclass of (P279)” with classes “occurrence (Q1190554), spacecraft (Q40218), vehicle (Q42889), payload (Q21211206), scientific instrument (Q3099911), pilgrims' way (Q337912), itinerary (Q1322323), fictional occurrence (Q14136353), expedition (Q2401485), space debris (Q275450), travel (Q61509)” 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/P1427#Type Q1190554, Q40218, Q42889, Q21211206, Q3099911, Q337912, Q1322323, Q14136353, Q2401485, Q275450, Q61509, SPARQL
Contemporaries:
if [item A] has this property (start point (P1427)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (start point (P1427)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1427#Contemporary, 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/P1427#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P1427#Scope, SPARQL
Opposite
editI do not know how to mention it, but this property seems to be the opposite of destination point (P1444).
all linear objekts
editthis property could be used for all linear (one dimentional) objekts, i.e. routes, streets, directions, etc--Avatar6 (talk) 09:20, 13 March 2016 (UTC)
Use on 'trek' violating constraint
editRevision 631398949 added a constraint check enforcing the property to only be used on occurrences. This seems to go counter to the description describing it as the "starting place of this journey, flight, voyage, trek [...]", so items not necessarily associated with a temporal entity. This causes e.g. a hiking trail to be marked as possibly problematic. Is this intended behavior? – The preceding unsigned comment was added by Pprtw (talk • contribs) at 16:34, 1 June 2018 (UTC).
- I update it with trail (Q628179) as a vàlid subclasse, because it's not only valid for the journey (occurrence (Q1190554), but also the via where the journey is done by. Amadalvarez (talk) 05:13, 7 August 2018 (UTC)
- I fear we are still producing many false positives. All instances of "space probe" have a starting point and many have a destination point as well, Q61742389 as example. In general all spaceflights, all individual airplane flights and so on have a starting point. --mfb (talk) 13:27, 10 April 2019 (UTC)
- "Trek" (not track) is also subclass of occurrence (Q1190554). For the linear feature where a journey occurs, P559 (terminus) or P609 (terminus location), not P1427 (start point) or P1444 (destination point), should be used. Relevant type constraints have been removed. --Neo-Jay (talk) 15:00, 8 June 2021 (UTC)
Extend usage scenarios
editI think this property should be extended to accept other usage scenarios, for example, the initial location of an activity, movement, era, etc. For example: Industrial Revolution (Q2269) started in (start point P1427) United Kingdom. We can use P495 today, but only when it refers to a country, not other locations like "Western Europe", "Liverpool", or anything else.