This thread reminds me of a project I started working on about 15 years ago and
some relevant things that came out of it.
To be brief ...
I think it is more accurate, with respect to anything one is recording or
presenting, to refer to it as an "assertion" rather than a "fact". An assertion
is a generalization of a fact or a belief.
Fundamentally, any individual detail we record or say qualifies as one of these:
1. The writer asserts they have first-hand experience, that is they are a
primary source.
2. The writer asserts hearsay, that is they assume or believe something is true
but without claiming first-hand experience or a specific other source.
3. The writer asserts that there is another specific record that is their
source, and they name such, for example a web url or other citation. In the
process they are also asserting that both the other record exists and says what
they are claiming it says. They can also say that the other source claims any
of the 3 categories of assertions I've mentioned here, so we essentially have
chains, he-said, she-said, and so on.
With specific respect to Infobitt, logically each bitt/fact can't logically
assert anything but that "the actor claiming to be this person has made this
other newsy claim and asserts that X third party is the source".
So when you express in terms of assertions rather than facts, you can easily
take into account conflicting claims or claims with different levels of
verifiability. Moreover, by recording chains of sources, and all of this
structure is recursive, everything you say about a source for an assertion is
itself an assertion that can itself have sources etc, you can most accurately
record what you REALLY know. The real power here is you empower others to check
sources for themselves, and use chaining to help with how much they might trust
one thing or another.
What I'm talking about is widely useful, whether in news or encyclopedias or
genealogies or science or law etc.
I believe that through properly applying structures like these, giving
information in a way that users can trust due to personal verifiability etc, any
problem can be solved, any problem at all. I see my life's work as being
related to try and enable this.
Something I like about Infobitt is that its a public project which actually
applies a fraction of what I'm talking about here, in contrast to say Wikipedia,
because Infobitt actually tries to work on the individual detail level, citing a
source for each, rather than blanket sources for an article, so it is
structurally in a better place to be accurate.
-- Darren Duncan
> call an opinions a bitt? "/Saddam Hussain is a dangerous man who possesses
> weapons of mass destruction./" or "/Saddam Husain is a threat to world
> peace/" is this a bitt? Is it a verifiable fact? This escalation of opinions
> turned into a war that still continues. In the run up to the war, a lot of
> people were writing Op-Eds about Iraq and Saddam Husain, while there was no
> actual facts/events happening. Do we count the sudden influx of Op-eds as
> "news", it certainly proved to be. So, at what time do we give importance to
> this opinion and how does the community decide that?
>
> *What am i doing with my prototype:*