[OAI-implementers] same xml namespace declaration in headerandpayload

Young,Jeff (OR) jyoung at oclc.org
Fri Sep 23 12:56:33 EDT 2011


I would argue that OAI-PMH is to blame here for forcing OAI wrappers on consumers who only care about the data. I think it would be healthy to have a conversation about how OAI-PMH could be improved after all these years.

Jeff

> -----Original Message-----
> From: oai-implementers-bounces at openarchives.org [mailto:oai-
> implementers-bounces at openarchives.org] On Behalf Of Kevin S. Clarke
> Sent: Friday, September 23, 2011 12:49 PM
> To: oai-implementers at openarchives.org
> Subject: Re: [OAI-implementers] same xml namespace declaration in
> headerandpayload
> 
> >> Considering that it is impossible to rid the world of naive
> > harvesters,
> >> the question is how an OAI provider should deal with this. Should it
> >> leave
> >> two namespace declarations in the response?
> 
> Not to be obnoxious, but isn't this problem of the naive harvester
> rather than the OAI provider?  The provider is doing the Right
> Thing(TM).  If someone is using a naive (i.e. broken) harvester
> shouldn't they be the one to work around the problems this causes?
> 
> Kevin
> 
> _______________________________________________
> OAI-implementers mailing list
> List information, archives, preferences and to unsubscribe:
> http://www.openarchives.org/mailman/listinfo/oai-implementers
> 



More information about the OAI-implementers mailing list