motion to drop gist:Component

[marksem]

I think Component is a Role something plays, not a rigid type. Therefore, I think it would be better for it to be modeled as a property.

Text definition of System is currently: "A system is an artifact with component parts where the parts contribute to the goal of the system"

Proposal

• Drop gist;Component
• Change gist:System to be: subclassOf (inverse contributesTo) some Thing
• NOTE It likely should also have something like 'hasGoal some Function, or hasGoal some Behavior', though goal is teleological, so it might exclude things like a 'river system' or 'the water cycle'. So we'd have to decide to do that, or defer it for now, to at least get Component to a role vs. a class.

Relates to #385

[uscholdm]

I agree. The component role can be modled using isPartOf in most if not all cases.