A data product is a unit or component of the data architecture that encapsulates functionality for making read-optimized data sets available for consumption by other domains.

So, yes.. In a way it covers both the data and platform, although you can also make the data directly available, for example, via data virtualization functionality. I'm not being explicit on the shape, because you can use either events, batches, APIs or other techniques to serve data. The data on the consuming side, you're referring to, can also become a data product. In such a situation I recommend to decouple the data from the underlying use case, so another layer of abstraction, which can be again events, batches, APIs, and so on.