Skip to content

System Role definition and 'arrangement of parts or elements' #302

@gregfowlerphd

Description

@gregfowlerphd

According to the definition, a system role inheres in an entity only if that entity is ‘an arrangement of parts or elements’. This doesn’t seem correct (or, at least, is a non-perspicuous way of putting things). Presumably material entities are supposed to be capable of having system roles. But no material entity is an arrangement, since the latter (it would appear) is a certain complex feature a plurality of entities have in virtue of the relations between them.

A better formulation of the definition, I think, would be something like the following:

A Role that inheres in an entity in virtue of its parts or elements being arranged in such a way that they together exhibit behavior or meaning that they do not exhibit individually.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions