Comments (1)
Thank you for the comments and research on this topic!
I'll make some comments on your proposed definitions and then some some general suggestions.
Definitions
Although it seems like a fiat object part of a longer cable, connectors would be their own 'Material Artifact.' A Fiat object part would be an arbitrary part of a cable, but the place where the connector begins and cable ends seems more bona fide than fiat. Also, connectors can be built and sold on their own, without a cable at all, like electric connectors for iPhones and power adapters for building wall sockets. A connector may be part of a cable, but it is not necessary.
Also, I would clarify that you mean electric connector, as opposed to other types of connectors for plumbing, for example.
A convention we use in creating definitions for Artifacts is to define the artifact in terms of the function that the artifact was designed for. So, an electronic connector is a material artifact designed to allow for the flow of electronic power between other artifacts? Just a start, not a final.
'Genders' and styles of electronic connectors are similar to car body types in that they come in a wide range of varieties and there may be special, one-off, or hybrid types that are routinely invented/created, just something to keep in mind. My initial impression is that these types are fiat object parts of connectors, since you can't have a connector without it being of such and such type. Every connector has a type, but the connector itself isn't just the type (the prongs, for example), so it seems like each connector
has part
some electronic connector pattern
.
The connection patterns are material types, not specifically dependent continuants. We might colloquially say that a power connector 'bears' some type, but it's really got an instance of a type as a part, steering me toward fiat object part.
I'm not sure what requirements that a power connection specification
prescribes. The requirements of the device that is using the power ('This device needs AAA batteries)? Or the power connector type, like prong or jack?
Open Questions
We would be happy to include 'electronic connectors' as a top level term, but I (personally) think that a full, nuanced representation should belong in a domain extension ontology build off of CCO. The purpose of the CCO is to cover a wide array of everyday entities--as opposed to medically and biologically relevant entities--so developers may have clear guidance on how to represent a special domain and be compatible with other ontologies that also use the Common Core. Your work here seems very relevant to the Industrial Ontologies Foundry (https://github.com/iofoundry/ontology), and they might be very receptive to including your work as an extension module. However, there may be plans to unify our communities and align together, so perhaps it is best to wait on committing. The IOF and CCO diverged a few years ago, so many of the things I said here would still be relevant for including your ontology there. Recently, a paper was written describing a 'maintenance' module that extends IOF, and your project seems similar in its place in a wider industrial ecosystem (https://arxiv.org/abs/2404.05224).
Also, if we were to fully acquire the representation of electronic connectors, it might slow the development of the domain since we are not specialists and do not have a primary interest in its full representation, as you might.
At first, Relational Quality seems like a good place for compatibility, but it seems like a very generic term that could either be narrowed or include new subclasses. Since one of the examples of relational quality is compatibility, it might be often mistaken for compatibility of personality. Perhaps 'Mechanical Compatibility' would be better. The other option is to say that there is a measurement, and that compatibility holds between two connectors which have been measured to be complimentary, though this starts to really get in the weeds, and one may have to start listing a large number of common connector types and which other types they are compatible with... which feeds into my opinion that the full representation of this idea should be in a domain extension (but I am open to other opinions).
from commoncoreontologies.
Related Issues (20)
- Define payload in terms of role and other payload issues HOT 5
- Definitions of Communication Reception Artifact Function's subclasses are too broad HOT 2
- Subclass relation between Poison Artifact Function and Damaging Artifact Function might be mistaken HOT 3
- Definitions of Signal Detection Artifact Function and Signal Processing Artifact Function too broad HOT 6
- Natural satellite (Portions of atmosphere, cryosphere, hydrosphere, lithosphere) HOT 3
- atmospheric, hydrographic, physiographic features HOT 3
- Definition of ‘Life Support Artifact Function’ too broad HOT 3
- Definition of ‘Sound Pressure’ ambiguous
- Artifact Function subclass justifications HOT 3
- Definitions of ‘Loudness’ and ‘Pitch’ suggest an unasserted subclass relation HOT 2
- Current version of CCO accessed on web does not import BFO! HOT 13
- Use of ‘describes’ in definitions of ‘Velocity’ and ‘Angular Velocity’ HOT 3
- Improve Definition Sources HOT 2
- Issue with definitions of ‘Waveform’ and ‘Wavelength’
- Use of ‘instance of’ in ‘has member of located in’ definition and other ERO definitions HOT 2
- Lack of context in definition of ‘has object’ HOT 1
- Problems with definitions for subproperties of inheres in aggregate
- Misuse of temporally projects onto in definition of ‘is temporal region of’? HOT 2
- Change definition of 'Pointing Orientation' HOT 2
- UnParseable http URLs
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from commoncoreontologies.