Removed the word “digital” before “content”

model/index.html

@@ -12,7 +12,7 @@
 
 <section id="abstract">
 
-    <p>The Open Digital Rights Language (ODRL) provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for describing statements about digital content usage. The ODRL Information Model describes the underlying concepts, entities, and relationships that form the foundational basis for the semantics of the ODRL statements. </p>
+    <p>The Open Digital Rights Language (ODRL) provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for describing statements about content usage. The ODRL Information Model describes the underlying concepts, entities, and relationships that form the foundational basis for the semantics of the ODRL statements. </p>
         <p>Policies are used to explicitly state what are the permitted and prohibited actions over a certain resource. In addition, policies may be integrated with complex constraints (e.g., time constraints) which apply to such actions to impose further restrictions to the uses of the resource. </p>
 
 </section>
@@ -29,15 +29,15 @@
 <section class="informative" id="intro">
 <h2>Introduction</h2>   
 
-<p>Several business scenarios require to express what are the permitted and prohibited actions over digital content. These permitted/prohibited actions are usually expressed under the form of policies, i.e., entities that allow to indicate those uses and re-uses of the digital content which are comform with the existing regulations or to the constraints assigned by the owner. Policies may also be enriched with additional information, i.e., who are the entities in charge of the definition of such Policy and those who are required to conform to it, what are the additional constrains to be associated with the Permissions, Prohibitions and Duties expressed by the Policy. The ability to express these concepts and relationships is important both for the producers of digital content, i.e., they may state in a clear way what are the permitted and the prohibited actions to prevent misuses, and for the consumers, i.e., they may know precisely how they are allowed to use and re-use the digital content to avoid breaking the law or the owner's constraints. This specification describes a common approach to expressing these concepts, and more.</p>
-<p>The ODRL Information Model defines the underlying semantic model for permission and obligation statements describing digital content usage. The information model covers the core concepts, entities and relationships that provide the foundational model for content usage statements. These machine-readable policies may be linked directly with the digital content they are associated to with the aim to allow consumers to easily retrieve those information.</p>
+<p>Several business scenarios require to express what are the permitted and prohibited actions over  content. These permitted/prohibited actions are usually expressed under the form of policies, i.e., entities that allow to indicate those uses and re-uses of the content which are comform with the existing regulations or to the constraints assigned by the owner. Policies may also be enriched with additional information, i.e., who are the entities in charge of the definition of such Policy and those who are required to conform to it, what are the additional constrains to be associated with the Permissions, Prohibitions and Duties expressed by the Policy. The ability to express these concepts and relationships is important both for the producers of content, i.e., they may state in a clear way what are the permitted and the prohibited actions to prevent misuses, and for the consumers, i.e., they may know precisely how they are allowed to use and re-use the content to avoid breaking the law or the owner's constraints. This specification describes a common approach to expressing these concepts, and more.</p>
+<p>The ODRL Information Model defines the underlying semantic model for permission and obligation statements describing content usage. The information model covers the core concepts, entities and relationships that provide the foundational model for content usage statements. These machine-readable policies may be linked directly with the content they are associated to with the aim to allow consumers to easily retrieve those information.</p>
 
 <section id="aimsModel">
 <h3>Aims of the Model</h3>
 
-<p>The primary aim of the ODRL Information Model is to provide a standard description model and format to express permission and obligation statements to be associated to digital content in general. These permission and obligation statements are employed to describe the terms of use and reuse of digital resources. The model should cover as many Permission and Obligation use cases as possible, while keeping the policy modeling easy even when dealing with complex uses.</p>
+<p>The primary aim of the ODRL Information Model is to provide a standard description model and format to express permission and obligation statements to be associated to content in general. These permission and obligation statements are employed to describe the terms of use and reuse of  resources. The model should cover as many Permission and Obligation use cases as possible, while keeping the policy modeling easy even when dealing with complex uses.</p>
 
-<p>The ODRL Information Model is a single, consistent model that can be used by all interested parties. All efforts have been made to keep the implementation costs for both digital content producers and consumers to a minimum. A single method of fulfilling a use case is strongly preferred over multiple methods, unless there are existing standards that need to be accommodated or there is a significant cost associated with using only a single method. While the Information Model is built using Linked Data principles, the design is intended to allow non-graph-based implementations also. </p>
+<p>The ODRL Information Model is a single, consistent model that can be used by all interested parties. All efforts have been made to keep the implementation costs for both content producers and consumers to a minimum. A single method of fulfilling a use case is strongly preferred over multiple methods, unless there are existing standards that need to be accommodated or there is a significant cost associated with using only a single method. While the Information Model is built using Linked Data principles, the design is intended to allow non-graph-based implementations also. </p>
 
 
 </section>
@@ -57,8 +57,8 @@ <h3>Terminology</h3>
      <dl class="termlist">
                   <dt><dfn>Resource</dfn></dt>
                   <dd>An item of interest that may be identified by an URI.</dd>
-                  <dt><dfn>Digital content</dfn></dt>
-                  <dd>Any type of content that exists in the form of digital data.</dd>
+                  <dt><dfn>Content</dfn></dt>
+                  <dd>Any type of content that exists and can be indentified.</dd>
 	          <dt><dfn>Policy</dfn></dt>
 	          <dd>A set of rules defining what is allowed, disallowed or obligatory over a resource.</dd>
 	          <dt><dfn>Rule</dfn></dt>
@@ -87,7 +87,7 @@ <h3>Terminology</h3>
 <h2>Relationship to the W3C ODRL Community Group Reports</h2>
 
 
