In message
<[log in to unmask]
uk>, "REYNOLDS, Trevor" <[log in to unmask]> writes
>OK Richard
>
>So in this senario if I'm looking at an item in the uniquely referenced
>source data how do I know whether or not Frankie (or anyone else) has
>put other data referencing the source data somewhere else on the web?
Good question, and one that needs answering if we are to move beyond the
current rather un-linked-data approach of "everything is in my silo".
Initiatives such as VoiD [1] are designed to help with the
discoverability issue.
I suspect that before too long something like Google (possibly something
_very_ like Google, given their recent interest in this area e.g.
acquisition of Freebase) will start "crawling" Linked Data resources and
creating centralized indexes. This will allow us all to breathe a sigh
of relief, and get on with searching Linked Data in exactly the way we
currently search web pages, i.e. at a single point of access. (Of
course, we'll be able to ask much more specific and interesting
questions, but that's a separate issue.)
Richard
[1] http://semanticweb.org/wiki/VoiD
>
>-----Original Message-----
>From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of
>Richard Light
>Sent: 11 March 2011 14:39
>To: REYNOLDS, Trevor
>Subject: Re: Science Museum, National Media Museum, National Railway
>Museum object records released
>
>In message
><[log in to unmask]>,
>James Morley <[log in to unmask]> writes
>>Absolutely.
>>
>>Which then also begs the question of when people do great stuff like
>>Frankie did (and of course not forgetting that it's also the users of
>>these tools/sites who are contributing), how do you feed that content
>>back into the process and hence eventually, as appropriate, back into
>>the source data, thereby capturing any enhancements?
>
>This is where "quick and dirty" gets to argue with "do it proper" ;-)
>
>If the source data were published as Linked Data, so that each object
>had a unique dereferenceable URL, then Frankie could simply publish his
>enhanced or additional data quoting these identifiers. This could be an
>RDF dump, custom XML, or even some more CSV. Either way, the object
>identifiers would act as uber-keys which attached each item of new data
>unambiguously to its intended object.
>
>Then, it doesn't really matter whether this "update resource" simply
>sits separately on the Web, or is picked up by NMSI and actively merged
>back into the source file.
>
>Richard
>
>>----------------------------------------------------------------------
>>James Morley [log in to unmask]
>>Website Manager Tel. +44 (0)20 8332 5759
>>Royal Botanic Gardens, Kew www.kew.org
>>-----------------------------------------------------------------------
>>________________________________________
>>From: Museums Computer Group [[log in to unmask]] On Behalf Of Mia
>>[[log in to unmask]]
>>Sent: 11 March 2011 13:38
>>To: [log in to unmask]
>>Subject: Re: Science Museum, National Media Museum, National Railway
>>Museum object records released
>>
>>On 11 March 2011 10:03, Frankie Roberto <[log in to unmask]> wrote:
>>
>>> large, fairly static databases like object
>>> records, complete data dumps are probably more useful for developers than an
>>> object-level API, at least initially.
>>
>>I should point out that 'static' is very relative - the documentations
>>team (who are completely brilliant and are really the ones responsible
>>for the success of this data release) made 50,000 improvements in
>>2010, though of course there's a lot of on-going auditing and cleaning
>>left to do.
>>
>>Cheers, Mia
>>
>>****************************************************************
>> 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/
>>****************************************************************
>>
>>
>>-----
>>No virus found in this message.
>>Checked by AVG - www.avg.com
>>Version: 10.0.1204 / Virus Database: 1497/3499 - Release Date: 03/10/11
>>
>>
>
>--
>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/
>****************************************************************
>
>Visit the new English Heritage website:
>http://www.english-heritage.org.uk . The site has a new, dedicated
>section for heritage professionals:
>http://www.english-heritage.org.uk/professional together with
>information on days out http://www.english-heritage.org.uk/daysout,
>heritage news http://www.english-heritage.org.uk/about/news, looking
>after listed properties
>http://www.english-heritage.org.uk/your-property and the latest
>information on heritage protection:
>http://www.english-heritage.org.uk/caring/listing.
>
>****************************************************************
> 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/
>****************************************************************
>
>
>-----
>No virus found in this message.
>Checked by AVG - www.avg.com
>Version: 10.0.1204 / Virus Database: 1497/3499 - Release Date: 03/10/11
>
>
--
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/
****************************************************************
|