-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
definition of Information Quality Entity #604
Comments
We should think about whether a more general term is more appropriate. Consider a pattern that is alternating red and blue. Colors are (properly) dispositions in CCO. So do we have an information quality entity here, made only of dispositions? The more general term would be 'information concretization entity' and it's definition would drop the quality requirement, being simply: =def concretizes some Information Content Entity |
I have been reading this paper to try to understand concretization in terms of BFO as a top level and CCO as a midlevel. Giacomo DeColle - Representing Cyberspace with the Basic Formal Ontology Although your proposed change sounds simpler, I am not sure this approach makes it simpler. Perhaps there is a logic representation that is made easier by making it more direct? The quality seems to be the linchpin according to the paper. Is there a distinction between concretization and bearing in the logic statements that could save a step? Is 'relation of concretization' defined to logically require 3 parts? De Colle, conferring with John Beverly seems to indicate that three elements are necessary when considering information.
Thanks for any wisdom you can provide. |
I think this should be defined by an equivalence class. The current axiom isn't quite right. For instance, if you have a square computer, that would satisfy the axioms for IQE, since square is a shape quality* and it inheres in a IBE.
The definition should be, IMO =def quality and concretizes some Information Content Entity
You can leave the current axiom as well, since it is still true.
The benefit of making it a defined class (i.e defined by equivalentClass) is that you might not want to subclass it directly since doing that might lead to multiple asserted superclasses, if there's a difference way that the particular IQA is classified in the ontology.
There's a time element to this. Whether something is an IQA can be time dependent. The example I've used is a swimming noodle shaped into a logo. While it's that shape its an IQA, but when the shape changes - it goes straight - it stops being an IQE.
The text was updated successfully, but these errors were encountered: