Are Components a candidate for reusable data models across application layers including Framework and Enterprise layers?
Look to package capability in a Component that can be used - standalone - regardless of which other Rulesets are available on your Ruleset stack.
Typically the data model used by an Application is composed of a combination of Enterprise-wide and Application-specific data types (as well as Framework-layer data types, if you are using Frameworks), and the data types would be encapsulated in those traditional layers. However, one client I have been at needed to publish audit events according to an industry-defined data model. Whilst we encapsulated that into a distinct Ruleset in the Enterprise Layer, this would have been a good candidate for a Component.