When the Qtopia stack is released a DRM compliance statement is made as part of the release. The Qtopia software as integrated into a final ROM image must implement compliance with DRM standards as per the compliance statement.
In OMA DRM compliance, compliance with the later-listed compliance points requires compliance with all previous levels as well. When reading the listings of compliance levels, bear in mind that each level includes rather than supersedes the previous levels. The only exception to this is for devices that support Forward Lock only, these must discard messages which contain a rights object. This requirement goes away under higher levels, obviously to be compliant those rights objects must be handled appropriately.
Under OMA DRM v1 devices which only comply with Forward Lock provisions can still be said to be standards compliant - these are the only provisions with the MUST keyword, the others are MAY. Forward Lock does not use any rights object and thus is the simplest to implement.
OMA DRM v1 Forward Lock (FL) compliance is enabled and initial integration of a 3rd party DRM solution completed. In line with OMA DRM v1 FL content is encrypted by the 3rd party agent if saved onto device storage.
Files and content subject to Digital Rights Management are able to be transparently (to the user) browsed, launched, moved, deleted and examined for their properties in the same way as other files.
File operations for example copy, move, rename are handled via the QContent API and follow OMA DRM standards for DRM controlled files. Access to DRM protected files is available in the server (backgrounds) and media player.
DCF encrypted files cannot be directly queried (/etc/magic) or file.extension checked for mime-type, the DRM agent must be asked for this information. Thumbnails of protected images are available without decrementing rights through the QContent API. Thumbnails of images with usage restricting rights (count, unstarted intervals) are watermarked and have the number of available uses superimposed in the top right corner. Thumbnails are not available for images with no current access rights.
DRM status is maintained in meta-information and can be viewed in the properties of a file. DRM is integrated into the content browser and DRM status is shown in different iconization.
DRM-type:
not subject to DRM - normal icon for that mimetype
DRM valid rights (able to view/render) - as normal, with DRM indication (key superimposed)
DRM invalid rights (not able to view/render) - show grayed out with key
The DRM agent functionality is provided by BeepScience DRM Agent. This is the Qtopia reference integration.
