-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathindex.html
More file actions
766 lines (731 loc) · 39.1 KB
/
index.html
File metadata and controls
766 lines (731 loc) · 39.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<title>Rich Skill Descriptor Standards Implementation Recommendations</title>
<script src='https://www.w3.org/Tools/respec/respec-w3c' class='remove' async></script>
<script class='remove'>
var respecConfig = {
specStatus: "unofficial",
edDraftURI: "https://rsd.osmt.dev",
editors: [
{
name: "Concentric Sky",
url: "https://www.concentricsky.com",
}
],
authors: [
{
name: "Concentric Sky",
url: "https://www.concentricsky.com",
},
{
name: "Western Governors University",
url: "https://www.wgu.edu",
},
{
name: "Credential Engine",
url: "https://credentialengine.org",
},
],
github: "https://github.com/concentricsky/rsd-respec"
};
</script>
<script type="text/javascript" src="static/jquery-3.5.1.min.js"></script>
<script type="text/javascript" src="static/jquery-accessible-tabs.js"></script>
<link rel="stylesheet" href="static/custom.css" type="text/css" />
</head>
<body>
<p class="copyright">
Copyright © 2020. This document is licensed under a
<a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 (CC-BY)
License</a>. Join the <a href="https://openskillsnetwork.org">Open Skills Network</a> to contribute.
<section id='abstract'>
<p>
This document describes the Rich Skill Descriptor (RSD) class and how RSDs should be published for
compatibility with services that process machine readable representations of skills and competencies. Each
RSD is primarily identified by a canonical URL and consists of a skillStatement and supporting metadata to
identify alignment to other skills or job categories.
</p>
</section>
<section id='sotd'>
<p>
This document is a working draft of a standards implementation recommendation document produced by the <a
href="https://openskillsnetwork.org">Open Skills Network</a> in order to advise members and collaborators about
available data standards and how to use them in a coordinated fashion to accomplish key use cases around the
publication, recognition, and consumption of skills for learning and employment.
</p>
</section>
<section id="conformance">
<p>
There is no conformance testing for implementers of these recommendations. Specific referenced standards often
have their own normative requirements that are required for interoperability using those standards.
</p>
</section>
<section class='informative'>
<h2>Introduction</h2>
<p>
In order to create an ecosystem of recognition around skills, where Achievements, Pathways, and Learner
Records make machine-readable references to skills and allow systems to take action based on the skills
learners hold, it is important for implementers to use skills in common ways. RSDs build on
<a href="https://credreg.net/ctdl/handbook#ctdlasnschema">CTDL-ASN</a> to enable skill authors to publish
definitions that can be referenced from digital credentials (including those that appear in learner records),
pathways, and job profiles. Partners in an interoperable skills ecosystem may use CTDL/CTDL-ASN and/or other
vocabularies and web standards to present skills descriptors and related concepts. This document provides the
Open Skills Network's technical guidance on approaches for publishing and making use of this data, taking best
advantage of available data standards.
</p>
<p>
Below are examples of use cases that sytems working with skills may implement, with recipes for how OSN
members recommend those sytems might implement those use cases in a harmonized interoperable manner. Examples
and usage notes provide guidance for how these concepts should be understood and used.
</p>
</section>
<section class='informative'>
<h2>Publish a Rich Skill Descriptor</h2>
<p>
<em>As an educational institution, I would like to publish a skill that is taught, assessed, and recognized
by the organization in machine-readable interoperable format so that it can be referenced in other resources
by the organization and employers</em>
</p>
<p>
The concept of a single skill or competency, expressed with rich metadata and alignment, is the foundation of
a skills vocabulary. Organizations or individuals in different roles in the skills ecosystem may find it
useful to publish a skill definition. That includes employers, individual educators, educational institutions,
industry consortia or professional associations, or collaborations between these different roles.
</p>
<p>Some of these publishers may at times describe the concept of a skill using different terminology, such as
competency, learning outcome or standard, but what is shared between all of these models is the possibility
for each skill to be associated with a canonical URL where it is made available and the ability to retrieve
descriptive metadata that expresses the full meaning of the skill definition.
</p>
<div class="js-tabs">
<ul class="js-tablist">
<li class="recipes-label"><span>Recipes:</span></li>
<li class="js-tablist__item">
<a href="#rsd_ctdl" id="label_rsd_ctdl" class="js-tablist__link override no-link-warnings">CTDL-ASN/CTDL</a>
</li>
<li class="js-tablist__item">
<a href="#rsd_caseld" id="label_rsd_caseld" class="js-tablist__link override no-link-warnings">CASE-LD</a>
</li>
</ul>
<div id="rsd_ctdl" class="js-tabcontent">
<h3 class="override informative notoc">Recipe: Publish a Rich Skill Descriptor with CTDL-ASN/CTDL</h3>
<p> CTDL-ASN and CTDL are published by Credential Engine. These vocabularies provide extensive attributes
with which to describe credentials, competencies or skills, organizations and other related concepts.
</p>
<table class="propertyList">
<thead>
<tr>
<th>RSD Property</th>
<th>Field Name</th>
<th>Data Type</th>
<th>Description</th>
<th>Term IRI</th>
</tr>
</thead>
<tbody>
<tr>
<td>id</td>
<td>ID</td>
<td>URI</td>
<td>Canonical URL that uniquely identifies the skill, from which more information may be retrieved.</td>
<td><code>@id</code></td>
</tr>
<tr>
<td>skillName</td>
<td>Skill Name</td>
<td>String</td>
<td>Short name or label for the skill.</td>
<td><a href="https://purl.org/ctdlasn/terms/competencyLabel">ceasn:competencyLabel</a></td>
</tr>
<tr>
<td>skillStatement</td>
<td>Skill Statement</td>
<td>String[<a href="#skill-statement">SkillStatement</a>]</td>
<td>Skills description written in standard syntax.</td>
<td><a href="https://purl.org/ctdlasn/terms/competencyText">ceasn:competencyText</a></td>
</tr>
<tr>
<td>keywords</td>
<td>Keywords</td>
<td>Array[String]</td>
<td>List of keyword strings to enhance searchability.</td>
<td><a href="https://purl.org/ctdl/terms/keyword">ceterms:keyword</a></td>
</tr>
<tr>
<td>category</td>
<td>Category</td>
<td>String</td>
<td>A category in which this RSD is filed, in the local vocabulary defined by the issuer</td>
<td><a href="https://purl.org/ctdlasn/terms/competencyCategory">ceasn:competencyCategory</a></td>
</tr>
<tr>
<td>author</td>
<td>Author</td>
<td>String</td>
<td>A person or organization chiefly responsible for the intellectual or artistic content of this skill</td>
<td><a href="https://purl.org/ctdlasn/terms/author">ceasn:author</a></td>
</tr>
<tr>
<td>creator</td>
<td>Creator</td>
<td>URI</td>
<td>
A person or organization primarily responsible for making this resource. This is the canonical
identifier of the source of the skill.
</td>
<td><a href="https://purl.org/ctdlasn/terms/creator">ceasn:creator</a></td>
</tr>
<tr>
<td>alignments</td>
<td>Alignments</td>
<td>Array[String:URI]</td>
<td>indicates alignment or overlap of this RSD to one or more underlying standards, skills, or
competencies identified in other frameworks or data sources (i.e.,Emsi; Burning Glass; LinkedIn;
Workday), each of which is uniquely identified by a URI. Each entry may be just the URI or may
contain descriptive metadata about the alignment target.</td>
<td><a href="https://purl.org/ctdlasn/terms/majorAlignment">ceasn:majorAlignment</a>
<a href="#alignmentNote">*</a></td>
</tr>
<tr>
<td>certifications</td>
<td>Certifications</td>
<td>Array[Credential]</td>
<td>Field for associating external certifications to RSDs</td>
<td><a href="https://purl.org/ctdlasn/terms/alignFrom">ceasn:alignFrom</a></td>
</tr>
<tr>
<td>occupations</td>
<td>Occuption Data Categories</td>
<td>Array[String:JobCode]</td>
<td>indicates skill alignment to releveant job roles/occupations aligned to an external categorization like BLS SOC or O*NET</td>
<td><a href="https://purl.org/ctdl/terms/occupationType">ceterms:occupationType</td>
</tr>
<tr>
<td>employers</td>
<td>Employers</td>
<td>Array [Employment Outcome Profile]</td>
<td>indicates support for a skill by specific employers who employ people who hold the skill</td>
<td><a href="https://purl.org/ctdl/terms/employmentOutcome">ceterms:employmentOutcome</a></td>
</tr>
<tr>
<td>ctid</td>
<td>Credential Transparency Identifier</td>
<td>Array[String]</td>
<td>
Unique Credential Transparency Identifier assigned by the creator perhaps through publication to
the Credential Engine Registry. Uniqueness can only be guaranteed for entities submitted to the
Credential Engine Registry.
</td>
<td><a href="https://purl.org/ctdlasn/terms/ctid">ceasn:ctid</a></td>
</tr>
</tbody>
</table>
<p class="note" id="alignmentNote" title="Alignment types may vary">
Available alignment types include <a href="https://purl.org/ctdlasn/terms/majorAlignment">majorAlignment</a>,
<a href="https://purl.org/ctdlasn/terms/broadAlignment">broadAlignment</a>,
<a href="https://purl.org/ctdlasn/terms/exactAlignment">exactAlignment</a>,
<a href="https://purl.org/ctdlasn/terms/minorAlignment">minorAlignment</a>,
<a href="https://purl.org/ctdlasn/terms/narrowAlignment">narrowAlignment</a>,
and <a href="https://purl.org/ctdlasn/terms/prerequsiteAlignment">prerequisiteAlignment</a>.
The most simple or default recommendation is majorAlignment, which implies a close but not exact match.
</p>
<h3>Skill Statement</h3>
<p>A skill statement is a string that expresses information about who the skill applies to, the nature of the skill itself,
and the context in which it is applied, together, e.g.: "{Subject} {Predicate} {Context}". Consistent formatting assists
interoperability of RSDs across organizations and the development of common usage of RSDs valued in common.
</p>
<pre class="example nohighlight" title="Example Skill Statement">
The learner saves copies of documents to their local machine.
</pre>
<table class="propertyList">
<thead>
<tr>
<th>Component</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>subject</td>
<td>Who this skill applies to, e.g "the learner"</td>
</tr>
<tr>
<td>predicate</td>
<td>The part of the statement that shows the action, knowledge, or ability at the core of the skill, e.g. "saves copies"</td>
</tr>
<tr>
<td>context</td>
<td>Supporting descriptive language to clarify the context in which the skill applies, e.g. "to their local machine"</td>
</tr>
</tbody>
</table>
<h3>Example RSD</h3>
<p></p>
<pre class="example" title="A RSD with basic alignment and occupation information">
{
"@context": "https://rsd.osmt.dev/context-v1.json",
"id": "https://osmt.example.com/skills/9cd84455-2086-4f41-bcac-6d518beeb6ac",
"type": "RichSkillDescriptor",
"author": "https://osmt.example.com/organization",
"skillName": "Document Saving",
"skillStatement": "The learner saves copies of documents to their local machine.",
"alignments": [{"id": "https://skillsource.example.com/base-skills/simple-compuhacking", "name": "Simple Compuhacking"}],
"employers": [{"name": "Acme, Inc."}],
"keywords": ["documents", "file operations", "computer basics"],
"category": "Productivity Software",
"certifications": [{"id": "https://credentials.example.com/supersaver", "name": "DocumentAlliance SuperSaver"}],
"occupations": [{"codedNotation": "13-2080", "targetNodeName": "Tax Examiners, Collectors and Preparers, and Revenue Agents"}]
}
</pre>
</div>
<div id="rsd_caseld" class="js-tabcontent">
<h3>Recipe: Publish a Rich Skill Descriptor with CASE-LD</h3>
<p> CASE is a specification published by IMS Global that enables organizations to describe a competency or
skill framework. The "CASE-LD" <a href="https://www.imsglobal.org/spec/case/v1p0/jsonld/">JSON-LD binding
for the CASE service definition</a> enables CASE data to be published as JSON-LD for semantic web needs
without any significant modification to the JSON expressed by the various endpoints.
</p>
<p> To publish an RSD with CASE-LD, return the data described by the CASE-LD <a
href="https://www.imsglobal.org/spec/case/v1p0/jsonld/#cfitem">CFItem endpoint</a> from the RSD's canonical URL.
To express information about a framework in which a skill appears, you may also implement the <a href="https://www.imsglobal.org/spec/case/v1p0/jsonld/#cfdocument">CFDocument
endpoint</a> to express authorship information across one or more RSDs. Terms below are defined in the <a
href="https://purl.imsglobal.org/spec/case/v1p0/context/imscasev1p0_context_v1p0.jsonld">CASE JSON-LD
context</a>.
</p>
<p>
If the implementer is also implemnting the <a
href="https://www.imsglobal.org/sites/default/files/CASE/casev1p0/rest_binding/caseservicev1p0_restbindv1p0.html">CASE
1.0 REST API</a>, the canonical URL of the RSD should be the value of the <code>url</code> property in the
CFItem objects expressed in those REST endpoints, in order to inform REST API clients of the canonical
URLs.
</p>
<table class="propertyList">
<thead>
<tr>
<th>RSD Property</th>
<th>Field Name</th>
<th>Data Type</th>
<th>Description</th>
<th>Term IRI</th>
</tr>
</thead>
<tbody>
<tr>
<td>id</td>
<td>ID</td>
<td>URI</td>
<td>Canonical URL that uniquely identifies the skill, from which more information may be retrieved.</td>
<td><code>@id</code></td>
</tr>
<tr>
<td>identifier</td>
<td>Code</td>
<td>String</td>
<td>An identifying code, local to the RSD's publisher for this item.</td>
<td><code>case:identifier</code></td>
</tr>
<tr>
<td>lastChangeDateTime</td>
<td>Code</td>
<td>String</td>
<td>A timestamp in ISO-8601 format, fully qualified with time zone indicator of the last point in time a change was reflected in this published object.</td>
<td><code>case:lastChangeDateTime</code></td>
</tr>
<tr>
<td>CFDocumentURI</td>
<td>Framework</td>
<td>LinkURI</td>
<td>A link back to the Framework/Collection object, which describes the authorship of this RSD.</td>
<td><code>case:CFDocumentURI</code></td>
</tr>
<tr>
<td>educationLevel</td>
<td>Education Level</td>
<td>Array of Strings</td>
<td>A list of education levels like <code>"03"</code> that are the level at which this RSD is expressed.</td>
<td><code>case:educationLevel</code></td>
</tr>
<tr>
<td>fullStatement</td>
<td>Code</td>
<td>String</td>
<td>The full skill statement, expressing a learner's capability, knowledge, and/or experience.</td>
<td><code>case:fullStatement</code></td>
</tr>
<tr>
<td>abbreviatedStatement</td>
<td>Code</td>
<td>String</td>
<td>A short label for the skill.</td>
<td><code>case:abbreviatedStatement</code></td>
</tr>
<tr>
<td>language</td>
<td>Language</td>
<td>String (Language Code)</td>
<td>A language identifier code such as <code>en</code> or <code>es-mx</code> describing the language in which the RSD is published.</td>
<td><code>case:abbreviatedStatement</code></td>
</tr>
<tr>
<td>associationSet</td>
<td>Associations (Alignments)</td>
<td>Array of AssociationSets</td>
<td>Associations (alignments) of this RSD to other entities</td>
<td><code>case:associationSet</code></td>
</tr>
</tbody>
</table>
<h3>LinkURI Properties</h3>
<p>A LinkURI object is a CASE-LD concept that expresses a relationship between the present document and another document.
<table class="propertyList">
<thead>
<tr>
<th>LinkURI Property</th>
<th>Field Name</th>
<th>Data Type</th>
<th>Description</th>
<th>Term IRI</th>
</tr>
</thead>
<tbody>
<tr>
<td>type</td>
<td>type</td>
<td><code>LinkURI</code></td>
<td>The exact string <code>LinkURI</code>, expressing that this link is a LinkURI</td>
<td><code>@type</code></td>
</tr>
<tr>
<td>targetId</td>
<td>Target ID</td>
<td>URI</td>
<td>URI of the object that is the target of this link, such as a CFDocument that is the target of a CFDocumentURI link from a CFItem.</td>
<td><code>case:targetId</code></td>
</tr>
<tr>
<td>identifier</td>
<td>Code</td>
<td>String</td>
<td>An identifying code, local to the RSD's publisher for this item.</td>
<td><code>case:identifier</code></td>
</tr>
<tr>
<td>title</td>
<td>Title</td>
<td>String</td>
<td>The name of the linked entity.</td>
<td><code>case:title</code></td>
</tr>
</tbody>
</table>
<h3>AssociationLink Properties</h3>
<p>A LinkURI object is a CASE-LD concept that expresses a relationship between the present document and another document.
<table class="propertyList">
<thead>
<tr>
<th>LinkURI Property</th>
<th>Field Name</th>
<th>Data Type</th>
<th>Description</th>
<th>Term IRI</th>
</tr>
</thead>
<tbody>
<tr>
<td>type</td>
<td>type</td>
<td><code>AssociationLink</code></td>
<td>The exact string <code>AssociationLink</code>, expressing that this link is an association/alignment.</td>
<td><code>@type</code></td>
</tr>
<tr>
<td>targetId</td>
<td>Target ID</td>
<td>URI</td>
<td>URI of the object that is the target of this link, such as another CFItem.</td>
<td><code>case:targetId</code></td>
</tr>
<tr>
<td>identifier</td>
<td>Code</td>
<td>String</td>
<td>An identifying code, local to the RSD's publisher for this item.</td>
<td><code>case:identifier</code></td>
</tr>
<tr>
<td>title</td>
<td>Title</td>
<td>String</td>
<td>The name of the linked entity.</td>
<td><code>case:title</code></td>
</tr>
</tbody>
</table>
<h3>Example RSD published using CASE-LD</h3>
<p></p>
<pre class="example" title="A RSD expressed in CASE-LD">
{
"@context": "https://purl.imsglobal.org/spec/case/v1p0/context/imscasev1p0_context_v1p0.jsonld",
"type": "CFItem",
"id": "https://case.example.com/skills/9cd84455-2086-4f41-bcac-6d518beeb6ac",
"identifier": "9cd84455-2086-4f41-bcac-6d518beeb6ac",
"lastChangeDateTime": "2020-01-10T18:40:58+00:00",
"CFDocumentURI": {
"type": "LinkURI",
"title": "IMS CLR Demo Framework",
"identifier": "17927658-3246-11ea-97fb-0242c0a83003",
"targetId": "https://case.example.com/skills/framework1"
},
"abbreviatedStatement": "Document Saving",
"fullStatement": "The learner saves copies of documents to their local machine.",
"conceptKeywords": ["documents", "file operations", "computer basics"],
"language": "en",
"associationSet": [
{
"type": "AssociationLink",
"targetId": "https://skillsource.example.com/base-skills/simple-compuhacking",
"associationType": "isRelatedTo",
"title": "Simple Compuhacking"
}
]
}
</pre>
</div> <!-- end .js-tabcontent -->
</div> <!-- end .js-tabs -->
</section>
<section class='informative'>
<h2>Publish a Collection</h2>
<p>
A collection of skills bundles a number of skills together for a particular purpose or presentation.
</p>
<div class="js-tabs">
<ul class="js-tablist">
<li class="recipes-label"><span>Recipes:</span></li>
<li class="js-tablist__item">
<a href="#collection_ctdl" id="label_collection_ctdl" class="js-tablist__link override no-link-warnings">CTDL-ASN/CTDL</a>
</li>
</ul>
<div id="collection_ctdl" class="js-tabcontent">
<h3 class="override informative notoc">Recipe: Publish a Collection with CTDL-ASN/CTDL</h3>
<p> CTDL-ASN and CTDL are published by Credential Engine. These vocabularies provide extensive attributes
with which to describe credentials, competencies or skills, organizations and other related concepts. Terms
from CTDL appear below with the prefix <code>ceterms</code> and terms from CTDL-ASN appear with the prefix
<code>ceasn</code>. This document provides the Open Skills Network's technical guidance on approaches for
publishing and making use of this data, taking best advantage of available data standards. </p>
<table class="propertyList">
<thead>
<tr>
<th>Collection Property</th>
<th>Field Name</th>
<th>Data Type</th>
<th>Description</th>
<th>Term IRI</th>
</tr>
</thead>
<tbody>
<tr>
<td>id</td>
<td>ID</td>
<td>URI</td>
<td>Canonical URL that uniquely identifies the collection, from which more information may be retrieved.</td>
<td><code>@id</code></td>
</tr>
<tr>
<td>name</td>
<td>Name</td>
<td>String</td>
<td>A descriptive name for the collection</td>
<td><code>@id</code></td>
</tr>
<tr>
<td>description</td>
<td>Description</td>
<td>URI</td>
<td>Brief explanation of the scope and purpose of the collection.</td>
<td><a href="https://purl.org/ctdlasn/terms/author">ceasn:description</a></td>
</tr>
<tr>
<td>author</td>
<td>Author</td>
<td>URI</td>
<td>A person or organization chiefly responsible for the content of this collection</td>
<td><a href="https://purl.org/ctdlasn/terms/author">ceasn:author</a></td>
</tr>
<tr>
<td>containsSkill</td>
<td>Contains Skill</td>
<td>Array[RichSkillDescriptor]</td>
<td>The skills contained within a collection. They are all at the top level with no hierarchy.</td>
<td><a href="https://purl.org/ctdlasn/terms/hasTopChild">ceasn:hasTopChild</a></td>
</tr>
</tbody>
</table>
<h3>Example Collection</h3>
<p></p>
<pre class="example" title="A Collection with one skill.">
{
"@context": "https://rsd.osmt.dev/context-v1.json",
"id": "https://osmt.example.com/collections/35b6ff86-2974-4dc6-be17-68fef37c86cd",
"type": "Collection",
"name": "Office Productivity Skills",
"description": "Skills for people who work in offices, generally at desks, on office chairs, often using computers.",
"author": "https://osmt.example.com/organization",
"containsSkills": [
{
"@context": "https://rsd.osmt.dev/context-v1.json",
"id": "https://osmt.example.com/skills/9cd84455-2086-4f41-bcac-6d518beeb6ac",
"type": "RichSkillDescriptor",
"author": "https://osmt.example.com/organization",
"skillName": "Document Saving",
"skillStatement": "The learner saves copies of documents to their local machine.",
"alignments": [{"id": "https://skillsource.example.com/base-skills/simple-compuhacking", "name": "Simple Compuhacking"}],
"employers": [{"name": "Acme, Inc."}],
"keywords": ["documents", "file operations", "computer basics"],
"category": "Productivity Software",
"certifications": [{"id": "https://credentials.example.com/supersaver", "name": "DocumentAlliance SuperSaver"}],
"occupations": [{"codedNotation": "13-2080", "targetNodeName": "Tax Examiners, Collectors and Preparers, and Revenue Agents"}]
}
]
}
</pre>
</div>
</section>
<section class='informative'>
<h2>Align a Credential to RSDs</h2>
<p>
<em>As an issuer of credentials that recognize the achievement of skills, I would like to include a reference
to one or more RSDs that a credential recognizes in the credential achievement description metadata.</em>
</p>
<p>
There are many contexts in which alignment is useful. Higher ed institutions would like to describe the skills
recognized by a credential they issue. This serves the purpose of communicating to potential earners what
skills are taught in curriculum, as well as communicating to the potential employers of learners who gain this
credential what skills have been achieved. For most purposes of alignment, the achievement level of a skill is
binary, rather than on a sliding scale. That means there is a threshold level of attainment that is required
in order to award a credential that recognizes that skill, and this is the same basic level that is referenced
in other objects that align to a skill, such as a job position description. There may be more advanced use
cases for alignment of skills that indicate an achievement level of the skill that the credential recognizes
that will be described separately.
</p>
<div class="js-tabs">
<ul class="js-tablist">
<li class="recipes-label"><span>Recipes:</span></li>
<li class="js-tablist__item">
<a href="#alignment_ob" id="label_alignment_ob" class="js-tablist__link override no-link-warnings">Open Badges</a>
</li>
<li class="js-tablist__item">
<a href="#alignment_ctdlasn" id="label_alignment_ctdlasn" class="js-tablist__link override no-link-warnings">CTDL/CTDL-ASN</a>
</li>
</ul>
<div id="alignment_ob" class="js-tabcontent">
<h3 class="override informative notoc">Recipe: Align a Credential to an RSD with Open Badges</h3>
<p> There are multiple approaches in different web standards communities for interoperable, portable, and
verifiable digital credentials, but a common pattern is an assertion awarded to an individual who the issuer
asserts has achieved a particular learning goal, whether that is a skill, learning objective, assessment,
certification, or other criteria.</p>
<p>In the below example, an Open Badges achievement definition is a BadgeClass with criteria that represents
the assessment of an underlying RSD, which the credential aligns to. Note that the OB vocabulary terms
<code>targetName</code> and <code>targetDescription</code> are used to represent the RSD terms
<code>skillName</code> and <code>skillStatement</code> respectively. When processing an example that may
contain extra information such as this, the relying party is encouraged to separately fetch the RSD itself
from the targetUrl to ensure that a canonical set of metadata is saved, based on the latest expression of the
RSD author's intent. This approach may be used within an Open Badges BadgeClass to align to an RSD expressed
using any recipe to <a href="#publish-a-rich-skill-descriptor">Publish a Rich Skill Descriptor</a> as long as
there is a canonical URL for that RSD where it may be retrieved in machine-readable format. The native Open
Badges terms are recommended for best compatibility with systems designed to read that format.</p>
<pre class="example" title="An Open Badges BadgeClass that aligns to an RSD.">
{
"@context": ["https://w3id.org/openbadges/v2"],
"id": "https://badges.example.com/badges/document-saving-1",
"type": "BadgeClass",
"name": "Document Savvy",
"description": "A basic skill of working on a computer is managing files. Recipients of this badge can save documents.",
"criteria": {"narrative": "Pass the document saving performance demonstration assessment."},
"issuer": "https://osmt.example.com/organization",
"alignment": [{
"targetUrl": "https://osmt.example.com/skills/9cd84455-2086-4f41-bcac-6d518beeb6ac",
"targetName": "Document Saving",
"targetDescription": "The learner saves copies of documents to their local machine."
}]
}
</pre>
</div>
<div id="alignment_ctdlasn" class="js-tabcontent">
<h3 class="override informative notoc">Recipe: Align a Credential to an RSD with CTDL/CTDL-ASN</h3>
<p>
CTDL-ASN has no classes for Credentials, so we fall back to CTDL for that data. These Credentials use CTDL's
alignment system to indicate alignment to a RSD expressed as a CTDL-ASN Competency.
</p>
<pre class="example" title="A CTDL Credential that aligns to a CDTL RSD."> {"TODO": true} </pre> </div> </div>
</section>
<section class='informative'>
<h2>Recognize Achievement of an RSD</h2>
<p> <em>As an educational institution, I want to
award a defined achievement credential to a single learner. As my organization defined this specific
achievement, which is tied to a particular learning experience and/or assessment, my organization is the only
one that may recognize that learners have achieved its criteria. Other organizations may recognize the same
skill by defining their own credentials that are aligned to it. </em> </p>
<p>
</p>
<div class="js-tabs">
<ul class="js-tablist">
<li class="recipes-label"><span>Recipes:</span></li>
<li class="js-tablist__item">
<a href="#award_ob" id="label_award_ob" class="js-tablist__link override no-link-warnings">Open Badges</a>
</li>
</ul>
<div id="award_ob" class="js-tabcontent">
<h3 class="override informative notoc">Recipe: Recognize Achievement of a Credential Aligned to an RSD with Open Badges</h3>
<p>
There are multiple approaches in different web standards communities for interoperable, portable, and
verifiable digital credentials, but a common pattern is an assertion awarded to an individual who the issuer
asserts has achieved a particular learning goal, whether that is a skill, learning objective, assessment,
certification, or other criteria. In the below example, there is an assertion of an Open Badges achievement definition that is a BadgeClass
with criteria that represents the assessment of an underlying RSD, which the credential aligns to. Note that
the OB vocabulary term <code>targetName</code> is used alongside the canonical RSD term
<code>skillName</code>.
</p>
<pre class="example" title="An Open Badges Assertion that Recognizes Achievment of an RSD.">
{
"@context": ["https://w3id.org/openbadges/v2", "https://rsd.osmt.dev/context-v1.json"],
"recipient": {
"type": "email",
"salt": "yUv2eMsVpQ1Y2uIU",
"hashed": true,
"identity": "sha256$0fdde2f81fcb3b06e50ca0d53d6bc2f5b576d027ddc7b4200455b99ce42e08c9"
},
"id": "https://badges.example.com/assertions/document-saving-1/abc123",
"badge": {
"id": "https://badges.example.com/badges/document-saving-1",
"type": "BadgeClass",
"name": "Document Savvy",
"description": "A basic skill of working on a computer is managing files. Recipients of this badge can save documents.",
"criteria": {
"narrative": "Pass the document saving performance demonstration assessment."
},
"issuer": "https://badges.example.com/organization",
"alignment": [{
"targetUrl": "https://osmt.example.com/skills/9cd84455-2086-4f41-bcac-6d518beeb6ac",
"type": "RichSkillDescriptor",
"author": "https://osmt.example.com/organization",
"skillName": "Document Saving",
"targetName": "Document Saving",
"skillStatement": "The learner saves copies of documents to their local machine.",
"alignments": ["https://skillsource.example.com/base-skills/simple-compuhacking"],
"keywords": ["documents", "file operations", "computer basics"],
"category": "Productivity Software",
"occupations": ["13-0000", "13-2000", "13-2010", "13-2030", "13-2040", "13-2060", "13-2080"]
}]
},
"verification": {
"type": "hosted"
}
}
</pre>
</div>
</div>
</section>
</body>
</html>