IEEE 1484.4 2007
$58.50
IEEE Trial Use Recommended Practice for Digital Rights Expression Languages (DRELs) Suitable for eLearning Technologies
Published By | Publication Date | Number of Pages |
IEEE | 2007 | 138 |
New IEEE Standard – Active. This recommended practice facilitates the creation, management and delivery of digitalcontent for eLearning by technology that implements Digital Rights Expression Languages(DRELs). This recommended practice determines what, if any, extensions are needed so thatthese DRELs can meet the identified requirements.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | IEEE Trial-Use Recommended Practice for Digital Rights Expression Languages (DRELs) Suitable for eLearning Technologies |
3 | Title page |
6 | Introduction Notice to users Errata Interpretations |
7 | Patents Participants |
9 | CONTENTS |
11 | 1. Overview 1.1 Scope 1.2 Purpose 1.3 Special terms |
12 | 1.4 Acronyms and abbreviations 2. Functional requirements for eLearning technologies |
13 | 2.1 Attributes of the Digital Rights Expression Language 2.2 Aggregation and disaggregation of learning objects |
14 | 2.3 Attribution 2.4 Conditional use |
15 | 2.5 Tracking 2.6 Offers 3. Issues 3.1 Requirements analysis |
16 | 3.2 Practitioner feedback |
17 | Annex A (informative) Use case requirements |
30 | Annex B (informative) Historical background B.1. Introduction |
33 | B.2. Learning, education, and training requirements |
36 | B.3. Issues |
37 | Annex C (informative) Mapping requirements to ORDL C.1. Introduction C.2. Requirement mapping to ODRL |
43 | C.2.2. Aggregation and disaggregation of learning objects |
48 | C.2.3. Attribution |
49 | C.2.4. Conditional use |
64 | C.2.5. Tracking |
65 | C.2.6. Offers |
67 | Annex D (informative) Mapping requirements to MPEG REL D.1. Introduction D.2 Example #1—University offer |
70 | D.3 Example #2—Tracking example |
72 | D.4 Example #3—Multi-tier distribution |
80 | D.5 Example #4—Site license with count conditions |
82 | D.6 Example #5—Default constraints |
84 | D.7 Example #6—Trusted device or online connectivity conditions |
86 | D.8 Example #7—Aggregation with attribution |
88 | D.9 Example #8—Disaggregation with attribution |
89 | D.10 Example #9—Conditions on an aggregated composite object |
91 | D.11 Example #10—Retention of metadata in learning object |
92 | D.12 Example #11—Supervision-based usage |
94 | D.13 Example #12—Subscription-based pricing |
100 | D.14 Example #13—Preserved constraints on an aggregated object |
103 | Annex E (informative) Mapping requirements to OeBF E.1. Introduction E.2 Example #1—University offer |
106 | E.3 Example #2—Tracking example |
108 | E.4 Example #3—Multi-tier distribution |
116 | E.5 Example #4—Site license with count conditions |
118 | E.6 Example #5—Default constraints |
120 | E.7 Example #6—Trusted device or online connectivity conditions |
123 | E.8 Example #7—Aggregation with attribution |
124 | E.9 Example #8—Disaggregation with attribution |
125 | E.10 Example #9—Conditions on an aggregated composite object |
127 | E.11 Example #10—Retention of metadata in learning object |
129 | E.12 Example #11—Supervision-based usage |
130 | E.13 Example #12—Subscription-based pricing |
137 | E.14 Example #13—Preserved constraints on an aggregated object |