Service oriented architecture for e-portfolio systems and services

The objective in this section is to set out plausible principles, and outline plausible architecture to fullfil them. Closely linked to section on main functionality.

Need: to be able to fully exploit the contents of my ePortfolio, using a multiplicity of services, e.g., cross-reference the contents of my ePortfolio with standards of competence hosted by an industry sector governing body in order to present a file for accreditation of prior work experience; search or apply for a job - this also requires of standardized data format, as well has protocols across applications, such as those defined by the Open Knowledge Initiative (OKI).

Strategy points:

An architectural approach that

• allows interface from multiple services
• allows interface with multiple repositories
• combination of peer to peer networks and client-server technologies to interact with various institutions and organizations.
• define web services that support the required (human) services.
• support federation of services and user privacy.

See the WS4RL project discussion document, outlining the PIADS architecture for reference.

• Are there any services, or repositories, that will require special treatment, and be impossible to integrate into this architecture? (See Functionality section)
• If there are, how will they be dealt with?
• What is a good development strategy for the web services and associated standards?

Another international and industrial reference is the Liberty Alliance set of specifications including the Identity Federation Framework (ID-FF), the secure Identity Web Services Framework (ID-WSF) and its collection of Identity Services Interface Specifications (ID-SIS) like People Service, Personal or Employee profiles, contact book...

For eGovernment point of view, here is the Liberty Alliance's Whitepaper: Benefits of Federated Identity to Government