1. While the audience is gathering. During breaks etc
While the audience is gathering. During breaks etc. Simple messages can be added in bold and white letters on the dark blue sea, eg. ”Welcome!”, ”Back at 15.15”

2. HOW-TO Find interoperable services to consume
This HOW-TO describes how services can be found and presented. The HOW-TO is only a guideline and not a requirement.

3. Interoperabiliy list using Service Design IDs
Service Interoperability list
ECDIS/STM Module from X
urn:mrn:stm:service:design:sma:vis-rest-2.2
Service Interoperability list
VTS/SC ”STM Module” from Y
urn:mrn:stm:service:design:sma:vis-rest-2.2
urn:mrn:stm:service:design:viktoria:amss
urn:mrn:stm:service:design:viktoria:message_broker[_legacy]
FOS from X
Service by Z
The commonality in interoperability lists, e.g. which service designs have been implemented, will be the key stone to enable service interoperability
Service Interoperability list
urn:mrn:stm:service:design:sma:vis-rest-2.2
Service Registry
VIS Design v2.2
SVC A Design
The Service Registry is (today) shared with other projects, hence there will be an increasing number of service designs and instances that have different API than VIS and PortCDM. These service most likely requires additional implementation to consume, other may be web services that can be consumed in a standard web browser.
PortCDM AMSS Design v0.5
SVC B Design
PortCDM MB Design v0.5
SVC C Design
PortCDM MB Design v0.6
SVC xxx Design

4. Service Design
The Service Design contains the detailed API specification (swagger) how to technically consume the service.
When a new design is registered, the new design and API specification needs to be checked, implemented and tested before releasing to ship for consumption.

5. (Service) Interoperability
If any of the service information changes regarding the Physical Data (Exchange) Model, Service Interface Design (API) or Service Dynamic Behaviour it must be distinguishable from previous Service Technical Design by its ID.
Service Technical Design
ServiceDesignID=urn:mrn:<>
Physical Data Model
Service Interface Design
Service Dynamic Behaviour
ISSUE: Service Registry allows several versions on same ID, hence ID is not unique in Service Registry regarding Service Technical Designs.

6. Service Interoperability in STM Live Testbed
Voyage Information Service Technical Design
PortCDM Message Broker Service Technical Design
ServiceDesignID=urn:mrn:stm:service:design:sma:vis-rest-2.2
ServiceDesignID=urn:mrn:stm:service:design:viktoria:message_broker
RTZ v1.1 STM
TXT v1.3
S124 v0.0.7
PCMF v0.0.16
REST v2.2 (ed2)
REST vx.y
Interaction pattern v2.2
Interaction pattern vx.u
PortCDM AMSS Service Technical Design
ServiceDesignID=urn:mrn:stm:service:design:viktoria:amss
PCMF v0.0.16
PCMF v0.x.0
REST vx.y
Interaction pattern vx.u

7. Service Designs by STM Voyage Information Service Design v2.2
urn:mrn:stm:service:design:sma:vis-rest-2.2
urn:mrn:stm:service:design:viktoria:amss
Voyage Information Service Design v2.2
PortCDM AMSS
urn:mrn:stm:service:design:viktoria:message_broker[_legacy]
PortCDM MB Legacy
urn:mrn:stm:service:design:viktoria:message_broker
PortCDM MB

8. Logical Service Tree Service Specification Service Specification
Service Design
Service Design
Service Design
ServiceType
ServiceType
Service Instance
Service Instance
Service Instance
Service Instance
Service Instance
Service Instance
Service Instance
Service Instance
Service Instance
Service Instance
*VIS Instances can be grouped by serviceType, e.g. ROS,EMS etc

