@@ -645,11 +645,11 @@ <h2>Terminology</h2>
645
645
</ p >
646
646
647
647
< dl class ="termlist definitions ">
648
- < dt > < dfn data-lt ="claims "> claim</ dfn > </ dt >
648
+ < dt > < dfn class =" export " data-lt ="claims "> claim</ dfn > </ dt >
649
649
< dd >
650
650
An assertion made about a [=subject=].
651
651
</ dd >
652
- < dt > < dfn data-lt ="credential|credentials "> credential</ dfn > </ dt >
652
+ < dt > < dfn class =" export " data-lt ="credential|credentials "> credential</ dfn > </ dt >
653
653
< dd >
654
654
A set of one or more [=claims=] made by an [=issuer=]. The [=claims=]
655
655
in a credential can be about different [=subjects=]. The definition of
@@ -715,7 +715,7 @@ <h2>Terminology</h2>
715
715
part of a graph; this is either explicit in the case of [=named graphs=], or
716
716
implicit for the [=default graph=].
717
717
</ dd >
718
- < dt > < dfn data-lt ="holders|holder's|holders' "> holder</ dfn > </ dt >
718
+ < dt > < dfn class =" export " data-lt ="holders|holder's|holders' "> holder</ dfn > </ dt >
719
719
< dd >
720
720
A role an [=entity=] might perform by possessing one or more
721
721
[=verifiable credentials=] and generating [=verifiable presentations=]
@@ -747,7 +747,7 @@ <h2>Terminology</h2>
747
747
[=identity provider=] concept into two distinct concepts: the [=issuer=]
748
748
and the [=holder=].
749
749
</ dd >
750
- < dt > < dfn data-lt ="issuers|issuer's "> issuer</ dfn > </ dt >
750
+ < dt > < dfn class =" export " data-lt ="issuers|issuer's "> issuer</ dfn > </ dt >
751
751
< dd >
752
752
A role an [=entity=] can perform by asserting [=claims=] about one or
753
753
more [=subjects=], creating a [=verifiable credential=] from these
@@ -761,23 +761,23 @@ <h2>Terminology</h2>
761
761
result in separate [=graphs=] that contain all [=claims=] defined in the
762
762
corresponding JSON objects.
763
763
</ dd >
764
- < dt > < dfn data-lt ="presentation|presentations "> presentation</ dfn > </ dt >
764
+ < dt > < dfn class =" export " data-lt ="presentation|presentations "> presentation</ dfn > </ dt >
765
765
< dd >
766
766
Data derived from one or more [=verifiable credentials=], issued by one or
767
767
more [=issuers=], that is shared with a specific [=verifier=].
768
768
</ dd >
769
- < dt > < dfn data-lt ="credential repository|credential repositories|repositories "> repository</ dfn > </ dt >
769
+ < dt > < dfn class =" export " data-lt ="credential repository|credential repositories|repositories "> repository</ dfn > </ dt >
770
770
< dd >
771
771
A program, such as a storage vault or personal [=verifiable credential=]
772
772
wallet, that stores and protects access to [=holders'=]
773
773
[=verifiable credentials=].
774
774
</ dd >
775
- < dt > < dfn > selective disclosure</ dfn > </ dt >
775
+ < dt > < dfn class =" export " > selective disclosure</ dfn > </ dt >
776
776
< dd >
777
777
The ability of a [=holder=] to make fine-grained decisions about what
778
778
information to share.
779
779
</ dd >
780
- < dt > < dfn data-lt ="subjects|subject's "> subject</ dfn > </ dt >
780
+ < dt > < dfn class =" export " data-lt ="subjects|subject's "> subject</ dfn > </ dt >
781
781
< dd >
782
782
A thing about which [=claims=] are made.
783
783
</ dd >
@@ -786,7 +786,7 @@ <h2>Terminology</h2>
786
786
A program, such as a browser or other Web client, that mediates the
787
787
communication between [=holders=], [=issuers=], and [=verifiers=].
788
788
</ dd >
789
- < dt > < dfn data-lt ="claim validation "> validation</ dfn > </ dt >
789
+ < dt > < dfn class =" export " data-lt ="claim validation|validate "> validation</ dfn > </ dt >
790
790
< dd >
791
791
The assurance that a [=claim=] from a specific [=issuer=] satisfies the
792
792
business requirements of a [=verifier=] for a particular use. This
@@ -799,13 +799,13 @@ <h2>Terminology</h2>
799
799
apply their own rules to determine which claims in which [=credentials=]
800
800
are suitable for use by their systems.
801
801
</ dd >
802
- < dt > < dfn data-lt ="verifiable credential|verifiable credentials| vc|vcs "> verifiable credential</ dfn > </ dt >
802
+ < dt > < dfn class =" export " data-lt ="vc|vcs "> verifiable credential</ dfn > </ dt >
803
803
< dd >
804
804
A verifiable credential is a tamper-evident credential that has authorship that
805
805
can be cryptographically verified. Verifiable credentials can be used to build
806
806
[=verifiable presentations=], which can also be cryptographically verified.
807
807
</ dd >
808
- < dt > < dfn data-lt ="verifiable data registries "> verifiable data registry</ dfn > </ dt >
808
+ < dt > < dfn class =" export " data-lt ="verifiable data registries "> verifiable data registry</ dfn > </ dt >
809
809
< dd >
810
810
A role a system might perform by mediating the creation and [=verification=]
811
811
of identifiers, keys, and other relevant data, such as
@@ -815,15 +815,15 @@ <h2>Terminology</h2>
815
815
registries, such as ones for UUIDs and public keys, might just act as namespaces
816
816
for identifiers.
817
817
</ dd >
818
- < dt > < dfn data-lt ="verifiable presentation|verifiable presentations| vp|vps "> verifiable presentation</ dfn > </ dt >
818
+ < dt > < dfn class =" export " data-lt ="vp|vps "> verifiable presentation</ dfn > </ dt >
819
819
< dd >
820
820
A verifiable presentation is a tamper-evident presentation encoded in such a way
821
821
that authorship of the data can be trusted after a process of cryptographic
822
822
verification. Certain types of verifiable presentations might contain data that
823
823
is synthesized from, but do not contain, the original [=verifiable
824
824
credentials=] (for example, zero-knowledge proofs).
825
825
</ dd >
826
- < dt > < dfn data-lt ="verify|verified|verifying|verifiable|verifiability "> verification</ dfn > </ dt >
826
+ < dt > < dfn class =" export " data-lt ="verify|verified|verifying|verifiable|verifiability "> verification</ dfn > </ dt >
827
827
< dd >
828
828
The evaluation of whether a [=verifiable credential=] or [=verifiable
829
829
presentation=] is an authentic and current statement of the issuer or
@@ -832,7 +832,7 @@ <h2>Terminology</h2>
832
832
if present, the status check succeeds. Verification of a credential does not
833
833
imply evaluation of the truth of [=claims=] encoded in the credential.
834
834
</ dd >
835
- < dt > < dfn data-lt ="verifier|verifiers|verifier's|credential verifiers|credential verifier's "> verifier</ dfn > </ dt >
835
+ < dt > < dfn class =" export " data-lt ="verifier|verifiers|verifier's|credential verifiers|credential verifier's "> verifier</ dfn > </ dt >
836
836
< dd >
837
837
A role an [=entity=] performs by receiving one or more
838
838
[=verifiable credentials=], optionally inside a
0 commit comments