CommonCoreOntologies
CommonCoreOntologies copied to clipboard
CommonCoreOntology
New Terms for CCO 1.5 Consideration
In anticipation of the upcoming 1.5 release which will sync to the BFO 2020 release, I want to put a list of terms and changes for consideration in one issue.
Terms:
- Odometer = def. An Information Bearing Artifact that is designed to bear some Information Content Entity that measures the distance of some spatial region that was the location of some Act of Location Change. OR a simpler version: An IBA that is designed to bear some ICE that measures the distance an entity has traveled. An Odometer bears a Distance Measurement Artifact Function.
- Mileage = def. A Distance Measurement Information Content Entity that measures distance in Miles. (looking for definition suggestions!).
- VehicleLicensePlate = def. A One-Dimensional (or Three?) Barcode that is designed to carry an ICE about the registration and/or legal status of the vehicle to which it is attached."
- WorkShift = def. A One-Dimensional Temporal Region during which a person performs tasks and acts in accordance with some contract or employment agreement.
Other changes:
- Make is_tokenized_by a data property. I am not confident others will agree, not sure if I agree, but I want to ask for thoughts. I know a number of ontologies are using it already, and I think we should thinking about doubling down. Right now it's an annotation property. Happy to push this issue down the line to a later release, but just start the conversation.
- CCO curate process profile. This is a hot button topic right now, so I'm happy to push this off to a later release, but I would be comfortable with CCO curating process profile, if and only if process profile can be clarified and vetted in the next few months.
Happy to amend any of these, change definitions, etc.
@cameronmore Your proposals with regard to Odometer and Mileage raise some questions about the concept of distance in CCO. There are currently (on branch bfo2020-core) two distance-related classes: Distance Measurement Information Content Entity and Distance Measurement Artifact Function. The definition of Distance Measurement Artifact Function is:
A Measurement Artifact Function that is realized during events in which an Artifact is used
to measure the spatial Distance to a specified object or class of objects.
"Distance" is capitalized. Someone must have intended it to be a class. That class was never added. It should be, probably as a subclass of One-Dimensional Extent, per the definition in Distance Measurement Information Content Entity.
One elucidation in Distance Measurement Information Content Entity says displacement is the shortest distance between two points, and that "further thought is needed" to handle paths, of which a curvy road is an example. It would be good to iron out the details before adding "Odometer" and "Mileage".
My first thought is to propose that CCO class Distance Measurement Information Content Entity should be Displacement Measurement Information Content Entity. There should be a new Distance Measurement Information Content Entity class to accommodate devices like odometers.
Good points. As I'm thinking about distance, I'm wondering if it's too general. Distance could be something like the distance between two points, 2D Distance, or the distance between things in a 3D space like the distance between cities on a road. Do we mean "extension in a spatial region" when we say distance? If so, we already have terms more clearly delineating one type of space from another. I would rather change the definition to say 'spatial region' rather than adding a class.
Distance can be displacement but displacement is not always distance, so they would be siblings in the hierarchy, not parent and child. Is displacement just distance in a 2D spatial region and distance the measurement of a 3D region?
Often when we talk about odometers measuring distance, we mean that the odometer measures the distance of the cco:ThreeDimensionalPath which is defined as A Three-Dimensional Spatial Region that encompasses the spatial region through which some Object travels. When we talk about geospatial distances, even if we think we're talking about straight lines, we mean the straight lines that bend around the curve of the earth.
All said, I like your comment and want feedback to keep the discussion going, those are just some of my immediate hesitations.
Talking with @mark-jensen , he noted that in modern cars, usually other sensors collect data that is used to calculate the mileage, and those sensors feed into other calculations as well (i.e. they are not purely odometer sensors).
He also pointed out that mileage is really just a Distance Measurement ICE that uses Miles as the Measurement Unit, so I'm thinking if there is a need to add it given we can handle it with those other two classes. @jonathanvajda
Hey Cameron,
Mark is right. I independently realized the design pattern for mileage should work that way, but forgot to reply. It is good for confirmation!
All the best, Jonathan Vajda /dʒɒnɑθɑn vaɪdɑ/
On Thu, Nov 30, 2023 at 1:21 PM Cameron More @.***> wrote:
Talking with @mark-jensen https://github.com/mark-jensen , he noted that in modern cars, usually other sensors collect data that is used to calculate the mileage, and those sensors feed into other calculations as well (i.e. they are not purely odometer sensors).
He also pointed out that mileage is really just a Distance Measurement ICE that uses Miles as the Measurement Unit, so I'm thinking if there is a need to add it given we can handle it with those other two classes. @jonathanvajda https://github.com/jonathanvajda
— Reply to this email directly, view it on GitHub https://github.com/CommonCoreOntology/CommonCoreOntologies/issues/207#issuecomment-1834316198, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIW242ENREK6GIKWT2UTDUDYHDFCJAVCNFSM6AAAAAA74RAWZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGMYTMMJZHA . You are receiving this because you were mentioned.Message ID: @.***>
