96
96
text-align : center;
97
97
}
98
98
99
+ summary {
100
+ font-weight : normal !important ;
101
+ }
102
+
99
103
</ style >
100
104
</ head >
101
105
< body typeof ="owl:Ontology ">
135
139
< section >
136
140
< h2 > Specification of terms</ h2 >
137
141
< p >
138
- In general, the terms — i.e., the properties and classes — used in
139
- the VCDM are formally specified in Recommendation Track documents published by
140
- the < a href ="https://www.w3.org/groups/wg/vc "> W3C Verifiable Credentials Working
141
- Group</ a > or, for some deprecated or reserved terms, in Reports published by the
142
- < a href ="https://www.w3.org/groups/cg/credentials "> W3C Credentials Community
143
- Group</ a > . In each case of such external definition, the term's description in
144
- this document contains a link to the relevant specification. Additionally, the
145
- `rdfs:definedBy` property in the RDFS representation(s) refers to the formal
146
- specification.
142
+ In general, the terms — i.e., the properties and classes — used in
143
+ the VCDM are formally specified in Recommendation Track documents published by
144
+ the < a href ="https://www.w3.org/groups/wg/vc "> W3C Verifiable Credentials Working
145
+ Group</ a > . In each case of such external definition, the term's description in
146
+ this document contains a link to the relevant specification. Additionally, the
147
+ `rdfs:definedBy` property in the RDFS representation(s) refers to the formal
148
+ specification.
147
149
</ p >
148
150
< p >
149
- In some cases, a local explanation is necessary to complement, or to replace,
150
- the definition found in an external specification. For instance, this is so when
151
- the term is needed to provide a consistent structure to the RDFS vocabulary,
152
- such as when the term defines a common supertype for class instances that are
153
- used as objects of specific properties. For such cases,
154
- the extra definition is included in the current
155
- document (and the `rdfs:comment` property is used to include them in the RDFS
156
- representations).
151
+ In some cases, a local explanation is necessary to complement, or to replace,
152
+ the definition found in an external specification. For instance, this is so when
153
+ the term is needed to provide a consistent structure to the RDFS vocabulary,
154
+ such as when the term defines a common supertype for class instances that are
155
+ used as objects of specific properties. For such cases,
156
+ the extra definition is included in the current
157
+ document (and the `rdfs:comment` property is used to include them in the RDFS
158
+ representations).
157
159
</ p >
158
160
</ section >
159
161
< section >
@@ -163,17 +165,23 @@ <h2>Namespaces</h2>
163
165
</ dl >
164
166
</ section >
165
167
168
+ < section >
169
+ < h2 > < code > @context</ code > files</ h2 >
170
+ < p > The following < code > @context</ code > files make use of the terms defined in this specification:</ p >
171
+ < ul id ="contexts ">
172
+ </ ul >
173
+ </ section >
174
+
166
175
< section id ="term_definitions ">
167
176
< h1 > Regular terms</ h1 >
177
+ < section id ="property_definitions " class ="term_definitions ">
178
+ < h2 > Property definitions</ h2 >
179
+ </ section >
168
180
169
181
< section id ="class_definitions " class ="term_definitions ">
170
182
< h2 > Class definitions</ h2 >
171
183
</ section >
172
184
173
- < section id ="property_definitions " class ="term_definitions ">
174
- < h2 > Property definitions</ h2 >
175
- </ section >
176
-
177
185
< section id ="datatype_definitions " class ="term_definitions ">
178
186
< h2 > Datatype definitions</ h2 >
179
187
</ section >
@@ -186,22 +194,19 @@ <h2>Definitions for individuals</h2>
186
194
< section id ="deprecated_term_definitions ">
187
195
< h1 > Deprecated terms</ h1 >
188
196
189
- < p class ="annoy ">
190
- All terms in this section are < em > < strong > deprecated</ strong > </ em > , and are only
191
- kept in this vocabulary for backward compatibility.
192
- </ p >
193
- < p >
194
- New applications should not use them.
197
+ < p class ="annoy "> All terms in this section are < em > < strong > deprecated</ strong > </ em > , and are only kept in this
198
+ vocabulary for backward compatibility.
199
+ < br > < br > New applications should not use them.
195
200
</ p >
196
201
197
- < section id ="deprecated_class_definitions " class ="term_definitions ">
198
- < h2 > Deprecated classes</ h2 >
199
- </ section >
200
-
201
202
< section id ="deprecated_property_definitions " class ="term_definitions ">
202
203
< h2 > Deprecated properties</ h2 >
203
204
</ section >
204
205
206
+ < section id ="deprecated_class_definitions " class ="term_definitions ">
207
+ < h2 > Deprecated classes</ h2 >
208
+ </ section >
209
+
205
210
< section id ="deprecated_property_definitions " class ="term_definitions ">
206
211
< h2 > Deprecated properties</ h2 >
207
212
</ section >
0 commit comments