Closed nedmsmith closed 2 years ago
I think that we struggled a lot to arrive at the compromise of saying "device". I agree with you that there are composite devices which contain "system components". But, if we do the direction of using that term, we will lose readers and lose comprehension. I do not agree with this proposal. If it is unclear that "device" is a role, then I guess we could add that to the Terminology.
If I were to be pedantic about what a device is using capital letter names, it is both, it's an entity (that performs the role). The Architecture is a description while normative drafts are more precise / formal descriptions or definitions. I don't feel strongly about it. But some people seem to feel strongly that device is used too much. Does it make sense to talk about how we use 'device' and refer to 4949 system component as being roughly equivalent?
We could say one time early in the text that we mean "system component" when we mean device, but for the sake of simplicity use device as a representative concept throughout the document.
Makes sense.
The word 'device' is used dozens of times throughout the document. However, it often doesn't imply 'device' but rather a component of the device. RFC4949 defines 'system component' as: system component
This definition seems appropriate for most of the places where 'device' is used. Alternatively, 'system' could be used if 'system component' would be to narrow.