Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add basic dcterms:conformsTo example #59

Merged
merged 4 commits into from
Sep 15, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 34 additions & 10 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -2123,14 +2123,28 @@ <h4>Additional Manifest Properties</h4>
RECOMMENDED that such terms be included using <a
href="https://www.w3.org/TR/json-ld/#compact-iris">Compact IRIs</a>&#160;[[!json-ld]],
with prefixes defined as part of the context.</p>

<p class="note"> A prefix definition <code>dc</code> for [[dcterms]] is included in the context
file of [[schema.org]]. This means that it is not necessary to add the prefix explicitly.
The same is true for a number of other public vocabularies; see the <a
href="https://schema.org/docs/jsonldcontext.json">schema.org context file</a> for
further details.</p>

<pre class="example" title="Usage of the schema.org 'copyrightYear' and 'copyrightHolder' terms, as an extension to the basic data.">

<pre class="example" title="Extending the basic data set using a vocabulary prefix declaration.">
{
"@context" : [
"https://schema.org",
"https://www.w3.org/ns/pub-context",
{"ex": "https://example.org/vocab"}
],
&#8230;
"ex:region" : "North America",
&#8230;
}
</pre>

<p class="note">The <a href="https://schema.org/docs/jsonldcontext.json">schema.org context
file</a> [[schema.org]] defines a number of prefixes for commonly used vocabularies,
such as the Dublin Core Terms (`dcterms`) [[dcterms]] and Element Set (`dc`) [[dc11]], the
FOAF vocabulary (`foaf`) [[foaf]], and the Bibliographic Ontology (`bibo`) [[bibo]].
Properties from these vocabularies can be used without their prefixes having to be
declared.</p>

<pre class="example" title="Extending the basic data using the schema.org 'copyrightYear' and 'copyrightHolder' terms.">
{
"@context" : ["https://schema.org","https://www.w3.org/ns/pub-context"],
"type" : "TechArticle",
Expand All @@ -2143,14 +2157,24 @@ <h4>Additional Manifest Properties</h4>
}
</pre>

<pre class="example" title="Usage of the Dublin Core 'subject' with the 2012 ACM Classification terms, as an extension to the basic data.">
<pre class="example" title="Extending the basic data set using the Dublin Core 'subject' term with the 2012 ACM Classification terms.">
{
"@context" : ["https://schema.org","https://www.w3.org/ns/pub-context"],
"type" : "CreativeWork",
&#8230;
"id" : "http://www.w3.org/TR/tabular-data-model/",
"url" : "http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/",
"dc:subject" : ["Web data description languages","Data integration","Data Exchange"],
"dcterms:subject" : ["Web data description languages","Data integration","Data Exchange"],
&#8230;
}
</pre>

<pre class="example" title="Extending the basic data set using the Dublin Core 'conformsTo' term to identify the version of a standard a publication conforms to.">
{
"@context" : ["https://schema.org","https://www.w3.org/ns/pub-context"],
"type" : "CreativeWork",
&#8230;
"dcterms:conformsTo" : "https://example.org/publishing/standard-11",
&#8230;
}
</pre>
Expand Down