-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.html
455 lines (394 loc) · 26 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="MCP, Maritime Connectivity Platform">
<meta name="keywords" content="MaritimeConnectivityPlatform,connectivity,platform,MCP,Maritime,Cloud,MaritimeCloud,identity,services,efficiensea,efficiensea2,stm,smart,navigation,communication,framework">
<meta name="author" content="Maritime Connectivity platform Consortium - MCC">
<link rel="icon" href="favicon.ico" type="image/x-icon">
<title>Maritime Connectivity Platform</title>
<!-- Bootstrap Core CSS -->
<link href="css/bootstrap.min.css" rel="stylesheet">
<!-- Custom CSS -->
<link href="css/landing-page.css" rel="stylesheet">
<!-- Custom Fonts -->
<link href="font-awesome/css/font-awesome.min.css" rel="stylesheet" type="text/css">
<link href="https://fonts.googleapis.com/css?family=Lato:300,400,700,300italic,400italic,700italic" rel="stylesheet" type="text/css">
<!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
<script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script>
<![endif]-->
</head>
<body>
<!-- Navigation -->
<nav class="navbar navbar-default navbar-fixed-top topnav" role="navigation">
<div class="container topnav">
<!-- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand topnav" href="#">Top</a>
</div>
<!-- Collect the nav links, forms, and other content for toggling -->
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav navbar-right">
<li>
<a href="#what">What</a>
</li>
<li>
<a href="#core">Core</a>
</li>
<li>
<a href="#governance">Governance</a>
</li>
<li>
<a href="#tech">Technical</a>
</li>
<li>
<a href="#instances">Instances</a>
</li>
<li>
<a href="#contact">Contact</a>
</li>
<!--<li>
<a href="#signup">Sign up</a>
</li>-->
</ul>
</div>
<!-- /.navbar-collapse -->
</div>
<!-- /.container -->
</nav>
<!-- Header -->
<a name="about"></a>
<div class="intro-header">
<div class="container">
<div class="row">
<div class="col-lg-12">
<div class="intro-message">
<h1>Maritime Connectivity Platform</h1>
<h3>Welcome to the webpage of the Maritime Connectivity Platform (MCP) and the MCP consortium (MCC). On this site you will find all relevant information about the MCP, including official documents defining the MCP and all procedures relating to the MCP and the MCC.</h3>
<hr class="intro-divider">
<!--<ul class="list-inline intro-social-buttons">
<li>
<a href="https://twitter.com/SBootstrap" class="btn btn-default btn-lg"><i class="fa fa-twitter fa-fw"></i> <span class="network-name">Twitter</span></a>
</li>
<li>
<a href="https://github.com/IronSummitMedia/startbootstrap" class="btn btn-default btn-lg"><i class="fa fa-github fa-fw"></i> <span class="network-name">Github</span></a>
</li>
<li>
<a href="#" class="btn btn-default btn-lg"><i class="fa fa-linkedin fa-fw"></i> <span class="network-name">Linkedin</span></a>
</li>
</ul>-->
</div>
</div>
</div>
</div>
<!-- /.container -->
</div>
<!-- /.intro-header -->
<!-- Page Content -->
<a name="what"></a>
<div class="content-section-a">
<div class="container">
<div class="row">
<div class="col-lg-5 col-sm-6">
<hr class="section-heading-spacer">
<div class="clearfix"></div>
<h2 class="section-heading"><a name="new_released_documents">News June 2021</a></h2>
<p class="lead">At the 4th General Assembly of the MCP Consortium held in June 2021, documents defining the criteria for being an MCP identity service provider were adopted. This is a very big milestone for the consortium, and the next step will be to officially endorse organisations to be such. The first organisation expected to be endorsed is the <a href="http://www.navelink.org" target="_blank">Navelink Consortium</a>. </p>
<p class="lead">The MCP Consortium is now focusing on making similar definitions for being service providers of MSR (Maritime Service Registry) and MMS (Maritime Messaging Service).
</p>
<p class="lead">The following documents define the criteria for being an MCP identity service provider:</p>
<p class="lead"> <a href="docs/MCP Gen4 Requirements for MCP identity service providers.pdf" target="_blank">Requirements for MCP identity service providers (high level description, making references to the more specific documents below)</a></p>
<p class="lead"> <a href="docs/MCP IDsec1 MCC Identity Management and Security; General Approach and Basic Requirements.pdf" target="_blank">Identity Management and Security: General Approach and Basic Requirements</a></p>
<p class="lead"> <a href="docs/MCP IDsec2 MCC Identity Management and Security; Identity Management.pdf" target="_blank">Identity Management and Security: Identity Management (the MCP usage of Maritime Resource Names, MRN)</a></p>
<p class="lead"> <a href="docs/MCP IDsec3 MCC Identity Management and Security; Public Key Infrastructure.pdf" target="_blank">Identity Management and Security: Public Key Infrastructure (PKI)</a></p>
<p class="lead"> <a href="docs/MCP IDsec4 MCC Identity Management and Security; Authentication and Authorization for Web Services.pdf" target="_blank">Identity Management and Security: Authentication and Authorisation for Web Services</a></p>
<p class="lead"> <a href="docs/MCC vetting procedures.pdf" target="_blank">Vetting procedure for MCP instance providers</a></p>
</div>
<div class="col-lg-5 col-lg-offset-2 col-sm-6">
<!--<img class="img-responsive" src="img/ipad.png" alt="">-->
<!-- org width and height: 640x360 -->
<iframe src="https://player.vimeo.com/video/246067705" width="480" height="280" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>
</div>
</div>
</div>
<!-- /.container -->
</div>
<!-- /.content-section-a -->
<a name="core"></a>
<div class="content-section-b">
<div class="container">
<div class="row">
<div class="col-lg-5 col-lg-offset-1 col-sm-push-6 col-sm-6">
<!--<hr class="section-heading-spacer">-->
<div class="clearfix"></div>
<h2 class="section-heading"><a name="core_components">The MCP</a></h2>
<p class="lead">
<p>The MCP is a decentralised platform that facilitates secure and reliable information exchange within the maritime domain and beyond. "Beyond", because the maritime world isn’t isolated, but needs to exchange information with other domains - for instance with other transport domains. The information exchanged can be of almost any nature, ranging from private confidential information between a vessel and the shore office of the shipowner, to public information provided by authorities, such as the provision of navigational warnings.</p>
<p>As a decentralised platform, there is no single entity operating this. Several organisations are MCP service providers, and collectively they form “the Maritime Connectivity Platform”.</p>
<h4>Maritime Identity Registry</h4>
<p>For secure and reliable identity information the MIR provides a unified means of authentication using identity information provided by trusted stakeholders.</p>
<h4>Maritime Service Registry</h4>
<p>The MSR can be used for registering, discovering and using all relevant e-Navigation and e-Maritime services, commercial and non-commercial, authorised and non-authorised, for free and against payment. It can be seen as a sophisticated yellow pages phone book.</p>
<h4>Maritime Messaging Service</h4>
<p>An information broker that intelligently exchanges information between different communication systems, taking into account the current geographical position and communication links available to the recipient.</p>
All the core components of the MCP are Open Source and available in <a href="https://github.com/maritimeconnectivity/" target="_blank">our GitHub repositories</a>. The source code for the MSR and MMS are still - work in progress, but the MIR is an up-to-date reference implementation aligned with the criteria for being an MCP identity service provider.
</p>
</div>
<div class="col-lg-5 col-sm-pull-6 col-sm-6">
<h2 class="section-heading"><a name="core_components">Core components of the MCP</a></h2>
<img class="img-responsive" src="img/mc-core-components.png" alt="">
</div>
</div>
</div>
<!-- /.container -->
</div>
<!-- /.content-section-b -->
<a name="governance"></a>
<div class="content-section-a">
<div class="container">
<div class="row">
<div class="col-lg-5 col-sm-6">
<!--<hr class="section-heading-spacer">-->
<div class="clearfix"></div>
<h2 class="section-heading"><a name="mcp_governance">MCP Governance</a></h2>
<p class="lead">
The MCP is governed by the MCP consortium (MCC). The MCP consortium was established on 8th of February 2019.
</p>
<p class="lead">
The MCC governs the standards relating to MCP, including the MCP source code. The MCC operates a testbed for MCP (done by a member on behalf of the consortium), but does not operate an operational instance of the MCP. Rather, the MCC authorises other organisations to run operational instances of the MCP.
</p>
</div>
<div class="col-lg-5 col-lg-offset-2 col-sm-6">
<img class="img-responsive" src="img/consortium.jpg" alt="">
<p class="lead">
From the innaguration of the MCP consortium onboard M/S Pearl Seaways during the conference - e-Navigation Underway International 2019
</p>
</div>
<div class="col-lg-10 col-sm-6">
<p class="lead">
The consortium is established by the following non-profit organisations:
<li><a href="https://www.offis.de" target="_blank">OFFIS, Germany</a></li>
<li><a href="https://www.kriso.re.kr" target="_blank">KRISO, Republic of Korea</a></li>
<li><a href="https://www.ri.se" target="_blank">RISE, Sweden</a></li>
<li><a href="https://www.ku.dk" target="_blank">University of Copenhagen, Danmark</a></li>
<li><a href="https://www.gla-rad.org" target="_blank">General Lighthouse Authorities of UK and Ireland</a></li>
</p>
<p class="lead">
And as Governmental Observers:
</p>
<p class="lead">
<li><a href="https://www.dma.dk" target="_blank">The Danish Maritime Authority</a></li>
<li><a href="https://www.sjofartsverket.se/en/" target="_blank">Swedish Maritime Administration</a></li>
<li><a href="https://www.mof.go.kr/eng/index.do" target="_blank">Ministry of Ocean and Fisheries of the Republic of Korea</a></li>
</p>
<p class="lead">
The terms of the consortium can be found in the consortium arrangement document, which can be found <a href="docs/Consortium_arrangement_1-1-1_clean.pdf" target="_blank">here</a>.
</p>
<h4>New members</h4>
<p class="lead">
All other relevant organisations (non-profit and for-profit) are invited to join the consortium.<br/>
Apply for membership by filling the <a href="docs/MCC application-1.pdf" target="_blank">application form</a> and send the filled application to the <a href="mailto:mcc@dmc.international">secretariat</a>.
</p>
<p class="lead">
Currently the following organisations have joined the consortium as regular members:
<ul>
<li><a href="https://www.dfds.com" target="_blank">DFDS (DK)</a></li>
<li><a href="https://www.sspa.se" target="_blank">SSPA (SE)</a></li>
<li><a href="https://cml.fraunhofer.de" target="_blank">Fraunhofer CML (DE)</a></li>
<li><a href="https://www.frequentis.com" target="_blank">Frequentis (AT)</a></li>
<li><a href="https://www.bergmann-marine.com" target="_blank">Bergmann Marine (DE)</a></li>
<li><a href="https://tmfg.fi/en/vts" target="_blank">VTS Finland (FI)</a></li>
<li><a href="https://www.p3ki.com" target="_blank">P3KI (DE)</a></li>
<li><a href="http://www.vissim.no" target="_blank">Vissim (NO)</a></li>
<li><a href="https://www.iridium.com" target="_blank">Iridium (US)</a></li>
<li><a href="https://www.ntua.gr/el/" target="_blank">National Technical University of Athens (GR)</a></li>
<li><a href="https://www.amsa.gov.au" target="_blank">Australian Maritime Safety Authority (AU)</a></li>
<li><a href="http://www.seatopic.fr" target="_blank">SeaTopic (FR)</a></li>
<li><a href="http://www.marine-fields.com" target="_blank">MarineFields (CY)</a></li>
<li><a href="https://navelink.org" target="_blank">Navelink (SE)</a></li>
<li><a href="https://www.sternula.com" target="_blank">Sternula (DK)</a></li>
<li><a href="http://www.sitronics-kt.ru" target="_blank">Sitronics (RU)</a></li>
<li><a href="https://www.marina.difesa.it/EN/Conosciamoci/hydroffice/Pagine/default.aspx" target="_blank">Italian Hydrographic Institute (IT)</a></li>
<li><a href="http://www.gmtc-global.kr" target="_blank">GMT (KR)</a></li>
</ul>
</p>
<p class="lead">
The consortium has an advisory board with representatives from the following international organisations/associations:
<ul>
<li><a href="https://www.iala-aism.org" target="_blank">IALA</a></li>
<li><a href="http://www.cirm.org" target="_blank">CIRM</a></li>
<li><a href="https://www.iho.int" target="_blank">IHO</a></li>
</ul>
</p>
</div>
</div>
</div>
<!-- /.container -->
</div>
<!-- /.content-section-a -->
<a name="tech"></a>
<div class="content-section-b">
<div class="container">
<div class="row">
<div class="col-lg-5 col-lg-offset-1 col-sm-push-6 col-sm-6">
<!--<hr class="section-heading-spacer">-->
<div class="clearfix"></div>
<h2 class="section-heading"><a name="technical_information">Technical Information</a></h2>
<p class="lead">
If you wish to dive into the technical information this is where you should start.<br/>
<ul>
<li>For developers there is <a href="https://docs.maritimeconnectivity.net" target="_blank">online documentation</a> describing the technical details of the MCP. Again, information relating to MIR is more up-to-date than the other components.</li>
<li>If you have a service you wish to make available in MCP, you must document it according to the MCP Service Specification. Please refer to the <a href="docs/Service_Documentation_Guidelines.pdf" target="_blank">guide</a> for how to fill out the templates for <a href="docs/Service_Specification_Template.docx" target="_blank">service specification</a>, <a href="docs/Service_Design_Description_Template.docx" target="_blank">service design</a> and <a href="docs/Service_Instance_Description_Template.docx" target="_blank">service instance</a>. As is evident in the document, the guideline is identical to the IALA guideline 1128. The MCP will at all times follow this guideline, and the MCC will seek to influence updates of this IALA guideline if deemed appropriate.</li>
<li>For updates, release information, discussions and questions concerning MCP, please use our <a href="https://mcp.discourse.group" target="_blank">Discourse forum</a>.</li>
</ul>
<!--<h4>Legacy documentation</h4>
<p>
The documentation listed here is considered legacy and outdated and will not be updated, but is provided as background information:<br/>
<ul>
<li><a href="http://dev.maritimecloud.net/">Legacy developers documentation</a> describing MMS and MSDL.</li>
<li><a href="http://faq.maritimecloud.net/">Old FAQ.</a></li>
</ul>
</p>-->
</p>
</div>
<div class="col-lg-5 col-sm-pull-6 col-sm-6">
<img class="img-responsive" src="img/code-820275-crop.jpg" alt="">
</div>
</div>
</div>
<!-- /.container -->
</div>
<!-- /.content-section-a -->
<a name="instances"></a>
<div class="content-section-a">
<div class="container">
<div class="row">
<div class="col-lg-5 col-sm-6">
<div class="clearfix"></div>
<h2 class="section-heading"><a name="mcp_instances">MCP Service providers</a></h2>
<p class="lead">
As MCP service providers become endorsed by the MCC, they will be listed here. As mentioned above, the first organisation envisioned to be such is the Navelink consortium.
</p>
<p class="lead">
In addition to this, the MCC operates (through two of its members, KRISO and Frequentis) an MCP testbed compromising three environments (test, staging, and public test environment). Any relevant organisation is invited to join this testbed by applying through the management portal of the public test environment <a href="https://management.maritimeconnectivity.net" target="_blank">here</a>.<br>
</p>
</div>
<div class="col-lg-5 col-lg-offset-2 col-sm-6">
<img class="img-responsive" src="img/MCP-Logo.png" alt="">
</div>
</div>
</div>
<!-- /.container -->
</div>
<!-- /.content-section-a -->
<a name="contact"></a>
<div class="content-section-b">
<div class="container">
<div class="row">
<div class="col-lg-5 col-sm-6">
<img class="img-responsive" src="img/control-427510_1280.png" alt="">
</div>
<div class="col-lg-5 col-lg-offset-2 col-sm-6">
<hr class="section-heading-spacer">
<div class="clearfix"></div>
<h2 class="section-heading"><a name="contact">Contact Information</a></h2>
<p class="lead">
To get more information, contact
<a href="mailto:thomas@dmc.international">Thomas Christensen</a>, the secretary general of the consortium.
</p>
</div>
</div>
</div>
<!-- /.container -->
</div>
<!-- /.content-section-a -->
<!--<a name="signup"></a>
<div class="content-section-a">
<div class="container">
<div class="row">
<div class="col-lg-5 col-sm-6">
<hr class="section-heading-spacer">
<div class="clearfix"></div>
<h2 class="section-heading">Sign up!</h2>
<p class="lead">
Whether you would like to add services to the Maritime Cloud or get access as a user, you must first sign up! To do this you must apply to get your organization added to the Maritime Cloud, so that you can login. Apply using the form found on the <a href="https://portal.maritimecloud.net/">Maritime Cloud Management Portal</a>.<br/>
To understand more about identities in the Maritime Cloud, please read the white paper on identity mentioned above.
</p>
</div>
<div class="col-lg-5 col-lg-offset-2 col-sm-6">
<img class="img-responsive" src="img/control-427510_1280.png" alt="">
</div>
</div>
</div>-->
<!-- /.container -->
<!--</div>-->
<!-- /.content-section-a -->
<!--<a name="contact"></a>
<div class="banner">
<div class="container">
<div class="row">
<div class="col-lg-6">
<h2>Connect to Start Bootstrap:</h2>
</div>
<div class="col-lg-6">
<ul class="list-inline banner-social-buttons">
<li>
<a href="https://twitter.com/SBootstrap" class="btn btn-default btn-lg"><i class="fa fa-twitter fa-fw"></i> <span class="network-name">Twitter</span></a>
</li>
<li>
<a href="https://github.com/IronSummitMedia/startbootstrap" class="btn btn-default btn-lg"><i class="fa fa-github fa-fw"></i> <span class="network-name">Github</span></a>
</li>
<li>
<a href="#" class="btn btn-default btn-lg"><i class="fa fa-linkedin fa-fw"></i> <span class="network-name">Linkedin</span></a>
</li>
</ul>
</div>
</div>
</div>-->
<!-- /.container -->
<!--</div>-->
<!-- /.banner -->
<!-- Footer -->
<footer>
<div class="container">
<div class="row">
<div class="col-lg-12">
<ul class="list-inline banner-social-buttons">
<li>
<a href="https://github.com/maritimeconnectivity" target="_blank" title="The source code for the MCP core componets">
<img src="img/Github-black.svg" alt=""/>
</a>
</li>
<li>
<a href="https://www.linkedin.com/company/maritime-connectivity-platform-consortium" target="_blank" title="News from the MCP consortium">
<img src="img/LinkedIn-color.svg" alt=""/>
</a>
</li>
<li>
<a href="https://mcp.discourse.group" target="_blank" title="Technical and general forum for the MCP">
<img src="img/discourse-icon.svg" width="48px" height="47px" alt=""/>
</a>
</li>
</ul>
</div>
</div>
</div>
</footer>
<!-- jQuery -->
<script src="js/jquery.js"></script>
<!-- Bootstrap Core JavaScript -->
<script src="js/bootstrap.min.js"></script>
<script type="text/javascript" src="js/cookie-bar/cookiebar-latest.min.js?forceLang=en&thirdparty=1&always=1"></script>
</body>
</html>