OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

search-ws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [search-ws] RE: content-type for Zeerex/Explain


All Atom data is passed with the media type of application/atom+xml.  I
don't see a problem with us following the same pattern.  It's not like
we're trying to use the media type to distinguish between SRU
operations.

Ralph

> -----Original Message-----
> From: Ray Denenberg [mailto:raydenenberg@starpower.net]
> Sent: Monday, June 28, 2010 5:44 PM
> To: 'OASIS SWS TC'
> Subject: [search-ws] RE: content-type for Zeerex/Explain
> 
> I wish to follow up on this discussion.
> 
> Do we really want to piggyback on the content type
'application/sru+xml'?
> Yes, it will work, but is it an awful cludge or an  acceptable
approach?
> 
> The argument that an Explain file is, after all, an SRU response,
seems a
> bit tortured. I'm not convinced it's a bad approach, just not
convinced it's
> right.   It avoids reqistering another content type, a huge pain, to
be
> sure, but
> one thing that bothers me about this, it isn't as easy as it seems, if
we
> extend the defintion of application/sru+xml to apply to Explain, then
we are
> going to have to extend the SRU response schema to include Explain,
aren't
> we?
> 
> 
> --Ray
> 
> 
> 
> -----Original Message-----
> From: SRU (Search and Retrieve Via URL) Implementors
[mailto:ZNG@loc.gov]
> On
> Behalf Of Adam Dickmeiss
> Sent: Tuesday, June 15, 2010 11:05 AM
> To: ZNG@LISTSERV.LOC.GOV
> Subject: Re: content-type for Zeerex/Explain
> 
> On 2010-06-15 16:38, LeVan,Ralph wrote:
> > application/xml is probably fine as the content type in a response.
> > But, if I want to provide a pointer to a server and indicate a mime
> > type in the link, something richer than application/xml would be
> desirable.
> >
> OK. Thanks for clarifying.
> 
> / Adam
> > Ralph
> >
> >
> >> -----Original Message-----
> >> From: Adam Dickmeiss [mailto:adam@indexdata.dk]
> >> Sent: Tuesday, June 15, 2010 10:16 AM
> >> To: SRU (Search and Retrieve Via URL) Implementors
> >> Cc: LeVan,Ralph
> >> Subject: Re: content-type for Zeerex/Explain
> >>
> >> On 2010-06-14 22:52, LeVan,Ralph wrote:
> >>
> >>> We just discussed that during our Oasis phone call this morning.
> >>>
> > We've
> >
> >>> applied to IANA for application/sru+xml.  Since an Explain record
is
> >>> what you get when you send a request to an SRU server with no
> >>> parameters, we figure that the application/sru+xml covers the
> >>>
> > Explain
> >
> >>> response as well as the searchRetrieveResponse.
> >>>
> >>>
> >>>
> >> Please remind me why application/xml is not good enough. I mean,
SRU
> >>
> > is
> >
> >> an XML application, no? And do SOAP tools allow you to customize
this?
> >>
> >>> Ralph
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: SRU (Search and Retrieve Via URL) Implementors
> >>>>
> >>>>
> >>> [mailto:ZNG@loc.gov]
> >>>
> >>>
> >>>> On Behalf Of Jonathan Rochkind
> >>>> Sent: Monday, June 14, 2010 4:48 PM
> >>>> To: ZNG@LISTSERV.LOC.GOV
> >>>> Subject: content-type for Zeerex/Explain
> >>>>
> >>>> Is there a MIME/IANA Content Type for an SRU/ZeeRex Explain
> >>>>
> > document?
> >
> >>>> There doesn't seem to be one registered, is there one
conventional?
> >>>>
> >>>> Or just use application/xml?
> >>>>
> >>>> I am not sure what SRU itself does, but what I'm doing is just
> >>>>
> >>>>
> >>> returning
> >>>
> >>>
> >>>> a raw Explain XML document, in some cases. My app is not actually
> >>>>
> > SRU,
> >
> >>>> but is using some parts of it.
> >>>>
> >>>> Jonathan
> >>>>
> >>>>
> >>>
> >>
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]