No, the end users don't care what we named our internal object, and they're already used to "SubscriptionDataFile" as the parameter name. We also have a bug to add back compatibility with the old file format, so it really will be a "SubscriptionDataFile"