repository-extension-services tagshttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags2018-08-16T15:17:31-04:00https://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.2.0repository-services-1.2.0[Gradle Release Plugin] - creating tag: 'repository-services-1.2.0'.
Aaron Coburnacoburn@apache.orghttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.1.2repository-services-1.1.2[Gradle Release Plugin] - creating tag: 'repository-services-1.1.2'.
<p data-sourcepos="1:1-2:57" dir="auto">This is a collection of HTTP-based services that can be used with
an LDP server to add behaviors to certain resource types.</p>
<p data-sourcepos="4:1-6:63" dir="auto">This release adds a new configuration option the the ORE and PCDM
extensions, such that an administrator can assign a timeout value
to the route when assembling the resources into a single graph.</p>
<p data-sourcepos="8:1-9:71" dir="auto">By default, the internal timeout value is 30 seconds, but this value
can be modified or changed to an indefinite timeout by setting it to 0.</p>
<p data-sourcepos="11:1-14:22" dir="auto">In the ORE extension, this value can be set in the
<code>edu.amherst.acdc.exts.ore.cfg</code> configuration file with
<code>ore.timeout=30000</code> (note: time is measured in milliseconds,
so 30000 = 30 seconds)</p>
<p data-sourcepos="16:1-17:66" dir="auto">The PCDM extension can be adjusted in a similar way by setting
<code>pcdm.timeout=30000</code> in the <code>edu.amherst.acdc.exts.pcdm.cfg</code> file.</p>2018-08-16T15:17:31-04:00Aaron Coburnacoburn@apache.orghttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.1.1repository-services-1.1.1[Gradle Release Plugin] - creating tag: 'repository-services-1.1.1'.
Aaron Coburnacoburn@apache.orghttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.1.0repository-services-1.1.0[Gradle Release Plugin] - creating tag: 'repository-services-1.1.0'.<h1 data-sourcepos="1:1-1:37" dir="auto">
<a id="user-content-repository-extension-services-110" class="anchor" href="#repository-extension-services-110" aria-hidden="true"></a>Repository Extension Services 1.1.0</h1>
<p data-sourcepos="3:1-3:123" dir="auto">This is a collection of HTTP-based services that can be used with an LDP server to add behaviors to certain resource types.</p>
<p data-sourcepos="5:1-5:41" dir="auto">This release contains two new extensions:</p>
<ul data-sourcepos="7:1-10:0" dir="auto">
<li data-sourcepos="7:1-8:0">
<p data-sourcepos="7:3-7:221">An RDFS entailment service. Given an RDF graph, this service will entail the graph with inferred triples, based on simple RDFS entailment rules. The ontologies used for inference are defined at runtime by configuration.</p>
</li>
<li data-sourcepos="9:1-10:0">
<p data-sourcepos="9:3-9:173">An ORE aggregation service. Given a composite ORE resource, this service will follow ore:aggregates links, assembling multiple resources into a single aggregated resource.</p>
</li>
</ul>
<p data-sourcepos="11:1-11:90" dir="auto">All of these services are deployable in Karaf and are compatible with the API-X framework.</p>
<p data-sourcepos="13:1-13:274" dir="auto">For anyone who has previously used these services, the main difference is that repository resources are referred to with the <code>context</code> query parameter. So for the resource at <a href="http://localhost/repo/ldp/path/to/resource" rel="nofollow noreferrer noopener" target="_blank">http://localhost/repo/ldp/path/to/resource</a>, a repository service refers to that resource like this:</p>
<div class="gl-relative markdown-code-block js-markdown-code">
<pre data-sourcepos="15:5-16:0" class="code highlight js-syntax-highlight language-plaintext" lang="plaintext" v-pre="true"><code><span id="LC1" class="line" lang="plaintext">http://localhost:9109/entailment?context=http://localhost/repo/ldp/path/to/resource</span></code></pre>
<copy-code></copy-code>
</div>
<p data-sourcepos="17:1-17:40" dir="auto">All of the services follow this pattern.</p>2018-08-16T15:19:13-04:00Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.10repository-services-1.0.10[Gradle Release Plugin] - creating tag: 'repository-services-1.0.10'.<p data-sourcepos="1:1-1:239" dir="auto">This release adds the <code>acrepo-connector-triplestore</code> service, which indexes repository content into isolated named graphs in an external triplestore. Typically that triplestore would be configured to make a union graph available for query.</p>
<p data-sourcepos="3:1-3:170" dir="auto">The release also adds a configuration option to <code>acrepo-exts-image</code> such that the default output format can be configured within Karaf (before, it was hard-coded as JPEG)</p>2017-03-03T10:35:20-05:00Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.9repository-services-1.0.9[Gradle Release Plugin] - creating tag: 'repository-services-1.0.9'.<p data-sourcepos="1:1-1:104" dir="auto">The 1.0.9 release adds LDPath support for NonRDFSources via the updates in <code>fcrepo-camel-toolbox/4.7.1</code>.</p>
<p data-sourcepos="3:1-3:54" dir="auto">Additionally, it includes some improved API-X support.</p>2018-08-16T15:19:43-04:00Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.8repository-services-1.0.8[Gradle Release Plugin] - creating tag: 'repository-services-1.0.8'.<p data-sourcepos="1:1-1:115" dir="auto">The 1.0.8 release removes support for the JSON extension, replacing it with a much improved LDPath-based extension.</p>
<p data-sourcepos="3:1-3:83" dir="auto">This release is aligned with <code>fcrepo-camel/4.5.0</code> and <code>fcrepo-camel-toolbox/4.7.0</code>.</p>2017-02-15T11:04:36-05:00Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.7repository-services-1.0.7[Gradle Release Plugin] - creating tag: 'repository-services-1.0.7'.bseegerhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.6repository-services-1.0.6[Gradle Release Plugin] - creating tag: 'repository-services-1.0.6'.Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.5repository-services-1.0.5[Gradle Release Plugin] - creating tag: 'repository-services-1.0.5'.Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.4repository-services-1.0.4[Gradle Release Plugin] - creating tag: 'repository-services-1.0.4'.Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.3repository-services-1.0.3[Gradle Release Plugin] - creating tag: 'repository-services-1.0.3'.Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.2repository-services-1.0.2[Gradle Release Plugin] - creating tag: 'repository-services-1.0.2'.Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.1repository-services-1.0.1[Gradle Release Plugin] - creating tag: '1.0.1'.Aaron Coburnhttps://gitlab.amherst.edu/acdc/repository-extension-services/-/tags/repository-services-1.0.0repository-services-1.0.0[maven-release-plugin] copy for tag repository-services-1.0.0Aaron Coburn