Topic on User talk:Swpb

Jump to navigation Jump to search

Interface, means, and cause classes

2
Daask (talkcontribs)

I removed the claim that means (Q12774177)subclass of (P279)cause (Q2574811), which I acknowledge was rather reckless and left Wikidata's class hierarchy in an undesirable state. Frankly, I didn't know what the appropriate superclass was then, and I don't know now.

Let's consider some of means (Q12774177)'s current direct subclasses:

A means, such as a search strategy, is just one way of achieving a goal. It is not the agent selecting or pursuing the goal. It may or may not be necessary for the goal to be achieved or change the outcome. With no change in the outcome or the probability of an outcome, it doesn't seem to me that we have the quality of w:en:Causality. Thus, I'm uncomfortable with the claim means (Q12774177)subclass of (P279)cause (Q2574811).

Separately, regarding the claim: interface (Q110558466)subclass of (P279)means (Q12774177). means (Q12774177) has a quality of functionality or purpose, whereas interface (Q110558466) may just be a point where two systems interact, without necessarily being part of any larger system. It may or may not be functional for either of the two systems which are interacting, thus I think it lacks this quality.

Swpb (talkcontribs)

How about means (Q12774177)subclass of (P279)converter (Q35825432)? A converter (Q35825432) is something that doesn't necessarily cause, but can cause.

And for the latter claim, how about interface (Q110558466)subclass of (P279)object (Q488383)? It may be hard to get more specific than that.

Reply to "Interface, means, and cause classes"