Barry,
I'm surprised and delighted that someone actually bothered to explore
the Linked Data behind the URL. :-)
The RDF rendition largely dates back to my original Linked Data
implementation, which I did 3-4 years ago. At the time, dbpedia was
seen as a standard way of doing things, and this is reflected in the
approach I adopted. I plan to replace this by a fully CRM-compatible
encoding of the data, but have been waiting on guidance from British
Musem, Collections Trust, etc. as to "best practice". (The data is
native XML anyway, so it's just a matter of switching in a better XSLT
transform.)
Point taken about the content negotiation and un-supported types: I
think it is helpful if those of us who are actually doing Linked Data
"kick the tyres" of each others' systems, to ensure that our efforts
actually work as intended.
Richard
On 28/10/2013 16:49, Barry Norton wrote:
> Richard, a big thumbs up for Linked Data principles.
>
>
>
> Just a caution though that, at the Linked Data level, you're not actually nominating your non-URI IDs as identifiers (only labels).
>
>
>
> Compare below your resource versus one in the British Museum collection (for which there's a new HTML UI and SPARQL enpoint at collection.britishmuseum.org).
>
>
>
> Sorry everyone for the techy stuff below - feel free to skip.
>
>
>
>
>
> Compare:
>
>
> $ curl -sLH "Accept:application/rdf+xml" http://collections.wordsworth.org.uk/Object/WTcoll/id/GRMDC.C104.4 | ./apache-jena-2.11.0/bin/rdfxml | grep '"GRMDC'
>
>
>
> <http://collections.wordsworth.org.uk/Object/WTcoll/id/GRMDC.C104.4> <http://www.w3.org/2000/01/rdf-schema#label> "GRMDC.C104.4" .
>
>
>
> You use a little of the CRM ontology in your descriptions, but might consider also crm:P1_is_identified_by.
>
>
>
> See, for example:
>
>
>
> $ curl -sLH "Accept:text/turtle" http://collection.britishmuseum.org/id/object/EOC3130 | grep 'P1_is_identified_by'
>
>
>
> crm:P1_is_identified_by <http://collection.britishmuseum.org/id/object/EOC3130/codexid> , <http://collection.britishmuseum.org/id/object/EOC3130/regno> ;
>
>
>
> Whereby:
>
>
> $ curl -sLH "Accept:text/turtle" http://collection.britishmuseum.org/id/object/EOC3130/regno
>
>
> <http://collection.britishmuseum.org/id/object/EOC3130/regno> a crm:E42_Identifier ;
> rdfs:label "Oc1869,1005.1" ;
> crm:P2_has_type <http://collection.britishmuseum.org/id/thesauri/identifier/regno> .
>
>
>
> And similar for other types of British Museum IDs.
>
>
>
> (Note also that you don't simply refuse to content-negotiate for Turtle, hence the Jena parsing, but instead go into an infinite redirect loop).
>
>
>
> Barry
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of Richard Light
> Sent: 28 October 2013 15:45
> To: [log in to unmask]
> Subject: Re: [MCG] Collections on-gallery & on-line?
>
>
>
> Mike,
>
>
>
> Linked Data publication of a collection can yield this as a handy by-product. Each object has a unique, persistent identifier, which "dereferences" by default to a web page, e.g.:
>
>
>
> http://collections.wordsworth.org.uk/Object/WTcoll/id/GRMDC.C104.4
>
>
>
> So you can stick that as it stands on an exhibition label, or print it on the label as a QR code and allow the public to grab the page with their phones. No need for Google searches ...
>
>
>
> These LD identifiers will typically be based on the object's accession/identity number, but are a whole lot more useful.
>
>
>
> Richard
>
>
>
> On 28/10/2013 11:45, Mike Ellis wrote:
>
>> Hello
>> I was down at Tate St Ives yesterday and being an interesting kind of person (~cough~) I started looking at - and searching for - accession numbers from the gallery labels using Google.
>> I was wondering if:
>> 1) your institution always / sometimes / never puts accession numbers
>> or unique ID's on-gallery
>> and
>> 2) whether your institution always / sometimes / never makes sure it has online catalogue entries for items that end up being on-gallery.
>> My in-depth research (of about 5 pictures) at the Tate seemed to indicate that everything I looked for was on their online catalogue with the exception of the borrowed items which [obviously] weren't.
>> Anyway - any thoughts / info / anecdotes / research would make most interesting reading to me..
>> thanks!
>> Mike
>> _____________________________
>> Mike Ellis
>> Thirty8 Digital: a small but perfectly formed digital agency:
>> http://thirty8.co.uk
>> * My book: http://heritageweb.co.uk *
>> ****************************************************************
>> website: http://museumscomputergroup.org.uk/
>> Twitter: http://www.twitter.com/ukmcg
>> Facebook: http://www.facebook.com/museumscomputergroup
>> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>> ****************************************************************
>
>
> --
>
> *Richard Light*
>
>
>
> ****************************************************************
>
> website: http://museumscomputergroup.org.uk/
>
> Twitter: http://www.twitter.com/ukmcg
>
> Facebook: http://www.facebook.com/museumscomputergroup
>
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>
> ****************************************************************
>
> ****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
> ****************************************************************
> .
>
--
*Richard Light*
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|