Base Service DocumentThis defines where to get the specific Service Documents for each resource type. Multiple services (backend connectors) can be defined here. I personally think 'resource types' should be explicitly defined in the spec (here I'm using Actors, Resources, Items and Status) so there's no ambiguity about what a client will be retrieving. You would only include IRIs for service documents for services that you actually support with at least one method. GET /services/ <?xml version="1.0" encoding='utf-8'?>
<service xmlns="http://www.w3.org/2007/app"
xmlns:atom="http://www.w3.org/2005/Atom">
<workspace>
<atom:title>Koha ILS</atom:title>
<collection
href="http://example.org/koha/services/actor" >
<atom:title>Actor</atom:title>
</collection>
<collection
href="http://example.org/koha/services/resource" >
<atom:title>Resource</atom:title>
</collection>
<collection
href="http://example.org/koha/services/item" >
<atom:title>Item</atom:title>
</collection>
</workspace>
<workspace>
<atom:title>ReservesDirect</atom:title>
<collection
href="http://example.org/resdirect/services/actor" >
<atom:title>Actor</atom:title>
</collection>
<collection
href="http://example.org/resdirect/services/collection" >
<atom:title>Collection</atom:title>
</collection>
<collection
href="http://example.org/resdirect/services/resource" >
<atom:title>Resource</atom:title>
</collection>
<collection
href="http://example.org/resdirect/services/item" >
<atom:title>Item</atom:title>
</collection>
</workspace>
</service>
|
Sign in to add a comment
