Symbian3/PDK/Source/GUID-788FCBFA-B4FB-4001-B838-4B59995E2E33.dita
author Dominic Pinkman <Dominic.Pinkman@Nokia.com>
Thu, 11 Mar 2010 18:02:22 +0000
changeset 3 46218c8b8afa
parent 1 25a17d01db0c
child 5 f345bda72bc4
permissions -rw-r--r--
week 10 bug fix submission (SF PDK version): Bug 1892, Bug 1897, Bug 1319. Also 3 or 4 documents were found to contain code blocks with SFL, which has been fixed. Partial fix for broken links, links to Forum Nokia, and the 'Symbian platform' terminology issues.

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License 
"Eclipse Public License v1.0" which accompanies this distribution, 
and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
<!-- Initial Contributors:
    Nokia Corporation - initial contribution.
Contributors: 
-->
<!DOCTYPE concept
  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-788FCBFA-B4FB-4001-B838-4B59995E2E33" xml:lang="en"><title>Rights issuer and content issuer</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>A rights issuer is an entity of a content provider that assigns permissions and constraints to DRM content and generates <xref href="GUID-6E09A5CE-F51A-4FFB-A578-70D09C38AAFA.dita">rights objects</xref>. A content issuer is an entity that delivers DRM content. OMA DRM defines the format of DRM content delivered to <xref href="GUID-E7F74FD2-C79E-4C9D-ADBC-5366F424D347.dita">DRM agents</xref> and the way DRM content can be transported from a content issuer to a DRM agent using several transport mechanisms, such as MMS or Bluetooth. The content issuer may do the actual packaging of DRM content, or it may receive prepackaged content from some other source, such as another content provider. </p>
<p>Depending on the deployment, the rights issuer and content issuer roles may be played by the same or different actors, and implemented by the same or different network nodes. For example, in one deployment, content owners may prepackage DRM content, which is then distributed by a content distributor acting as both content issuer and rights issuer.</p>
</conbody></concept>