-
Notifications
You must be signed in to change notification settings - Fork 2
Open issues
This page is for describing technical issues related with governance and management context.
Please refer the description of the problem This may include the format of coverage area.
Minimal requirements for registration of MSR can be listed as below (from the easiest to the hardest):
- owning a valid MRN
- having an operational end-point, i.e., url, like https://maritimeconnectivity.net
- owning a valid MCP identity
- being vetted as a service provider by relevant authorities (national or public domain services)
- having a valid G1128 instance description XML and a word file
- having a instance description based on valid link to G1128 technical design and service specification
- having a reference to a valid G1128 technical design and service specification
A proper procedure for registration of service to the distributed ledger must be defined and guided by MCC and relevant interest group. Here our problem formulation covers more technical issues of its implementation such as:
- how the criteria and progress can be represented for an instance?
- which role/permission of MSR can be defined for a request of the registration?
- which role/permission of MSR can be defined for an approval of the request?
The issue covers a complete stream of service registration process with relevant actors, such as service provider, MSR operator, and other parties, including how the process is initiated by whom.
It is now able to update the service status by the service provider themselves. This may lead to an inappropriate case where the service provider keeping their service as released even though the service got deprecated by a MSR administrator for a good reason.
Similar use case of the role/permission can be observed from MIR. The degree of freedom in the level of roles shall be flexible, leaving several roles as fixed for those are essential for running a MSR.
We need to be convinced by having a demonstration of running a simple repository.
Copyright (c) 2021 Maritime Connectivity Platform Consortium