Digital Rights Management - Revision history

Tom: /* Device Control */

2026-02-27T17:33:39Z

‎Device Control

Tom: /* Policy */

2025-06-10T16:20:26Z

‎Policy

Tom: /* Policy */

2025-06-10T16:19:25Z

‎Policy

Tom at 16:17, 10 June 2025

2025-06-10T16:17:55Z

Tom: /* Device Control */

2023-02-12T00:45:32Z

‎Device Control

Tom: /* Policy */

2023-02-12T00:44:51Z

‎Policy

Tom: /* Policy */

2023-02-12T00:42:59Z

‎Policy

Tom: /* Policy */

2023-02-12T00:42:23Z

‎Policy

Tom: /* Policy */

2023-02-12T00:41:14Z

‎Policy

Tom: /* Device Control */

2023-02-12T00:40:26Z

‎Device Control

@@ Line 15: / Line 15: @@
 ==Solutions==
 ===Device Control===
-* At first the media companies attempted to convince the lawmakers that it was someone else's problem to protect their revenue stream.  That worked for a while, but eventually they backed off.
+* At first the media companies attempted to convince the lawmakers that it was [[Someone Else's Problem]] (SEP) to protect their revenue stream.  This SEP field worked for a while, but eventually they had to back off.
 * Enterprise-owed devices allowed the Enterprise to install Mobile Device Management (MDM) on the device and continue to control their content no matter where the user would travel.
 * Bring your Own Device (ByoD) to work allows some level of control, but there is resistance to allowing an Enterprise MDM on a user-owned device.

@@ Line 24: / Line 24: @@
 * [https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml OASIS eXtensible Access Control Markup Language (XACML) TC] with errata Version 2 (2008-07-29), version 3 (2017-07-12). <blockquote>The [https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml XACML Technical Committee] defines a core XML schema for representing authorization and entitlement policies.</blockquote>
 * [https://www.w3.org/TR/odrl-model/ 2018-02-15 ODRL Information Model 2 W3C Recommendation] <blockquote>Policies are used to represent permitted and prohibited actions over a certain asset, as well as the obligations required to be meet by stakeholders. In addition, policies may be limited by constraints (e.g., temporal or spatial constraints) and duties (e.g. payments) may be imposed on permissions.</blockquote>
-* [https://www.w3.org/TR/odrl/#:~:text=The%20Open%20Digital%20Rights%20Language,expressing%20rights%20information%20over%20content.&text=The%20ODRL%20has%20no%20license,of%20%22open%20source%22%20software. Open Digital Rights Language (ODRL) Version 1.1] (2002-09-19) <blockquote>The Open Digital Rights Language (ODRL) is a proposed language for the Digital Rights Management (DRM) community for the standardization of expressing rights information over content. The ODRL is intended to provide flexible and interoperable mechanisms to support transparent and innovative use of digital resources in publishing, distributing and consuming of electronic publications, digital images, audio and movies, learning objects, computer software and other creations in digital form. The ODRL has no license requirements and is available in the spirit of "open source" software. </blockquote>
+* 2002-09-19 [https://www.w3.org/TR/odrl/#:~:text=The%20Open%20Digital%20Rights%20Language,expressing%20rights%20information%20over%20content.&text=The%20ODRL%20has%20no%20license,of%20%22open%20source%22%20software. Open Digital Rights Language (ODRL) Version 1.1] <blockquote>The Open Digital Rights Language (ODRL) is a proposed language for the Digital Rights Management (DRM) community for the standardization of expressing rights information over content. The ODRL is intended to provide flexible and interoperable mechanisms to support transparent and innovative use of digital resources in publishing, distributing and consuming of electronic publications, digital images, audio and movies, learning objects, computer software and other creations in digital form. The ODRL has no license requirements and is available in the spirit of "open source" software. </blockquote>
 ==References==

@@ Line 23: / Line 23: @@
 See the wiki page on [[Policy-Based Access Control]] for more examples of policy languages. This works best, of course, on apps owned or controlled by the [[Enterprise]].
 * [https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml OASIS eXtensible Access Control Markup Language (XACML) TC] with errata Version 2 (2008-07-29), version 3 (2017-07-12). <blockquote>The [https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml XACML Technical Committee] defines a core XML schema for representing authorization and entitlement policies.</blockquote>
-* [https://www.w3.org/TR/odrl-model/ 2018-02-15 ODRL Information Model 2 W3C Recommendation]
+* [https://www.w3.org/TR/odrl-model/ 2018-02-15 ODRL Information Model 2 W3C Recommendation] <blockquote>Policies are used to represent permitted and prohibited actions over a certain asset, as well as the obligations required to be meet by stakeholders. In addition, policies may be limited by constraints (e.g., temporal or spatial constraints) and duties (e.g. payments) may be imposed on permissions.</blockquote>
 * [https://www.w3.org/TR/odrl/#:~:text=The%20Open%20Digital%20Rights%20Language,expressing%20rights%20information%20over%20content.&text=The%20ODRL%20has%20no%20license,of%20%22open%20source%22%20software. Open Digital Rights Language (ODRL) Version 1.1] (2002-09-19) <blockquote>The Open Digital Rights Language (ODRL) is a proposed language for the Digital Rights Management (DRM) community for the standardization of expressing rights information over content. The ODRL is intended to provide flexible and interoperable mechanisms to support transparent and innovative use of digital resources in publishing, distributing and consuming of electronic publications, digital images, audio and movies, learning objects, computer software and other creations in digital form. The ODRL has no license requirements and is available in the spirit of "open source" software. </blockquote>

@@ Line 23: / Line 23: @@
 See the wiki page on [[Policy-Based Access Control]] for more examples of policy languages. This works best, of course, on apps owned or controlled by the [[Enterprise]].
 * [https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml OASIS eXtensible Access Control Markup Language (XACML) TC] with errata Version 2 (2008-07-29), version 3 (2017-07-12). <blockquote>The [https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml XACML Technical Committee] defines a core XML schema for representing authorization and entitlement policies.</blockquote>
-*[https://www.w3.org/TR/odrl/#:~:text=The%20Open%20Digital%20Rights%20Language,expressing%20rights%20information%20over%20content.&text=The%20ODRL%20has%20no%20license,of%20%22open%20source%22%20software. Open Digital Rights Language (ODRL) Version 1.1] (2002-09-19) <blockquote>The Open Digital Rights Language (ODRL) is a proposed language for the Digital Rights Management (DRM) community for the standardization of expressing rights information over content. The ODRL is intended to provide flexible and interoperable mechanisms to support transparent and innovative use of digital resources in publishing, distributing and consuming of electronic publications, digital images, audio and movies, learning objects, computer software and other creations in digital form. The ODRL has no license requirements and is available in the spirit of "open source" software. </blockquote>
+* [https://www.w3.org/TR/odrl-model/ 2018-02-15 ODRL Information Model 2 W3C Recommendation]
 ==References==
 [[Category: Glossary]]
 [[Category: Authorization]]

@@ Line 18: / Line 18: @@
 * Enterprise-owed devices allowed the Enterprise to install Mobile Device Management (MDM) on the device and continue to control their content no matter where the user would travel.
 * Bring your Own Device (ByoD) to work allows some level of control, but there is resistance to allowing an Enterprise MDM on a user-owned device.
-* The best solution has proven to be an [Enterprise] supplied app that allowed access to [Enterprise] data.
+* The best solution has proven to be an [[Enterprise]] supplied app that allowed access to [Enterprise] data.
 ===Policy===