Property talk:P619
Jump to navigation
Jump to search
This property was previously considered for deletion but kept. |
Documentation
- Start a query
- Current uses
- With precision and calendarmodel
- Statistics by class
- By century
- Date precision
- Calendar models
- List of qualifiers
- Count
UTC date of spacecraft launch
date of spacecraft launch in UTC
date of spacecraft launch in UTC
[create Create a translatable help page (preferably in English) for this property to be included here]
Single value: this property generally contains a single value. (Help)
"exceptions" is incompatible with "mandatory" parameter List of violations of this constraint: Database reports/Constraint violations/P619#Single value, hourly updated report, SPARQLRange from “+1957-10-04T00:00:00Z” to “+2099-12-31T00:00:00Z”: values should be in the range from “+1957-10-04T00:00:00Z” to “+2099-12-31T00:00:00Z”. (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/P619#Range
Type “vehicle (Q42889), spacecraft (Q40218), spaceflight (Q5916), payload (Q21211206), scientific instrument (Q3099911), space debris (Q275450)”: item must contain property “instance of (P31)” with classes “vehicle (Q42889), spacecraft (Q40218), spaceflight (Q5916), payload (Q21211206), scientific instrument (Q3099911), space debris (Q275450)” 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/P619#Type Q42889, Q40218, Q5916, Q21211206, Q3099911, Q275450, 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/P619#Item P1427, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P619#Item P1427, SPARQL
Item “space launch vehicle (P375)”: Items with this property should also have “space launch vehicle (P375)”. (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/P619#Item P375, 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/P619#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/P619#Scope, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
|
Ship launch date?
[edit]Any reason why this can't be used for ships? It is after all where the phrase originates. Danrok (talk) 21:44, 23 June 2013 (UTC)
- It is hard to make common name for these events types in Russian. It must be named "дата спуска на воду" for ships but "дата запуска" for launch vehicles. — Ivan A. Krestinin (talk) 06:21, 24 June 2013 (UTC)
- However, I think it is still essentially the same. Shouldn't we try to generalize properties? I don't speak Russian, but how about something like "дата спуска на воду и́ли запуска"? Petr Matas 06:01, 19 November 2014 (UTC)
- Double naming says that we mix different entities in one object. This is not good from point view of data structure. Why you suggest mix rocket lift off time and ship launch? Why not date of birth (P569) and ship launch? Another point: rocket launch time in known with high precession (usually seconds, sometimes milliseconds). For ships only year is known often. Space vehicles and ships are described in different sources / databases, different groups of users are interested in these areas. I see only one point for this merge: these two different concepts are described using single word in English language. — Ivan A. Krestinin (talk) 18:46, 19 November 2014 (UTC)
- You are probably right. I came to this idea when thinking about the fictional star ship Enterprise, where the analogy is stronger. Still, I think that the similarity between different properties should be recorded somehow. If properties could have properties, I would say that UTC date of spacecraft launch (P619) and ship launch date are both a subclass of the date of first use or something like that. Petr Matas 02:41, 20 November 2014 (UTC)
- Double naming says that we mix different entities in one object. This is not good from point view of data structure. Why you suggest mix rocket lift off time and ship launch? Why not date of birth (P569) and ship launch? Another point: rocket launch time in known with high precession (usually seconds, sometimes milliseconds). For ships only year is known often. Space vehicles and ships are described in different sources / databases, different groups of users are interested in these areas. I see only one point for this merge: these two different concepts are described using single word in English language. — Ivan A. Krestinin (talk) 18:46, 19 November 2014 (UTC)
- However, I think it is still essentially the same. Shouldn't we try to generalize properties? I don't speak Russian, but how about something like "дата спуска на воду и́ли запуска"? Petr Matas 06:01, 19 November 2014 (UTC)
Future launch
[edit]Why is there a constraint on the value of this property forcing it to be a date in the past? Shouldn't it also be used for planned launch dates? Regards, -- Whidou (talk) 11:55, 30 March 2018 (UTC)
- Good question. @Ivan A. Krestinin: could you comment it? --Rif.8i. (talk) 05:52, 23 April 2022 (UTC)
Categories:
- Pages using the JsonConfig extension
- Properties for deletion
- All Properties
- Properties with time-datatype
- Properties used on 1000+ items
- Mandatory constraints with exceptions
- Properties with single value constraints
- Properties with range constraints
- Properties with constraints on type
- Properties with constraints on items using them
- Properties with entity type constraints
- Properties with scope constraints
- Vehicle properties