Re: [search-ws] sru:recordPacking = unpacked ?

["Hammond, Tony" <t.hammond@nature.com>]

Hi Ralph:

Maybe I should wait until next week before responding properly (by which
time I would hope to have a working implementation - which would be easier
all round to see).

My requirement is to send back a complete SRU response in RSS (and ATOM and
...). And I can do that. To my satisfaction at least (given that there are
no templates for this).

My problem is with SRU. It's fine to have the search response locked down by
an XSD schema so that one can validate it out. But many applications do not
require XSD validation and incline towards open data models with
easy-to-get-at data. More trusting or more carefree - whatever. But easier
to use certainly. I would also like to make my data easier to access, *while
retaining fidelity to a complete SRU response*.

I want to have my cake and eat it too. And I really don't see why not. If
record data is "packed", then that implies that it can be "unpacked". I
merely want to record that fact. The data was here, now it's gone. But I'm
still a conformant SRU response by the way.

And the reason for wanting to maintain an SRU response is purely pragmatic.
It allows me to express a number of response elements in a standard way,
e.g. diagnostics, resultSetId, etc. (I haven't inventoried that list.) If I
don't use SRU response elements then I have to set about making up my own
set.

Why does it got to be so hard to do useful things in a standard fashion? Am
only asking for a marker to say the data has been processed and is no longer
here.

Tony



On 21/8/09 13:43, "LeVan,Ralph" <levan@oclc.org> wrote:

>> -----Original Message-----
>> From: Hammond, Tony [mailto:t.hammond@nature.com]
>> 
>> What I am proposing to implement in my service is to return unpacked
> records
>> for OpenSearch style responses (e.g. RSS, ATOM, JSON). I am hoping to
> have
>> this implemented next week so that I can show what this would look
> like on a
>> live implementation.
> 
> I'm still not getting it.
> 
> If that is the RSS that you want to return, then just return that.  Why
> do you need changes in SRU?  There is nothing in SRU that makes
> returning that particular RSS response difficult.
> 
> Maybe we can start over here.
> 
> Would you share with us what your requirement is, rather than what your
> proposed solution is?
> 
> My sense is that you want to support clients that send in SRU queries
> and get back RSS/Atom responses.  I think we can do that already.  I'm
> certainly doing that now.  If that isn't what you want to do, please
> help me understand.
> 
> Thanks!
> 
> Ralph
> 


********************************************************************************   
DISCLAIMER: This e-mail is confidential and should not be used by anyone who is
not the original intended recipient. If you have received this e-mail in error
please inform the sender and delete it from your mailbox or any other storage
mechanism. Neither Macmillan Publishers Limited nor any of its agents accept
liability for any statements made which are clearly the sender's own and not
expressly made on behalf of Macmillan Publishers Limited or one of its agents.
Please note that neither Macmillan Publishers Limited nor any of its agents
accept any responsibility for viruses that may be contained in this e-mail or
its attachments and it is your responsibility to scan the e-mail and 
attachments (if any). No contracts may be concluded on behalf of Macmillan 
Publishers Limited or its agents by means of e-mail communication. Macmillan 
Publishers Limited Registered in England and Wales with registered number 785998 
Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS   
********************************************************************************