I agree with Rob, it's just one more response schema. BTW, if this idea goes ahead, we could make it better including geoRSS (georss.org), because it's good for locating the information. Then, we can integrate easily with Google Maps/Earth and OpenGIS tools.

Best Regards,

Rondon


> > I disagree.  We can't make it a standard parameter, but we absolutely
> > can make it an extension.  If not a formal extension from the SRU
> > namespace, then a broadly adopted extension from my namespace.
> 
> There isn't an SRU namespace for extensions, 1 is Library of Congress, 2 
> is me, etc.
> </unnecessarily-pedantic>
> 
> > If there is some quibbling about whether SRU servers can return non-SRU
> > response, then I'm fine with declaring them to be not-SRU servers while
> > making that response.
> 
> I'm happy with that too, because there's nothing we could do to 
> prevent it.  Better to say here is how you officially unofficially 
> support RSS as a response schema, if that is an important thing to be 
> able to do, than to simply ignore it.
> 
> Considering OpenSearch and the number of RSS aware applications, I think 
> it's an important thing to be able to do.
> 
> Rob
>