...
All active GitHub repositories related to EWP are documented on a separate page:
...
...
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
GitHub repositories
In September November 2023 there are 76 repositories in GitHub, 18 of which were archived.
There are 26 public repositories for APIs – their names start with the prefix ewp-specs-api. Typically they follow the same structure and contain (among others) the following elements:
...
Repositories with APIs are listed in a separate section, with a short description of their content.
Some supplementary repositories are listed and explained below.
...
Introduction to EWP Network
Architecture and common datatypes
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
Authentication and security in the context of the EWP Network is described in this GitHub repository. The security of the communication is split into four security aspects, for which the following methods are available:
Client authentication
Handling Anonymous Clients.Authenticating Clients with TLS Certificate.
Server authentication
Request encryption
Response encryption
Each endpoint of each API must support at least one method of covering each of these security aspects. Before making the request, clients verify security protocols supported by the server, and construct their request appropriately.
...
Registry
The following repositories in GitHub are related to the EWP registry:
...
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.
...
Catalogue file
The Registry Service catalogue file endpoint takes no parameters and returns the response at a specified URL. The response format is described in the catalogue.xsd file.
...
EWP Registry Catalogue which enables replicating the EWP registry service on multiple servers pulls the most recent version of the catalogue file from ewp-registry-log-prod and ewp-registry-log-dev, respectively.
...
Github source code
Some EWP-related GitHub repositories contain the source code and binaries.
...
The EWP registry can be installed in a local environment for testing local development installation. There is a package ready for download with embedded README and HOWTO files. The local environment package is named local_configuration.zip.
...
Issues
Each EWP repository has its own, separate issue tracker. If a developer plans to submit a new issue, and the topic of this issue applies to the contents of a single repository only, then it should be submitted in the issue tracker of this repository. There is also one special repository, general-issues, for tracking issues which do not apply to any single project.
...