762762 </ p >
763763
764764 < p >
765- A < dfn class ="external "> conforming DID document</ dfn > is any concrete expression
765+ A < dfn class ="export "> conforming DID document</ dfn > is any concrete expression
766766of the data model described in this specification which complies with the
767767relevant normative statements in [[[#data-model]]] and [[[#core-properties]]]. A
768768serialization format for the conforming document is deterministic,
782782 </ p >
783783
784784 < p >
785- A < dfn class ="external "> conforming DID method</ dfn > is any specification that
785+ A < dfn class ="export "> conforming DID method</ dfn > is any specification that
786786complies with the relevant normative statements in [[[#methods]]].
787787 </ p >
788788
@@ -819,7 +819,7 @@ <h2>Terminology</h2>
819819to process than the inputs themselves.
820820 </ dd >
821821
822- < dt > < dfn class ="external " data-lt ="decentralized identifiers|DID|DIDs "> decentralized identifier</ dfn > (DID)</ dt >
822+ < dt > < dfn class ="export " data-lt ="decentralized identifiers|DID|DIDs "> decentralized identifier</ dfn > (DID)</ dt >
823823
824824 < dd >
825825A globally unique persistent identifier that does not require a centralized
@@ -831,7 +831,7 @@ <h2>Terminology</h2>
831831network.
832832 </ dd >
833833
834- < dt > < dfn class ="external " data-lt ="did controllers|did controller(s) "> DID controller</ dfn > </ dt >
834+ < dt > < dfn class ="export " data-lt ="did controllers|did controller(s) "> DID controller</ dfn > </ dt >
835835
836836 < dd >
837837An entity that has the capability to make changes to a [=DID document=]. A
@@ -854,7 +854,7 @@ <h2>Terminology</h2>
854854be permitted to add other personal devices without the parent's permission.
855855 </ dd >
856856
857- < dt > < dfn class ="external " data-lt ="DID documents "> DID document</ dfn > </ dt >
857+ < dt > < dfn class ="export " data-lt ="DID documents "> DID document</ dfn > </ dt >
858858
859859 < dd >
860860A set of data describing the [=DID subject=], including mechanisms, such as
@@ -871,7 +871,7 @@ <h2>Terminology</h2>
871871(< code > #</ code > ). DID fragment syntax is identical to URI fragment syntax.
872872 </ dd >
873873
874- < dt > < dfn data-lt ="DID methods "> DID method</ dfn > </ dt >
874+ < dt > < dfn class =" export " data-lt ="DID methods "> DID method</ dfn > </ dt >
875875
876876 < dd >
877877A definition of how a specific [=DID method scheme=] is implemented. A DID method is
@@ -898,7 +898,7 @@ <h2>Terminology</h2>
898898syntax. See < a href ="#query "> </ a > .
899899 </ dd >
900900
901- < dt > < dfn > DID resolution</ dfn > </ dt >
901+ < dt > < dfn class =" export " > DID resolution</ dfn > </ dt >
902902
903903 < dd >
904904The process that takes as its input a [=DID=] and a set of resolution
@@ -908,7 +908,7 @@ <h2>Terminology</h2>
908908defined in [[?DID-RESOLUTION]].
909909 </ dd >
910910
911- < dt > < dfn data-lt ="DID resolvers "> DID resolver</ dfn > </ dt >
911+ < dt > < dfn class =" export " data-lt ="DID resolvers "> DID resolver</ dfn > </ dt >
912912
913913 < dd >
914914A [=DID resolver=] is a software and/or hardware component that performs the
@@ -1032,7 +1032,7 @@ <h2>Terminology</h2>
10321032 </ dd >
10331033
10341034 < dt >
1035- < dfn data-lt ="verifiable data registry|verifiable data registries ">
1035+ < dfn class =" export " data-lt ="verifiable data registry|verifiable data registries ">
10361036 verifiable data registry</ dfn >
10371037 </ dt >
10381038
0 commit comments