There is a wide range of use cases where vehicles are described with respect to their vehicle plate (and the number), and this assists with entity resolution. This seems useful for manufacturing, commerce, government, university, and other contexts. I think this makes a good case for it being included in the common core rather than a lower-level ontology.
Just as with VIN (see the other issue #204 ) we need to be clear on what design pattern we are following here. Is this correct?
VehicleLicensePlate subClassOf cco:OneDimensionalBarcode
VehicleLicensePlateNumber subcClassOf cco:CodeIdentifier
For example:
VehicleLicensePlate _carries_ VehicleLicensePlateNumber
VehicleLicensePlate _has_text_value_ "ABC 1234"
VehicleLicensePlateNumber _designates_ VehicleLicense
My hesitation is that a vehicle plate number does not designate a vehicle, but rather a vehicle license. But people use it to designate a vehicle, indirectly. Is this correct?
There is a wide range of use cases where vehicles are described with respect to their vehicle plate (and the number), and this assists with entity resolution. This seems useful for manufacturing, commerce, government, university, and other contexts. I think this makes a good case for it being included in the common core rather than a lower-level ontology.
Just as with VIN (see the other issue #204 ) we need to be clear on what design pattern we are following here. Is this correct?
For example:
My hesitation is that a vehicle plate number does not designate a vehicle, but rather a vehicle license. But people use it to designate a vehicle, indirectly. Is this correct?