ISO/PAS 22853-2005
船舶和海上技术.计算机应用.海上安全标记语言(MSML)的规范

Ships and marine technology - Computer applications - Specification of Maritime Safety Markup Language (MSML)

标准号

ISO/PAS 22853-2005

发布日期

2005年10月

实施日期

废止日期

无

中国标准分类号

U07

国际标准分类号

35.240.60;47.020.99

发布单位

IX-ISO

适用范围

This Publicly Available Specification specifies the XML application MSML (Maritime Safety Markup Language). MSML is a language for structuring information and the goal is to create an open standard that can be used generally in the maritime sector. The basis of MSML is the data model which defines what kind of maritime data, related to vessel and shore base, it is possible to store. The data model represents the current state and only limited historic information is kept in the data model. This Publicly Available Specification defines perspectives associated with the data model of MSML. The term indicates that the MSML data model can be seen from different views. Perspectives contain information that is orthogonal to the data model. A certain amount of shore base information is included in the data model of MSML. The main reason to include this information is to support vessel safety related aspects and vessel repair and maintenance. 1.2 Limitations An MSML instance will contain extensive history information only if included in the definition of a perspective. For example, repair and maintenance contains an extensive history of what has been changed and when, but there is no extensive history information for e.g. bunkering. The reason for including history is that actions made in the past can affect future events and decisions. However, some minor historic information is included in the data model of MSML (i.e. not within perspectives), e.g. the history of vessel name changes. If other types of extensive history information are needed, a new version of the MSML instance has to be stored for each significant change and this must be handled outside the scope of MSML (probably using a native XML database). The data model of MSML should not primarily be seen as a support for normal work onboard. Instead it is an add-on support for transfers of safety related information to/from the vessel from/to external units and within the vessel. For example, current propeller revolutions per minute cannot be extracted from the computerized MSML system, instead the value is read directly from the ordinary equipment. In the same way the shore base part of the MSML data model is seen as a support to the safety related vessel information and not from normal work ashore. Generally, normal dynamic information during a voyage between two shore bases is not included within MSML. On the other hand, alarms and malfunctioning units are generally safety related and of interest internally and externally and thus included in the data model of MSML. If alarms are set automatically or not is a question outside the scope of MSML. 1.3 Exclusions The following aspects are not included in the scope of MSML: • aspects concerning costs and fees; • geographic information; • logs, e.g. log of communication; • specific cargo information, e.g. tracing, Smart and Secure Tradelanes; • presentation of information; • users and their authorities; • actual use of data and instances, e.g. definition of messages; • bindings to protocols. 1.4 Summary To sum up the main characteristics of MSML, it • contains an XML-based data model for information exchange and processing in safety-critical maritime applications; • does not describe how data is used; • supports information security and extensibility; • is a framework and future open standard for the maritime safety sector.