<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Practice on DCMI</title>
    <link>https://www.dublincore.org/specification_type/practice/</link>
    <description>Recent content in Practice on DCMI</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 26 Apr 2018 00:00:00 +0000</lastBuildDate>
    
        <atom:link href="https://www.dublincore.org/specification_type/practice/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Using Dublin Core</title>
      <link>https://www.dublincore.org/specifications/dublin-core/usageguide/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/usageguide/</guid>
      <description>&lt;p&gt;&lt;mark&gt;NOTE: This document was maintained from 2001 to 2005 as an entry point for new users of Dublin Core™ wishing to create simple descriptive records for information resources (for example, electronic documents) and as a ready reference document for specialists. It has been superseded by &lt;a href=&#34;https://www.dublincore.org/resources/userguide&#34;&gt;more recent guidance materials&lt;/a&gt;.&lt;/mark&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>The Use of Dublin Core™ Metadata in WebDAV</title>
      <link>https://www.dublincore.org/specifications/dublin-core/dc-webdav/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/dc-webdav/</guid>
      <description>&lt;p&gt;&lt;strong&gt;&lt;a id=&#34;status&#34; name=&#34;status&#34;&gt;&lt;/a&gt;Status of this Memo&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Plans for a distributed registry of Dublin Core™ in multiple languages.</title>
      <link>https://www.dublincore.org/specifications/dublin-core/distributed-registry/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/distributed-registry/</guid>
      <description>&lt;p&gt;Note: This is a provisional version for discussion only; points 6 through 8 have not been approved by the group as a whole.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Dublin Core™ and z39.50</title>
      <link>https://www.dublincore.org/specifications/dublin-core/dc-z3950/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/dc-z3950/</guid>
      <description>&lt;p&gt;This document is substantially changed from the previous draft. It incorporates changes reflecting the results of the January meeting of the Z39.50 Implementors Group (ZIG).&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>DCMI Box Encoding Scheme</title>
      <link>https://www.dublincore.org/specifications/dublin-core/dcmi-box/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/dcmi-box/</guid>
      <description>&lt;h2 id=&#34;table-of-contents&#34;&gt;Table of Contents&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;ol&gt;
&lt;li&gt;Introduction&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;ol start=&#34;2&#34;&gt;
&lt;li&gt;Identifying a place - the DCMI Box scheme&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;ol start=&#34;3&#34;&gt;
&lt;li&gt;Encoding DCMI Box with DCSV syntax&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;ol start=&#34;4&#34;&gt;
&lt;li&gt;Examples&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;ol start=&#34;5&#34;&gt;
&lt;li&gt;References&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;1-introduction&#34;&gt;&lt;a name=&#34;sec1&#34;&gt;&lt;/a&gt;1. Introduction&lt;/h2&gt;
&lt;p&gt;Several methods are available to indicate a place. These include, but are not limited to:&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>A Cross-Domain Attribute Set</title>
      <link>https://www.dublincore.org/specifications/dublin-core/cross-domain-attribute/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/cross-domain-attribute/</guid>
      <description>&lt;p&gt;&lt;strong&gt;The Problems with Cross-Domain Searching&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Searching is almost always about compromises. The kinds of access points that the searcher is expecting may or may not be accurately reflected in the indexing provided by the database server. The searching is most accurate, and the searcher is least surprised, when the searcher and client software have a complete understanding of the schema of the database being searched. The next least surprising environment is when the searcher has no expectations about the database and the server provides the complete document in a single index (e.g. WAIS). This may not be very accurate, but no one is surprised by the results. Anything in between complete understanding and complete ignorance is a compromise and subject to the user being surprised by the results of a search.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Guidelines for Dublin Core™ Application Profiles</title>
      <link>https://www.dublincore.org/specifications/dublin-core/profile-guidelines/</link>
      <pubDate>Mon, 18 May 2009 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/profile-guidelines/</guid>
      <description>&lt;h2 id=&#34;table-of-contents&#34;&gt;Table of contents&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&#34;#sect-1&#34;&gt;Introduction&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#sect-2&#34;&gt;Framework for Dublin Core™ Application Profiles&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#sect-3&#34;&gt;Defining Functional Requirements&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#sect-4&#34;&gt;Selecting or Developing a Domain Model&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#sect-5&#34;&gt;Selecting and Defining Metadata Terms&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#sect-6&#34;&gt;Designing the Metadata Record with a Description Set Profile&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#sect-7&#34;&gt;Usage Guidelines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#sect-8&#34;&gt;Syntax Guidelines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#appa&#34;&gt;Appendix A: Description Set Model (from DCMI Abstract Model)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#appb&#34;&gt;Appendix B: &lt;strong&gt;MyBookCase&lt;/strong&gt; Description Set Profile&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#appc&#34;&gt;Appendix C: Using RDF properties in profiles: a technical primer&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a id=&#34;sect-1&#34; name=&#34;sect-1&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Dublin Core™ Application Profile Guidelines</title>
      <link>https://www.dublincore.org/specifications/dublin-core/application-profile-guidelines/</link>
      <pubDate>Sat, 03 Sep 2005 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/application-profile-guidelines/</guid>
      <description>&lt;h1 id=&#34;dublin-core8482-application-profile-guidelines&#34;&gt;Dublin Core™ Application Profile Guidelines&lt;/h1&gt;
&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;A Dublin Core™ Application Profile (DCAP) is a declaration specifying which metadata terms an organization, information provider, or user community uses in its metadata. By definition, a DCAP identifies the source of metadata terms used – whether they have been defined in formally maintained standards such as Dublin Core, in less formally defined element sets and vocabularies, or by the creator of the DCAP itself for local use in an application. Optionally, a DCAP may provide additional documentation on how the terms are constrained, encoded, or interpreted for application-specific purposes.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Guidelines for Encoding Bibliographic Citation Information in Dublin Core™ Metadata</title>
      <link>https://www.dublincore.org/specifications/dublin-core/dc-citation-guidelines/</link>
      <pubDate>Mon, 13 Jun 2005 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/dc-citation-guidelines/</guid>
      <description>&lt;h2 id=&#34;1-introduction-and-scope&#34;&gt;1 Introduction and Scope&lt;/h2&gt;
&lt;p&gt;This document provides guidelines for capturing bibliographic citation information within a Dublin Core™ description. It focuses primarily on:&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Element Refinement in Dublin Core™ Metadata</title>
      <link>https://www.dublincore.org/specifications/dublin-core/dc-elem-refine/</link>
      <pubDate>Mon, 13 Jun 2005 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/dc-elem-refine/</guid>
      <description>&lt;h3 id=&#34;elements-properties-and-statements&#34;&gt;Elements, Properties and Statements&lt;/h3&gt;
&lt;p&gt;Dublin Core™ elements and element refinements are properties. A property is &amp;quot;a specific aspect, characteristic, attribute, or relation used to describe resources&amp;quot;. According to the &lt;em&gt;DCMI Abstract Model&lt;/em&gt;, all these &amp;quot;aspects, characteristics, attributes and relations&amp;quot; involve relationships between resources [DCMIAM]. Each property corresponds to a type of relationship, such as the notion that a resource &amp;quot;is created by&amp;quot; an agent (the agent is a second resource), or that a resource &amp;quot;is about the subject of&amp;quot; some concept (the concept is also a resource).&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
