LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


ZNG@C4VLPLISTSERV01.LOC.GOV


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

ZNG Home

ZNG Home

ZNG  February 2014

ZNG February 2014

Subject:

Re: SRU recordPacking and JSON

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Wed, 19 Feb 2014 17:23:15 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (66 lines)

Makes sense to me!

On 2/19/14 5:02 PM, LeVan,Ralph wrote:
> You are absolutely correct.  The correct negotiation request would be: application/ld+json, application/json;q=0.9
>
> That says, I want JSONLD, but will accept any JSON.  I *don't* get to just pick another JSON format if they asked only for ld+json.  But, given the recordAccept (yes, I just coined that name now) parameter above, I *would* be allowed to return application/vnd.oclc.viaf+json if I wasn't able to return application/ld+json.
>
> Ralph
>
> -----Original Message-----
> From: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]] On Behalf Of Jonathan Rochkind
> Sent: Wednesday, February 19, 2014 4:44 PM
> To: [log in to unmask]
> Subject: Re: SRU recordPacking and JSON
>
> I'm wondering whether it actually makes sense at all to content negotiate to a different JSON-based format then the one you think they are asking for?
>
> Does someone have a use case where software asking for one JSON-based format, but which gets a different JSON-based format instead, is still going to be able to do something useful with it? It's not something I've encountered myself.
>
> Even for "+xml" content types (which actually are standardized -- every content type ending in "+xml" must, by standard, be an XML type; the same is not true of "+json") -- I don't _think_ conneg usually works such that a client asking for only "something+xml" is given "other+xml"
> instead -- rather than an error message saying "something+xml" can not be provided.
>
>
> On 2/19/14 4:13 PM, LeVan,Ralph wrote:
>>>   Sure, it's just as sensible, the concept is good. But how you go
>>> about
>> doing content
>>
>>> negotiation at the record level?  Can you give an example.
>>
>> http://rdap02pxdu.dev.oclc.org:8080/viaf/search?query=local.names+all+
>> %22ralph%20levan%22&httpAccept=application/json
>>
>> Here's a generic request for an SRU response in JSON.  It doesn't say
>> anything about how the records should be returned, but certainly
>> implies that they should be in JSON too.  (Sadly, it gets an XML
>> record now, because I'm not doing record content negotiation yet.)
>> Right now, I have two different JSON schemas: vnd.oclc.viaf+json
>> (that's my VIAF XML record run through a lovely mechanical XML->JSON
>> translator) and ld+json (that's a hand-built implementation of the
>> current Linked Data in JSON proposal).  I'd propose specifying them
>> using recordSchema (that being the closest match we have.)
>>
>> http://rdap02pxdu.dev.oclc.org:8080/viaf/search?query=local.names+all+
>> %22ralph%20levan%22&httpAccept=application/json&recordSchema=applicati
>> on/ld%2Bjson(Sadly, that URL gets you a nice SRU diagnostic returned
>> as JSON, because that recordSchema isn't recognized yet.  I'm really
>> hoping for some feedback on the idea before I implement record content
>> negotiation.)
>>
>> Now, if they asked for application/bob+json, then we fall into regular
>> HTTP negotiation and I'd return what I thought was my best JSON and
>> I'd tell them they were getting application/vnd.oclc.viaf+json in the
>> recordSchema element (or whatever they get called in JSON) of the
>> record response.
>>
>> Ralph
>>
>> p.s. Here's the hack I'm using right now to get that VIAF record in
>> JSON.  Like I said, I'm looking for a cleaner way to do this that
>> doesn't make you all gag. J
>>
>> http://rdap02pxdu.dev.oclc.org:8080/viaf/search?query=local.names+all+
>> %22ralph%20levan%22&recordPacking=string&recordSchema=JSON&httpAccept=application/json
>>

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

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 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
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
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager