Data sets, Data collections, Data aggregates - what is the proper BFO branch? #365
jonathanvajda
started this conversation in
General
Replies: 2 comments
-
Some common suggestions:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Discussions of this issue, and other ICE-related issues, are occurring in other forums, so this issue will be converted to a discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to sort out what a collection of information entities is. If someone says, "I have a dataset", I want to translate that into either the Information Bearing Entity (IBE) that carries multiple ICEs, or the Information Content Entity (ICE) that has multiple ICEs as parts.
The purpose: I want to get all the information asserted in the data set. I'm leaving it ambiguous what is the nature of the data set so far.
Here's my grasp of an important difference between IBEs and ICEs, that I haven't heard anyone assert:
I want to run through some examples.
What is the best way to conceive of the entity called a data set, in the last two bullets?
If the data set is an IBE, then it is a part of the server IBE, and the gain or loss of a row of data just is a change in the qualities (or IBE parts?), and the maximal ICE carried by the dataset at time 1 is not the same as the maximal ICE carried by the dataset at time 5.
If the data set is an ICE, then we cannot say that the data set is token identical across time1-time5.
Is there a best practice to capture the totality of ICEs in a data set?
Beta Was this translation helpful? Give feedback.
All reactions