Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add an example showing how availability of a Book at a Library is modelled #733
@dbs :) I've just talked Eric Miller through installing AppEngine on his laptop, but if you can take a lead here that would be great.
AFAIK "seller" is still the best practice for relating the Offer to the Library, rather than say "provider". Nobody has shouted about this being terrible but I'm open to trying to find less $-oriented language if it is proving an obstacle.
Let's work out some ideal examples here in the issue tracker to make sure they're capturing the use cases everyone cares about, rather than getting distracted by redesigning vocab.
So let's start with a simplified example of the offer made of a DVD from the Music Resource Centre (MRC), which is part of the Laurentian University system. This is based on https://laurentian.concat.ca/eg/opac/record/2845929:
So we're mapping the shelving location to
Note that we include a little inline description of the library (it's name) in case the agents won't follow their nose and retrieve the data at the assigned URL. If they do resolve that, however, there they will find:
Well, okay, you would actually get the deprecated
I suppose one could model the same sort of relationships using
How is that for a start--relatively clear so far?
referenced this issue
Sep 11, 2015
So something like:
added a commit
Oct 2, 2015
One example still needed converting to JSON-LD from Turtle. I tried it automatically but result is ugly: