The article also says that it's normal that if you have Apple Music, but you don't have Itunes Match, your offline content will then have DRM.
I don't really see the justification for this. If I own the music, I have purchased it as a DRM free copy. Why should Apple then have the right to put DRM on it if I download it back again?
I've also seen a couple of reports claiming that Apple Music actually changed a file to a DRM file on someones PC after they listened to the file (when it was previously non DRM), not to mention the many reports stating that DRM is being imposed even when the person is subscribed to Itunes Match as well.
If these are true this is what is really disturbing - it's the feeling that if you have a large music collection, is Apple secretly changing some or all of your files to DRM files behind the scenes (whether it be a bug or intentional, the result is the same)?
Firstly, I would like to see a statement from Apple that under no circumstances will they replace an existing unprotected music file with a DRM one.
Secondly, I am hoping they will say that files that you have already purchased or uploaded from CD that you own should remain unprotected at all phases. Unfortunately the article you linked suggest that it's intentional that if you have only Apple Music and not Itunes match, any file you download will have DRM even if it was from your own music library originally.
Next, I do agree with some of the other comments on this forum that Apple should somehow provide an option to "unlink" a track on your local files from Apple Music such that your own copy is an upload. This can avoid all the situations where the wrong track is matched.
Finally, they should provide a way to completely erase a track from the cloud with all metadata and re-upload. I've seen various situations where tracks appeared wrongly on some devices, and even after attempting to completely delete from the cloud, changing metadata, and deleting all trace of it and re-importing from CD, it still somehow remembered the previous data and carried on displaying it wrong on the IOS device.