Don't you first also have to define the concrete operations your ILS must support to wrap them to Jangle? We have a SOAP API that supports all CRUD operations (create, retrieve, update, delete) for a PICA database:
This should be very easy to map to Jangle but I am still somehow confused where to start. Each record in the catalog is identified by an id but there are no actors, collections and such. And is http://search.cpan.org/perldoc?Atompub the right library to build a Jangle server in Perl on?
Operations of a connector
Don't you first also have to define the concrete operations your ILS must support to wrap them to Jangle? We have a SOAP API that supports all CRUD operations (create, retrieve, update, delete) for a PICA database:
http://www.gbv.de/wikis/cls/CWS#Webcatws - German description
http://cws.gbv.de/ws/webcatws.wsdl - WSDL
http://search.cpan.org/perldoc?PICA::Store - Perl client library
This should be very easy to map to Jangle but I am still somehow confused where to start. Each record in the catalog is identified by an id but there are no actors, collections and such. And is http://search.cpan.org/perldoc?Atompub the right library to build a Jangle server in Perl on?
Greetings,
Jakob