LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  July 2012

CODE4LIB July 2012

Subject:

Re: Worldcat schema.org & search API

From:

Richard Wallis <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 11 Jul 2012 00:02:14 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (246 lines)

On 10 July 2012 23:13, Karen Coyle <[log in to unmask]> wrote:

> On 7/10/12 2:10 PM, Roy Tennant wrote:
>
>> Uh...what? For the given use case you would be much better off simply
>> using the WorldCat Search API response. Using it only to retrieve an
>> identifier and then going and scraping the Linked Data out of a
>> WorldCat.org page is, at best, redundant.
>>
>
> I do not consider using "linked data" to be "scraping" by any meaning of
> that term.


The tools and code libraries that extract the RDF wrapped in RDFa markup in
html are doing just that - scraping it out of the page markup.  However, as
it is embedded in there in a structured form, so that process can be
considered far more reliable than is normally expected a scraping process
that is easily upset by visual changes.

Machine-actionable data is returned in formats like RDF/XML or ttl or JSON.


From the code and tools that interpret the RDFa in the page, yes.


> And I'm curious that linked data is somehow not considered to be usable as
> "data" and that microformat data is not considered to be searchable


Of course it is usable as data - I think what Roy was getting at is that
you could have satisfied your use case with tools that were available
before the embedding of linked data in to WorldCat detail pages.


> -- in fact, its raison d'etre is search optimization.


Yes one of the reasons for embedding structured data and identifiers, as
well as text [as Google puts it 'things not strings'] is SEO.   I'm sure
that the search engines are already using it for that now.

However, SEO is not the only reason for linked data - [as a linked data
enthusiast] I would suggest that better SEO is a nice side benefit of
something much more powerful.  <evangelism>off</evangelism>


>
>
>> As Richard pointed out, some use cases -- like the one Karen provided
>> -- are not really a good use case for linked data. It's a better use
>> case for an API, which has been available for years.
>>
>
> But is it available to everyone, and is the data retrieved also usable as
> ODC-BY by any member of the Web public?


Yes it is, and at this stage it is only available from within a html page.

This experiment is the first step in a process to make linked data about
WorldCat resources available.  As it will evolve over time other areas such
as API access, content-negotiation, search & other query methods,
additional RDF data vocabularies, etc., etc., will be considered in concert
with community feedback (such as this thread) as to the way forward.

Karen I know you are eager to work with and demonstrate the benefits of
this way of publishing data.  But these things take time and effort, so
please be a little patient, and keep firing off these use cases and issues
they are all valuable input.

~Richard.

