Property talk:P729

From Wikidata
Jump to navigation Jump to search

Documentation

service entry
date or point in time on which a piece or class of equipment entered operational service
DescriptionDate on which a type of equipment entered operational service. Opposite of service retirement (P730). See also inception (P571).
Representsservice entry (Q29933828)
Data typePoint in time
Template parameteren:template:infobox aircraft (introduced)
Domain
According to this template: manufactured products - appliance (Q1183543)
According to statements in the property:
equipment (Q10273457), vehicle (Q42889), vehicle model (Q29048322), watercraft type (Q16335899), railway line (Q728937), canal (Q12284), building (Q41176), weapon model (Q15142894), harbor (Q283202), facility (Q13226383), collection (Q2668072), reservoir (Q131681), factory (Q83405), transport infrastructure (Q376799), lit beacon (Q110113149), petroleum reservoir (Q1845437), fictional entity (Q14897293), aircraft fleet (Q1875630), stock market index (Q223371), system (Q58778), infrastructure (Q121359) or design of a banknote or a coin (Q28794013)
When possible, data should only be stored as statements
ExampleTamarins Road (Q2169460) →
General Dynamics F-16 Fighting Falcon (Q100026) →
Titanic (Q25173) →
Tsuen Wan line (Q1194568) →
Tracking: sameno label (Q42533422)
Tracking: usageCategory:Pages using Wikidata property P729 (Q21037781)
<complementary property>service retirement (P730)
See alsoinception (P571), date of official opening (P1619), date of commercialization (P5204), state of use (P5817)
Lists
Proposal discussionProposal discussion
Current uses
Total138,292
Main statement137,87199.7% of uses
Qualifier4140.3% of uses
Reference7<0.1% of uses
[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 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/P729#Single value, SPARQL
Type “equipment (Q10273457), vehicle (Q42889), vehicle model (Q29048322), watercraft type (Q16335899), railway line (Q728937), canal (Q12284), building (Q41176), weapon model (Q15142894), harbor (Q283202), facility (Q13226383), collection (Q2668072), reservoir (Q131681), factory (Q83405), transport infrastructure (Q376799), lit beacon (Q110113149), petroleum reservoir (Q1845437), fictional entity (Q14897293), aircraft fleet (Q1875630), stock market index (Q223371), system (Q58778), infrastructure (Q121359), design of a banknote or a coin (Q28794013)”: item must contain property “instance of (P31), subclass of (P279)” with classes “equipment (Q10273457), vehicle (Q42889), vehicle model (Q29048322), watercraft type (Q16335899), railway line (Q728937), canal (Q12284), building (Q41176), weapon model (Q15142894), harbor (Q283202), facility (Q13226383), collection (Q2668072), reservoir (Q131681), factory (Q83405), transport infrastructure (Q376799), lit beacon (Q110113149), petroleum reservoir (Q1845437), fictional entity (Q14897293), aircraft fleet (Q1875630), stock market index (Q223371), system (Q58778), infrastructure (Q121359), design of a banknote or a coin (Q28794013)” 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/P729#Type Q10273457, Q42889, Q29048322, Q16335899, Q728937, Q12284, Q41176, Q15142894, Q283202, Q13226383, Q2668072, Q131681, Q83405, Q376799, Q110113149, Q1845437, Q14897293, Q1875630, Q223371, Q58778, Q121359, Q28794013, SPARQL
Conflicts with “instance of (P31): proposed building or structure (Q811683)”: this property must not be used with the listed properties and values. (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/P729#Conflicts with P31, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

This property is being used by:

he:תבנית:טנק

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Applicability other than aircraft[edit]

Is there any reason this should be limited to aircraft?

Trains (locomotives in particular) seem like this would apply to them.

I have expanded the description to allow other uses.

 – The preceding unsigned comment was added by Hawke666 (talk • contribs). on Jan 14, 2014.

Redundant?[edit]

I don't see any need for this property. Use start time (P580) as a qualifier to operator (P137) instead. /ℇsquilo 16:34, 16 March 2014 (UTC)[reply]

That seems impractical, given the huge number of operators for many classes of equipment (e.g. https://en.wikipedia.org/wiki/List_of_Boeing_747_operators ) In fact, I just tried to work out the use of this for Air Algérie. Here are the start/end date ranges where they operated a Boeing 747:
1975-11-12 – 1976-01-11, 1977-11-01 – 1977-12-14, 1979-10-03 – 1979-10-13, 1979-10-15 – 1980-04-10, 1981-09 – 1981-10, 1982-10-01 – 1982-10-19, 1983-08-22 – 1983-09-11, 1983-09-22 – 1983-10-11, 1985-04-15 – 1985-05-18, 1986-10 – 1991-10-01, 2000-06-28 – 2000-09, 2001-06-25 – 2001-09, 2003-07-02 – 2004-03, 2004-08-18 – 2004-10-17
Not exactly feasible to enter similar content for every one of the huge list of operators… — Hawke666 (talk)
Why not? Every operator started to use the Boeing 747 at some point. /ℇsquilo 09:20, 18 March 2014 (UTC)[reply]
Because there are 262 operators, and if each one has even half of the above, that’s 16 dates apiece — 4000 pieces of information to enter. And that’s just for a a single well-documented plane model. The amount of effort to enter them all would be just absurd. This property is still good enough for a quick overview, even if it does duplicate some more detailed information that may be available. —Hawke666 (talk)
The suggestion is not absurd, quite the opposite. If this data: https://en.wikipedia.org/wiki/List_of_Boeing_747_operators was entered once in wikidata, then the tables you see on that page could be generated in different forms and languages, without the need to manually copy/paste, etc. to different languages. This is the whole point of having large amounts of data in a structured form, it makes things easier once the data has been entered. It allows the data to be used and processed in clever ways by scripts and programs. Danrok (talk) 12:40, 25 May 2014 (UTC)[reply]
I understand the point, and I’m not saying someone shouldn’t go ahead and add that data if they want to. I am however saying that it’s not bad to have something quicker and easier that will work in the majority of cases and be easier to use than the above. —Hawke666 (talk)

This property should contain only one item (это свойство должно содержать единственное значение)[edit]

What if main date is one but for other items (i.e. countries) service entry (P729) has other dates. there should be constraint, if property has more then one meanings - meanings should have qualifiers, i.e. such as country (P17), etc.--Avatar6 (talk) 18:39, 26 March 2016 (UTC)[reply]

Please do not add nonsensical English labels to properties. Danrok (talk) 23:47, 26 March 2016 (UTC)[reply]

property name: service entry or time of service entry or date of service entry[edit]

I dont understand - what completely it means - does it means this item is a process of service entry or place of service entry of that item is or service entry made by or is that item is a process of service entry of. do you? pls do name, at least, properties, as exact as we can, - to not do the babylon tower!!!--Avatar6 (talk) 22:30, 26 March 2016 (UTC)[reply]

Perhaps your understanding of English is at fault here? Danrok (talk) 23:43, 26 March 2016 (UTC)[reply]
@Danrok::Yeah. That's why I want english label to be as exact as it can, as should be on every language
Danrok, pls do add english labels to mean as exact as it can! If you think time of service entry is non-sence comparely to service entry, than do propose better name to define, that property exactly means point in time (date), so it'll be better understood by most users--Avatar6 (talk) 04:25, 27 March 2016 (UTC)[reply]
@Danrok: Perhaps your understanding of what is Wikidata, what is label in Wikidata, what is other names in Wikidata, what is languages/meanings/translations in Wikidata is at fault here? Then may be you at fault here? or finaly do understant the purpose of that things?--Avatar6 (talk) 10:35, 27 March 2016 (UTC)[reply]
Property datatype of P729 is "time". Currently that datatype can only include dates, not times. So, whatever its English label. The value would be a date of entry in service.
--- Jura 09:24, 27 March 2016 (UTC)[reply]
The more it means! I think items/properties names should describe themselves as exact as possible by common sense at apparent language! - to understand them and to do translations and descriptions. Thats to do not mess with possible meanings of terms in languages and semantique of each word in each lang. If they cant - then use aliases... - but why Danrok deleting aliases??? Its nonsence.
datatype of property has'nt exact any readable/understandable commons wth its name/meaning in particular lng.--Avatar6 (talk) 10:17, 27 March 2016 (UTC)[reply]
When you read property name service entry in your browser - do any user understand that this property whether can only include dates, not times nor any other particular info about service entry, if its hasnt term time/data of service entry? I wont them to understand!--Avatar6 (talk) 10:28, 27 March 2016 (UTC)[reply]
The label is not meant to be a long description of the property. Ordinarily the English labels are set to commonly used English terms. The same terms are used elsewhere, in books, on Wikipedia, etc. I can understand that someone who does not speak English as a first language may not know what a label means without looking it up. This is why we can add labels in other languages. Adding every word you can think of as an alternative label really isn't helpful, quite the opposite! Danrok (talk) 12:01, 27 March 2016 (UTC)[reply]
Where we can read offitial Wikidata rule about opinion your expressed in your post? Deleting every word you can think of (not first case of such your doings) is more helpful in searching as more apropriate terms as can?--Avatar6 (talk) 13:45, 27 March 2016 (UTC)[reply]
Does label time of service entry is nonsensical English label? You do not used to mean property you created as your property, isnt it? --Avatar6 (talk) 13:49, 27 March 2016 (UTC)[reply]

Application to ships[edit]

Hi. I have a question about this property's applicability to ships. A ship (particularly a warship) has a number of distinct initial dates:

  1. The date the ship was authorised, i.e. the national authorities agreed to spend money to buy it
  2. The "laid down" date, i.e. the date that construction of the hull of the ship commenced (construction of equipment or armament for the ship may have preceded this)
  3. The "launched" date, i.e. the date at which the ship is first floated
  4. The "commissioning" date, on which the purchaser of the ship formally puts it into service, having tested to see that it meets the specification.

This property could potentially deal with all 4 of these dates, though it is more obvious that it means either the date of launch or commissioning. How should this be used? Can subproperties be created to disambiguate these separate dates? Regards. The Land (talk) 19:16, 25 September 2016 (UTC)[reply]

4 commissioning makes most sense, as only then is it operational. Vicarage (talk) 21:42, 29 August 2023 (UTC)[reply]

Constraint issue[edit]

As currently constrained, this property should only be used on items which are instances of vehicle (Q42889) or appliance (Q1183543). This excludes any item tagged as being an instance of a vehicle class (or, often concurrently, a subclass of vehicle (Q42889)). In the case of mass-produced vehicles, individual instances of a vehicle model aren't usually notable, but using this property on the model item is often useful. -happy5214 09:00, 6 December 2017 (UTC)[reply]

Constraints on usage[edit]

Should this apply also to power stations? As an example, Q1699945. There seem to be no better property to describe when this kind of things started operation. Ita140188 (talk) 05:35, 25 July 2018 (UTC)[reply]

Retrieved from "https://www.wikidata.org/w/index.php?title=Property_talk:P729&oldid=2055747868"