<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Semantics on DCMI</title>
    <link>https://www.dublincore.org/specification_type/semantics/</link>
    <description>Recent content in Semantics on DCMI</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 01 Sep 2017 00:00:00 +0000</lastBuildDate>
    
        <atom:link href="https://www.dublincore.org/specification_type/semantics/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Representing Peoples Names in Dublin Core</title>
      <link>https://www.dublincore.org/specifications/dublin-core/name-representation/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/name-representation/</guid>
      <description>&lt;p&gt;This note provides some guidance on representing people&#39;s names in metadata.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. The Problem&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;While most people only have one name, that name may be written down in many different ways. The name may be written in full (e.g. &#39;John Stuart Mills&#39;). Components of the name can be abbreviated (e.g. &#39;John S. Mills&#39;, or &#39;J.S. Mills&#39;), or omitted (e.g. &#39;John Mills&#39;). Names may be extended by titles or honorifics (e.g. &#39;Mr. John Mills&#39;). The components of the name may be reordered (e.g. &#39;Mills, John Stuart&#39;). Complexity is added by the fact that people frequently do not use their &#39;official&#39; name. People often prefer to use shortened or alternative forms of their name (e.g. &#39;Kathy&#39; for &#39;Kathryn&#39;, and using &#39;Jack&#39; for &#39;John&#39; was once common in Australia). Some people prefer to use their second name instead of their given name (e.g. &#39;Margaret Read&#39; instead of &#39;Frances M. Read&#39;).&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Format Element Working Draft</title>
      <link>https://www.dublincore.org/specifications/dublin-core/format-element/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/format-element/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Format Position Paper (Revised)&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The &lt;strong&gt;Format&lt;/strong&gt; (DC.Format) of a resource refers to the medium, data format, and materials of the instantiation of that resource, including its size if required. This is important in resource discovery as it allows a user to discriminate on the basis of the software, hardware, and other infrastructure that might be needed to display, operate or otherwise use the resource. For the sake of interoperability, the value of the data format or media should be selected from an enumerated list, as discussed below. Values for DC.Format selected from these lists will be used without annotation in simple Dublin Core™.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Domains and Ranges for DCMI Properties</title>
      <link>https://www.dublincore.org/specifications/dublin-core/domain-range/</link>
      <pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/specifications/dublin-core/domain-range/</guid>
      <description>&lt;h2 id=&#34;table-of-contents&#34;&gt;Table of contents&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Introduction&lt;/li&gt;
&lt;li&gt;The Classes&lt;/li&gt;
&lt;li&gt;Domain and Range assertions for DCMI Properties&lt;br&gt;
References&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h2 id=&#34;1-introduction&#34;&gt;&lt;a id=&#34;sect-1&#34; name=&#34;sect-1&#34;&gt;1. Introduction&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This document uses the terminology of the DCMI Abstract Model [DCAM]. The relationship types with which this document is principally concerned are described by the DCAM as follows:&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
