loading please wait..
close
Sign up for our newsletter
menu

Acronyms and terminology

 

Gathering acronymes and terminology, if there´s anything you need explained please add that in the Q&A form.

Updated: 2017-02-22

To find out exactly what we mean regarding the STM-services, check this taxonomy out!

Updated: 2016-11-03

REST

(REpresentational State Transfer) is an architectural style, and an approach to communications that isoften used in the development of Web services. The use of REST in VIS is preferred over the moreheavyweight SOAP (Simple Object Access Protocol) style because REST does not leverage as muchbandwidth, which makes it a better fit for use in communication between vessels and shore basedrepresentation of the same.REST, which typically runs over HTTP (Hypertext Transfer Protocol), has several architectural constraints:

􀀀Decoupling – Decouples consumers from producers which suits SeaSWIM decentralized architecturewell.

􀀀Stateless existence – Also a good prerequisite for a decentralized architecture design.

􀀀Able to leverage a cache – Probably less important in SeaSWIM since most of the interaction isbetween machines, although for services with man-machine interfaces this is of importance.

􀀀Leverages a layered system – SeaSWIM is dependant on good scaling capabilities which has RESTsupport.

􀀀Leverages a uniform interface – Again since SeaSWIM defines the available services centrally in aService registry this constraint supports implementations being decoupled from the services theyprovide.3.2


Swagger

Swagger is a simple yet powerful representation of RESTful API. With the largest ecosystem of API tooling onthe planet, thousands of developers are supporting Swagger in almost every modern programming languageand deployment environment. With a Swagger-enabled API, you get interactive documentation, client andserver SDK generation together with discoverability.A reference to provided Swagger JSON file is included in the Service Design Xml description.