Open main menu

Property talk:P289

Documentation

vessel class
series of vessels built to the same design of which this vessel is a member
DescriptionVessel class (ship class, submarine class or spacecraft class) to which a vessel belongs.

This property is the main indicator for large vessels; it triggers multiple constraint validations (listed below).

Part of WikiProject Ships properties
Showcase ship class item: Nelson-class battleship (Q1329840)
Representsvessel class (Q19832479)
Data typeItem
Template parameter"ship class" in en:Template:Infobox ship characteristics - Template:Infobox ship characteristics (Q14114368)
Domain
According to this template: vessel (Q16391167), most generally ship (Q11446)
According to statements in the property:
watercraft (Q1229765), vessel (Q16391167), fictional ship (Q16708006) and fictional spacecraft (Q14637321)
When possible, data should only be stored as statements
Allowed valuesinstances of ship class (Q559026), types of ship (Q11446) (note: this should be moved to the property statements)
ExampleCosta Serena (Q1136377)Concordia-class cruise ship (Q1124097)
USS Enterprise (Q834003)Constitution class (Q3265302)
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: usageCategory:Pages using Wikidata property P289 (Q28525757)
Lists
  • Items with the most statements
  • Count of items by number of statements (chart)
  • Count of items by number of sitelinks (chart)
  • Items with the most identifier properties
  • Items with no other statements
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history
  • Chart by item creation date
  • Database reports/Constraint violations/P289
  • Proposal discussionProposal discussion
    Current uses11,354
    Search for values
      Value type “vessel class (Q19832479), fictional spacecraft class (Q18039177): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value vessel class (Q19832479), fictional spacecraft class (Q18039177) (or a subclass thereof). (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P289#Value type Q19832479, Q18039177, SPARQL, SPARQL (new)
      Conflicts with “instance of (P31): ship (Q11446): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P289#Conflicts with P31, search, SPARQL, SPARQL (new)
      Property “subclass of (P279)” declared by target items of “vessel class (P289): If [item A] has this property with value [item B], [item B] is required to have property “subclass of (P279)”. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P289#Target required claim P279, SPARQL, SPARQL (by value), SPARQL (new)
      Property “short name (P1813)” declared by target items of “vessel class (P289): If [item A] has this property with value [item B], [item B] is required to have property “short name (P1813)”. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P289#Target required claim P1813, SPARQL, SPARQL (by value), SPARQL (new)
      Property “image (P18)” declared by target items of “vessel class (P289): If [item A] has this property with value [item B], [item B] is required to have property “image (P18)”. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P289#Target required claim P18, SPARQL, SPARQL (by value), SPARQL (new)
      Property “operator (P137)” declared by target items of “vessel class (P289): If [item A] has this property with value [item B], [item B] is required to have property “operator (P137)”. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P289#Target required claim P137, SPARQL, SPARQL (by value), SPARQL (new)
      Property “topic's main category (P910)” declared by target items of “vessel class (P289): If [item A] has this property with value [item B], [item B] is required to have property “topic's main category (P910)”. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P289#Target required claim P910, SPARQL, SPARQL (by value), SPARQL (new)
    Require explicit subtypes of ship (Q11446); use the ship type (Q2235308) of the vessel class (P289)


    Indirect property requirements on target ship classes
    See also Wikidata:WikiProject_Ships/Properties#Ship_classes


    Future requirements (too much data imports still missing)
    Ships: require pennant number (P879) on all ships that belong to a class (75% missing one, as of Jan 2015)

    {{Constraint:Item|property=P879}}

    Ship classes: require service entry (P729) (90% missing, Feb 2015)

    {{Constraint:Target required claim|property=P729}}

    Ship classes: require service retirement (P730) (98% missing, Feb 2015)

    {{Constraint:Target required claim|property=P730}}


    NameEdit

    Shouldn't this property renamed simply as "class"? So it could be used in general, for other things too. --#Reaper (talk) 19:42, 8 April 2013 (UTC)

    No. This is for ships, that were built, launched, operated and eventually scraped. -- LaddΩ chat ;) 18:58, 31 January 2015 (UTC)

    The property is used for ships AND submarines, therefore renamed from "ship class" to "watercraft class". FreightXPress (talk) 18:13, 25 April 2015 (UTC)

    @FreightXPress: "ship" in ship class means "vessel" - it includes spacecrafts, submarines, hydrofoils etc. -- LaddΩ chat ;) 22:39, 25 April 2015 (UTC)
    @Laddo: In Wikipedia it says "A ship is a large buoyant watercraft." In Wikidata a ship is subclass of watercraft and subclass of vessel. How can readers of Wikidata be aware of the re-definition of the English language word "ship" in P289? FreightXPress (talk) 12:28, 26 April 2015 (UTC)
    @FreightXPress: ;) You were pretty quick to create vessel class, but I'm personally OK with that term. There will be some re-writing needed in Wikidata:WikiProject Ships... -- LaddΩ chat ;) 12:46, 26 April 2015 (UTC)
    @Laddo: ;) I did that to reflect your addition of that term to the description in the property page [1]. FreightXPress (talk) 12:55, 26 April 2015 (UTC)

    Nominated for deletionEdit

    I nominated this for deletion at Wikidata:Properties_for_deletion#Property:P289. Superm401 - Talk 23:41, 28 May 2013 (UTC)

    Related discussions:
    and also
    -- LaddΩ chat ;) 19:03, 31 January 2015 (UTC)

    Error in documentationEdit

    USS Enterprise is not a watercraft. Andrea Shan (talk) 02:47, 25 November 2014 (UTC)

    Changes to vessel classEdit

    (copy from my talk)

    Please see this discussion] on en:wiki - Your changes to the vessel class field may have broken a bunch of Infoboxes that are (attempting to) import data from Wikidata.Nigel Ish (talk) 18:04, 26 April 2015 (UTC)

    Please provide details how that field is used in English Wikipedia at Property talk:P289. I tried to understand en:Template:Infobox ship characteristics but didn't see how the problem could be based on my edits to the "vessel class field". I did not edit Southern Swan (Q15628294). FreightXPress (talk) 18:22, 26 April 2015 (UTC)
    I guess, in the template |WD=ship class should be replaced by |WD=P289 --Pasleim (talk) 18:26, 26 April 2015 (UTC)
    As a quick fix I changed "subject item of this property" back to "ship class". But Southern Swan even with page purge was still broken. So, maybe they really rely on the label. FreightXPress (talk) 18:33, 26 April 2015 (UTC)
    Label change did not help either. FreightXPress (talk) 18:39, 26 April 2015 (UTC)
    Fixed. Please know what will be effected before you make such changes. And why isn't there the equivalent of a redirect that would have eliminated this kerfuffle?
    Trappist the monk (talk) 19:03, 26 April 2015 (UTC)
    It is impossible to know that. Please take more care, and why did you change to the new label, instead of following the suggestion of Pasleim to use "|WD=P289"? Changing a statement will never create a redirect. FreightXPress (talk) 19:10, 26 April 2015 (UTC)
    But I agree, "ship class" is an alias, so the software could have handled it. No idea why not. FreightXPress (talk) 19:13, 26 April 2015 (UTC)
    Before you changed from 'ship class' to 'vessel class', did you consult with any of the consumers of that data? If you did not, then don't be asking me to take more care.
    [Why] did [I] change to the new label, instead ... of using "|WD=P289"? Because to mere humans, 'P289' is a meaningless construct that conveys no useful information. This is my biggest objection to Wikidata. Every tidbit of information must, must, be labeled with human-readable names that are understandable by humans in a way that is meaningful to us in our everyday languages. We are clever enough to create programming languages so that we can write and read programs and understand them outside of their native binary representation. This same must apply to Wikidata: leave the translation of 'vessel class' → 'P289' for the machine; 'P289' should rarely if ever appear where a human uses it. Alpha numeric strings like 'P298' can't be spell checked; what if I inadvertently type 'P299'? I know that I wanted to type 'P289' so that is what I see. At least if I misspell 'vesel class', my browser's spell checker can help me.
    Now, to add to the above, I have new objection: an editor can rename something at Wikidata and thereby corrupt who knows how many articles across the whole of Wikimedia.
    Trappist the monk (talk) 19:53, 26 April 2015 (UTC)
    @Trappist the monk: P289 is the permanent identifier. Period. (This is not changing any time soon. [heh]) Any other value on this page is subject to change, and so IMO not using P289 in the Lua or elsewhere is asking for trouble and thus isn't our fault. (Though maybe there aren't enough big red warnings in the documentation...?) If you want to get the value of 289 but have something human-readable, is it not trivial to assign the value of 289 to a variable (in Lua), or to comment the meaning of the number in the context of a wikitext template?

    Regards things changing across the whole of Wikimedia, this comes with the positives as well as the negatives, so I'm not going to take that objection up in any detail. --Izno (talk) 16:57, 28 April 2015 (UTC)

    What probably should happen, as pointed out somwhere earlier, is that referencing an alias should resolve to the property value. The concern of course with any non-unique ID being the referenced value is that you could run into ambiguous cases. I'm fairly certain we don't have any so far, but if you start permitting the alias to be a reference value, pulling the value could get messy quick (at which point you should just have used the unique value anyway). --Izno (talk) 17:12, 28 April 2015 (UTC)
    I believe User:Bene* recently released this change to ensure that property labels and aliases remain unique, ignoring the case. -- LaddΩ chat ;) 17:24, 28 April 2015 (UTC)
    That change doesn't appear to affect aliases. --Izno (talk) 19:24, 28 April 2015 (UTC)

    No longer used by WikipediaEdit

    See this discussion and this change. ---- LaddΩ chat ;) 13:55, 13 December 2015 (UTC)

    Use with locomotives?Edit

    Might this be adapted for use with locomotives as well as (oceangoing) vessels? It seems to have the same derivation (individuals which share a common prototype and are generally the same perhaps with minor differences).

    Examples of usage:

    Return to "P289" page.