9. STM Live Testbed in MCP PRODUCTION 2018-03-27
Service Design ID
urn:mrn:mcl:service:design:dma:nw-nm-rest
urn:mrn:mcl:service:design:dmi:METOC_SejlRute-service
urn:mrn:mcl:service:design:dmi:IceChart_Baltic-service
urn:mrn:stm:service:design:sma:vis-rest-2.2
urn:mrn:stm:service:design:viktoria:message_broker
urn:mrn:mcl:service:design:dma:generic_web_page
urn:mrn:stm:service:design:viktoria:portcdm-host
urn:mrn:mcl:service:design:ngl:tli-rest
urn:mrn:mcl:service:design:dmi:IceChart_Greenland-service
urn:mrn:stm:service:design:viktoria:amss
urn:mrn:mcl:service:design:dmi:Iceberg_number_density-service
urn:mrn:mcl:service:design:dma:tiles-service
STM Live Testbed in MCP PRODUCTION
urn:mrn:stm:service:design:sma:vis-rest-2.2
urn:mrn:stm:service:design:viktoria:amss
urn:mrn:stm:service:design:viktoria:message_broker
urn:mrn:stm:service:design:viktoria:message_broker-v06
Voyage Information Service Design v2.2
AMSS Service Design
MB Service Design
MB Service Design v0.6.0
serviceType=”Evaluation Service”
serviceType=”Ship Voyage Information”
serviceType=”Route Catalogue”
serviceType=”Route Optimization”
serviceType=”Enhanced Monitoring”
serviceType=”Winter Navigation”
serviceType=”Route Crosscheck”
serviceType=”Navigational Warnings”
serviceType=”Port Call Synchronization”
urn:mrn:stm:service:instance:viktoria:segot-amss
urn:mrn:stm:service:instance:viktoria:segot-message-broker-legacy
urn:mrn:stm:service:instance:viktoria:segot-message-broker
PortCDM Assisted Message Submission Service - SEGOT
PortCDM Message Broker (Legacy) - SEGOT
PortCDM Message Broker - SEGOT
urn:mrn:stm:service:instance:sspa:ropt
urn:mrn:stm:service:instance:sma:bnw
urn:mrn:stm:service:instance:viktoria:portcdm:segot:vis
urn:mrn:stm:service:instance:sma:verification-service
urn:mrn:stm:service:instance:adveto:imo
urn:mrn:stm:service:instance:sma:nordic-prs
urn:mrn:stm:service:instance:sma:vis:ems:gothenburg
urn:mrn:stm:service:instance:fta:winvis
urn:mrn:stm:service:instance:viktoria:seume-amss
urn:mrn:stm:service:instance:viktoria:seume-mb-legacy
urn:mrn:stm:service:instance:viktoria:seume-message-broker
Baltic Bright
Nordic Pilot Route Service
SSPA Route Optimization
PortCDM VIS Connector Service - SEGOT
Verification Service
Gothenburg SC
Winter Navigation Service
Baltic Navigational Warning Service
PortCDM Assisted Message Submission Service - SEUME
PortCDM Message Broker (Legacy) - SEUME
PortCDM Message Broker - SEUME
urn:mrn:stm:service:instance:adveto:imo
urn:mrn:stm:service:instance:viktoria:portcdm:seume:vis
urn:mrn:stm:service:instance:sma:stmvalidation
urn:mrn:stm:service:instance:rdnccis:rdnccis-ems
urn:mrn:stm:service:instance:viktoria:fivaa-message-broker
STM Validation Centre
Birka Stockholm
urn:mrn:stm:service:instance:viktoria:fivaa-amss
Royal Danish Navy Shore Center
PortCDM VIS Connector Service - SEUME
PortCDM AMSS - FIVAA
PortCDM Message Broker - FIVAA
urn:mrn:stm:service:instance:portofrotterdam:arrivaltimesync
urn:mrn:stm:service:instance:adveto:imo
Gabriella
Port of Rotterdam Arrival Time Synchronization Service
urn:mrn:stm:service:instance:adveto:imo
Amorella

10. Search for service instances
C# SSC
findService
Service Registry
/api/_search/serviceInstance
/api/_searchGeometryWKT/serviceInstance
/api/serviceInstance
/api/_searchUnlocode/serviceInstance
JAVA SSC
findService
/api/_searchGeometryGeoJSON/serviceInstance
Three different APIs
/api/_searchKeywords/serviceInstance
/api/_searchLocation/serviceInstance

11. Search through C# VIS/SSC
The base filter should contain
Status=released (suppress provision, depracted and deleted instances)
List of Service Designs implemented in the application
Find services based on VIS Technical Design
POST findServices {
"filter": {
    "serviceStatus": "released",
    "serviceDesignId": "urn:mrn:stm:service:design:sma:vis-rest-2.2" },
"page": 0,
"pageSize": 1000 }
Find services based on VIS, PortCDM AMSS and MB {
"filter": {
    "serviceStatus": "released",
"serviceDesignId": "+urn:mrn:stm:service:design:sma:vis-rest-2.2 +urn:mrn:stm:service:design:viktoria:amss +urn:mrn:stm:service:design:viktoria:message_broker" },
"page": 0,
"pageSize": 1000 }

12. Search through C# VIS/SSC
Find all VIS services for ships
Find all VIS services except ships
POST findServices {
"filter": {
"coverageArea": {
"coverageType": "WKT",
"value": null },
"UnLoCode": null,
"ServiceProviderIds": null,
"serviceDesignId": "urn:mrn:stm:service:design:sma:vis-rest-2.2", "serviceInstanceId": null,
"mmsi": null,
"imo": null,
"serviceType": "\"Ship Voyage Information\"",
"serviceStatus": “released”,
"keyWords": null,
"freeText": null
"page": 0,
"pageSize": 1000 }
POST findServices {
"filter": {
"coverageArea": {
"coverageType": "WKT",
"value": null },
"UnLoCode": null,
"ServiceProviderIds": null,
"serviceDesignId": "urn:mrn:stm:service:design:sma:vis-rest-2.2",
"serviceInstanceId": null,
"mmsi": null,
"imo": null,
"serviceType": "(-\"Ship Voyage Information\")",
"serviceStatus": “released",
"keyWords": null,
"freeText": null
"page": 0,
"pageSize": 1000 }

13. Search through JAVA SSC
Find all VIS services for ships
Find all VIS services except ships
POST findServices {
"filter": {
"coverageArea": {
"coverageType": "WKT",
"value": null },
"UnLoCode": null,
"ServiceProviderIds": null,
"serviceDesignId": "urn:mrn:stm:service:design:sma:vis-rest-2.2", "serviceInstanceId": null,
"mmsi": null,
"imo": null,
"serviceType": "\"Ship Voyage Information\"",
"serviceStatus": “released”,
"keyWords": null,
"freeText": null
"page": 0,
"pageSize": 1000 }

14. Search directly from Service Registry
Find released services based on VIS Technical Design
GET " query=designId:urn\:mrn\:stm\:service\:design\:sma\:vis-rest-2.2 AND status:released&page=0&size=5000
curl.exe --output "search.txt" -k --header Accept:application/json --header Content-Type:application/json --http1.1 -X GET " query=designId%3Aurn%5C%3Amrn%5C%3Astm%5C%3Aservice%5C%3Adesign%5C%3Asma%5C%3Avis-rest-2.2%20AND%20status%3Areleased&&page=0&size=5000
See online documentation of Service Registry for developers
See also the Service Registry Excel Tool

15. At the end – you could add text in black like ”Thank You !”