Clarifications.

1. Obviously, the singular quale and plural qualia are used interchangeably.

2. Sense data (singular sense datum) are also used in philosophy, however,
I don't think a distinction is required because I use the term in a
different enough sense not to have to think that they'd ever clash. I use
sense data because a sense datum is data that has been generated by some
sensation.

3. The action of my qualia (paraqualia) would, with a few other bits of my
concept, I contend, give rise to philosophical qualia.

4. My Java peer devices have been developed with the help of Netbeans, and
hence, are the reason why I am a user of Netbeans and I am writing to this
email list.

5. An individual quale wraps a distinct sense datum. No two qualia will
wrap the same sense datum.

6. Qualia are singletons. Sense data are not; more than one sense datum may
describe a distinct sensedation, but if a corresponding quale exists in the
quale container, it will wrap only one sense datum instance. Hence,
internalising any corresponding sense datum will return the same quale from
the quale container, but externalising a quale will only return the sense
datum instance wrapped in it. Internalising this sense datum will return
the same quale instance from the quale container, and externalising this
quale will return the same sense datum instance as it did before.

7. A sensation, encoded in a sense datum, is a state. A state isn't
necessarily a sensation. This is a difference borne out from the
implementation, and it appears that this difference must transcend
implementations.

8. Qualia can be composed of other qualia; sense data can be composed of
other sense data. The structure of this composition is mirrored in these
two concepts.

Alright. I think I'm done with this off-topic disclosure.

On Sat, 19 Sept 2026 at 11:22, Owen Thomas <[email protected]>
wrote:

> Seeing as I have been asked, I'll let everyone on the Netbeans users' list
> know a bit about Clique Space(TM).
>
> Clique Space is what I call my work. It is based upon the communication of
> the real-time state of one's devices; within one's own network, and between
> networks that represent any number of individuals. You own the devices in
> your own network; this is called your co-sovereign Clique Space, and these
> devices represent your physical presence in cyberspace to yourself and to
> others.
>
> The basic unit of state in Clique Space is called the "quale". I took this
> term from philosophy because I envisage my qualia to serve a purpose that
> is similar in concept to the phenomenon of the same name presented in
> philosophy of mind. To avoid confusion, it seems preferable to use the term
> "paraqualia" to refer to my term when discussing philosophical implications
> of my work so the domain-dependent contexts remain separate and
> confusion is avoided. I will herein use qualia because I will not be
> making any further direct reference to qualia in philosophy.
>
> A Clique Space aware hardware or software device hosts an instance of a
> peer device. These peers (currently implemented in Java) maintain knowledge
> about the state of their world as collections of qualia in a quale
> container. Pairs of qualia in the quale container can build arbitrarily
> complex relationships by being associated in a structure called a
> resonance, which is also a quale, held in the quale container. Qualia are
> singletons; only one quale describing a specific state can exist in the
> quale container at a time.
>
> State is described by a sense datum. Qualia are individually known by a
> sense datum. Every quale wraps a sense datum, but not all sense data are
> wrapped in qualia; a sense datum is internalised to yield a quale, and a
> quale is externalised to yield the sense datum instance that it wraps.
> Sense data are serialisable proxy objects; the serialised equivalents of
> sense data can be persisted and communicated between Peers.
>
> That's plenty for now. I would welcome constructive criticism and comment
> about what I've been up to.
>
> Have a great day.
>
>   Owen.
>

Reply via email to