-<p>The basis for the deliverables for the Permissions &amp; Obligations Expression Working Group are the reports created by the <a href="https://www.w3.org/community/odrl/">W3C ODRL Community Group</a>. The ODRL Community Group has developed a family of specifications to support innovative expression of digital asset usage for the publication, distribution and consumption of content services.
+<p>The basis for the deliverables for the Permissions &amp; Obligations Expression Working Group are the reports created by the <a href="https://www.w3.org/community/odrl/">W3C ODRL Community Group</a>. The ODRL Community Group has developed a family of specifications to support innovative expression of  asset usage for the publication, distribution and consumption of content services.
 The final outputs of the ODRL Community Group were the ODRL Version 2.1 specifications that were a major update for ODRL and superseded the original ODRL Version 1.1 [[odrl]] (published as a W3C NOTE).</p>
 
 <p>The following documents are part of the ODRL Community Group report series:</p>

vocab/index.html

@@ -20,7 +20,7 @@
 	<body>
 <section id="abstract">
 
-    <p>The Open Digital Rights Language (ODRL) provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for describing  statements about digital content usage. The ODRL Vocabulary and Expression describes the terms used in such statements and how to encode them.</p>
+    <p>The Open Digital Rights Language (ODRL) provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for describing  statements about content usage. The ODRL Vocabulary and Expression describes the terms used in such statements and how to encode them.</p>
 </section>
 <section id="sotd">
 <p>
@@ -32,7 +32,7 @@
 <h2>Introduction</h2>   
 
 <p>
-  The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing digital content usage based on the ODRL Information Model [[!odrl-model]].
+  The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing content usage based on the ODRL Information Model [[!odrl-model]].
    </p>
 
 </section>
@@ -41,7 +41,7 @@ <h2>Introduction</h2>
 <h2>Relationship to the W3C ODRL Community Group Reports</h2>
 
 
-<p>The basis for the deliverables for the Permissions &amp; Obligations Expression Working Group are the reports created by the <a href="https://www.w3.org/community/odrl/">W3C ODRL Community Group</a>. The ODRL Community Group has developed a family of specifications to support innovative expression of digital asset usage for the publication, distribution and consumption of content services. The final outputs of the ODRL Community Group were the Version 2.1 specifications that were a major update for ODRL and superseded the original ODRL Version 1.1 [[odrl]] (published as a W3C NOTE)</p>
+<p>The basis for the deliverables for the Permissions &amp; Obligations Expression Working Group are the reports created by the <a href="https://www.w3.org/community/odrl/">W3C ODRL Community Group</a>. The ODRL Community Group has developed a family of specifications to support innovative expression of  asset usage for the publication, distribution and consumption of content services. The final outputs of the ODRL Community Group were the Version 2.1 specifications that were a major update for ODRL and superseded the original ODRL Version 1.1 [[odrl]] (published as a W3C NOTE)</p>
 
 <p>The following documents are part of the ODRL Community Group report series:</p>
 <ul>
@@ -1595,7 +1595,7 @@ <h2>Inline Assets</h2>
     </section>
 
     <section id="json">
-   	<h2>JSON Encoding</h2>         
+   	<h2>JSON-LD Encoding</h2>         
        <p>This section describes how to encode both the ODRL Model and Vocabulary, including any community developed Profiles, using the JSON syntax [[rfc4627]] and using a JSON Schema [[json-schema]].</p>
 
 <div class="issue">

vocab/parts/abstract.html

@@ -1,4 +1,4 @@
 <section id="abstract">
 
-    <p>The Open Digital Rights Language (ODRL) provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for describing  statements about digital content usage. The ODRL Vocabulary and Expression describes the terms used in such statements and how to encode them.</p>
+    <p>The Open Digital Rights Language (ODRL) provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for describing  statements about content usage. The ODRL Vocabulary and Expression describes the terms used in such statements and how to encode them.</p>
 </section>

vocab/parts/community.html

@@ -3,7 +3,7 @@
 <h2>Relationship to the W3C ODRL Community Group Reports</h2>
 
 
-<p>The basis for the deliverables for the Permissions &amp; Obligations Expression Working Group are the reports created by the <a href="https://www.w3.org/community/odrl/">W3C ODRL Community Group</a>. The ODRL Community Group has developed a family of specifications to support innovative expression of digital asset usage for the publication, distribution and consumption of content services. The final outputs of the ODRL Community Group were the Version 2.1 specifications that were a major update for ODRL and superseded the original ODRL Version 1.1 [[odrl]] (published as a W3C NOTE)</p>
+<p>The basis for the deliverables for the Permissions &amp; Obligations Expression Working Group are the reports created by the <a href="https://www.w3.org/community/odrl/">W3C ODRL Community Group</a>. The ODRL Community Group has developed a family of specifications to support innovative expression of  asset usage for the publication, distribution and consumption of content services. The final outputs of the ODRL Community Group were the Version 2.1 specifications that were a major update for ODRL and superseded the original ODRL Version 1.1 [[odrl]] (published as a W3C NOTE)</p>
 
 <p>The following documents are part of the ODRL Community Group report series:</p>
 <ul>

vocab/parts/intro.html

@@ -2,7 +2,7 @@
 <h2>Introduction</h2>   
 
 <p>
-  The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing digital content usage based on the ODRL Information Model [[!odrl-model]].
+  The ODRL Vocabulary and Expression defines a set of concepts and terms (the vocabulary) and encoding mechanism (the expression) for permissions and obligations statements describing content usage based on the ODRL Information Model [[!odrl-model]].
    </p>
 
 </section>

vocab/template.phtml

@@ -85,7 +85,7 @@ writeGroup('assetRelations');
     </section>
 
     <section id="json">
-   	<h2>JSON Encoding</h2>         
+   	<h2>JSON-LD Encoding</h2>         
        <?php
         readfile(dirname(__FILE__) . '/parts/json.html');  
           ?>