Within the realm of e-Navigation, a Maritime Service in the context of e-Navigation can be implemented by one or more e-Navigation Technical Services. Drawing inspiration from service-oriented architectures, a Technical Service is defined as a cohesive set of software functions that can be repurposed for various needs, along with the policies that oversee and regulate its application.
In essence, a Technical Service is a digital service offered by an electronic device to another electronic device.
This page aims at improving the visibility and accessibility of available e-Navigation Technical Services and information provided by them. This enables service providers, consumers, and regulatory authorities to share a common understanding of a Technical Service and how to implement and use it.
Service specifications play a crucial role in amassing the outcomes of service identification and design processes. They serve to chronicle the pivotal features of a specific service at the logical tier. The service specification provides a holistic overview of a service and its building blocks at the logical level.
The service specification is intended to be technology-agnostic. The service specification shall not describe the details of a specific service implementation. For that purpose, a service design description shall also be provided, where the actual realization of the service with a dedicated technology shall be described.
Be aware that Edition 1.0 is only for testing and evaluation purposes and is not prepared for actual implementation. Edition 2.0, on the other hand, will be fully geared for implementation.
Service technical design
The service design description equips service architects and designers with a systematic, documented portrayal of the service’s technical layout. Guideline G1128 offers a template detailing the layout of sections the author should complete during the service technical design phase.
The service instance description’s core objective is to catalog, in an easily comprehensible format, all information pertinent to a particular service’s implementation and instantiation.
Note that one service implementation may be deployed several times at different access points thus forming several different service instances. In this case, several service instance description XML files need to be produced – one for each deployed instance, whereas the service instance description document can be identical, if all instances behave equivalently.
R1019 Provision of Maritime Services in the context of e-Navigation in the Domain of IALA
G1128 The specification of e-Navigation technical services
G1114 A Technical Specification for the Common Shore-based System Architecture (CSSA) track
G1157 Web Service based S-100 Data Exchange
G1155 The Development of a Description of a Maritime Service in the Context of e-Navigation
IALA complies with the General Data Protection Regulations of the EU. IALA will include a list of participants with their contact information on the website and in the report of this meeting. Any participant who wishes to remove their contact details from the participants' list should advise the Committee Secretary as soon as possible.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.