<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="http://iplus.ukoln.ac.uk/taxonomy/term/85/component-associated/all" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
  <channel>
    <title>Technical overview and related use cases: romeo</title>
    <link>http://iplus.ukoln.ac.uk/taxonomy/term/85/component-associated/all</link>
    <description>RSS feed: components in specified supplier category</description>
    <language>en</language>
          <item>
    <title>RoMEO</title>
    <link>http://iplus.ukoln.ac.uk/technology/romeo</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;RoMEO is a registry service (developed and managed by University of Nottingham) specifying publisher copyright and archiving policies.  RoMEO summarises publisher copyright rules about deposit in institutional repositories and shows which publishers comply with funding agencies conditions on open access.&lt;/p&gt;
&lt;p&gt;Note: RoMEO is one of the repository infrastructure components supported in &#039;Wave 1&#039; of &lt;a href=&quot;http://www.repositorynet.ac.uk/about-repositorynet/&quot;&gt;RepositoryNet+&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 30 Apr 2012 13:25:44 +0000</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">4 at http://iplus.ukoln.ac.uk</guid>
  </item>
  <item>
    <title>Proposed API for RoMEO / JULIET</title>
    <link>http://iplus.ukoln.ac.uk/usecase/proposed-api-romeo-juliet</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;This use case outlines potential user requirements and technical development considerations for a proposed integrated data-feed API that is able to supply machine-readable, machine-executable information on both publisher- and funder-policies regarding Open Access (OA) publication.  The proposed API would support enhanced sharing of data-driven infrastructure functionality across both Current Research Information System (CRIS) and Institutional Repository (IR) platforms.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Thu, 01 Nov 2012 15:41:51 +0000</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">70 at http://iplus.ukoln.ac.uk</guid>
  </item>
  </channel>
</rss>
