<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog posts from 2011 on DCMI</title>
    <link>https://www.dublincore.org/blog/2011/</link>
    <description>Recent content in Blog posts from 2011 on DCMI</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 16 May 2018 00:00:00 +0000</lastBuildDate>
    
        <atom:link href="https://www.dublincore.org/blog/2011/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Dublin Core™ Application Profiles at eleven years (2011)</title>
      <link>https://www.dublincore.org/blog/2011/application_profile/</link>
      <pubDate>Tue, 17 May 2011 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/blog/2011/application_profile/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Note: This piece, posted to a DCMI wiki in 2011, was reformatted and lightly edited for the DCMI blog in 2019.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The notion of an &amp;quot;application profile&amp;quot; was introduced to the Dublin Core™ community by Rachel Heery at the 8th Dublin Core™ workshop of October 2000. The idea distinguished sharply between &amp;quot;namespace schemas&amp;quot; (sets of data elements as defined by their maintainers) and &amp;quot;application profile schemas&amp;quot; (sets of data elements drawn from one or more namespace schemas and optimized for local needs by implementors), introducing the notion of &amp;quot;mixing-and-matching Dublin Core™ elements with elements from related vocabularies.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Reflections on the DCMI Abstract Model (2011)</title>
      <link>https://www.dublincore.org/blog/2011/dcmi_abstract_model/</link>
      <pubDate>Fri, 13 May 2011 00:00:00 +0000</pubDate>
      
      <guid>https://www.dublincore.org/blog/2011/dcmi_abstract_model/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Note: This short piece, posted to a DCMI wiki in 2011, was reformatted and lightly edited for the DCMI blog in 2019.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The &lt;a href=&#34;https://www.dublincore.org/specifications/dublin-core/abstract-model&#34;&gt;DCMI Abstract Model (DCAM)&lt;/a&gt; specifies an abstract syntax for metadata records independent of particular concrete encoding syntaxes. The components of DCAM&#39;s abstract syntax map unambiguously to components of the RDF abstract syntax. In addition, DCAM&#39;s abstract syntax provides several grouping constructs not present in RDF -- notably &amp;quot;description sets&amp;quot; (mappable in principle to a named graph instantiated as a &amp;quot;metadata record&amp;quot;), &amp;quot;descriptions&amp;quot; (mappable in principle to a sub-graph of RDF triples about a single subject), &amp;quot;DCAM statements&amp;quot; (mappable to a sub-graph composed of an RDF statement plus contextual information about the value of that statement), and &amp;quot;value surrogates&amp;quot; (mappable to the different sets of statements used to describe values directly encoded as literal string values as opposed to values identified by URIs or blank nodes).&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
