But, unfortunately, so far, Re-sourceSync has not enjoyed wide adoption despite itspower and simplicity. Possible explanations includecompetition with its significantly less powerful and 15year old predecessor OAI-PMH, an overall tendency byportals to resort to rolling their own bespoke APIs, and alack of concrete action regarding interoperability despitea general sentiment that more is needed.