On 3 March 2010 16:52, Andy Powell <[log in to unmask]> wrote:
> Linked Data (capital L capital D) is as defined at
> http://www.w3.org/DesignIssues/LinkedData.html and I'm not sure it is
> helpful to try and define it differently for the museum community?
Definitely not! But I've had the feeling that the phrase currently means
different things to different people, and I wanted to come to a shared
understanding of what it means.
Having a shared definition means we can move onto the next question -
'what's the minimum I'd need to do to publish linked data?'.
Frankie's differentiation of 'heavy' and 'light' linked data might be useful
here - it's relatively easy for us to publish in RDF, but I wouldn't know
where to start providing a SPARQL end point.
The 'semantically interoperable' question depends on answers to questions
about suitable vocabularies and/or ontologies. I know the kinds of questions
I want to ask about this, but not quite how to ask them at this point.
> So I think your question is really something like, "do we want to do Linked
> Data in the museums sector or do we want to do something else, let's call it
> 'open data' or 'machine-readable data' (as used by Mike Ellis at
> http://www.slideshare.net/dmje/dont-think-websites-think-data)?".
>
That's a slightly different question, but it's definitely a good one.
I'm wary of conflating 'open data' and 'linked data', though I suspect in
most cases our data could be both linked and open.
> APIs and linked data can definitely work together, at least in the sense
> that SPARQL is an API and Linked Data is an architectural approach - both
> are compatible. However, I suspect that you mean non-RDF-based APIs here?
No - I just wanted to leave room to bring in the traditional MCG obsession
with APIs :)
cheers, Mia
****************************************************************
For mcg information visit the mcg website at
http://museumscomputergroup.org.uk/
To manage your subscription to this email list visit
http://museumscomputergroup.org.uk/email-list/
****************************************************************
|