https://www.dublincore.org/specification_type/semantic/ Recent content in Semantic on DCMI Hugo -- gohugo.io en-gb Thu, 26 Apr 2018 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-terms/ Mon, 20 Jan 2020 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-terms/ <p>This document is an up-to-date, authoritative specification of all metadata terms maintained by the Dublin Core™ Metadata Initiative. Included are the fifteen terms of the Dublin Core™ Metadata Element Set (also known as &quot;the Dublin Core&quot;) plus several dozen properties, classes, datatypes, and vocabulary encoding schemes. The &quot;Dublin Core&quot; plus these extension vocabularies are collectively referred to as &quot;DCMI metadata terms&quot; (&quot;Dublin Core terms&quot; for short). These terms are intended to be used in combination with metadata terms from other, compatible vocabularies in the context of application profiles.</p> https://www.dublincore.org/specifications/dublin-core/type-element/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/type-element/ <p>The Dublin Core™ <strong>Resource Type</strong> (DC.Type) element is used to describe the <em>category</em> or <em>genre</em> of the content of the resource. For the sake of interoperability, the primary value should be selected from the enumerated list presented here. Values for DC. Type selected from these lists will be used without annotation or qualification in <em>simple</em> Dublin Core™.</p> https://www.dublincore.org/specifications/dublin-core/rdf-relation-types/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/rdf-relation-types/ <p>This document provides an <a href="http://www.w3.org/RDF">RDF Schema</a> declaration of the Relation Types defined by the <a href="https://www.dublincore.org/groups/relationtype/">Dublin Core™ Relation Type Working Group</a>. This schema declaration consists of both machine-understandable information and human-readable prose for each of the agreed upon Relation Types. The machine-understandable declaration of these types are found embedded in the HTML source code. Human readable declarations of the relation types are as followed:</p> https://www.dublincore.org/specifications/dublin-core/dcmi-namespace/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-namespace/ <p><strong>Glossary:</strong></p> <p>This document follows the DCMI Abstract Model [DCAM] in its use of the following terminology:</p> <dl> <dt><em>term</em></dt> <dd>A property (element), class, vocabulary encoding scheme, or syntax encoding scheme.</dd> <dt><em>URI</em></dt> <dd>A Uniform Resource Identifier [<a href="#URI">URI</a>] or Internationalized Resource Identifier [<a href="#IRI">IRI</a>].</dd> </dl> <p>In addition, this document uses the following terminology:</p> https://www.dublincore.org/specifications/dublin-core/education-namespace/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/education-namespace/ <p>This document is a Proposal from the Dublin Core™ Education Working Group [<a href="https://www.dublincore.org/groups/education/">DCEd</a>] to the Dublin Core™ Usage Committee of the Dublin Core™ Metadata Initiative [<a href="https://www.dublincore.org/">DCMI</a>]. The content of this document is intended to reflect the consensus reached within DCEd. It reports decisions reached by DCEd through its online discussions and face-to-face meetings in Frankfurt (October 25-27, 1999) and Melbourne (February 19-20, 2000). A <a href="http://www.ischool.washington.edu/sasutton/dc-ed/Dc-ac/DC-Education_Report.html">Report of Deliberations</a> is referenced throughout in support of the Proposal.</p> https://www.dublincore.org/specifications/dublin-core/type-rfc-review/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/type-rfc-review/ <p>The main changes from the earlier definition in RFC 2413 are:</p> <ul> <li>Adoption of ISO 11179 representation</li> <li>Deletion of examples</li> <li>More general statement about use of enumerated lists and indication of SCHEME used</li> <li>Statement to contrast with Format</li> </ul> <h3 id="proposed-definition">Proposed Definition</h3> <p><strong>Name:</strong> Resource Type<br> <strong>Identifier:</strong> Type<br> <strong>Definition:</strong> The nature or genre of the content of the resource<br> <strong>Obligation:</strong> Optional<br> <strong>Datatype:</strong> Character String<br> <strong>Maximum Occurrence:</strong> Unlimited<br> <strong>Comment:</strong> Recommended best practice is to select a value from an enumerated list and to identify the list being used. Type may be repeated as necessary to include different categories. To describe the form of the manifestation of the content (medium, MIME type, size, etc.) of the resource, use FORMAT element.</p> https://www.dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/ <mark><b><i>Please note that this version of the specification for the DCMI Type Vocabulary is somewhat out of date. Please see <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/">the DCMI Metadata Terms</a> for the current  documentation about the DCMI Type Vocabulary</i></b></mark> <p> <table cellspacing="0" class="docinfo"> <tr> <th>Title:</th> <td>DCMI Type Vocabulary</td> </tr> <tr> <th>Creator:</th> <td> <a href="mailto:dc-usage@jiscmail.ac.uk">DCMI Usage Board</a> </td> </tr> <tr> <th>Identifier:</th> <td> <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/2010-10-11/">http://dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/2010-10-11/</a> </td> </tr> <tr> <th>Date Issued:</th> <td>2010-10-11</td> </tr> <tr> <th>Latest Version:</th> <td> <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/">http://dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/</a> </td> </tr> <tr> <th>Replaces:</th> <td> <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/2008-01-14/">http://dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/2008-01-14/</a> </td> </tr> <tr> <th>Replaced By:</th> <td>Not applicable</td> </tr> <tr> <th>Translations:</th> <td> <a href="https://www.dublincore.org/resources/translations/">http://dublincore.org/resources/translations/</a> </td> </tr> <tr> <th>Document Status:</th> <td>This is a DCMI Recommendation.</td> </tr> <tr> <th>Description:</th> <td> The DCMI Type Vocabulary provides a general, cross-domain list of approved terms that may be used as values for the Resource Type element to identify the genre of a resource. The terms documented here are also included in the more comprehensive document "DCMI Metadata Terms" at <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/">http://dublincore.org/specifications/dublin-core/dcmi-terms/</a>.</td> </tr> </table> <br> <table cellspacing="0" class="border"> <tr> <th colspan="2"> <a name="Collection-003"></a>Term Name:   Collection</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/Collection">http://purl.org/dc/dcmitype/Collection</a> </td> </tr> <tr> <td>Label: </td> <td>Collection</td> </tr> <tr> <td>Definition: </td> <td>An aggregation of resources.</td> </tr> <tr> <td>Comment: </td> <td>A collection is described as a group; its parts may also be separately described.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#Collection-003">http://dublincore.org/usage/terms/history/#Collection-003</a> </td> </tr> <tr> <th colspan="2"> <a name="Dataset-003"></a>Term Name:   Dataset</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/Dataset">http://purl.org/dc/dcmitype/Dataset</a> </td> </tr> <tr> <td>Label: </td> <td>Dataset</td> </tr> <tr> <td>Definition: </td> <td>Data encoded in a defined structure.</td> </tr> <tr> <td>Comment: </td> <td>Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#Dataset-003">http://dublincore.org/usage/terms/history/#Dataset-003</a> </td> </tr> <tr> <th colspan="2"> <a name="Event-003"></a>Term Name:   Event</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/Event">http://purl.org/dc/dcmitype/Event</a> </td> </tr> <tr> <td>Label: </td> <td>Event</td> </tr> <tr> <td>Definition: </td> <td>A non-persistent, time-based occurrence.</td> </tr> <tr> <td>Comment: </td> <td>Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, and responsible agents associated with an event. Examples include an exhibition, webcast, conference, workshop, open day, performance, battle, trial, wedding, tea party, conflagration.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#Event-003">http://dublincore.org/usage/terms/history/#Event-003</a> </td> </tr> <tr> <th colspan="2"> <a name="Image-004"></a>Term Name:   Image</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/Image">http://purl.org/dc/dcmitype/Image</a> </td> </tr> <tr> <td>Label: </td> <td>Image</td> </tr> <tr> <td>Definition: </td> <td>A visual representation other than text.</td> </tr> <tr> <td>Comment: </td> <td>Examples include images and photographs of physical objects, paintings, prints, drawings, other images and graphics, animations and moving pictures, film, diagrams, maps, musical notation. Note that Image may include both electronic and physical representations.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Broader Than: </td> <td> <a href="http://purl.org/dc/dcmitype/StillImage">http://purl.org/dc/dcmitype/StillImage</a> </td> </tr> <tr> <td>Broader Than: </td> <td> <a href="http://purl.org/dc/dcmitype/MovingImage">http://purl.org/dc/dcmitype/MovingImage</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#Image-004">http://dublincore.org/usage/terms/history/#Image-004</a> </td> </tr> <tr> <th colspan="2"> <a name="InteractiveResource-003"></a>Term Name:   InteractiveResource</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/InteractiveResource">http://purl.org/dc/dcmitype/InteractiveResource</a> </td> </tr> <tr> <td>Label: </td> <td>Interactive Resource</td> </tr> <tr> <td>Definition: </td> <td>A resource requiring interaction from the user to be understood, executed, or experienced.</td> </tr> <tr> <td>Comment: </td> <td>Examples include forms on Web pages, applets, multimedia learning objects, chat services, or virtual reality environments.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#InteractiveResource-003">http://dublincore.org/usage/terms/history/#InteractiveResource-003</a> </td> </tr> <tr> <th colspan="2"> <a name="MovingImage-003"></a>Term Name:   MovingImage</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/MovingImage">http://purl.org/dc/dcmitype/MovingImage</a> </td> </tr> <tr> <td>Label: </td> <td>Moving Image</td> </tr> <tr> <td>Definition: </td> <td>A series of visual representations imparting an impression of motion when shown in succession.</td> </tr> <tr> <td>Comment: </td> <td>Examples include animations, movies, television programs, videos, zoetropes, or visual output from a simulation. Instances of the type Moving Image must also be describable as instances of the broader type Image.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Narrower Than: </td> <td> <a href="http://purl.org/dc/dcmitype/Image">http://purl.org/dc/dcmitype/Image</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#MovingImage-003">http://dublincore.org/usage/terms/history/#MovingImage-003</a> </td> </tr> <tr> <th colspan="2"> <a name="PhysicalObject-003"></a>Term Name:   PhysicalObject</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/PhysicalObject">http://purl.org/dc/dcmitype/PhysicalObject</a> </td> </tr> <tr> <td>Label: </td> <td>Physical Object</td> </tr> <tr> <td>Definition: </td> <td>An inanimate, three-dimensional object or substance.</td> </tr> <tr> <td>Comment: </td> <td>Note that digital representations of, or surrogates for, these objects should use Image, Text or one of the other types.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#PhysicalObject-003">http://dublincore.org/usage/terms/history/#PhysicalObject-003</a> </td> </tr> <tr> <th colspan="2"> <a name="Service-003"></a>Term Name:   Service</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/Service">http://purl.org/dc/dcmitype/Service</a> </td> </tr> <tr> <td>Label: </td> <td>Service</td> </tr> <tr> <td>Definition: </td> <td>A system that provides one or more functions.</td> </tr> <tr> <td>Comment: </td> <td>Examples include a photocopying service, a banking service, an authentication service, interlibrary loans, a Z39.50 or Web server.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#Service-003">http://dublincore.org/usage/terms/history/#Service-003</a> </td> </tr> <tr> <th colspan="2"> <a name="Software-003"></a>Term Name:   Software</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/Software">http://purl.org/dc/dcmitype/Software</a> </td> </tr> <tr> <td>Label: </td> <td>Software</td> </tr> <tr> <td>Definition: </td> <td>A computer program in source or compiled form.</td> </tr> <tr> <td>Comment: </td> <td>Examples include a C source file, MS-Windows .exe executable, or Perl script.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#Software-003">http://dublincore.org/usage/terms/history/#Software-003</a> </td> </tr> <tr> <th colspan="2"> <a name="Sound-003"></a>Term Name:   Sound</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/Sound">http://purl.org/dc/dcmitype/Sound</a> </td> </tr> <tr> <td>Label: </td> <td>Sound</td> </tr> <tr> <td>Definition: </td> <td>A resource primarily intended to be heard.</td> </tr> <tr> <td>Comment: </td> <td>Examples include a music playback file format, an audio compact disc, and recorded speech or sounds.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#Sound-003">http://dublincore.org/usage/terms/history/#Sound-003</a> </td> </tr> <tr> <th colspan="2"> <a name="StillImage-003"></a>Term Name:   StillImage</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/StillImage">http://purl.org/dc/dcmitype/StillImage</a> </td> </tr> <tr> <td>Label: </td> <td>Still Image</td> </tr> <tr> <td>Definition: </td> <td>A static visual representation.</td> </tr> <tr> <td>Comment: </td> <td>Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Instances of the type Still Image must also be describable as instances of the broader type Image.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Narrower Than: </td> <td> <a href="http://purl.org/dc/dcmitype/Image">http://purl.org/dc/dcmitype/Image</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#StillImage-003">http://dublincore.org/usage/terms/history/#StillImage-003</a> </td> </tr> <tr> <th colspan="2"> <a name="Text-003"></a>Term Name:   Text</th> </tr> <tr> <td>URI: </td> <td> <a href="http://purl.org/dc/dcmitype/Text">http://purl.org/dc/dcmitype/Text</a> </td> </tr> <tr> <td>Label: </td> <td>Text</td> </tr> <tr> <td>Definition: </td> <td>A resource consisting primarily of words for reading.</td> </tr> <tr> <td>Comment: </td> <td>Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</td> </tr> <tr> <td>Type of Term: </td> <td> <a href="http://www.w3.org/2000/01/rdf-schema#Class">Class</a> </td> </tr> <tr> <td>Member Of: </td> <td> <a href="http://purl.org/dc/terms/DCMIType">http://purl.org/dc/terms/DCMIType</a> </td> </tr> <tr> <td>Version: </td> <td> <a href="https://www.dublincore.org/usage/terms/history/#Text-003">http://dublincore.org/usage/terms/history/#Text-003</a> </td> </tr> </table> </p> https://www.dublincore.org/specifications/dublin-core/dcmi-point/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-point/ <h2 id="table-of-contents">Table of Contents</h2> <ul> <li> <ol> <li>Introduction</li> </ol> </li> <li> <ol start="2"> <li>Identifying a place - the DCMI Point scheme</li> </ol> </li> <li> <ol start="3"> <li>Encoding DCMI Point with DCSV Syntax</li> </ol> </li> <li> <ol start="4"> <li>Examples</li> </ol> </li> <li> <ol start="5"> <li>References</li> </ol> </li> </ul> <h2 id="1-introduction"><a name="sec1"></a>1. Introduction</h2> <p>Several methods are available generally to indicate a <strong>place</strong>. These include, but are not limited to:</p> https://www.dublincore.org/specifications/dublin-core/dcmi-period/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-period/ <h2 id="table-of-contents">Table of Contents</h2> <ul> <li> <ol> <li>Introduction</li> </ol> </li> <li> <ol start="2"> <li>Identifying a time interval - the DCMI Period scheme</li> </ol> </li> <li> <ol start="3"> <li>Encoding DCMI Period with DCSV Syntax</li> </ol> </li> <li> <ol start="4"> <li>Examples</li> </ol> </li> <li> <ol start="5"> <li>References</li> </ol> </li> </ul> <h2 id="1-introduction"><a name="sec1"></a>1. Introduction</h2> <p>Several methods are available to indicate a time interval. These include, but are not limited to:</p> https://www.dublincore.org/specifications/dublin-core/dcmi-dcsv/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-dcsv/ <h2 id="table-of-contents">Table of Contents</h2> <ol> <li>Introduction</li> <li>Structured Value Strings</li> <li>Parsing DCSV</li> <li>Sample Code for parsing DCSV-encoded values</li> <li>Glossary</li> <li>Acknowledgements</li> <li>References</li> </ol> <h2 id="1-introduction"><a name="introduction"></a>1. Introduction</h2> <p>It is often desirable to encode or _serialise_simple structured data within a text string. Some generic methods are in common use. Borrowing conventions from natural languages, commas (,) and semi-colons (;) are frequently used as list separators. Similarly, comma-separated values (CSV) and tab-separated values (TSV) are common export formats from spreadsheet and database software, with _line feeds_separating rows or tuples. Dots (.) and dashes (-) are sometimes used to imply hierarchies, particularly in thesaurus applications. The eXtensible Markup Language [XML] provides a more general solution, using tags contained within angle brackets (&lt;, &gt;) to indicate structure.</p> https://www.dublincore.org/specifications/dublin-core/dcmi-box/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-box/ <h2 id="table-of-contents">Table of Contents</h2> <ul> <li> <ol> <li>Introduction</li> </ol> </li> <li> <ol start="2"> <li>Identifying a place - the DCMI Box scheme</li> </ol> </li> <li> <ol start="3"> <li>Encoding DCMI Box with DCSV syntax</li> </ol> </li> <li> <ol start="4"> <li>Examples</li> </ol> </li> <li> <ol start="5"> <li>References</li> </ol> </li> </ul> <h2 id="1-introduction"><a name="sec1"></a>1. Introduction</h2> <p>Several methods are available to indicate a place. These include, but are not limited to:</p> https://www.dublincore.org/specifications/dublin-core/date-element/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/date-element/ <p>This report is a record of the efforts of the Date working group constituted following the Helsinki Dublin Core™ Metadata Workshop (DC-5) of October, 1997. The recommendations are provisional and can be expected to evolve in the light of further implementation experience.</p> https://www.dublincore.org/specifications/dublin-core/coverage-rfc-review/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/coverage-rfc-review/ <p>A proposed revision to the definition of Coverage appears below. The main changes from the RFC 2413 definition are</p> <ul> <li>Clarification of element definition</li> <li>Removal of comments on experimental nature of element</li> <li>Explicit recognition of the main uses of Coverage within the implementor community</li> <li>Adoption of ISO 11179 representation, including separation of &quot;Definition&quot; from &quot;Comment&quot;</li> </ul> <h2 id="proposed-definition-for-coverage">Proposed definition for Coverage</h2> <p>Name: Coverage</p> https://www.dublincore.org/specifications/dublin-core/coverage-element/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/coverage-element/ <h2 id="table-of-contents">Table of Contents</h2> <ul> <li><strong>Definition</strong></li> <li><strong>Use of Qualifiers</strong></li> <li><strong>Use of Schemes</strong></li> <li><strong>Examples</strong><br> <a id="Definition" name="Definition"></a></li> </ul> <hr> <h2 id="definition"><strong>Definition</strong></h2> <p>The Coverage element describes the spatial and temporal characteristics of the object or resource and is the key element for supporting spatial or temporal range searching on document-like objects that are spatially or temporally referenced. Coverage may be modified by spatial or temporal qualifiers.</p> https://www.dublincore.org/specifications/dublin-core/bib-citation/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/bib-citation/ <p>I understand from the Guidelines for Dublin Core™ Working Groups (draft 1.4) that once a Chair has established consensus within the WG, the Group's recommendations should be circulated to the <a href="http://www.jiscmail.ac.uk/lists/dc-general.html">dc-general</a> list for comment. Below, you will find our Recommendations. (Please refer to <a href="http://www.jiscmail.ac.uk/lists/dc-citation.html">http://www.jiscmail.ac.uk/lists/dc-citation.html</a> if you would like to see who is in the Working Group and the discussions behind the recommendations.) Comments should be posted to <a href="http://www.jiscmail.ac.uk/lists/dc-general.html">dc-general</a> by Monday 19 July.</p> https://www.dublincore.org/specifications/dublin-core/thesauri-definition/ Fri, 01 Sep 2017 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/thesauri-definition/ <p>This message summarizes the definition of thesauri and classification as indexing tools and gives the distinction between entity (taxonomic) and bibliographic classification. It also explains the difference between thesauri and classification and the difference between the general classification schemes suggested for DCMES element SUBJECT: LCC, DCC and UDC.</p> https://www.dublincore.org/specifications/dublin-core/dc-kernel/ Thu, 14 Aug 2014 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dc-kernel/ <p>Note: This is the experimental draft of a potential DCMI Recommended Resource description. This experimental document provides a landing page for Kernel metadata. It has no official status, has not been publicized, and if found, should not be cited.</p> https://www.dublincore.org/specifications/dublin-core/dces/ Thu, 14 Jun 2012 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dces/ <div class="alert alert-warning" role="alert"> <p><b><i>Please note that this version of the specification for the Dublin Core Element Set is somewhat out of date. Please see <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/">the DCMI Metadata Terms</a> for the current documentation of its fifteen terms</i></b></p> https://www.dublincore.org/specifications/dublin-core/dces/2012-06-14/ Thu, 14 Jun 2012 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dces/2012-06-14/ <p><a name="introduction" id="introduction"></a></p> <h2 id="introduction">Introduction</h2> <p>The Dublin Core™ Metadata Element Set is a vocabulary of fifteen properties for use in resource description. The name &quot;Dublin&quot; is due to its origin at a 1995 invitational workshop in Dublin, Ohio; &quot;core&quot; because its elements are broad and generic, usable for describing a wide range of resources.</p> https://www.dublincore.org/specifications/dublin-core/dcmi-namespace-generic/ Mon, 02 May 2011 00:00:00 +0000 https://www.dublincore.org/specifications/dublin-core/dcmi-namespace-generic/ <h2 id="rdf-vocabularies-require">RDF vocabularies require:</h2> <ul> <li><strong>Use of URIs</strong>. Each term (e.g., property or class) in an RDF vocabulary must be identified with a URI.</li> <li><strong>Stable identifiers</strong>. Each term URI should refer to the same term in perpetuity and should not be repurposed, sold, or forfeited through neglect (e.g., by non-payment of domain name fees). This commitment should be backed by institutional guarantees. Note that stable URIs (such as PURLs) do not automatically refer to stable documentation (such as content to which PURLs are redirected).</li> <li><strong>Machine-processable documentation</strong>. Each term URI should remain resolvable to a machine-processable expression of its semantics in accordance with principles of Web architecture. As of 2011, such expressions include RDF schemas and OWL ontologies and are documented in forms ranging from stand-alone schema files to formal representations embedded in Web pages.</li> <li><strong>Change policies</strong>. The stability of the meaning of the terms should be determinable -- i.e., the meanings of terms should evolve according to known change management policies and with responsibility for changes traceable to individuals or organizations. Change histories should also be published so that a vocabulary's evolution over time is a matter of public record.</li> <li><strong>Open access provisions</strong>. Vocabularies should be made available for public access under the terms of copyright models that encourage re-use and collaboration and with well-defined mechanisms for community feedback.</li> <li><strong>Preservation provisions</strong>. As for any other artifact of cultural and historical significance, arrangements should be made for the long-term preservation of a vocabulary.</li> </ul> <h2 id="subscribers-to-these-principles">Subscribers to these principles</h2> <ul> <li>FOAF Project</li> <li>Dublin Core™ Metadata Initiative</li> </ul>