I'm puzzled about why you want to use linked data for this. At first glance
the requirement simply seems to be to fetch data from your ILS server,
which likely could be sent in any number of simple packages that don't
require an RDF wrapper. If you are the only one consuming this data then
you can use whatever (simplistic, proprietary) format you want. I just
don't see what benefits you would get by creating "linked data" in this
case that you wouldn't get by doing something much more straightforward and
simple. And don't be harshing on duct tape. Duct tape is a perfectly fine
solution for many problems.
On Wed, Aug 6, 2014 at 2:45 PM, Michael Beccaria <[log in to unmask]>
> I have recently had the opportunity to create a new library web page and
> host it on my own servers. One of the elements of the new page that I want
> to improve upon is providing live or near live information on technology
> availability (10 of 12 laptops available, etc.). That data resides on my
> ILS server and I thought it might be a good time to upgrade the bubble gum
> and duct tape solution I now have to creating a real linked data service
> that would provide that availability information to the web server.
> The problem is there is a lot of overly complex and complicated
> information out there onlinked data and RDF and the semantic web etc. and
> I'm looking for a simple guide to creating a very simple linked data
> service with php or python or whatever. Does such a resource exist? Any
> advice on where to start?
> Mike Beccaria
> Systems Librarian
> Head of Digital Initiative
> Paul Smith's College
> [log in to unmask]
> Become a friend of Paul Smith's Library on Facebook today!