| Note |
|---|
Work in progress |
GitHub is a platform and cloud-based service for software development and version control using Git, allowing developers to store and manage their code and documentation. It provides the distributed version control of Git plus access control, bug tracking, software feature requests, task management, continuous integration, and wikis. It is commonly used to host open source software development projects.
...
Some supplementary repositories are listed and explained below.
...
Registry
The following repositories in GitHub are related to the EWP registry:
EWP Registry API. It contains a specification of the EWP Registry API. The Registry API is implemented by the Registry Service.
EWP Registry Service. It contains the Java implementation of the registry server part. There are two public installations of the EWP registry:
EWP Registry Client. It contains Java implementation of the EWP Registry Service client.
Developers, who implement a client, can use it to discover institutions in the network and APIs implemented by them.
Developers, who implement a server, can use it to verify incoming requests (prove that they come from within the EWP network and prove which institutions the requester covers).
EWP Registry Catalogue. It contains the implementation of the application that enables replicating the EWP registry service on multiple servers.
EWP Registry log. It contains a record of changes made to the Registry’s catalogue in the production network (for logging purposes).
EWP DEV Registry log. It contains a record of changes made to the DEV Registry’s catalogue (for logging purposes).
The Registry Service is described in GitHub. It is the only centralized part of the EWP architecture. It allows all EWP hosts to access the list of other EWP hosts and to list APIs implemented by these hosts, along with the URLs these APIs are implemented at.
The registry is being updated automatically. It periodically reads all the information that all EWP Hosts provide within their Discovery Manifest files, and these changes are instantly reflected in the Registry Service responses.
The major advantage of such automatic updating is that the partners do not need to contact the registry maintainer when they want to change some of their Registry entries. Most changes in the registry can be performed simply by updating the manifest on the partner's server (and the Registry will fetch these changes automatically). This process is both more convenient and more secure than updating the registry manually.
...
Working with EWP technical documentation
https://github.com/erasmus-without-paper/ewp-specs-management/Workibg with EWP Tchnical Documentation
This document explains how to work with the technical documentation within the EWP project (where to store it, how to submit change proposals, etc.).
...
Architecture and common datatypes
https://github.com/erasmus-without-paper/ewp-specs-architecture/ Description of EWP’s Architecture and Security
This document describes EWP vocabulary, network components, common features and data types, and explains basic rules about how partners communicate with each other and handle errors.
...
Authentication and security in the context of the EWP Network is described in the repository https://github.com/erasmus-without-paper/ewp-specs-sec-intro GitHub repository. The security of the communication is split into four security aspects, for which the following methods are available:
...