...

http://www.example.com/x-oaixoai/<context>

Contexts could be seen as virtual distinct OAI interfaces, so with this one could have things like:

• http://www.example.com/x-oaixoai/driver
• http://www.example.com/x-oaixoai/openaire
• http://www.example.com/x-oaixoai/request
  With this ingredients it is possible to built a robust solution that fulfill all requirements in Driver, OpenAIRE and also other projects specific requirements. As shown in Figure 1, with contexts one could select a subset of all available items in the data source. So when entering the OpenAIRE context, all OAI-PMH request will be restricted to that subset of items.

...

At this stage, contexts could be seen as sets (also defined in the basic OAI-PMH protocol). The magic of X-OAI XOAI happens when one need specific metadata format to be shown in each context. Metadata requirements by Driver slightly differs from the OpenAIRE ones. So for each context one must define it's specific transformer. So, contexts could be seen as an extension to the concept of sets.

...