>
>
> kc
>
>
>  Roy
>>
>> On Tue, Jul 10, 2012 at 2:08 PM, Kevin Ford <[log in to unmask]> wrote:
>>
>>> The use case clarifies perfectly.
>>>
>>> Totally feasible.  Well, I should say "totally feasible" with the caveat
>>> that I've never used the Worldcat Search API.  Not letting that stop me,
>>> so
>>> long as it is what I imagine it is, then a developer should be able to
>>> perform a search, retrieve the response, and, by integrating one of the
>>> tools advertised on the schema.org website into his/her code, then
>>> retrieve
>>> the microdata for each resource returned from the search (and save it as
>>> RDF
>>> or whatever).
>>>
>>> If someone has created something like this, do speak up.
>>>
>>> Yours,
>>>
>>> Kevin
>>>
>>>
>>>
>>>
>>>
>>> On 07/10/2012 04:48 PM, Karen Coyle wrote:
>>>
>>>> Kevin, if you misunderstand then I undoubtedly haven't been clear (let's
>>>> at least share the confusion :-)). Here's the use case:
>>>>
>>>> PersonA wants to create a comprehensive bibliography of works by
>>>> AuthorB. The goal is to do a search on AuthorB in WorldCat and extract
>>>> the RDFa data from those pages in order to populate the bibliography.
>>>>
>>>> Apart from all of the issues of getting a perfect match on authors and
>>>> of manifestation duplicates (there would need to be editing of the
>>>> results after retrieval at the user's end), how feasible is this? Assume
>>>> that the author is prolific enough that one wouldn't want to look up all
>>>> of the records by hand.
>>>>
>>>> kc
>>>>
>>>> On 7/10/12 1:43 PM, Kevin Ford wrote:
>>>>
>>>>> As for someone who might want to do this programmatically, he/she
>>>>> should take a look at the "Programming languages" section of the
>>>>> second link I sent along:
>>>>>
>>>>> http://schema.rdfs.org/tools.**html<http://schema.rdfs.org/tools.html>
>>>>>
>>>>> There one can find Ruby, Python, and Java extractors and parsers
>>>>> capable of outputting RDF.  A developer can take one of these and
>>>>> programmatically get at the data.
>>>>>
>>>>> Apologies if I am misunderstanding your intent.
>>>>>
>>>>> Yours,
>>>>>
>>>>> Kevin
>>>>>
>>>>>
>>>>>
>>>>> On 07/10/2012 04:34 PM, Karen Coyle wrote:
>>>>>
>>>>>> Thanks, Kevin! And Richard!
>>>>>>
>>>>>> I'm thinking we need a good web site with links to tools. I had
>>>>>> already
>>>>>> been introduced to
>>>>>>
>>>>>> http://www.w3.org/2012/pyRdfa/
>>>>>>
>>>>>> where you can past a URI and get ttl or rdf/xml. These are all good
>>>>>> resources. But what about someone who wants to do this
>>>>>> programmatically,
>>>>>> not through a web site? Richard's message indicates that this isn't
>>>>>> yet
>>>>>> available, so perhaps we should be gathering use cases to support the
>>>>>> need? And have a place to post various solutions, even ones that are
>>>>>> not
>>>>>> OCLC-specific? (Because I am hoping that the use of microformats will
>>>>>> increase in general.)
>>>>>>
>>>>>> kc
>>>>>>
>>>>>>
>>>>>> On 7/10/12 12:12 PM, Kevin Ford wrote:
>>>>>>
>>>>>>> is there an open search to get one to the desired records in the
>>>>>>>>
>>>>>>> first
>>>>>>>
>>>>>>>> place?
>>>>>>>>
>>>>>>> -- I'm not certain this will fully address your question, but try
>>>>>>> these two sites:
>>>>>>>
>>>>>>> Website: http://www.google.com/**webmasters/tools/richsnippets<http://www.google.com/webmasters/tools/richsnippets>
>>>>>>> Example: http://tinyurl.com/dx3h5bg
>>>>>>>
>>>>>>> Website: http://linter.structured-data.**org/<http://linter.structured-data.org/>
>>>>>>> Example: http://tinyurl.com/bmm8bbc
>>>>>>>
>>>>>>> These sites will extract the data, but I don't think you get your
>>>>>>> choice of serialization.  The data are extracted and displayed on the
>>>>>>> resulting page in the HTML, but at least you can *see* the data.
>>>>>>>
>>>>>>> Additionally, there are a number of "tools" to help with microdata
>>>>>>> extraction here:
>>>>>>>
>>>>>>> http://schema.rdfs.org/tools.**html<http://schema.rdfs.org/tools.html>
>>>>>>>
>>>>>>> Some of these will allow you to output specific (RDF) serializations.
>>>>>>>
>>>>>>>
>>>>>>> HTH,
>>>>>>>
>>>>>>> Kevin
>>>>>>>
>>>>>>>
>>>>>>> On 07/10/2012 02:42 PM, Karen Coyle wrote:
>>>>>>>
>>>>>>>> I have demonstrated the schema.org/RDFa microdata in the WC
>>>>>>>> database to
>>>>>>>> various folks and the question always is: how do I get access to
>>>>>>>> this?
>>>>>>>> (The only source I have is the Facebook API, me being a "user"
>>>>>>>> rather
>>>>>>>> than a "maker".) The microdata is CC-BY once you get a Worldcat
>>>>>>>> URI, but
>>>>>>>> is there an open search to get one to the desired records in the
>>>>>>>> first
>>>>>>>> place? I'm poorly-versed in WC APIs so I'm hoping others have a
>>>>>>>> better
>>>>>>>> grasp.
>>>>>>>>
>>>>>>>> @rjw: the OCLC website does a thorough job of hiding email
>>>>>>>> addresses or
>>>>>>>> I would have asked this directly. Then again, a discussion here
>>>>>>>> could
>>>>>>>> have added value.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> kc
>>>>>>>>
>>>>>>>>
> --
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet
>



-- 
Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Tel: +44 (0)7767 886 005

Linkedin: http://www.linkedin.com/in/richardwallis
Skype: richard.wallis1
Twitter: @rjw
IM: [log in to unmask]

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

November 2024
October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager