Property talk:P587
Documentation
Maritime Mobile Service Identity of a ship station. Format 8 or 9 digits
Description | ship identification number assigned by the Maritime Mobile Service, MMSI. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Has quality | numeric identifier (Q93868746) | ||||||||||||
Data type | External identifier | ||||||||||||
Template parameter | en:Template:MMSI Number, used as as subtemplate of en:Template:Infobox ship career - Template:MMSI Number (Q14441357) | ||||||||||||
Domain | According to this template:
ship (Q11446) or more generally watercraft (Q1229765) : ship stations, boats and other marine vessels
According to statements in the property:
When possible, data should only be stored as statementswatercraft (Q1229765), radio communication station (Q1474493), beacon (Q7321258), Maritime Rescue Coordination Centre (Q56885501) or oil platform (Q689880) | ||||||||||||
Allowed values | \d{8,9} (numeric string, 8 or 9 digits) | ||||||||||||
Example | Ebba Mærsk (Q4037895) → 220497000 Queen Mary 2 (Q191888) → 310627000 | ||||||||||||
Source | various sources, exists in some infoboxes for ships, otherwise easily found (note: this information should be moved to a property statement; use property source website for the property (P1896)) | ||||||||||||
Formatter URL | https://www.vesselfinder.com/vessels/details/$1 https://sd.ic.gc.ca/pls/engdoc_anon/mmsi_search.Ship_Search?inMMSI=$1&inVesName=&inName=&inCallsign=&inVesId= https://sd.ic.gc.ca/pls/frndoc_anon/mmsi_search.Ship_Search?inMMSI=$1&inVesName=&inName=&inCallsign=&inVesId= https://www.marinetraffic.com/en/ais/details/ships/mmsi:$1/ | ||||||||||||
Tracking: same | no label (Q28979889) | ||||||||||||
Tracking: differences | no label (Q28979899) | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P587 (Q28979903) | ||||||||||||
Tracking: local yes, WD no | no label (Q28979894) | ||||||||||||
See also | maritime identification digits (P2979), IMO ship number (P458), ENI number (P5910) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P587#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P587#Entity types
List of violations of this constraint: Database reports/Constraint violations/P587#mandatory qualifier, SPARQL
Pattern ^MMSI: -$ will be automatically replaced to novalue. Testing: TODO list |
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Single-value constraint
editThe MMSI number usually changes when the ships change owner, so I think the single-value constraint should change to a single-best-value constraint. Infrastruktur (talk) 13:10, 12 December 2023 (UTC)
- On second thought, since this number is akin to phone numbers, there is little point in keeping old values around. So never mind. Infrastruktur (talk) 23:35, 7 January 2024 (UTC)
Adding required qualifier
editSince MMSI codes tend to change with new owners I'm considering adding "point in time" as a required qualifier to keep track of which ones are outdated. Any objections or blessings? Infrastruktur (talk) 11:26, 27 March 2024 (UTC)
I should add here that I did consider "start time" and "end time" too. But I'm not interested in keeping a log of all the MMSI codes the ship has had in the past. We also may not have access to all the ship's registry details, but we do definitely know if the MMSI code is valid the day it is added, and that is all that I'm interested in. Infrastruktur (talk) 17:20, 28 March 2024 (UTC)