Middleware as a term is applied in different ways by different organisations. JISC uses the term middleware to describe the process of:
'helping institutions to connect people to resources'
Middleware can be implemented at all levels and is not a single piece of software or single service that resides visibly on an end-user’s desktop. Technically, it can be viewed as a layer of software or 'glue' between the network and applications. Middleware can be shared by many applications serving various purposes in different environments. This might include:
-
Institutional Tools (for example peer-to-peer applications) interacting with:
-
National Services (for example Athens and the JISC Shared Services) which may in turn participate in:
-
International Efforts (for example the Shibboleth initiative).
To enable people to access resources many issues need to be addressed. JISC development work deals specifically with the different parts engaging in this process.
People are not isolated. They are affiliated to many different groups, institutions and collaborations, and work within the existing structures put in place by these affiliations. This will include existing institutional middleware that supports the day-to-day management of internal collaboration. JISC development work supports existing practises whilst enabling people to work beyond institutional boundaries, drawing on a much wider range of relevant and essential resources.
Current JISC development is focussed on Core Middleware. Core Middleware is defined as the central services that are essential to middleware as a whole. These are: authentication, authorisation, directory services, and identifiers.
For more information about JISC middleware activities, please contact Nicole Harris.